jiafulow/cmssw

CMS Offline Software

cmssw's Issues

Add/Update interface to all the Phase-2 trigger primitives

The EMTF emulator needs to be upgraded to handle all the Phase-2 trigger primitives, including GEM, ME0, and iRPC. It's also nice to be able to handle DT/TwinMux. Majority of the work has been done during the development for Phase-2 EMTF++, and used for L1T Phase-2 Upgrade TDR studies. These changes are now being ported to the official CMSSW. For Run 3 specifically, the GE1/1 interface is needed to continue the rest of the EMTF-GEM integration.

There are a lot of changes because what's in the existing EMTF emulator related to GEM/ME0/iRPC is not correct/updated. Also, unused codes related to converting track trigger stubs into muon trigger primitives have been removed.

Sepcific tasks:

• Add interface to GEM
• Add interface to ME0
• Add interface to DT
• A lot of cleanup

Notes:

• The definition of Subsector() for EMTFHit converted from RPC hit has changed. It is now consistent with the CSC definition (1 or 2 in ME1, 0 in ME2,3,4). The old definition is no longer stored, but can be recovered via Subsector_RPC().
• GEM input is now GEMPadDigiClusterCollection.
• ME0 input is now ME0TriggerDigiCollection.
• Regarding input: access to simTwinMuxDigis, simDtTriggerPrimitiveDigis, rpcRecHits, me0TriggerConvertedPseudoDigis has been added, but none of them are turned on by default.
• Regarding output: no change. While the interface has been implemented, the rest of the track finder logic has not been updated to use the new trigger primitives.

Additional notes:

• No dependence on other PRs or externals.
  • This PR does not interfere with the recent EMTF PRs by Andrew that are related to UL2016 emulation bugs.
• The plan for EMTF emulator update is discussed here.

Add NN vertex-unconstrained pT assignment

K-BMTF has introduced the ability to trigger on displaced muons for Run 3. We would like to do the same with EMTF. A NN approach to find the vertex-unconstrained pT and transverse impact parameter d0 for a displaced muon has been ongoing.

Specific tasks:

• Implement the NN.
• Add to the output to GMT: vertex-unconstrained pT, transverse impact parameter d0.

Guard against changes from the trigger primitives

Changes in the trigger primitives (CSC/RPC/GEM/etc) might break the EMTF emulator. Things become more complicated with different CMSSW releases, eras (Run 2, Run 3, Phase 2, ...), geometries and pileup conditions. If something breaks, there's no way to easily tell "who" breaks the EMTF. Need some kind of RelVal for our own EMTF?

Adapt to upcoming changes in the CSC trigger primitives

For Run 3, CSC LCTs will be updated with new definitions for LCT position & bend. In addition, for ME1/1, the CSC-only LCTs will become GEM+CSC integrated-LCTs. The EMTF emulator needs to adapt to those changes.

Add interface to having more than 1 pT assignment modules

To be able to run the BDT pT assignment & NN vertex-unconstrained pT assignment at the same time, the EMTF emulator needs to have an interface that allows more than 1 pT assignment modules.

Specific tasks:

• Add the interface.

Include GE1/1 in the rest of track building algorithm

Currently, the interface to receive the GEM trigger primitives has been added. The rest of the track building algorithm has to be modified to include GE1/1. The first step is likely to match the GE1/1 pads to the ME1/1 LCTs, in order to form the GEM-CSC bend angle. This is similar to how the GEM+CSC integrated LCTs are built at the OTMB.

For reference, these are the tasks assigned by the GEM-CSC Trigger Task Force: https://indico.cern.ch/event/918652/ (see Minutes)

Ensure correct emulation for historical events

Some issues have been reported when using the EMTF emulator from the latest CMSSW release to run on old collision & MC simulation data, due to conflicts among global tags/O2O/python config. The emulator needs to ensure that (global tag, O2O, era, python config, CMSSW release)-combination gives consistent results.

Specific tasks:

• Implement EMTFSetup class used to carry "global" objects (such as VersionControl).
• Implement VersionControl class (detailed below).
• Also clean up the assert statements.

Update EMTF packer/unpacker

Changes in the EMTF input/output will require updates to the EMTF packer & unpacker