... | ... | @@ -17,11 +17,11 @@ You will need a unique context config file for each project. To get started go t |
|
|
![smallestcreatecontextconfig](/uploads/d1632e0d4616b94e5235e3cca0821112/smallestcreatecontextconfig.png)
|
|
|
|
|
|
## Editing
|
|
|
You can create a new or edit and old context config in this user interface. To load an existing config file click on the |`Load Context Config`| button. You will need to fill out a number of fields depending on whether you will be running the job locally or remotely. All jobs must fill out the local dependency fields at the top of the block.
|
|
|
You can create a new or edit and old context config in this user interface. To load an existing config file click on the | `Load Context Config` | button. You will need to fill out a number of fields depending on whether you will be running the job locally or remotely. All jobs must fill out the local dependency fields at the top of the block.
|
|
|
![contextedit](/uploads/936947f6c07f2c7ba518432524a44d4d/contextedit.png)
|
|
|
***
|
|
|
A detailed description of each of the fields can be found below:
|
|
|
:so: Set the matlab workspace as your project_name directory that way these fields can be filled out neater.
|
|
|
:so: Set the matlab workspace as your project_name directory so your path names can be shorter.
|
|
|
***
|
|
|
*Required for All Jobs*
|
|
|
***
|
... | ... | @@ -92,7 +92,7 @@ A detailed description of each of the fields can be found below: |
|
|
fusermount -u [cd]/[mount_work]*
|
|
|
|
|
|
## Saving
|
|
|
Once you have filled out all of the fields click on the |`Save As`| button to save the file. :so: Name this file to includes the project and the user
|
|
|
Once you have filled out all of the fields click on the | `Save As` | button to save the file. :so: Name this file to includes the project and the user
|
|
|
(:b: *contextconfig_local.txt* and *contextconfig_remote.txt* can be found in the *analysis/support/config* directory).
|
|
|
Now when running a job you can simply load this file and it will populate the required fields for you. You can also use this text file as a template to quickly edit and create new context config files in a text editor.
|
|
|
|
... | ... | @@ -103,7 +103,7 @@ There needs to be a unique batch config file created for each script in the pipe |
|
|
![smallestcreatebatchconfig](/uploads/48f5df1610f2c60bbad7158a49b01dcd/smallestcreatebatchconfig.png)
|
|
|
|
|
|
## Editing
|
|
|
You can create a new or edit and old batch config in this user interface. To load existing batch files click on the |`Get Batch Config File Names`| button. This interface allows you to look at, and edit, multiple config files at once. This helps you visualise the pipeline order, and ensure that every script you are using has a designated configuration file for it. You will need to fill out a number of fields depending on whether you will be running the job locally or remotely.
|
|
|
You can create a new or edit and old batch config in this user interface. To load existing batch files click on the | `Get Batch Config File Names` | button. This interface allows you to look at, and edit, multiple config files at once. This helps you visualise the pipeline order, and ensure that every script you are using has a designated configuration file for it. You will need to fill out a number of fields depending on whether you will be running the job locally or remotely.
|
|
|
![editconfigbuttons](/uploads/15cfea01e62161d13011548c19254ffe/editconfigbuttons.png)
|
|
|
***
|
|
|
|
... | ... | @@ -151,7 +151,7 @@ In the example below the first script is number [1]. After it is complete both s |
|
|
|
|
|
**5. Session Init**
|
|
|
* This field will contain the location of any scripts you need to run on the remote sever at the beginning of the session. If you are running a project locally you can leave this field blank.
|
|
|
:b: Remote Default is *analysis/support/comfig/octave.sesinit* a script file that initialises the octave software on the remote server.
|
|
|
:b: Remote Default is *analysis/support/config/octave.sesinit* a script file that initialises the octave software on the remote server.
|
|
|
|
|
|
**6. Job Init**
|
|
|
* This field will contain the location of any scripts you need to run on the remote sever at the beginning of the job. If you are running a project locally you can leave this field blank.
|
... | ... | @@ -162,7 +162,7 @@ In the example below the first script is number [1]. After it is complete both s |
|
|
:b: Default is left blank ' '.
|
|
|
|
|
|
**8. Scheduler Options**
|
|
|
* This section contains a series of characters to communicate the job specifications to the remote server, such as memory and time. Click on the field and look at the information box below to see the sepecific commands. If you are running a project locally you can leave this field blank.
|
|
|
* This section contains a series of characters to communicate the job specifications to the remote server, such as memory and time. Click on the field and look at the information box below to see the specific commands. If you are running a project locally you can leave this field blank.
|
|
|
:b: Remote default is *-r 4h -o [batch_hfn]*
|
|
|
|
|
|
**8. Software**
|
... | ... | @@ -182,7 +182,7 @@ These fields once filled out play a part in creating a *submit string* that is u |
|
|
***
|
|
|
|
|
|
## Saving
|
|
|
Once you have filled out all of the fields click on the |`Save As`| button to save. If you have multiple files open *Ctrl - Click* to select as many as you would like to save. These will **not** be combined into one 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* )
|
|
|
Once you have filled out all of the fields click on the | `Save As` | button to save. If you have multiple files open *Ctrl - Click* to select as many as you would like to save. These will **not** be combined into one 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.
|
|
|
|
|
|
***
|
... | ... | |