User:Rlc/gears

From Mu2eWiki
< User:Rlc
Revision as of 03:30, 7 May 2024 by Rlc (talk | contribs) (Created page with "Gears is the Mu2e replacement for POMS ==Introduction== Each stage is independent, connected only by the dataset name. A campaign is only a way to set parameters for all sta...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Gears is the Mu2e replacement for POMS

Introduction

Each stage is independent, connected only by the dataset name. A campaign is only a way to set parameters for all stages

User interface

the jobs is configured from a directory. Typically a campaign directory where stages are subdirectories. The work is driven by starting a process like "gears <dir> &" the process should be able to be killed and restarted. It should detect a duplicate. This might also be a cron job. The campaign directory has a config file, and each stage has a config file which inherits from the campaign file.

states

stop - don't do anything idle - don't submit, but update records for running jobs run - submit and update records test - submit and update only one test job

commands

  • run - go to run state
  • pause - go to idle state
  • stop - kill running jobs and go to stopped state
  • testN - create a test slice, go to test state
  • reset - kill running jobs, delete output files, archive records, go to stop state