... | ... | @@ -12,7 +12,7 @@ These are config text files are are unique to each pipeline *script*, but do not |
|
|
If is highly suggested that you always save you config files in the support/config directory as text files. This will make them easy to edit and save outside of the batch_context user interface, as well as having an easy to load file when [Running the Scripts](https://git.sharcnet.ca/jdesjard/batch_context/wikis/running-scripts)
|
|
|
# Context configuration files (*.cfg)
|
|
|
A user will need a unique context config file for each project. To get started go to:
|
|
|
* *File -> Context Configuation*
|
|
|
* *File -> Context Configuration*
|
|
|
![smallestcreatecontextconfig](/uploads/d1632e0d4616b94e5235e3cca0821112/smallestcreatecontextconfig.png)
|
|
|
|
|
|
## Editing
|
... | ... | @@ -73,15 +73,15 @@ A detailed description of each of the fields can be found below: |
|
|
* text
|
|
|
|
|
|
## Saving
|
|
|
Once you have filled out all of the fields click `Save As` to save the file. It is recommended that this file's name includes the project and the user.
|
|
|
(ie. *adlofts_eyespilot2016_contextconfig.cfg* ) Make sure to place it in support/config.
|
|
|
Now when running a job your can simply load this file and it will populate the required fields for you. You can also use the text file created as a template to quickly edit and create new context config files in a text editor.
|
|
|
Once you have filled out all of the fields click on the |`Save As`| button to save the file. It is recommended that this file's name includes the project and the user. (ie. *adlofts_eyespilot2016_contextconfig.cfg* ) Make sure to place it in support/config.
|
|
|
Now when running a job you can simply load this file and it will populate the required fields for you. You can also use the text file created as a template to quickly edit and create new context config files in a text editor.
|
|
|
|
|
|
# Job configuration files (*.cfg)
|
|
|
text
|
|
|
## Editing
|
|
|
text
|
|
|
![smallestcreatebatchconfig](/uploads/48f5df1610f2c60bbad7158a49b01dcd/smallestcreatebatchconfig.png)
|
|
|
There needs to be a unique file created for each script in the pipeline. As the batch config files are not dependant on the project or the user, it is recommended that you only create one local and one remote file for each script. To get started go to:
|
|
|
* *File -> Batch -> Batch Configuration*
|
|
|
![smallestcreatebatchconfig](/uploads/48f5df1610f2c60bbad7158a49b01dcd/smallestcreatebatchconfig.png)
|
|
|
|
|
|
## Editing
|
|
|
text
|
|
|
![editconfigbuttons](/uploads/15cfea01e62161d13011548c19254ffe/editconfigbuttons.png)
|
|
|
***
|
... | ... | @@ -122,8 +122,7 @@ text |
|
|
* text
|
|
|
|
|
|
## Saving
|
|
|
text
|
|
|
## Loading
|
|
|
text
|
|
|
Once you have filled out all of the fields click on the |`Save As`| button to save the file. It is recommended that the files are named to mirror their corresponding scripts as they used hand in hand. (ie. *S1_Script1.htb* and *C1_Config_for_Script1.cfg* )
|
|
|
Now when running a job you can simply load this file and it will populate the required fields for you. You can also use the text file created as a template to quickly edit and create new batch config files in a text editor.
|
|
|
|
|
|
# Best Practices |
|
|
\ No newline at end of file |