Running Art Tutorial: Difference between revisions

From Mu2eWiki
Jump to navigation Jump to search
Line 7: Line 7:


== Session Introduction ==
== Session Introduction ==
Mu2e Offline is a collection of code and scripts used for simulation, reconstruction and analysis of Mu2e data.
Art is a software framework for running modular code with lots of run-time configurability.  Art is controlled by scripts in a
Offline is kept in a git repository.  It depends on external software provided through cvmfs (Cern virtual machine file system).
Users interact with Offline in several ways, with more or less of the code resident in your local working area.  Art is a
software framework for running modular code with lots of run-time configurability.  Art is controlled by scripts in a
dedicated configuration language called fhicl (.fcl suffix).
dedicated configuration language called fhicl (.fcl suffix).


This tutorial will cover creating the local environment to work with Offline, how to build and run several different
This tutorial will cover how to build and run several different
kinds of art jobs, and how to use the mu2e job tools to divide large projects into many separate jobs, and how to
kinds of art jobs, and how to use the mu2e job tools to divide large projects into many separate jobs, and how to
run those jobs in parallel on Fermigrid or the OSG (open science grid).
run those jobs in parallel on Fermigrid or the OSG (open science grid).

Revision as of 00:00, 30 May 2019

Tutorial Session Goal

In this Tutorial you will learn how to run the Mu2e 'art' framework executable (mu2e), both interactively and on the grid.

Session Prerequisites and Advance Preparation

Session Introduction

Art is a software framework for running modular code with lots of run-time configurability. Art is controlled by scripts in a dedicated configuration language called fhicl (.fcl suffix).

This tutorial will cover how to build and run several different kinds of art jobs, and how to use the mu2e job tools to divide large projects into many separate jobs, and how to run those jobs in parallel on Fermigrid or the OSG (open science grid).

Exercises

NB: these are just suggestions, please add/remove/edit as you see fit. Link these to actual exercises

  • run the mu2e executable directly from the release in the tutorial container
  • create a satellite release on top of the tutorial release
  • edit some configuration in your satellite to change the art behavior: debug-config, print, etc
  • create a partial-checkout release of a single package from Offline
    • compile and link the package and rerun the mu2e app
  • Explore the JobConfig scripts for various kinds of mu2e production jobs
  • Run some simple production jobs
    • Primary Particle generation and simulation
    • Mixing
    • reconstruction
  • setup and run generateFcl to prepare for grid running
  • run mu2eProdSys --dryrun

Reference Materials

  • art workbook
  • various DocDBs that reference production, satellite release, partial checkout, etc.