Run 2 trigger changelog

This page tries to collect the key changes that occurred in the L0, HLT1, and HLT2 systems throughout Run 2 that may be particularly relevant for analysts. It is currently very far from being comprehensive. The ultimate authority is always the contents of the TCK.




Track and TwoTrack lines

The Hlt1TrackMVA and Hlt1TwoTrackMVA lines ran all year with no prescale but with two different configurations (sets of cuts).

In the nominal TCKs, the selections were considered ‘tight’. A set of ‘loose’ TCKs relaxed some MVA parameters, and have Loose in their names.

The HLT1 TCKs were changed according to the status of the disk buffer. If the simulations projected a ‘big enough’ chance of the buffer becoming full, the tight TCK was used. Otherwise, the loose TCK was used.

Note that more MagUp data than MagDown was taken with the tight TCK (and conversely, more MagDown than MagUp with the loose TCK) and so selection/detection asymmetries may not cancel fully when averaging MagUp and MagDown.

This setup changed in 2017.

Very loose Hlt1 TCKs beginning of 2016

0x11291603 ('Physics_pp_May2016', 'MOORE_v25r2', 'Hlt1, Physics_pp_May2016, 0x1603, 1200 colliding bunches, CEP hadron prescaled to 15%')
0x11291604 ('Physics_pp_May2016', 'MOORE_v25r2', 'Hlt1, Physics_pp_May2016, 0x1604, 1600 colliding bunches, CEP hadron prescaled to 3%')
0x11291605 ('Physics_pp_May2016', 'MOORE_v25r2', 'Hlt1, Physics_pp_May2016, 0x1605, 2000 colliding bunches, CEP hadron prescaled to 3%')
0x11321609 ('Physics_pp_June2016', 'MOORE_v25r3', 'Hlt1, Physics pp June 2016, 1715 bunches L0, with SumETPrev')

Tight Hlt1 TCKs Summer 2016

0x11351609 ('Physics_pp_LateJune2016', 'MOORE_v25r3', 'Hlt1, Physics pp Late June 2016, 1715 bunches L0, optimized speed and rate, LHCBPS-1569')
0x1137160e ('Physics_pp_July', 'MOORE_v25r4', 'Hlt1, Physics pp August 2016, 2000 bunches L0, JIRA-LHCBPS-1615')
0x11371609 ('Physics_pp_July', 'MOORE_v25r4', 'Hlt1, Physics pp August 2016, 1715 bunches L0, JIRA-LHCBPS-1615')
0x11341609 ('Physics_pp_MidJune2016', 'MOORE_v25r3', 'Hlt1, Physics pp Mid June 2016, 1715 bunches L0, reduced Hlt1 rate (LHCBPS-1558)')
0x11361609 ('Physics_pp_July2016', 'MOORE_v25r3', 'Hlt1, Physics pp Late June 2016, 1715 bunches L0, optimized speed and rate, incl LowMult, LHCBPS-1600')

Loose Hlt1 TCKs Autumn 2016

0x1138160f ('Physics_pp_Loose_August2016', 'MOORE_v25r4', 'Hlt1, Physics pp August 2016, 2036 bunches L0, loose Hlt1, JIRA-1621')
0x11381611 ('Physics_pp_Loose_August2016', 'MOORE_v25r4', 'Hlt1, Physics pp August 2016, 2036 bunches L0 (920 kHz), loose Hlt1, LBHLT-41')
0x11381612 ('Physics_pp_Loose_August2016', 'MOORE_v25r4', 'Hlt1, Physics pp August 2016, 2036 bunches L0 (920 kHz retuned), loose Hlt1, LBHLT-48')
0x1138160e ('Physics_pp_Loose_August2016', 'MOORE_v25r4', 'Hlt1, Physics pp August 2016, 2000 bunches L0, loose Hlt1, JIRA-1621')
0x11381609 ('Physics_pp_Loose_August2016', 'MOORE_v25r4', 'Hlt1, Physics pp August 2016, 2442 bunches L0, loose Hlt1, JIRA-1621')

2017 + 2018

Track and TwoTrack lines

In contrast to 2016, in 2017 two versions of each of the Hlt1TrackMVA and Hlt1TwoTrackMVA lines were run continually throughout the year.

