Updates to VrtSecInclusive to prevent timeout errors
The VrtSecInclusive algorithm performs secondary vertex finding in the reconstruction step, but has recently been scheduled to be re-run in the SUSY15 derivation step as well (see merge request !31432 (merged)). When testing the new SUSY15 derivation step with secondary vertexing, we encountered problems with timeout errors, where an event takes longer than 1 hour to process, causing the derivation job to fail. This is caused by the vertexing step, which sometimes takes very long to run, especially in signal MC events with displaced decays of massive particles.
At the beginning of the vertexing step, a list of all possible combinations of tracks which are compatible to form a secondary vertex are compiled into a "work vertices container". In rare cases, the vertexing step finds several thousand working vertices, and it is these events which cause timeout errors. To prevent timeout, the work vertices container is truncated if more than a certain number (default: 1500) of working vertices are found at the beginning of the vertexing step. This has been shown to allow all events tested to finish well before the 1 hour mark.
A decoration to the event info has been added, which indicates if this truncation, or a failure in the VrtSecInclusive algorithm, has occurred.