ATR-17404, adding EF to bphysics chains
Adding EF muons + dimuon hypothesis for EF combined muons on top of existing bphys chains. Seems to work ok out of the box.
- block of code for muons added to TrigBphysHypo/TrigMultiTrkHypoMT.cxx to get tracks+decisions map for muons (as opposed to L2 tracks).
- few configuration variables added to specify muon container and whether the hypo should vertex track, muons, etc. (int for now - would like to adapt to string->enum or something more user-friendly later)
- dimuEFSequence added to BphysicsSequenceSetup
- reference updated for the bphysics slice - but not for full menu, because there were other differences that I suspect someone else will make a MR today for, and I don't want to cause a conflict.
ctests all pass, and from TrigUpgradeTest:
INFO 24 tests succeeded out of 33 executed
ERROR ==================================================
ERROR The following 9 tests failed:
ERROR test_trigUpgr_met_fromJets_build.sh
ERROR test_trigUpgr_slice_bphysics_build.sh
ERROR test_trigUpgr_slice_mu_mc_build.sh
ERROR test_trigUpgr_met_fromCells_build.sh
ERROR test_trigUpgr_met_fromClustersPufit_build.sh
ERROR test_trigUpgr_full_menu_build.sh
ERROR test_trigUpgr_met_fromClusters_build.sh
ERROR test_trigUpgr_slice_bjet_build.sh
ERROR test_trigUpgr_bjet_menu_ALLTE_build.sh
ERROR ==================================================
and all but bphysics and menu also had the same regtest differences in the nightly (http://atlas-computing.web.cern.ch/atlas-computing/links/distDirectory/gitwww/GITWebArea/nightlies/master/2019-05-28T2128/Athena/x86_64-slc6-gcc8-opt/Athena/art.log.html), so I think I can say this is ok.
cheers, Heather
Edited by Heather Russell