| ... | ... | @@ -101,7 +101,7 @@ Remote configurations require you to know what your remote scheduler is and any |
|
|
|
[Merge Request](https://git.sharcnet.ca/bucanl_eeglab_extensions/batch_context/merge_requests)
|
|
|
|
if you think there is something we can do better.
|
|
|
|
|
|
|
|
For remotes jobs we usually use GNU Octave. GNU Octave is a free and open source implementation of the Matlab language. GNU Octave is becoming more and more compatible with Matlab every day and is much easier to work with due to its GPL licensing which makes it openly available. Ensure you have GNU Octave installed on your remote cluster. We write all our scripts to be compatible with both Octave/Matlab
|
|
|
|
For remotes jobs we usually use GNU Octave. GNU Octave is a free and open source implementation of the Matlab language. GNU Octave is becoming more and more compatible with Matlab every day and is much easier to work with due to its GPL licensing which makes it openly available. Ensure you have GNU Octave installed on your remote cluster. We write all our scripts to be compatible with both Octave/Matlab. Tweeks may be required for remote running but will be talked about in the [Running remotely section](tutorial-running-remotely).
|
|
|
|
|
|
|
|
## Bandpass Configuration (Remote)
|
|
|
|
|
| ... | ... | @@ -111,11 +111,41 @@ You can open this in `Batch > Batch Configuration` and edit it there. |
|
|
|
|
|
|
|
You will need to add the following fields
|
|
|
|
* session_init = `config/octave.sesinit
|
|
|
|
* m_init = `config/octave.minit`
|
|
|
|
* memory = `1 + c*0.001g`
|
|
|
|
* this specifies to request 1 gigabyte plus an additional mb per channel
|
|
|
|
* time_limit = `15 + c*0.1m`
|
|
|
|
* this specifies to request 15 minutes, plus 0.1 additional minutes per channel
|
|
|
|
|
|
|
|
*WIP*
|
|
|
|
Based on your scheduler additional options may be required. If you require specific options that are not abstracted you can put them in submit_options as well.
|
|
|
|
|
|
|
|
Save as `config/c01_bandpass_remote.cfg`
|
|
|
|
|
|
|
|
## Amica Configuration (Remote)
|
|
|
|
|
|
|
|
Start with the [Amica Local configuration](#amica-configuration-local)
|
|
|
|
|
|
|
|
First we need a submission session initialization for Amica, this will run the code in this file on the remote before submitting the job. We use the session init to setup environment variables and other short setups.
|
|
|
|
* session_init = `config/amica.sesinit`
|
|
|
|
|
|
|
|
Amica can run in multiple threads (as well as multiple machines using MPI however we will not cover that here. In order to leverage multiple cores on a cluster you often need to specify the number of cores. Do so by setting
|
|
|
|
* threads_per_task = 8
|
|
|
|
* num_tasks = 1
|
|
|
|
* mpi = false
|
|
|
|
|
|
|
|
Note that num_tasks defaults to 1 and mpi was already false. This set of settings specifies to use one process with 8 cores. Which matches the config in our Amica params.
|
|
|
|
|
|
|
|
Save as `config/c02_amica_remote.cfg`
|
|
|
|
|
|
|
|
and
|
|
|
|
|
|
|
|
Save as `config/c03_amica_remote.cfg`
|
|
|
|
|
|
|
|
## Fin Configuration (Remote)
|
|
|
|
|
|
|
|
Start with [Fin Configuration Local](#fin-configuration-local)
|
|
|
|
|
|
|
|
Save as `config/c04_fin_remote.cfg`
|
|
|
|
|
|
|
|
*Updated/Verified by Brad Kennedy on 2017-08-11*
|
|
|
|
|
| ... | ... | |
