Understand Issues Related to Legacy DTTF Trigger Primitive Re-Emulation

[mulhearn]

To encounter the problem, please follow recipe here:

#101

But use this config instead:

/afs/cern.ch/user/m/mulhearn/public/debug/dttf_debug.py

You should see immediately the message:

[DTTrigProd] CCB configuration is not valid for this run, empty
collection will be produced

[mulhearn]

We are having trouble using the legacy re-Emulation of DTTF as the initial stage in the BMTF emulation. The work-around we are using at the moment is to use the unpacked DTTF data instead:

3898f53

But this will no longer work when DTTF payload is no longer in RAW data. Fix is in the works.

[mulhearn]

Related: Giannis is working on removing the sector collector code from legacy DTTF emulator, as this is no longer present in the actual hardware since the commissioning of the TwinMux.

[mulhearn]

Note also that before the work-around, the BMTF was only producing candidates from RPC input and so had low efficiency. The observed "increase" in rate from BMTF from TSG is almost certainly simply the expected effect of this fix.

[mulhearn]

@thomreis note this.

[mulhearn]

@gflouris needed by Carlo:

1. A working configuration for the reEmulation (for comparison, if it exists)
2. Confirmation that TwinMux inputs are written and unpacked... otherwise bitwise re-Emulation won't be possible.

[gflouris]

1. cmsRun /afs/cern.ch/work/g/gflouris/public/reEmul.py max=500 era=stage1

• Using input from line 35 or 36 (RunD) produces: "[DTTrigProd] CCB configuration is not valid for this run, empty collection will be produced"
• Using input from line 37 (RunB): no error. produces reasonable results.

[mulhearn]

Thanks, I forwarded it to Carlo...