Module Writing Tutorial: Difference between revisions
Jump to navigation
Jump to search
Line 4: | Line 4: | ||
== Session Prerequisites and Advance Preparation == | == Session Prerequisites and Advance Preparation == | ||
This tutorial | This tutorial requires the user to: | ||
* Perform the [[ Mu2e_Offline_Tutorial | Tutorial on setting up the Mu2e Offline ]] | |||
* Perform the [[ Running_Art_Tutorial | tutorial on running Mu2e art Framework jobs ]] | |||
* Perform the tutorial on running Mu2e art Framework jobs | |||
* Install the following docker containers () | * Install the following docker containers () | ||
== Session Introduction == | == Session Introduction == | ||
* Plan on spending 5 minutes in the beginning making sure everyone has fulfilled the prerequisites and has performed the advance preparation. | * Plan on spending 5 minutes in the beginning making sure everyone has fulfilled the prerequisites and has performed the advance preparation. |
Revision as of 23:51, 23 May 2019
Tutorial Session Goal
This tutorial will show how to write an art module for Mu2e. It will explain how to structure the code, define runtime parameters, produce histograms and/or TTrees, and consume and produce data products.
Session Prerequisites and Advance Preparation
This tutorial requires the user to:
- Perform the Tutorial on setting up the Mu2e Offline
- Perform the tutorial on running Mu2e art Framework jobs
- Install the following docker containers ()
Session Introduction
- Plan on spending 5 minutes in the beginning making sure everyone has fulfilled the prerequisites and has performed the advance preparation.
- If necessary, present a brief (~5 minutes) overview on goals, background information, and context. Make sure to link the slides to the session page.
Exercises
The majority of the session time should be spent performing exercises, which you link or embed in the session page.
- Each exercise should have a title; ie Create a histogram of the reconstructed Ce momentum
- Exercises may be chained (ie the output of the first is used as input to the next), but in that case make sure the output is also part of the downloads, so people who failed at step 1 can continue with the subsequent steps. Design this so that a failed step 1 does not overwrite the downloaded file that is the input to step 2.
- Some steps may take considerable processing time. In that case, have your attendees perform a short version (ie process 10 events), and provide the full output (ie histograms from 10^5 events) as part of the session download for subsequent steps.
- Each exercise should take between 5 and 15 minutes to complete. Count on your attendees taking twice as much time as would an experienced person.
- Start each exercise by bringing the exercise up on the main screen and going through its intro.
- Perform each step of the exercise on the screen, describing any decisions or issues involved as you do it. Check with your audience to make sure most (preferably all) have finished each step before going on to the next. If someone seems stuck, assign a session helper to help them individually and move on.
- It's OK to provide more exercises than most people will complete during the tutorial; they can be completed as homework.
Session Organization Guideline
- Encourage your attendees to ask questions if they are unsure what to do.
- You may or may not have session helpers, who have already performed the tutorial
- If someone finishes a step or exercise early, have them look around for neighbors that need help.
- If someone is stuck, have them raise their hand to get help.
Reference Materials
- Use this place to add inks to reference materials.