Difference between revisions of "Getting Started - Farm Jobs"
m (Cmorean moved page Getting Started - Farm Jobs to GettingStarted FarmJobs) |
|||
| Line 1: | Line 1: | ||
| − | ==Using JLab Farm== | + | ==Using the Jefferson Lab Farm== |
| − | + | ||
| − | + | ===Documentation=== | |
| − | + | This wiki is to be used as a conglomerate of resource links and practice. The documents here are not necessarily the most up-to-date, but it serves as a starting point for new users to get familiar with the JLab HPC environment and get some hands-on practice. Here is a list of useful information: | |
| − | + | ;Farm Usage | |
| − | + | : [//https://indico.jlab.org/event/319/contributions/4916/attachments/4046/4891/Computing_tools-tricks-Jun2019.pdf Brad's famous JLab Compute Resources "How-to"] | |
| + | : [//https://scicomp.jlab.org/docs/FarmUsersGuide Farm Users Guide] | ||
| + | ;Analyzer Information | ||
| + | : [//https://indico.jlab.org/event/319/contributions/4914/attachments/4066/4912/Software-HallAC-Collab-Meeting-2019-06-28.pdf Ole's 2019 Hall A/C Analyzer Software Overview] | ||
| + | : [//https://redmine.jlab.org/projects/podd/wiki/Workshop2018 2018 Joint A/C Analysis Workshop] | ||
| + | : [//https://hallcweb.jlab.org/hcana/docs/ hcana docs] | ||
| + | ; | ||
| + | |||
| + | ===Overview=== | ||
| + | All current tasks in the XEM2 group require submitting many single-core jobs to the farm using either SWIF or AUGER. hcswif is used to submit replay jobs run-by-run to the farm nodes to run in parallel using SWIF (Outlined in the Farm Users Guide). Auger is used to submit multiple single-core jobs that do not need to access the tape library. This includes running multiple mc-single-arm instances, or running rc-externals with multiple cores. | ||
| + | The following example(s) are in support of the XEM2 use case. | ||
| + | |||
| + | ===AUGER=== | ||
| + | *Practice submitting stuff... | ||
| + | |||
| + | ===SWIF=== | ||
| + | *Practice submitting stuff... | ||
| + | |||
| + | === Using hcswif=== | ||
| + | hcswif is used to submit many analysis jobs based on run-number. | ||
| + | |||
| + | ===Troubleshooting=== | ||
'''Common commands and difficulties with jobs''' | '''Common commands and difficulties with jobs''' | ||
| + | |||
| + | ===Common Failure Modes=== | ||
Revision as of 17:30, 30 August 2021
Using the Jefferson Lab Farm
Documentation
This wiki is to be used as a conglomerate of resource links and practice. The documents here are not necessarily the most up-to-date, but it serves as a starting point for new users to get familiar with the JLab HPC environment and get some hands-on practice. Here is a list of useful information:
- Farm Usage
- Brad's famous JLab Compute Resources "How-to"
- Farm Users Guide
- Analyzer Information
- Ole's 2019 Hall A/C Analyzer Software Overview
- 2018 Joint A/C Analysis Workshop
- hcana docs
Overview
All current tasks in the XEM2 group require submitting many single-core jobs to the farm using either SWIF or AUGER. hcswif is used to submit replay jobs run-by-run to the farm nodes to run in parallel using SWIF (Outlined in the Farm Users Guide). Auger is used to submit multiple single-core jobs that do not need to access the tape library. This includes running multiple mc-single-arm instances, or running rc-externals with multiple cores. The following example(s) are in support of the XEM2 use case.
AUGER
- Practice submitting stuff...
SWIF
- Practice submitting stuff...
Using hcswif
hcswif is used to submit many analysis jobs based on run-number.
Troubleshooting
Common commands and difficulties with jobs
