...
| Tip |
|---|
| title | sbatch command line option |
|---|
|
Like any other SBATCH directive, you may alternatively pass the export in the sbatch command line instead: | No Format |
|---|
sbatch --export=STHOST=ws2 job.sh |
|
To use ecsbatch with Troika, you can use configuration file:
| Bitbucket file |
|---|
| repoSlug | ecflow_include |
|---|
| branchId | refs/heads/master |
|---|
| projectKey | USS |
|---|
| filepath | troika.yml |
|---|
| progLang | yml |
|---|
| collapsible | true |
|---|
| applicationLink | a675ea11-b2c4-336c-bfb6-077e786ef5b2 |
|---|
|
.Troika module on Atos HPC is configured to use ecbatch by default.
| Note |
|---|
| title | ksh and all ecFlow jobs special requirement |
|---|
|
Make sure you include this line right after the SBATCH directives header: | Code Block |
|---|
source /etc/profile |
|
...
| Warning |
|---|
While the availability of virtual infrastructure to run ecFlow servers remains limited, you may start your ecFlow servers in the interim HPCF dedicated node to be able to run your suites, as detailed in HPC2020: Using ecFlow. However, keep in mind the new model model when migrating or designing your solution. |
...