Mu2e Offline Tutorial: Difference between revisions
Jump to navigation
Jump to search
Line 4: | Line 4: | ||
== Session Prerequisites and Advance Preparation == | == Session Prerequisites and Advance Preparation == | ||
Look through the [ComputingTutorials Getting Started] wiki page. Not | |||
all of those links are live. | |||
== Session Introduction == | == Session Introduction == | ||
Mu2e Offline is a collection of code and scripts used for simulation, reconstruction and analysis of Mu2e data. | Mu2e Offline is a collection of code and scripts used for simulation, reconstruction and analysis of Mu2e data. |
Revision as of 14:36, 31 May 2019
Tutorial Session Goal
This tutorial will show you how to work within the Mu2e Offline computing environment.
Session Prerequisites and Advance Preparation
Look through the [ComputingTutorials Getting Started] wiki page. Not all of those links are live.
Session Introduction
Mu2e Offline is a collection of code and scripts used for simulation, reconstruction and analysis of Mu2e data. 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. to link the slides to the session page. This tutorial will cover the basic structure of Offline, and show you how to create the local environment to work with Offline.
Exercises
- make sure everyone has a working install of docker and has downloaded the necessary containers
- Maybe we can use a loaner computer for people having problems?
- test docker using some standard containers (helloworld, bash, ...)
- start an interactive docker session using the tutorial container, and explore the structure of Offline
- Examine the directory tree and substructure
- Look at the different kinds of source files: .cc, .inc, .fcl, _module.cc
- Search for content (data products) in RecoDataProducts, MCDataProducts, etc
- Search for algorithms (modules) that (say) build tracks, find clusters, identify background ,...
- setup a satellite release (or partial checkout?)
- explore scons script and run a simple build
- experiment with .build_opts
- look at content in /cvmfs
- look at setup.sh
- log in to mu2egpvm* machine?
- kinit? certificates? docdb?
Reference Materials
other wiki pages on Offline