February 2007 Commit Log

Number of Commits:

11

Number of Active Developers:

2

farshadm 2007-02-27 04:59 #11 Rev.: 28

reverting back to version 1.1

1 lines of code changed in 1 file:

• mrLoadRet/ROI: restrictROI.m (+1 -2)

farshadm 2007-02-27 04:53 #10 Rev.: 27

*** empty log message ***

7 lines of code changed in 2 files:

• mrLoadRet/Analysis/EventRelated: eventRelatedMultiple.m (+5 -1)
• mrLoadRet/ROI: restrictROI.m (+2 -1)

farshadm 2007-02-24 00:35 #9 Rev.: 26

*** empty log message ***

3 lines of code changed in 1 file:

• mrLoadRet/Analysis/EventRelated: eventRelatedMultiple.m (+3 -1)

eli 2007-02-15 03:00 #8 Rev.: 25

copied the version of cbiNifti from /share/wotan/heegerlab/mrUtilities-3.1/File/Nifti/, which is the most recent version

26 lines of code changed in 7 files:

• mrUtilities/File/Nifti: cbiCreateNiftiHeader.m (+16 -10), cbiHomogeneousToQuaternion.m (+1 -133), cbiReadNifti.m (+4 -1), cbiReadNiftiHeader.m (+1 -2), cbiSetNiftiQform.m (+1 -1), cbiSetNiftiSform.m (+2 -3), cbiWriteNiftiHeader.m (+1 -1)

eli 2007-02-15 02:49 #7 Rev.: 24

inc some bugfixes by jonas

81 lines of code changed in 1 file:

• mrUtilities/File/Nifti: cbiWriteNifti.m (+81 -28)

eli 2007-02-15 02:39 #6 Rev.: 23

*** empty log message ***

38 lines of code changed in 1 file:

• mrUtilities/File/Nifti: cbiSwapNiftiDimensions.m (+38 -9)

farshadm 2007-02-06 07:18 #5 Rev.: 22

eventRelatedMultiple.m: performs deconvolution analysis on multiple files without requiring to concatenate them.

371 lines of code changed in 1 file:

• mrLoadRet/Analysis/EventRelated: eventRelatedMultiple.m (new 371)

farshadm 2007-02-06 04:51 #4 Rev.: 21

disppercent.m: references to mydisp were revised to mrDisp.

6 lines of code changed in 1 file:

• mrUtilities/MatlabUtilities: disppercent.m (+6 -6)

farshadm 2007-02-02 06:21 #3 Rev.: 20

eventRelated.m: renamed mydisp to mrDisp.

3 lines of code changed in 1 file:

• mrLoadRet/Analysis/EventRelated: eventRelated.m (+3 -3)

farshadm 2007-02-02 02:49 #2 Rev.: 19

eventRelated.m: handles two formats for event timings. 1: the original 'traces' format (myscreen.traces and myscreen.stimtrace contain the temporal information) 2: a simplified 'eventtimes' format (mylog.stimtimes_s is a cell array of the times of each event catgory wrt the onset of the scan)

viewGet.m: when loading the stimulus files, "viewGet.m" determines which of the two formats (traces vs. eventtimes) is applicable. If the stimulus file contains a non-empty myscreen structure then viewGet returns it and assumes that the file is using the 'traces' format. Otherwise, viewGet return the content of mylog variable and assumes the 'eventtimes' format. The format can be determined by checking the filetype field.

9 lines of code changed in 1 file:

• mrLoadRet/View: viewGet.m (+9 -1)

farshadm 2007-02-02 02:44 #1 Rev.: 18

eventRelated.m: can handle two formats for event timing. 1: the original 'traces' format (myscreen.traces and myscreen.stimtrace contain the temporal information) 2: a simplified 'eventtimes' format (mylog.stimtimes_s is a cell array of the times of each event catgory wrt the onset of the scan)

viewGet.m: when loading the stimulus files determines which of the two formats is applicable. If the stimulus file contains a myscreen variable then it assumes that the file is using 'traces' format. Otherwise it looks for a mylog variable and uses the 'eventtimes' format. The format can be determined by checking the filetype field.

55 lines of code changed in 1 file:

• mrLoadRet/Analysis/EventRelated: eventRelated.m (+55 -26)

January 2007 »