-
Notifications
You must be signed in to change notification settings - Fork 16
Pilot Workflows
Paul Nilsson edited this page Apr 25, 2022
·
1 revision
The Pilot workflows refer to the particular run mode that the Pilot should use. This includes the Standard workflow and HPC Pilot workflow. The desired workflow is selected by the wrapper script that launches the Pilot, using option -w workflow (e.g. generic_hpc; default: generic) and it determines how the jobs will be processed by selecting the corresponding Pilot module. For the HPC Pilot workflow, the HPC resource name needs to be specified using option --hpc-resource resource_name (e.g. titan).
The Standard and HPC Pilot workflows are explained in the following sections.
- Introduction
- Pilot Architecture
- Project Structure
- Pilot Workflows
- Event service
- Metadata
- Signal Handling
- Error Codes
- Containers
- Special Algorithms
- Timing Measurements
- Data Transfers
- Copy Tools
- Direct Access
- Fallback Mechanism in Unified PanDA Queues
- Memory Monitoring
- Job Metrics
- Pilot release procedure
- Core count