Update L0 monitoring

L0DU :

• reduce verbosity in L0DURawBank and L0DUReport monitoring
• better handling in case of different sources for the same L0ProcessorData in L0ProcessorDataDecoder L0Calo :
• fix minor bug (wrong format) in L0Candidate.h when building L0Processor data for SpdMult and SumEt from the L0Calo rawBank. The bug has no impact on default processing as L0ProcessorData are not build from the L0Calo rawbank but directly from the emulator.
• L0CaloCandidatesFromRaw : produce (empty) L0ProcessorData in case there is no corresponding L0 candidate + add the possibility to plug/unplug processor data 'fiber' (e.g. for L0pi0s/HC switching)

@deschamp could you please elaborate a bit on this MR? Where in the 2018 data taking software will this run?

This update is ransparent for normal usage. This is just needed for monitoring purpose online. I'll commit an update asap with the changes suggested above

added 1 commit

• b4ec45f9 - 'minor update'

Compare with previous version

changed title from 'Update L0 monitoring' to Update L0 monitoring

• [2018-05-26 00:02] Validation started with lhcb-g4r103#368
• [2018-05-26 00:03] Validation started with lhcb-gauss-dev#1651
• [2018-05-26 00:05] Validation started with lhcb-moore-test#68
• [2018-05-26 00:09] Validation started with lhcb-2018-patches#224

added 1 commit

• 5b5b28cd - Update L0ProcessorDataDecoder.cpp to remove spurious white space changes

Compare with previous version

resolved all discussions

merged

mentioned in commit 405291fb

I will cherry-pick this also to run2-patches. But not to master, as L0 will not exist in Run 3...

mentioned in commit 0fd6172f

mentioned in merge request !1342 (merged)

I could not guess that from the minimal information given in the merge request title and non existent description. Please add a description along the lines above, I will then cherrypick to master

sorry I didn't realize the description was gone. It happens when I fill the description and then 'change branch' to select the 2018-patches (I always have master as default destination branch even when I push a local installation from another branch). I restored the original description.

changed the description

Unfortunately cherry pick of this to master does not work trivially. Can you please submit a separate MR?

OK, I'll do it asap

done (!1343 (merged))

mentioned in merge request !1343 (merged)