You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/usage.rst
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -156,15 +156,15 @@ Known issues with HPC
156
156
templateflow.api.get('MNI152NLin2009cAsym') # change template if needed
157
157
158
158
159
-
then provide the templates to the container by mounting the ``TEMPLATEFLOW_HOME`` folder and setting the ``TEMPLATEFLOW_HOME`` environment variable:
159
+
then provide the templates to the container by mounting the ``templateflow`` home directory and setting the ``TEMPLATEFLOW_HOME`` environment variable:
160
160
161
161
.. code-block:: bash
162
162
163
-
apptainer run -v /path/to/templates:/path/to/templateflow --env TEMPLATEFLOW_HOME=/path/to/templateflow ...
163
+
apptainer run -v /path/to/templateflow:/path/to/templates --env TEMPLATEFLOW_HOME=/path/to/templates ...
164
164
165
165
#. Socket error:
166
166
167
-
When running multiple instances of MRIQC on HPC, you may encounter the following error:
167
+
When running multiple instances of MRIQC on a HPC, you may encounter the following error:
168
168
169
169
.. code-block:: python
170
170
@@ -177,7 +177,7 @@ Known issues with HPC
177
177
apptainer run --net --network none ...
178
178
179
179
This solution might prevent the container from accessing the internet and downloading templates.
180
-
In this case, you can download the templates manually and mount provide access to the templates as explained in the previous section.
180
+
In this case, you can download the templates manually and provide access to the downloaded files as explained in the previous section.
0 commit comments