| ... | ... | @@ -27,8 +27,8 @@ Meld 1.7 (or later), sshfs, and rsync.* |
|
|
|
# Tutorials and Best Practice
|
|
|
|
There are three symbols that you should keep an eye out for in this documentation:
|
|
|
|
* :so: These stars highlight our recommended **Best Practices**.
|
|
|
|
* :b: The letter B indicates an **example** based off of the BUCANL Pipeline Tutorials.
|
|
|
|
* :warning: This warning indicates when you have to make a change to a file in the tutorial package
|
|
|
|
* :b: The letter B indicates an **Example** based off of the BUCANL Pipeline Tutorials.
|
|
|
|
* :warning: This warning indicates when you have to **Change a Tutorial File** if you are using one of the EEG_pipe packages
|
|
|
|
|
|
|
|
# Overview
|
|
|
|
Running a successful job using batch context consists of 5 main components:
|
| ... | ... | @@ -37,8 +37,11 @@ Running a successful job using batch context consists of 5 main components: |
|
|
|
3. [Batch Configuration Files](https://git.sharcnet.ca/jdesjard/batch_context/wikis/configuration-files)
|
|
|
|
4. [Context Configuration File](https://git.sharcnet.ca/jdesjard/batch_context/wikis/configuration-files)
|
|
|
|
5. [Local or Remote Computing Resources ](https://git.sharcnet.ca/jdesjard/batch_context/wikis/running-scripts)
|
|
|
|
|
|
|
|
All of these components will need to be selected or loaded into the main batch context user interface before the batch is executed. Running your data file in a batch is an effective way to execute script pipelines on large sets of data files.
|
|
|
|
|
|
|
|
:so: Download a * [Tutorial Pipeline](https://git.sharcnet.ca/jdesjard/batch_context/wikis/tutorials) and work your way through the wiki pages. If you want to get right to running a job go to * [Running scripts](https://git.sharcnet.ca/jdesjard/batch_context/wikis/running-scripts) and use the provide
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ... | ... | |
