End Cap Muon Log Warnings

[aloeliger]

What

Right now we are seeing very noisy output from end cap muon modules. The exact log info is:

%MSG-w L1T:  L1TMuonEndCapTrackProducer:simEmtfDigis 13-May-2023 11:29:10 CEST  Run: 366727 Event: 121426611
Found error in LCT quality: 0 (allowed range: 1-15).
%MSG
%MSG-w L1T:  L1TMuonEndCapTrackProducer:simEmtfDigis 13-May-2023 11:29:10 CEST  Run: 366727 Event: 121426611
From endcap 2, sector 3, station 2, ring 2, cscid 6. (Note that this LCT may be reported multiple times. See source code for explanations.)
%MSG
%MSG-w L1T:  L1TMuonEndCapTrackProducer:simEmtfDigis 13-May-2023 11:29:10 CEST  Run: 366727 Event: 121426611
Found error in LCT quality: 0 (allowed range: 1-15).
%MSG

These warnings originate here

After some discussion I understood this to be a muon unpacker issue with a fix in the works.

@eyigitba I figured I would tag you since we have discussed this.

Recipe to recreate

2023 data relvals apparently include this right now.

[eyigitba]

Hi @aloeliger , this is due to muon shower objects in EMTF DAQ. Currently our unpacker creates an LCT with quality 0 when we get a muon shower bit. This needs to be fixed. I'll submit a PR fixing unpacker for muon shower bits this week.

[aloeliger]

@eyigitba Any news on this?

[eyigitba]

I'll try to submit the PR today/tomorrow. I decided to include it as a part of a bigger PR involving muon showers in EMTF unpacker. The tests are all good, I need to check just one more thing.

[eyigitba]

Hi @aloeliger , 132X PR is here: cms-sw#41993

[aloeliger]

closed in cms-sw#41993