form.yml

---
cluster: "owens"
form:
  - bc_account
  - bc_num_hours
  - node_type
  - num_cores
  - job_runner
  - bc_email_on_started
attributes:
  num_cores:
    widget: "number_field"
    label: "Number of cores"
    value: 1
    help: |
      Number of cores on node type (4 GB per core unless requesting whole
      node). Leave blank if requesting full node.
    min: 1
    max: 28
    step: 1
    id: 'num_cores'
  bc_account:
    label: "Project"
    help: "You can leave this blank if **not** in multiple projects."
  node_type:
    widget: select
    label: "Node type"
    help: |
      - **any** - (*1-28 cores*) Use any available Owens node. This reduces the
        wait time as there are no node requirements.
      - **hugemem** - (*4-48 cores*) Use an Owens node that has 1.5TB of
        available RAM as well as 48 cores. There are 16 of these nodes on
        Owens.
      - **debug** - (*1-28 cores*) For short sessions (= 1 hour) the debug
        queue will have the shortest wait time. This is only accessible during
        8AM - 6PM, Monday - Friday. There are 6 of these nodes on Owens.
    options:
      - [ "any",     "any"     ]
      - [ "hugemem", "hugemem" ]
      - [ "debug",   "debug"   ]
  job_runner:
    widget: select
    label: "Galaxy tool runner"
    help: |
      - **local** - When running tools locally, they are child processes of the Galaxy server. 
        The maximum number of concurrent jobs is the number of cores.
        When session ends, you lose contact with those jobs still running, 
        and they must be restarted.
      - **cluster** - When running tools in a cluster, they are separate processes from the Galaxy server.
        They are jobs submitted to Owens Cluster as configured above and there is no maximum number of concurrent jobs. 
        When session ends, the jobs will continue to run and finish.
    options:
      - [ "local",     "local"]
      - [ "cluster", "pbs" ]