Main menu
You are here
Batch Job Tracks
Thu, 10/03/2013 - 11:10 — ychen
NOTE: This information is no longer valid for our slurm-based queue manager. See 'account' and 'partition' information under https://scicomp.jlab.org/cli/add-job.html
All jobs submitted to the farm will belong to a track. The track is used to determine both what queue a job runs in and what type of job it is for accounting purposes.
| Track | Batch Queue | Description |
|---|---|---|
| debug | priority | For debug use |
| reconstruction | production | Reconstruction of raw data |
| analysis | production | Analysisjobs |
| one_pass | production | Combined reconstruction/analysis jobs |
| simulation | production | Simulation jobs |
| test | priority | Test run of code on the farm |
| theory | --- | Running long theory jobs |
Special Tracks
Note that there are two special tracks: debug and test. The debug track is useful when you are trying to debug your jobs to make sure that they run correctly. They get the highest priority when running on the farm, but are limited to 4 hours of CPU time. The test track is at the opposite end of the spectrum and is used for jobs that don't have to finish any time soon. Not only do jobs in the test track get the lowest priority for being dispatched to the farm, but even after being dispatched these jobs will be suspended if the farm gets busy.
- Log in to post comments
Comments
Is this still up to date?
Is this still up to date. Did try running with track debug and get an error saying partition debug does not exist.
Joerg
I meanwhile figured out that
I meanwhile figured out that this is not up to date anymore. Slurm uses "account" and "partition" instead of "project" and "track". See for example https://scicomp.jlab.org/docs/swif2.