New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding a new platform #7

Closed
sahilseth opened this Issue Jul 10, 2015 · 0 comments

Comments

Projects
None yet
1 participant
@sahilseth
Copy link
Owner

sahilseth commented Jul 10, 2015

Adding a new platform involves a few moving pieces.

  1. Job submission
  2. Parsing of job IDs, the platform returns upon submission
  3. Providing job IDs to the subsequent, as a dependency to subsequent jobs

Example, adding torque:

  1. submission: Template used for submission:
    https://github.com/sahilseth/flowr/blob/master/inst/conf/torque.sh
  2. parse_jobid: The job ids should parse using regular expression as provided by:
    https://github.com/sahilseth/flowr/blob/master/inst/conf/flowr.conf
    As used in parse-jobids():
    https://github.com/sahilseth/flowr/blob/master/R/parse-jobids.R
  3. parse_dependency: These are then parsed to create a dependency string, as seen here:
    https://github.com/sahilseth/flowr/blob/master/R/parse-dependency.R
  4. job(): Add a new class using the platform name. This is essentially just a wrapper around job class.
    https://github.com/sahilseth/flowr/blob/master/R/class-def.R
    setClass("torque", contains = "job")
  5. Killing jobs
  • Its important to have the right kill command in: detect_kill_cmd()

@sahilseth sahilseth added the question label Jul 10, 2015

@sahilseth sahilseth closed this Jul 18, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment