Mu2e Offline Tutorial: Difference between revisions

From Mu2eWiki
Jump to navigation Jump to search
Line 6: Line 6:
Look through the [[ComputingTutorials | Getting Started]] wiki page.  Not
Look through the [[ComputingTutorials | Getting Started]] wiki page.  Not
all of those links are live.
all of those links are live.
[[LoginTutorial]]
[[CodeArtFclTutorial]]
[[CheckoutAndBuildCodeTutorial]]


== Session Introduction ==
== Session Introduction ==

Revision as of 19:20, 17 June 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 Getting Started wiki page. Not all of those links are live. LoginTutorial CodeArtFclTutorial CheckoutAndBuildCodeTutorial

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
  • look at content in /cvmfs
  • look at the ReleaseList and the Tutorial Release Notes
  • run setup.sh for the tutorial release
    • locate the mu2e app
  • setup a satellite release
    • locate the mu2e
  • create a partial-checkout release of a single package from Offline
    • explore scons script
    • compile and link the package
  • experiment with .build_opts
  • look at setup.sh
  • run git
    • checkout a package
    • examine the history of a file
    • diff two versions of a file
  • log in to mu2egpvm* machine?
  • kinit? certificates? docdb?

Reference Materials

other wiki pages on Offline