DQM activities
to be done
to be done (not a priority)
done
25/02/2015
DQM in Run 2
Status
DAQ
shifter and non shifter agents for the DAQ module
- the non-shifter agents publish everything and we could just use for the shifter
- layout can be changed:
DAQ_PHYSICS_1 instead of DAQshifter_PHYSICS_1
DAQTime_PHYSICS_1 instead of DAQshifterTime_PH_2
 to be done (Daniele)
- shifter agents could be marked as not production
 to be done (Daniele)
eventSizeClusters
- remove from instructions (now it is an expert plot)
 to be done (Daniele)
PHOS
- from AliRoot QA framework to custom module  expert working on it
CPV
- custom module  work will start soon by the expert
- nominal event size thresholds set  DONE
- agent CPV_DA publishing in AMORE histos retrieved by the DA (only for experts?)  DONE
25/02/2015
DQM in Run 2
Status
TOF
- TOFQAshifter agent keeps adding paves to the histograms  will be fixed by expert
AD
- available in DQM when AliRoot v5.06 will be installed and quality of the code confirmed
 to be done (Barth and AD expert)
ZDC
- amoreZDC01 1.27 released  DONE
SSD
- SSD01 default source changed from @gdc-GLOBAL-04 to ^SSD  DONE
TRI
- amoreTRI: issues likely not related to probems with AliRawReaderDate and AliRawReaderRoot
 expert working on it
- expert will change after this fix (Marek Bombara)
25/02/2015
DQM in Run 2
Status
General
- using cosmic configuration for DAQ agents (eventSizeCosmic.config)  DONE
- quality flags: make them coherent with quality of the plots)  to be done by experts
space on device
- AMORE database stuck: no space left on device (SDD01 produces 1000 histograms)
- all histograms in SDD01 needed: for half of them no need to archive them at high
frequency (maybe no need to archive them at all)
- implement a protection against this case in AMORE: for example the archiver could
identify this case and remove the archives earlier than a week after creation  DONE
- add a panel to the amoreEditDb to be able to identify easily this type of problems: for
example by showing the size of every table and the space left on disk  to be done (Barth)
- possibility (proposed by SDD expert) to assign a parameter that describes “if” &/or “how
frequently” &/or "how long” published objects should be stored in the DB  to be done (Barth)
(think how to do it: in particular, an option not to archive at SOR could be provided)
ED
- display cosmics  DONE
- crash when including Muon Arm (Run 1): fixed for geometry, to be checked for reconstruction
25/02/2015
DQM in Run 2