MCProdWorkflow: Difference between revisions

From Mu2eWiki
Jump to navigation Jump to search
No edit summary
Line 6: Line 6:


This page assumes that the user is familiar with the basic infrastructure and its references:
This page assumes that the user is familiar with the basic infrastructure and its references:
* [[Fclintro|fcl]]
* [[FclIntro|fcl]]
* [[Simulation]]
* [[Simulation]]
* [[JobPlan|job planning]]
* [[JobPlan|job planning]]
Line 37: Line 37:
show what will be done without performing the action.
show what will be done without performing the action.


==Prestage inputs==
==Collecting Inputs==
<pre>
# input dataset, if needed
export INPUTDS=sim.mu2e.cd3-beam-g4s1-dsregion.0506a.art
#
# project, similar to cd3-beam or cd3-cosmic
export PROJECT=abc-phys
# stage, like g4s1
export STAGE=g4s1
export WORKDIR=/mu2e/data/users/$USER/projects/$PROJECT
export FCLDIR=$WORKDIR/fcl
# user or mu2e for mu2epro for collaboration work
DSOWNER=mu2e
# a unique string for versions in case project has restarts or variations
DSCONF=v0
#
# tags, one each for for output steams, like dsregion, mubeam, truncated, crv
# output datas
export OUTDS1=out1
export CATSTAGE=cs1
export CATDIR1=/mu2e/data/users/$USER/projects/$PROJECT/fcl/out1
</pre>
 
<pre>
mkdir -p $FCLDIR
mkdir -p $CATDIR1
# repeated ..
 
 
</pre>
 
==1) Prestage inputs==
 
We recommend starting the prestaging as soon as possible since it can take several days.  Please follow the [[Prestage|prestage]] instructions for $INPUTDS.
 
==2) Generate fcl ==
 
Please follow the

Revision as of 21:01, 4 April 2017

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:

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.

Collecting Inputs

# input dataset, if needed
export INPUTDS=sim.mu2e.cd3-beam-g4s1-dsregion.0506a.art
#
# project, similar to cd3-beam or cd3-cosmic
export PROJECT=abc-phys 
# stage, like g4s1
export STAGE=g4s1
export WORKDIR=/mu2e/data/users/$USER/projects/$PROJECT
export FCLDIR=$WORKDIR/fcl
# user or mu2e for mu2epro for collaboration work
DSOWNER=mu2e
# a unique string for versions in case project has restarts or variations
DSCONF=v0
#
# tags, one each for for output steams, like dsregion, mubeam, truncated, crv
# output datas
export OUTDS1=out1
export CATSTAGE=cs1
export CATDIR1=/mu2e/data/users/$USER/projects/$PROJECT/fcl/out1
mkdir -p $FCLDIR
mkdir -p $CATDIR1
# repeated ..


1) Prestage inputs

We recommend starting the prestaging as soon as possible since it can take several days. Please follow the prestage instructions for $INPUTDS.

2) Generate fcl

Please follow the