Документ взят из кэша поисковой машины. Адрес оригинального документа : http://antares.sinp.msu.ru/docs/highQC_2011_Bamberg.pdf Дата изменения: Mon Dec 16 17:03:28 2013 Дата индексирования: Thu Feb 27 20:24:35 2014 Кодировка:

High level DQ control
Vladimir Kulikovskiy


Data/MC 3N trigger only.
· The same plot as in Colas presentaAon, but only for 3N trigger. · NB the 20% correcAon for 5 line data


Data/MC 3N trigger only.
· Colas presentaAon ­ raAo seems to be different for different trigger setups. · Should we separate the events by trigger? · 3N trigger selecAon of events · Other trigger selecAons? · New DQ parameter? =8.8%

=3.8%

=5.9%


A Seatray module.
· Wiki >Data >Quality Assessment (boYom) · It's a SeaTray module (antares qa used as a base) to be added in future to the producAon chain. · It has a root file output with plots (1D, 2D histograms, graphs) and ntuple (one raw ­ runnumber and quality parameters). · There are also a root files for each run with data and plotgraphs.py which creates all the gif plots.


Aafit charge sigma

aachargesigma AafitChargePerOM RMS / MEAN * 100%


Residual

Residual ­ Ame(ns) difference between real hit Ame and expected hit Ame from Aafit reconstructed track. Only hits, used in the ImPDF Aafit were used (since all Calibrated pulses aren't reachable in the last producAon i3 files)


AXY

AXY an angle (rad) between photons and OMs (photon direcAon is obtained from Aafit reconstructed track)


plambda

plambda maximum bin X of Lambda distribuAon (the most probable value)


Summary
· All cumulaAve distribuAons look rather stable in Ame. · Do analysis for all runs. · Design some quality cut and check it together with QB cuts, ExpectedMuonPerMin ExpectedMuonPerMin cut, 3N data/mc cut..