Analysis Code » History » Version 16
Overton, Edward, 02 November 2015 13:56
1 | 1 | George, Melissa | h1. Analysis Code |
---|---|---|---|
2 | |||
3 | 9 | George, Melissa | Please put any code that you have written to perform analysis and reconstruction tasks plots etc into the table below along with a description of what it does and how and the language it is written in. |
4 | 1 | George, Melissa | |
5 | 4 | George, Melissa | h2. Useful Code |
6 | |||
7 | 9 | George, Melissa | |_.Code |_.Language |_.Description |_. date |_.name | |
8 | 7 | George, Melissa | |blah.py |Python |What it does | 12/12/99 | nameX | |
9 | | | | | | nameY | |
||
10 | 4 | George, Melissa | |
11 | h2. Final Script Development |
||
12 | |||
13 | 6 | George, Melissa | OnRec and OnMon are visible through MAUS directly |
14 | |||
15 | 12 | George, Melissa | |_.Code |_.Language |_.Description |_. date | |
16 | 16 | Overton, Edward | | https://github.com/e-overton/mice-tracker-calibration | Python | Calibration Script / Tools to be run and checked by experts. TODO: Automatic (shifter) running. |28/10/15 | |
17 | 13 | George, Melissa | | attachment:ReconstructionPlots.py |Python | Python Script (or eventually an Analysis Package)of Reconstruction Plots |28/10/15 | |
18 | 12 | George, Melissa | | DataValidation.py | Python | Script to be run once per run and checked by shifters to check the |
19 | validity of the data and that the calibrations are valid. Then a final |
||
20 | line that based on those checks and tolerances says whether the run is |
||
21 | good for the tracker or not. In Physics Devel. |28/10/15 | |
||
22 | 14 | Dobbs, Adam | | attachment:scifi_run_summary_plots.py | Python | Python script producing various data quality plots, takes a maus_output.root file as an argument |29/10/15 | |