Skip to content

Do not try to unpack Turbo for non-Turbo jobs

Alex Pearce requested to merge apearce-accidental-turbo-unpacking into 2018-patches

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.

Merge request reports