| ... | ... | @@ -10,39 +10,25 @@ For our purposes we will only discuss the changes from the provided configuratio |
|
|
|
|
|
|
|
Begin by navigating to File > Batch > Context configuration.
|
|
|
|
|
|
|
|
Next click the "Load context config" button. Navigate the file chooser to `bids/code/lossless/config` and select the `contextconfig.cfg` file.
|
|
|
|
Next click the "Load context config" button. Navigate the file chooser to `/bids/code/lossless/config` and select the `contextconfig.cfg` file.
|
|
|
|
|
|
|
|
You should now be presented with the following screen:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Click "Load context config" in the top left of your window. Navigate to analysis/support/config and select `contextconfig.cfg`. Pressing "Refresh" in the Context configuration will also load your system commands if you desire to use those.
|
|
|
|
Pressing "Refresh" in the Context configuration will also load your system commands if you desired.
|
|
|
|
|
|
|
|
We can provide only limited support for these options as they are environment specific and require knowledge from your system administrators.
|
|
|
|
The following list details the minimum options that should be changed to your respective cluster's information and updated inside of the context configuration menu.
|
|
|
|
|
|
|
|
The options we will be changing are as follows:
|
|
|
|
* **remote_user_name** - Username on the cluster.
|
|
|
|
|
|
|
|
**remote_user_name**
|
|
|
|
* **remote_exec_host** - ssh host name, this should be a fully qualified host name or a host name that can be resolved by the system as your cluster host name.
|
|
|
|
|
|
|
|
This should be your username on the remote cluster
|
|
|
|
* **remote_project_archive** - Directory on the same remote server safe for archiving potentially large data files.
|
|
|
|
|
|
|
|
**remote_exec_host**
|
|
|
|
* **remote_project_work** - Directory the containing data files and all other project files. Should mirror the location chosen for remote installation.
|
|
|
|
|
|
|
|
ssh host name, this should be a fully qualified host name or a host name that can be resolved by the system as your cluster host name.
|
|
|
|
|
|
|
|
Tip: `.ssh/config` applies here so aliases built into the ssh config file can be used instead of full host names this applies to all of the remote paths
|
|
|
|
|
|
|
|
**remote_project_archive**
|
|
|
|
|
|
|
|
This is the directory on a remote server we use for archiving data files, this not necessary for the pipeline to function properly but is used with some of the system commands.
|
|
|
|
|
|
|
|
**remote_project_work**
|
|
|
|
|
|
|
|
This is the directory the contains your data files and all other project files that were remotely copied to the server in the install steps.
|
|
|
|
|
|
|
|
**remote_dependency**
|
|
|
|
|
|
|
|
This field should be equal to the value of remote_project_work followed by `/analysis/support/dependencies`
|
|
|
|
* **remote_dependency** - This field should be equal to the value of remote_project_work followed by `/bids/code/lossless/dependencies`.
|
|
|
|
|
|
|
|
Press Save as and save the new context configuration as "mycontextconfig.cfg" in your analysis/support/config directory
|
|
|
|
|
| ... | ... | |
