Difference between revisions of "FSL"

From UFRC
Jump to navigation Jump to search
Line 88: Line 88:
 
* if you run bedpostx and the output directory already exists, it will look to see if any slices need to be processed. It will then run jobs for all the unprocessed slices and post process all the slice data.
 
* if you run bedpostx and the output directory already exists, it will look to see if any slices need to be processed. It will then run jobs for all the unprocessed slices and post process all the slice data.
 
* there are 3 stages in the execution of bedpostx:
 
* there are 3 stages in the execution of bedpostx:
   1. pre-processing  - use qstat -u youruserid to view job status
+
   1. pre-processing  - to view job status use: qstat -u youruserid
 
   2. slice processing - a job is posted for each individual slice as part of a job array,  
 
   2. slice processing - a job is posted for each individual slice as part of a job array,  
                         use qstat -t -u youruserid to view individual job status
+
                         to view individual job status use: qstat -t -u youruserid
   3. post-processing  - use qstat -u youruserid to view job status
+
   3. post-processing  - to view job status use: qstat -u youruserid
  
 
Notes:
 
Notes:

Revision as of 03:04, 25 December 2013

Description

fsl website  

FSL is a comprehensive library of analysis tools for FMRI, MRI and DTI brain imaging data.

Required Modules

Serial

  • fsl

System Variables

  • HPC_{{#uppercase:fsl}}_DIR

Additional Information

Running bedpostx

The bedpostx script has been modified to work with Moab/Torque for job submissions. In addition to the bedpostx options, the following Moab/Torque command line options have been added:

(the wiki table template appears to not work properly - options will be shown once fixed)


Sequence for running bedpostx:

  • log into DEV1 or DEV2
  • cd into the directory that contains your bedpostx data directory
  • run screen and turn the log on (ctl-a shift-h)
  • run module load fsl
  • run bedpostx, a typical command should look like: bedpostx datadir -M emailaddr
  • you may detach the screen at any time and then use screen -r to reattach at a later time
  • once the script has finished running you may turn the log off
  • use the log file to view the script output and also check your emails for any error notifications

Note: If you can make sure that the terminal is not disconnected at any time while running the bedpostx script then you don't need to use screen.


What you should know about running bedpostx:

  • a directory will be created for the output data. It will be named using the original data folder name followed by .bedpostX
  • only one bedpostx script at a time can be run for a given data directory otherwise the output data will be unreliable.
  • if you run bedpostx and the output directory already exists, it will look to see if any slices need to be processed. It will then run jobs for all the unprocessed slices and post process all the slice data.
  • there are 3 stages in the execution of bedpostx:
  1. pre-processing   - to view job status use: qstat -u youruserid
  2. slice processing - a job is posted for each individual slice as part of a job array, 
                        to view individual job status use: qstat -t -u youruserid
  3. post-processing  - to view job status use: qstat -u youruserid

Notes:

  • Because of issues with job arrays and qstat, the job array is not considered completed until all the individual jobs stop showing up in qstat - about 5 minutes after completion.
  • You can not allow the terminal from which you run bedpostx to get disconnected while the script is running. If the terminal is disconnected, it will cause the job array completion detection to fail and the post processing will run before the slice processing is finished. This is why using screen is recommended.
  • Be aware that the job array numbers do not match the sub-directory numbers in the diff_slices directory. The jobs are always numbered 1-n and the directory numbers 0-(n-1) the first time you run bedpostx. If you were to rerun bedpostx again with some slices already processed in a prior run, then the only way to match job numbers with sub-directory numbers is via the job control file commands.txt.
  • using qstat -u youruserid for a job array is not reliable. It will sometimes consider the job array done and gone, i.e. it will not display an entry for it, even though one or more of the individual jobs are still running.



Citation

If you publish research that uses fsl you have to cite it as follows:

  1. M. Jenkinson, C.F. Beckmann, T.E. Behrens, M.W. Woolrich, S.M. Smith. FSL. NeuroImage, 62:782-90, 2012
  2. M.W. Woolrich, S. Jbabdi, B. Patenaude, M. Chappell, S. Makni, T. Behrens, C. Beckmann, M. Jenkinson, S.M. Smith. Bayesian analysis of neuroimaging data in FSL. NeuroImage, 45:S173-86, 2009
  3. S.M. Smith, M. Jenkinson, M.W. Woolrich, C.F. Beckmann, T.E.J. Behrens, H. Johansen-Berg, P.R. Bannister, M. De Luca, I. Drobnjak, D.E. Flitney, R. Niazy, J. Saunders, J. Vickers, Y. Zhang, N. De Stefano, J.M. Brady, and P.M. Matthews. Advances in functional and structural MR image analysis and implementation as FSL. NeuroImage, 23(S1):208-19, 2004