... | ... | @@ -27,6 +27,10 @@ Begin by clicking the **Load context configuration** button on the GUI. You shou |
|
|
# 2. Batch Configuration
|
|
|
The next step is to load the configuration files that specify how the scripts will interact with the cluster and its scheduler. First, click **Load batch config**. A small GUI should be presented. Click **Batch configuration file** to open a file chooser. Either navigate to your own personalized scripts, or navigate to `/bids/derivatives/lossless/code/config/remote-sbatch`. Select all files beginning with the **c** prefix and press **open**. The lower text area of the small GUI should now have entries in it corresponding to the selected filed. Press **ok** to load these configurations into Matlab.
|
|
|
|
|
|
The batch configuration area should now be filled with texts.
|
|
|
|
|
|
**NOTE:** Users will **need** to modify the 'submit_options' field. Instead of '--acount=def-desjardins', it should be updated to be '--account=USERGROUP'.
|
|
|
|
|
|
**NOTE:** These configurations assume your testing session is of average length. Increasing various parameters can cause a **major** increase in queue time. See the batch configuration [page](tuning-pipeline-configs) on how to customize memory and time parameters safely.
|
|
|
|
|
|
# Selecting the correct history files
|
... | ... | |