MCProdWorkflow

Introduction

This workflow is for production-style simulation jobs. It can be used for stage-1 jobs which start with a generator, or later simulation stages which start with the output files of previous stages. It will result in the output files being concatenated and uploaded to tape and properly documented through the SAM database. It is intended for cases where the output needs to be saved for more than a month or so, or that might be used by many collaborators, or needs to be carefully documented. If your work doesn't need to be uploaded or is more personal or temporary, you can follow the scratch workflow which does not concatenate or upload. Most commonly this procedure would be part of a collaboration simulation effort and would be run out of the mu2epro account, but is can be run in a personal account.

The user should prepare the physics, and relevant fcl in detail and perform basic test before starting this procedure.

This page assumes that the user is familiar with the basic infrastructure and its references:

• fcl
• Simulation
• job planning
• grid
• file names
• file tools
• SAM
• grids
• dCache
• enstore
• prestaging
• concatenation
• mu2egrid
• monitoring

The basic steps, expanded below are

• if needed, prestage input files
• generate a set of fcl files
• register the fcl dataset with SAM, and copy fcl files to dCache
• submit jobs
• check output and recover failed jobs
• if needed, concatenate output files
• upload output files
• tar and upload log files

The mu2egrid and related packages provides Mu2e-specific code required for submitting jobs and manipulating files. Most scripts support the --help option. Look for the --dry-run and --verbose options to show what will be done without performing the action.