Do not try to unpack Turbo for non-Turbo jobs

This addresses some problems reported on the mailing list about crashes related to Turbo unpacking.

The issue was that Turbo unpacking was being triggered by an MC relations algorithm looking up Turbo locations by default, which the ParticlesToVerticesMapper tries to provide for. The unpacking fails because the job is not configured to process Turbo data (the RootInTES is incorrect).

This MR modifies ParticlesToVerticesMapper so that one can configure a list of streams to ignore, e.g. /Event/Turbo, under which the mapper will not try to unpack data. I've also modified DstConf to configure the mapper.

This fix should be also ported to 2017-patches.

Thanks, does this patch apply to all years of data taking or is it only needed for 2017+ MC?

assigned to @jonrob

It's needed for running over any MC sample which contains Turbo information, when the job isn't configured as a Turbo job.

resolved all discussions

added 1 commit

• fe7aac35 - Append in case the value has been set already.

Compare with previous version

• [2018-02-21 00:06] Validation started with lhcb-2018-patches#123

merged

mentioned in commit 8806441e

mentioned in commit a32d9ec0

mentioned in merge request !1141 (merged)

mentioned in merge request !1142 (merged)

mentioned in commit bbf0ef2f

mentioned in commit 97bc6722

mentioned in commit 833433c9

mentioned in merge request !1343 (merged)