ProductionProcedures: Difference between revisions

From Mu2eWiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(One intermediate revision by the same user not shown)
Line 37: Line 37:
mu2einit
mu2einit
sl7container
sl7container
source $HOME/bin/authentication.sh
mu2einit
</pre>
</pre>
run the job script
run the job script


<pre>
<pre>
MOO_CAMPAIGN_STAGE=Reco
export MOO_CAMPAIGN_STAGE=Reco
MOO_SOURCE=v00_03_02
export MOO_SOURCE=v00_03_02
MOO_DATASET=CRVWB-000
export MOO_DATASET=CRVWB-000
MOO_VERBOSE=1
export MOO_VERBOSE=1
MOO_OUTDIR=production
export MOO_OUTDIR=production
MOO_APPEND_NAME=none
export MOO_APPEND_NAME=none
MOO_CFG=CRVWB-008
export MOO_CFG=CRVWB-008
MOO_CONFIG=CRVWB-000-008-000
export MOO_CONFIG=CRVWB-000-008-000
MOO_CAMPAIGN=CRVWB-000-0
export MOO_CAMPAIGN=CRVWB-000-0
MOO_SCRIPT=CRVWB/reco.sh
export MOO_SCRIPT=CRVWB/reco.sh
MOO_CRVTESTSTAND=v17
export MOO_CRVTESTSTAND=v17


export MOO_LOCAL_INPUT=https://fndcadoor.fnal.gov:2880/pnfs/fnal.gov/usr/mu2e/tape/phy-raw/raw/mu2e/CRV_wideband_cosmics/crvled-001/dat/3b/a7/raw.mu2e.CRV_wideband_cosmics.crvled-001.001303_056.dat
export MOO_LOCAL_INPUT=https://fndcadoor.fnal.gov:2880/pnfs/fnal.gov/usr/mu2e/tape/phy-raw/raw/mu2e/CRV_wideband_cosmics/crvled-001/dat/3b/a7/raw.mu2e.CRV_wideband_cosmics.crvled-001.001303_056.dat

Latest revision as of 15:41, 23 July 2024

Introduction

Running jobs locally

In production log files, there is configuration dump stanzas like

************** control summary exe ***************
MOO_CAMPAIGN_STAGE=Reco
MOO_SOURCE=v00_03_02
MOO_DATASET=CRVWB-000
MOO_VERBOSE=1
MOO_OUTDIR=production
MOO_APPEND_NAME=none
MOO_CFG=CRVWB-008
MOO_CONFIG=CRVWB-000-008-000
MOO_CAMPAIGN=CRVWB-000-0
MOO_SCRIPT=CRVWB/reco.sh
MOO_CRVTESTSTAND=v17
************** control summary exe ***************

Jobs are run in a a generic wrapper script and are completely controlled by these variables and the input files. The variables are set through the process of interpreting the POMS campaign configuration, the cfg files, and the wrapper script itself. The easiest way to get a complete of control variable is from a log file, but if that's not available, there is currently no simple verified way to extract them from the sources (if, for example, no jobs run). To rerun a jobs locally, you only need to write a little script that sets these variables, then provides one more:

export MOO_LOCAL_INPUT=https://fndcadoor.fnal.gov:2880/pnfs/fnal.gov/usr/mu2e/tape/phy-raw/raw/mu2e/CRV_wideband_cosmics/crvled-001/dat/3b/a7/raw.mu2e.CRV_wideband_cosmics.crvled-001.001303_056.dat

Goto an area with some space

cd /exp/mu2e/data/users/mu2epro/production_recovery
# pick a subdirectory
cd 1
# cleanup, make it look a grid dir
rm -f * jsb_tmp/*
mkdir -p jsb_tmp

if needed to run in sl7.

mu2einit
sl7container
mu2einit

run the job script

export MOO_CAMPAIGN_STAGE=Reco
export MOO_SOURCE=v00_03_02
export MOO_DATASET=CRVWB-000
export MOO_VERBOSE=1
export MOO_OUTDIR=production
export MOO_APPEND_NAME=none
export MOO_CFG=CRVWB-008
export MOO_CONFIG=CRVWB-000-008-000
export MOO_CAMPAIGN=CRVWB-000-0
export MOO_SCRIPT=CRVWB/reco.sh
export MOO_CRVTESTSTAND=v17

export MOO_LOCAL_INPUT=https://fndcadoor.fnal.gov:2880/pnfs/fnal.gov/usr/mu2e/tape/phy-raw/raw/mu2e/CRV_wideband_cosmics/crvled-001/dat/3b/a7/raw.mu2e.CRV_wideband_cosmics.crvled-001.001303_056.dat

nice /cvmfs/mu2e.opensciencegrid.org/bin/OfflineOps/wrapper.sh  \
  1> jsb_tmp/JOBSUB_LOG_FILE 2> jsb_tmp/JOBSUB_ERR_FILE

# optionally put in the background