... | ... | @@ -3,8 +3,8 @@ |
|
|
# Introduction
|
|
|
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: It is recommended that this file's name includes the project and the user.
|
|
|
(ie. *adlofts_eyespilot2016_contextconfig.cfg* )
|
|
|
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* )
|
|
|
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.
|
|
|
(ie. *S1_Script1.htb* and *C1_Config_for_Script1.cfg* )
|
... | ... | |