Differences between revisions 9 and 10
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
 ["findsession"] To find your data, run the findsession command, passing it the "patient name", which is the name that you registered the subject under when scanning:

["findsession patientname"]

This will give you a list of all matching data sets, including paths to where each one can be found. Eg,

/space/chartres/6/siemens/TRIO-20501-20020416-124756-468000

== Unpack the data ==

Unpacking is the processes through which you convert the data from DICOM format (which is not very useful) to a format that can be used by an analysis programe (eg, bhdr, nifti, analyze, mgh, mgz). The program that does this is unpacksdcmdir (this is only used to unpack Siemens DICOM files). mri_convert can also be used to convert individual runs.

Unpack the data from bourget:

Find your subject...

To find your data, run the findsession command, passing it the "patient name", which is the name that you registered the subject under when scanning:

["findsession patientname"]

This will give you a list of all matching data sets, including paths to where each one can be found. Eg,

/space/chartres/6/siemens/TRIO-20501-20020416-124756-468000

Unpack the data

Unpacking is the processes through which you convert the data from DICOM format (which is not very useful) to a format that can be used by an analysis programe (eg, bhdr, nifti, analyze, mgh, mgz). The program that does this is unpacksdcmdir (this is only used to unpack Siemens DICOM files). mri_convert can also be used to convert individual runs.

Ask it to start, and you will find that instead it will tell you the path for unpacking.

  • ["unpacksdcmdir"] -src <source> -targ <target> -scanonly file

NOTE: you must be in the targ dir for that command to work. This outputs the type of scans used. Now use a file at

  • $FREESURFER_HOME/numaris4-protocols.unpackcfg

to correctly make a config file. If you cannot find the file, check here

The format is: num folder format fileprefix Here is an example config file.

1 scout bshort f

3 bold bshort f

4 bold bshort f

5 bold bshort f

6 bold bshort f

7 bold bshort f

8 bold bshort f

The number is acquisition number. The folder is where that acquisition is stored (bold directory, scout directory etc) The format is the form of the data files. The fileprefix is how the filenames start.

Next run it again with your config file.

  • ["unpacksdcmdir"] -src <source> -targ <target> -cfg<configfile> -fsfast

If it is .ima format data...

Note: I have come across old data which was *.ima format. This can be unpacked using

  • ["unpackimadir2"]

which works just like unpacksdcmdir.

Check for TR bug

*** There is always a problem after unpacking that the TR is not set correctly. Please fix it.

  • pico $SUBJECTS_DIR/$SUBJECT/bold/seq.info

Copy the 3danat

Goto the 3danat/ dir

  • cd $SUBJECTS_DIR/$SUBJECT/

Copy contents to mri/orig. For example...

  • cp 3danat/* mri/orig

FsFastUnpackData (last edited 2019-07-30 13:58:54 by PaulRaines)