Thanks for the support! If you could, please submit all pull requests in devel
branch. We test things in devel
and push then to master
after a few tests.
Adding a new platform involves a few steps, briefly we need to consider the following steps where changes would be necessary.
parsing job ids: flowr keeps a log of all submitted jobs, and also to pass them along as a dependency to subsequent jobs. This is taken care by the parse_jobids() function. Each job scheduler shows the jobs id, when you submit a job, but each shows it in a slightly different pattern. To accommodate this one can use regular expressions as described in the relevant section of the flowr config.
render dependency: After collecting job ids from previous jobs, flowr renders them as a dependency for subsequent jobs. This is handled by render_dependency.PLATFORM functions.
Essentially this requires us to add a new line like: setClass("torque", contains = "job")
.
There are several job scheduling systems available and we try to support the major players. Adding support is quite easy if we have access to them. Your favourite not in the list? re-open this issue, with details on the platform: adding platforms
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.