@@ -69,18 +69,18 @@ Singularity Container
69
69
For security reasons, many HPCs (e.g., TACC) do not allow Docker containers, but do
70
70
allow `Singularity <https://github.com/singularityware/singularity >`_ containers.
71
71
72
- Preparing a Singularity image (Singualrity version >= 2.5)
72
+ Preparing a Singularity image (Singularity version >= 2.5)
73
73
----------------------------------------------------------
74
74
If the version of Singularity on your HPC is modern enough you can create Singularity
75
75
image directly on the HCP.
76
- This is as simple as
76
+ This is as simple as: ::
77
77
78
78
$ singularity build /my_images/fmriprep-<version>.simg docker://poldracklab/mriqc:<version>
79
79
80
80
Where ``<version> `` should be replaced with the desired version of fMRIPrep that you want to download.
81
81
82
82
83
- Preparing a Singularity image (Singualrity version < 2.5)
83
+ Preparing a Singularity image (Singularity version < 2.5)
84
84
---------------------------------------------------------
85
85
In this case, start with a machine (e.g., your personal computer) with Docker installed.
86
86
Use `docker2singularity <https://github.com/singularityware/docker2singularity >`_ to
@@ -134,15 +134,17 @@ If the data to be preprocessed is also on the HPC, you are ready to run fmriprep
134
134
participant \
135
135
--participant-label 387 --nthreads 16 -w $WORK/lonestar/work \
136
136
--omp-nthreads 16
137
-
138
- or, unset the ``PYTHONPATH`` variable before running:
139
-
137
+
138
+
139
+ or, unset the ``PYTHONPATH`` variable before running: ::
140
+
140
141
$ unset PYTHONPATH; singularity run ~/poldracklab_fmriprep_latest-2016-12-04-5b74ad9a4c4d.img \
141
142
/work/04168/asdf/lonestar/ $WORK/lonestar/output \
142
143
participant \
143
144
--participant-label 387 --nthreads 16 -w $WORK/lonestar/work \
144
145
--omp-nthreads 16
145
-
146
+
147
+
146
148
.. note ::
147
149
148
150
Depending on how Singularity is configured on your cluster it might or might not
0 commit comments