Difference between revisions of "AFNI"

From UFRC
Jump to navigation Jump to search
Line 5: Line 5:
 
<!--CONFIGURATION: OPTIONAL (|1}} means it's ON)-->
 
<!--CONFIGURATION: OPTIONAL (|1}} means it's ON)-->
 
|{{#vardefine:conf|}}          <!--CONFIGURATION-->
 
|{{#vardefine:conf|}}          <!--CONFIGURATION-->
|{{#vardefine:exe|}}            <!--ADDITIONAL INFO-->
+
|{{#vardefine:exe|1}}            <!--ADDITIONAL INFO-->
 
|{{#vardefine:pbs|}}            <!--PBS SCRIPTS-->
 
|{{#vardefine:pbs|}}            <!--PBS SCRIPTS-->
 
|{{#vardefine:policy|}}        <!--POLICY-->
 
|{{#vardefine:policy|}}        <!--POLICY-->
Line 40: Line 40:
 
<!--Run-->
 
<!--Run-->
 
{{#if: {{#var: exe}}|==Additional Information==
 
{{#if: {{#var: exe}}|==Additional Information==
WRITE_ADDITIONAL_INSTRUCTIONS_ON_RUNNING_THE_SOFTWARE_IF_NECESSARY
+
 
 +
Starting with version 2016_2_09 - the first AFNI version on HiPerGator2 - use the 'launch_afni' command to access afni executables. In addition, if you use absolute paths (starting with /ufrc/) in your arguments you have to convert them to relative paths. We have a relative_path script in the ufrc module for it. For example, the following commands in a job script will run the 3dcalc analysis:
 +
 
 +
module load ufrc afni
 +
launch_afni 3dcalc -a $(relative_path /ufrc/group/user/Map_repository/S01_19_DA/fnirted_FA.nii.gz) -expr 'step(a)' -prefix $(relative_path /ufrc/group/user/test_afni.nii.gz)
 +
 
 +
If you already use relative paths then the use of 'relative_path' is not required.
 +
 
 
|}}
 
|}}
 
<!--PBS scripts-->
 
<!--PBS scripts-->

Revision as of 21:11, 17 August 2016

Description

afni website  

AFNI is a set of C programs for processing, analyzing, and displaying functional MRI (FMRI) data - a technique for mapping human brain activity. It should be used for research purposes only.

Required Modules

Serial

  • afni

System Variables

  • HPC_{{#uppercase:afni}}_DIR

Additional Information

Starting with version 2016_2_09 - the first AFNI version on HiPerGator2 - use the 'launch_afni' command to access afni executables. In addition, if you use absolute paths (starting with /ufrc/) in your arguments you have to convert them to relative paths. We have a relative_path script in the ufrc module for it. For example, the following commands in a job script will run the 3dcalc analysis:

module load ufrc afni
launch_afni 3dcalc -a $(relative_path /ufrc/group/user/Map_repository/S01_19_DA/fnirted_FA.nii.gz) -expr 'step(a)' -prefix $(relative_path /ufrc/group/user/test_afni.nii.gz)

If you already use relative paths then the use of 'relative_path' is not required.



Citation

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

RW Cox. AFNI: Software for analysis and visualization of functional magnetic resonance neuroimages. Computers and Biomedical Research, 29:162-173, 1996.

RW Cox and JS Hyde. Software tools for analysis and visualization of FMRI Data. NMR in Biomedicine, 10:171-178, 1997.

S Gold, B Christian, S Arndt, G Zeien, T Cizadlo, DL Johnson, M Flaum, and NC Andreasen. Functional MRI statistical software packages: a comparative analysis. Human Brain Mapping, 6:73-84, 1998.