Mvesteri moore rate test signal mc
Moore_RateTest.py in PRConfig now has an "efficiency" mode. I added two qmtests
- Rerun L0 on an already jugged MC sample in the TestFileDB
- Run $PRCONFIGROOT/.../MooreRateTest.py with --mode="efficiency" using the output of the previous step as input Only asked to run over 500 events. Now we are in a better position to ask line authors to report their efficiencies. The nice thing is that the Moore_RateTest reports the inclusive and exclusive contributions to your efficiency from all Hlt lines.
Merge request reports
Activity
Validation started with lhcb-2016-patches#31
Validation started with lhcb-2016-patches#32
Validation started with lhcb-2016-patches#33
Validation started with lhcb-2016-patches#34
Added 1 commit:
- acd691a0 - Fix test prerequisite
Validation started with lhcb-2016-patches#35
Validation started with lhcb-2016-patches#36
@mvesteri, there seems to be a problem with the script, can you check? https://lhcb-archive.cern.ch/artifacts/nightly/lhcb-2016-patches/36/summaries.x86_64-slc6-gcc49-opt/Moore/html/index.html?test=all_results/moore0/rates1//mc_mooreratetest_eff
Validation started with lhcb-2016-patches#37
Validation started with lhcb-2016-patches#38
@rmatev, @raaij, Moore doesn't seem to like running with Simulation=True now, and complains that MonitorSequence doesn't exist. It seems to configure OK if you say Simulation=False, though obviously you fail later on due using data conditions with MC. Let's move this discussion to one of the JIRAs. I'm looking through HltConf in the mean time...
mentioned in commit daf51175
Mentioned in commit daf51175