venturia / cmssw Goto Github PK

All the new code for 94x should be backported to 92x, too

Describe the EDAnalyzer which creates the profiles of the pixel module occupancy

The list of sources of the fill number should be reviewed. There should be a way to get the fill number event by event. In this case I have to add a method to update the fill number event by event in the RunHistogramManager class. I have to prepare the code not to use the information if it is not valid and use the previous source. Very likely I will first check the information per run and then per event. In case of inconsistency I have to define which has the priority and in case of invalid information I have to use the valid one.
The pieces of code which use RunHistogramManager to fill "per fill" histograms will have to be modified to update the fill number event by event
Finally the impact on the timing has to be checked

TCDS is recording both the history of the previous L1As and the orbit number when the B-GO signals have been issued for the last time. The code in DPGAnalysis/SiStripTools have to be modified to use these new data formats (still to be defined) and ad hoc code to compare SCAL and TCDS on large statistics have to be written

Define a histogram (TProfile) with the average event number vs the orbit number. With a macro it should be possible to create an histogram with the average L1 rate vs the orbit number

Some of the occupancy plots are presently only per fill. They have to be duplicated and make them also per run and controlled with a sensible configuration parameter.
Existing configuration fragments should be updated to use the new configuration parameter if the one used to fill the "per fill" histograms changes its name (likely to happen)

New code has to be backported in 80x and 5xy for old Run 1 and Run 2 data analyses