Differences between revisions 7 and 8
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
 ["unpacksdcmdir"] -src <source> -targ <target> -scanonly  ["unpacksdcmdir"] -src <source> -targ <target> -scanonly file

Unpack the data from bourget:

Find your subject...

  • ["findsession"]

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

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)