Aggregate 2017 changes to herschel operations code

Updates to Herschel operations analysis code and scripts to

• move from 2017 to 2018 default paths
• tweak some minor analysis options (fit ranges, styles etc)
• simplify the delay scan working-point selection code
• add bxid monitoring to online monitoring task

added 1 commit

• 43cda63d - Tolerate unexpected BXIDs in the data if explicitly allowed (e.g. the case where…

Compare with previous version

• [2018-04-18 19:15] Validation started with lhcb-gaudi-merge#490
• [2018-04-19 00:12] Validation started with lhcb-lcg-dev3#499
• [2018-04-19 00:14] Validation started with lhcb-clang-test#925
• [2018-04-19 00:15] Validation started with lhcb-lcg-dev4#499
• [2018-04-19 00:16] Validation started with lhcb-tdr-test#124
• [2018-04-19 00:17] Validation started with lhcb-gaudi-head-py3#128
• [2018-04-19 00:17] Validation started with lhcb-head#1823
• [2018-04-19 00:17] Validation started with lhcb-gaudi-head#1840
• [2018-04-19 08:24] Validation started with lhcb-gaudi-merge#491
• [2018-04-20 00:08] Validation started with lhcb-moore-test#32
• [2018-04-20 00:10] Validation started with lhcb-2018-patches#188

added 1 commit

• 88ee6127 - bugfix in delay scan code to allow tail and head bb bxids to be the same in the…

Compare with previous version

changed the description

changed target branch from master to 2018-patches

@johndan I think you had put this in the wrong branch, as we won't need Herschel in the upgrade, but we do need it in 2018... I have changed the target branch from master to 2018-patches, please check that it remains as expected

Please note that a release on 2018-patches has just been done. The next one is not yet scheduled....

Thanks @cattanem . How does one know which branch is upgrade and which is 2018? Perhaps you could add a readme file in the repo explaining the names of the branches? (just a thought - perhaps it's only me who gets a bit lost)

Otherwise, this is totally fine. No problem that the release is out - this just needed to be committed somewhere central.

This was all discussed in my LHCb week plenary talk... https://indico.cern.ch/event/705559/contributions/2898607/attachments/1611344/2558732/Run2_software.pdf

It's a fair point about the readme, but I think things will become more obvious very soon, when we stop maintaining upgrade software in the run2 patches branches and run1/run2 software in the master branch.

Thanks for the pointers, Marco.

merged

mentioned in commit 13931b60