Tests for reco sequence with muon matching

Tests setting up the hlt1 reco sequence with muon matching

• only the .ref.x86_64-opt files are valid, the others have to be updated (- the mc-checking part contains a gentle hack because "MuonMatch" tracks are not valid for the PrChecker yet)

added hlt1 reconstruction [DEPRECATED] ~1664 labels

changed milestone to %v50r1 (HLT1 showcase)

assigned to @apearce

added 1 deleted label

assigned to @cprouve

added 1 commit

• 2f6e29b5 - replacing hack by using same principle as for standalone_hlt2_reco + applying...

Compare with previous version

added 1 commit

• 060d1913 - Fixed formatting

Compare with previous version

unassigned @cprouve

resolved all threads

• [2019-10-29 00:12] Validation started with lhcb-head#2413
• [2019-10-30 00:08] Validation started with lhcb-gaudi-head-py3#215
• [2019-10-30 00:08] Validation started with lhcb-test-throughput2#198
• [2019-10-30 00:09] Validation started with lhcb-sanitizers#416
• [2019-10-30 00:11] Validation started with lhcb-lcg-dev3#1067
• [2019-10-30 00:12] Validation started with lhcb-tdr-test#719
• [2019-10-30 00:13] Validation started with lhcb-head#2414
• [2019-10-30 00:13] Validation started with lhcb-gaudi-head#2434
• [2019-10-30 00:16] Validation started with lhcb-lcg-dev4#1078
• [2019-10-31 00:08] Validation started with lhcb-gaudi-head-py3#216
• [2019-10-31 00:09] Validation started with lhcb-sanitizers#417
• [2019-10-31 00:09] Validation started with lhcb-test-throughput2#199
• [2019-10-31 00:09] Validation started with lhcb-gaudi-head#2435
• [2019-10-31 00:10] Validation started with lhcb-tdr-test#720
• [2019-10-31 00:11] Validation started with lhcb-lcg-dev3#1068
• [2019-10-31 00:15] Validation started with lhcb-head#2415
• [2019-10-31 00:17] Validation started with lhcb-lcg-dev4#1079

I think all the non-opt tests have now completed, so you should be able to grab the references now @cprouve.

The differences look pretty large to me though, e.g. in the dbg build (looking at the "CountersMismatch" field):

    (SciFiTrackForwarding ref) Search S1UV | 53
    (SciFiTrackForwarding new) Search S1UV | 180
    (SciFiTrackForwarding ref) Created long tracks | 935 | 47 | 0.050267
    (SciFiTrackForwarding new) Created long tracks | 935 | 138 | 0.14759
    (SciFiTrackForwarding ref) Search S2 UV | 76
    (SciFiTrackForwarding new) Search S2 UV | 248
    (SciFiTrackForwarding ref) Search S3UV | 411
    (SciFiTrackForwarding new) Search S3UV | 1337
    (SciFiTrackForwarding ref) Accepted input tracks | 71
    (SciFiTrackForwarding new) Accepted input tracks | 240
    (SciFiTrackForwarding ref) Search S1 | 93
    (SciFiTrackForwarding new) Search S1 | 293
    (SciFiTrackForwarding ref) Search S2 | 251
    (SciFiTrackForwarding new) Search S2 | 835
    (SciFiTrackForwarding ref) Search S3 | 2166
    (SciFiTrackForwarding new) Search S3 | 7546

Are such big differences expected?

When I moved the velo_track_min_ip parameter into the standalone_hlt1_muonmatching_reco method I changed it's default value. I assume the difference is from there. Sorry.

resolved all threads

added 1 commit

• 120dfb91 - updated references

Compare with previous version

Thanks! Let's run for one more night

added all-slots label and removed 1 deleted label

added 1 commit

• a0206b96 - update reference files

Compare with previous version

mentioned in merge request !285 (merged)