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: doc/run_fmriprep.md
+4-5Lines changed: 4 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,8 @@ To contribute see [here](https://cpp-lln-lab.github.io/CPP_HPC/contributing/)
15
15
16
16
## Prepare to run fmriprep on the cluster
17
17
18
-
- have your data on the cluster
18
+
- have your data on the cluster and unlock them if they are managed by datalad
19
+
- get your `freesurfer` license (user specific) for free [here](https://surfer.nmr.mgh.harvard.edu/registration.html) and move it to the cluster at `~/tools`
19
20
- install datalad on your user (see [here](https://github.com/cpp-lln-lab/CPP_HPC/install_datalad))
20
21
- get the fmriprep singularity image as follow:
21
22
@@ -38,14 +39,12 @@ cd path/to/containers
38
39
datald update --merge
39
40
``````
40
41
41
-
Depending on the cluster “unlock” is needed or not. No need for`lemaitre3`. !!! TO CHECK ON LEMAITRE4
42
+
Depending on the cluster “unlock” is needed or not. No need for`lemaitre4`.
- get your `freesurfer` license (user specific) for free [here](https://surfer.nmr.mgh.harvard.edu/registration.html) and move it to the cluster
48
-
49
48
## Submit a fmriprep job via a `slurm` script
50
49
51
50
- pros:
@@ -60,7 +59,7 @@ Content of the `cpp_fmriprep.slurm` file (download and edit from [here](cpp_fmri
60
59
!!! Warning
61
60
62
61
1. Read the fmriprep documentation to know what you are doing and how the arguments of the run call effects the results
63
-
2. All the paths and email are set afte Marco's users for demosntration.
62
+
2. All the paths and email are set afte Marco's users for demosntration. Change them for your user.
64
63
3. Edit the scripts with the info you need to make it run for your user from top to buttom of the script, do not over look the first "commented" chunk cause it is not a real commented section (check the email and job report path, data paths and the `username` etc.).
0 commit comments