Analysis Code » History » Version 5
George, Melissa, 28 October 2015 15:43
1 | 1 | George, Melissa | h1. Analysis Code |
---|---|---|---|
2 | |||
3 | 4 | George, Melissa | Please put any code that you have written to perform analysis and reconstruction tasks plots etc into the tabel 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 | |_.Code |_.Language |_.Description |_. date | |
||
8 | |blah.py |Python |What it does | 12/12/99 | |
||
9 | | | | | | |
||
10 | |||
11 | h2. Final Script Development |
||
12 | |||
13 | |_.Code |_.Language |_.Description |_. date | |
||
14 | 5 | George, Melissa | | Calibration.py | Python | Claibration Script to be run once per shift and checked by experts |
15 | 1 | George, Melissa | to check the calibrations are valid | 28/10/15 | |
16 | | ReconstructionPlots.py |Python | Python Script (or eventually an Analysis Package)of Reconstruction Plots | 28/10/15 | |
||
17 | 5 | George, Melissa | | DataValidation.py | Python | Script to be run once per run and checked by shifters to check the |
18 | validity of the data and that the calibrations are valid. Then a final |
||
19 | line that based on those checks and tolerances says whether the run is |
||
20 | good for the tracker or not. In Physics Devel | 28/10/15 | |