|  |  | **Table of contents** | 
|  |  |  | 
|  |  | [[_TOC_]] | 
|  |  |  | 
|  |  | # Context Configuration | 
|  |  |  | 
|  |  | Using our pipeline requires the use of [Batch Context](https://git.sharcnet.ca/bucanl_eeglab_extensions/batch_context) which combines the use of user configuration and job configuration. You will see there are 4 options under File > Batch in your eeglab window that are pertinent to Batch Context. You can learn more about the [different interfaces of Batch Context here.](https://git.sharcnet.ca/bucanl_eeglab_extensions/batch_context/wikis/functions) | 
|  |  |  | 
|  |  | This page describes the settings related to the user configuration in Context configuration and use with the pipeline. Explanation of Context configuration itself is available [on the Batch Context wiki](https://git.sharcnet.ca/bucanl_eeglab_extensions/batch_context/wikis/configuration-files#context-configuration-files-cfg) | 
|  |  |  | 
|  |  | Navigate to File > Context configuration | 
|  |  |  | 
|  |  | # Required changes | 
|  |  |  | 
|  |  | For our purposes we will only discuss the changes from the provided configuration file required. | 
|  |  |  | 
|  |  |  | 
|  |  |  | 
|  |  | 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. | 
|  |  |  | 
|  |  | We can provide only limited support for these options as they are environment specific and require knowledge from your system administrators. | 
|  |  |  | 
|  |  | The options we will be changing are as follows: | 
|  |  |  | 
|  |  | **remote_user_name** | 
|  |  |  | 
|  |  | This should be your username on the remote cluster | 
|  |  |  | 
|  |  | **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. | 
|  |  |  | 
|  |  | 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` | 
|  |  |  | 
|  |  | Press Save as and save the new context configuration as "mycontextconfig.cfg" in your analysis/support/config directory | 
|  |  |  | 
|  |  | *** | 
|  |  | [ :arrow_right: **Next Step**](running-your-first-job) | 
|  |  | [ :house: **Return to Main Page**](https://git.sharcnet.ca/bucanl_pipelines/eeg_pipe_asr_amica/wikis/home) | 
|  |  | \ No newline at end of file |