G4MICE’s DataQualityCheck application G4MICE’s DataQualityCheck application: Preliminary thoughts Mark Rayner 23 rd February 2010

G4MICE’s DataQualityCheck application Introduction  The DataQualityCheck application  May be run online on the live data feed in the control room  May be run offline on a MICE dataset  Produces standardized format histograms  Painted to the screen  Saved on the GRID for posterity  Per run  Per MICE dataset  The aim is to standardize procedures  For validating and summarizing data  Early in the life of the experiment  And in anticipation of the requirements of GRID storage  Goal  Analyze and present data in an explicitely consistent way

G4MICE’s DataQualityCheck application How might we define a MICE dataset?  A collection of runs which may be analyzed consistently as a single dataset  Contains reconstructed kinematic data  Detector experts’ expertise has already been added  After selection of ‘good’ muons  Expected to be constant within a MICE dataset:  Geometry  Hardware settings (magnet currents, etc)  Cabling  Calibration  Version of G4MICE used to perform the reconstruction and analysis  For example, two separate MICE datasets may analyze the same set of runs, but be reconstructed using a different version of G4MICE, or set of calibrations

G4MICE’s DataQualityCheck application Coding convention  DataQualityCheck application  Required to analyze a wide variety of data  Long lived  A large number of people will contribute  However it’s parameters of operation are well defined  Coding convention  Delimit responsibility for maintaining the various portions of code:  DataQualityCheck.cc  Maintained by person X  Code which creates individual plots per detector  Written by detector experts  Located in a single file per detector plot  Formatted in a clear, pre-determined way  Person X  Doesn’t need to understand how the plotting code works  Simply calls the Process(), Plot(), and Write() functions as desired

G4MICE’s DataQualityCheck application Code for a the standardized detector plots DataQualityPlot public: virtual Process()=0 virtual Plot()=0 virtual Write()=0 private: 1 canvas, output file, &MICEEvent, &MICERun TemplatePlotClass public: Process() Plot() Write() private: histograms, graphs… TofMonitor Written by TOF experts CkovMonitor Written by CKOV experts etc… Add an event’s data to the histograms etc Paint fresh histograms to the screen Write final plots to the output file

G4MICE’s DataQualityCheck application The event loop  Code snippet from DataQualityPlot.cc  The hardcoded true needs careful thought!

G4MICE’s DataQualityCheck application Final thoughts  Ultimately, the user may analyze ZustandVektors  High level kinematic data from ‘good’ muons  However the trackers may not be fully operational for a year or so  An intermediate solution is required  And we need to learn how to decide which muons are ‘good’  DataQualityCheck can help us learn this  Documentation  An evolving draft of a web page is in the G4MICE CVS repository  $MICESRC/Applications/DataQualityCheck/OnOffApps.html  Everyone is encouraged to contribute their ideas to this  Contains:  Checklist of required plots  Preliminary thoughts on what consititutes a dataset  An explanation of the coding convention

G4MICE’s DataQualityCheck application