Analysis Code » History » Revision 15
Revision 14 (Dobbs, Adam, 29 October 2015 17:20) → Revision 15/19 (Overton, Edward, 02 November 2015 13:56)
h1. Analysis Code 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. h2. Useful Code |_.Code |_.Language |_.Description |_. date |_.name | |blah.py |Python |What it does | 12/12/99 | nameX | | | | | | nameY | h2. Final Script Development OnRec and OnMon are visible through MAUS directly |_.Code |_.Language |_.Description |_. date | | https://github.com/e-overton/mice-tracker-calibration Calibration.py | Python | Calibration Script / Tools to be run once per shift and checked by experts. TODO: Automatic (shifter) running. experts to check the calibrations are valid |28/10/15 | | attachment:ReconstructionPlots.py |Python | Python Script (or eventually an Analysis Package)of Reconstruction Plots |28/10/15 | | DataValidation.py | Python | Script to be run once per run and checked by shifters to check the validity of the data and that the calibrations are valid. Then a final line that based on those checks and tolerances says whether the run is good for the tracker or not. In Physics Devel. |28/10/15 | | 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 |