Skip to content

Changes

Page history
No commit message authored by Andrew Lofts's avatar Andrew Lofts 
No commit message
Hide whitespace changes
Inline Side-by-side
configuration-files.md
View page @ 6d5f9013
......@@ -4,13 +4,14 @@
The batch_context plugin relies on two types of configuration files in order to correctly handle the job batch.
1. A **Context Config File**
This is a single config text file that specifies local and remote directories and system communications. It is unique to the *user* and the *project*. A user needs to create a new one of these for every project. :so: Name the file to includes the project, user and execution type.
(:b: *contextconfig_local.txt* and *contextconfig_remote.txt* )
(:b: *contextconfig_local.cfg* and *contextconfig_remote.cfg* )
2. **Batch Config Files**
These are config text files are are unique to each pipeline *script*, but do not need to be changed according to the user or project. These handle the data file identification, pipeline order, software and computing resources of each of the scripts. :so: It is recommended that these are named to mirror their corresponding scripts as they used hand in hand.
(:b: *c1_.scalpart.txt* is the config file for *s1_scalpart.htb*)
(:b: *c1_.scalpart.cfg* is the config file for *s1_scalpart.htb*)
:so: Save you config files as text files, this will make them easy to view, edit and save outside of the batch_context user interface.
:b: All the configuration files are saved as .txt and located in the *analysis/support/config* directory.
:b: All the configuration files are saved as .cfg and located in the *analysis/support/config* directory.
# Context configuration files (*.cfg)
You will need a unique context config file for each project. To get started go to:
* *File ->Batch-> Context Configuration*
......