NA62 Monte Carlo Simulations
This wiki describes how to set up and distribute the NA62 Monte Carlo simulation code.
Software
- Test tarball from Antonino Sergi: NA62MC.tar.zip
- Job submission and output management system code components are held on and SVN repo at IC (access list: Dan, Janusz, Stuart). The files attached to this wiki are not the latest versions.
Code compilation
- Versions:
- v4 - Contains bug in the MC which Tonino spotted after giving us the tar ball
- v5 - Installed by Janusz on May 10 (see table below)
- Unpack tarball to NA62MC
- Fix libs path problems in GNUMakefile-s (Generator/ and Beam/)
- Make changes to env.sh: source 'offline' environment; clear XAWLIBS variable
- Rearrange paths (move system paths after NA62-specific paths)
- Type 'make' and be patient
Code distribution
- Create tarballs for geant4, root, X11 and sw (CreateTarballs.sh)
- Run special job (with an SGM Admin role) to wget and unpack these tarballs on sites (InstallSoftware.sh)
- Run test job
Job submission
- Run parameters given in the StandardRun.mac file: run number, number of events, random seed, root output file name
- Job environment parameters are set by sourcing the
na62jobenv.sh
script created by InstallSoftware.sh
- The .mac is modified using
sed
on the worker node to modify paths to LAV matrix files, which are installed in the software area by InstallSoftware.sh
- The actual job script is attached (needs editing and streamlining)
Automated jobs scripts creator
There's now a suite of tools for submitting jobs either one-by-one or in bulk. Jobs submitted via this interface have the advantage that everything about the jobs (input and output files, scripts, run parameters and statistics) are archived for later reference.
The
script creator interface lets the production manager (PM) set up the job parameters (both MC parameters and output options) and choose the number of 'runs' to launch. The
scripter prints out in the browser a list of commands that the PM has to run on his grid UI in order to launch the job or production with
his credentials. For individual jobs, the PM updates the DB by hand, for multiple runs, it is done via a wrapper script. A cron job periodically updates the list of jobs and files in the DB.
Workflow
Site resources
This is a simple table to keep track of site resources (please update if changes occur):
Note on s/w labelling: both a NA62 release number (e.g. r170) and a tarball version (e.g. v5) are used. They are kept track of in a dedicated DB table.
To do before next production round
- Install new tarball once it's available from Tonino
- Resolve CERN FTS channel problem GGUS ticket #83133
- Scale scripts for largers submissions
To log problems encountered and solutions use this wiki:
Links