The tight variations of the lines, Hlt1TrackMVATight and Hlt1TwoTrackMVATight, always run with the same configuration and prescale (of 1). The loose variants, Hlt1TrackMVA and Hlt1TwoTrackMVA, have a prescale that depends on the TCK.

The tight TCKs set the prescale of the loose lines to 0.01 and have Tight in their names. The prescale for the loose lines is 1 for nominal TCKs. The prescale for the Tight lines is always one.

Unlike in 2016, this means there are new trigger lines that analysts should consider when looking at the data, e.g. with TupleToolTISTOS.

Any HLT2 lines making requirements on the HLT1 Track lines were modified to accept both variants in 2017.

Note: the Tight TCKs were never used to take data in 2017 nor 2018.


A general selection misconfiguration issue affected the creation of refitted PVs for several Charm Turbo lines. More information is available on the TurboPVRefittingBug page.

2015 + 2017

AALLSAMEBPV functor bug

Some trigger lines, including the topological B lines, were affected by a bug in the AALLSAMEBPV functor. This can in principle affect all analyses.



CHARMSPEC stream prescaling

The CHARMSPEC stream is an output stream of Tesla, which processes the TURBO stream output of HLT2. CHARMSPEC contained lines that reconstruct abundantly-produced Cabibbo-favoured final states.

Because the data volume was so large in 2016, initially only a subset of the stream was made available on tape. This stream was called CHARMSPECPRESCALED. The full dataset was 'parked' on tape, and was called CHARMSPECPARKED. Sometime in 2017, enough disk space became available that a replica of the parked stream could be created on disk. The CHARMSPECPARKED stream contains all data collected by the CHARMSPEC lines in 2016. Analysts should use this stream if they wish to examine all the data.

HLT2 SelReports in Turbo stream

The HLT2 SelReports were discarded in Tesla, and so are not available for TIS/TOS'ing.

The motivation for this was to reduce the event size. Most of the time, TIS/TOS'ing HLT2 in the Turbo stream is not very useful as the selections that did not produce your Turbo candidate are orthogonal. One can not TIS/TOS on Stripping lines for the same reason.

Identical track objects in PersistReco

The PersistReco option for Turbo HLT2 lines was introduced in 2016, which saves the full HLT2 reconstruction in addition to the usual Turbo information (the candidate that fired the HLT2 line).

Due to an implementation detail, the LHCb::Track objects that are directly associated to Turbo candidates are saved in a separate location from the container that contains all Track objects. When performing a naive track overlap check, by comparing the track's key in its container, a Turbo candidate track and a PersistReco track can then pass the check despite being truly 'identical'. This can create problems offline, where performing Turbo+PersistReco combinatorics can result in the same track being used twice in a single candidate.

To work around this, a more robust overlap checking tool should be used, which compares the set of LHCbID objects associated to each track. One such tool is LoKi::CheckOverlap. A CombineParticles configuration using that tool looks like this:

combiner = CombineParticles(
    # ...

More details can be found in the corresponding JIRA task and merge request, LHCBPS-1537 and Phys!74.


HLT2 SelReports in Turbo stream

After being removed completely in 2016, the HLT2 SelReports were re-introduced for a specific subset of lines. The list is defined in a Tesla options file, copied here for reference:


Identical track objects in PersistReco

Unlike in 2016, LHCb::Track objects associated directly to Turbo candidates are now stored in the same container in the TES as PersistReco objects. This means the standard overlap check tool is sufficient for standard use cases. The LoKi::CheckOverlap tool can still be used if desired.

Missing RelatedInfo

The persistence of RelatedInfo, e.g. isolation variables, was missing in 2017. It was re-added in 2018 before data-taking began.

CaloHypo objects missing links to associated CaloClusters

CaloHypo objects and their related CaloCluster objects were persisted in 2017, but a bug caused the explicit link between the two to be lost, as described in LHCBPS-1842. This can affect some physics measurements that rely on the information from the CaloCluster objects.


AALLSAMEBPV functor bug

The bug was fixed before the beginning of 2018 data-taking.






Edit | Attach | Watch | Print version | History: r14 < r13 < r12 < r11 < r10 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r14 - 2021-01-06 - AlexPearce
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LHCb All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback