... | @@ -25,9 +25,9 @@ As specified in the context [tutorial](configuring-context-config) page, this co |
... | @@ -25,9 +25,9 @@ As specified in the context [tutorial](configuring-context-config) page, this co |
|
Begin by clicking the **Load context configuration** button on the GUI. You should be presented with a file chooser. Either navigate to your personally saved configuration or navigate to `/bids/derivatives/lossless/code/config` and select `contextconfig.cfg`. This will load some default options assuming the graham cluster's specifications. From this point you will need to modify the options as they only contain sample paths. For an in depth explanation of what needs to be modified, see the [tutorial](configuring-context-config).
|
|
Begin by clicking the **Load context configuration** button on the GUI. You should be presented with a file chooser. Either navigate to your personally saved configuration or navigate to `/bids/derivatives/lossless/code/config` and select `contextconfig.cfg`. This will load some default options assuming the graham cluster's specifications. From this point you will need to modify the options as they only contain sample paths. For an in depth explanation of what needs to be modified, see the [tutorial](configuring-context-config).
|
|
|
|
|
|
# 2. Batch Configuration
|
|
# 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.
|
|
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 prestened. 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`.
|
|
|
|
|
|
**NOTE:** These configurations assume your testing session is of average length. See the batch configuration [page](tuning-pipeline-configs) on how to customize memory and time parameters.
|
|
**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
|
|
# Selecting the correct history files
|
|
Once you have your context configuration loaded clicking "History file" will open you directly to your scripts directory.
|
|
Once you have your context configuration loaded clicking "History file" will open you directly to your scripts directory.
|
... | | ... | |