Selective saving of Hlt2SelReports in Tesla

An extra property InputHlt2RepsToKeep is added to Tesla, which if set together with KillInputHlt2Reps = True, allows to keep some of the Hlt2SelReports.

Closes LBHLT-75

WIP as I didn't even run Tesla or any test. I will probably add a test.

I can do a more detail review later, but how about only having the InputHlt2RepsToKeep property, with a default value of []?

unmarked as a Work In Progress

This is just so we can distinguish between "keep all selreports", "keep only some selreports", "kill all selreports".

added 19 commits

• 4da82baa - Draft configuration of Tesla with selective persistence.
• 7e40c0a4 - Decode and persist RecSummary.
• 3d5dee31 - Use stream-specific packers to avoid configuration clash.
• 78521014 - Require algorithm passes when writing outputs.
• c4ee977a - Remove some old configuration.
• d7ea7aaa - Move imports to the top of the file.
• 7f3895c2 - Move per-stream configuration to a method.
• da59555c - Support a single anonymous stream (AKA 'no streaming').
• c0f1578e - Import DecoderDB only when used.
• b2c947f5 - More general configuration of persistence service.
• 0a54c5af - Clean up some logic.
• 241408b5 - Add TeslaLineChecker to TurboSP configuration.
• ce9c61eb - Allow for 2016-style Tesla configuration on 2017 data.
• 5a642357 - Add DaVinci().Turbo flag.
• 362cfae4 - Use new TurboConf slots to run only what we need.
• 4d56dec4 - Always save DAQ/RawEvent.
• fa039702 - Don't run the HLT1 vertex decoder if not needed.
• 2567b82e - Remove the DstData bank from the output.
• 446e1d45 - Implement selective saving of Hlt2SelReports in Tesla

Compare with previous version

Rebased on top of !66 (merged), such that there is no merge conflict. !66 (merged) has to be merged first

assigned to @erodrigu

• [2017-06-12 00:07] Validation started with lhcb-old-stripping-tests#432
• [2017-06-12 00:12] Validation started with lhcb-2017-patches#45
• [2017-06-12 00:13] Validation started with lhcb-head#1503
• [2017-06-12 00:14] Validation started with lhcb-lcg-dev3#187
• [2017-06-12 00:14] Validation started with lhcb-gaudi-head-noavx2#18
• [2017-06-12 00:14] Validation started with lhcb-lcg-dev4#187
• [2017-06-12 00:14] Validation started with lhcb-gaudi-head#1500
• [2017-06-12 00:14] Validation started with lhcb-turbosp#31
• [2017-06-12 00:15] Validation started with lhcb-clang-test#610
• [2017-06-12 00:15] Validation started with lhcb-gaudi-head-noavx#37

mentioned in merge request !66 (merged)

@rmatev Will this also go to the 2017-patches branch or not? If not I can for sure accept this now.

yes, this should definitely go to the 2017 branch, together with !66 (merged) and !70 (merged). I didn't see the branch yesterday, so I presume you'll create it after the release.

Indeed. (Oops, where's my brain for having forgotten that I am still to create the branch after the stack is released!)

merged

mentioned in commit 41847f68