-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLCT comparator code calculation (CCLUT-5) #30103
CLCT comparator code calculation (CCLUT-5) #30103
Conversation
The code-checks are being triggered in jenkins. |
A new Pull Request was created by @dildick (Sven Dildick) for master. It involves the following packages: L1Trigger/CSCTriggerPrimitives @cmsbuild, @rekovic, @benkrikler can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
The code-checks are being triggered in jenkins. |
Pull request #30103 was updated. @cmsbuild, @rekovic, @benkrikler can you please check and sign again. |
The code-checks are being triggered in jenkins. |
Pull request #30103 was updated. @cmsbuild, @rekovic, @benkrikler can you please check and sign again. |
@rekovic Can you run the tests, please? |
test parameters |
please test |
@silviodonato , this also failed to merge |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
The single failure is coming from the pixel system. So this looks good to me. |
@rekovic, can you please check and eventually sign? |
+1 |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR introduces the comparator code calculation in the CLCT processor (actually part of the OTMB/TMB firmware logic). Run-3 will use new CLCT patterns which, in combination with the CCLUT algorithm, allow for a more precise determination of LCT position and bending in the CSC local trigger. More information on the CCLUT algorithm and CSC trigger data formats can be found here: https://gitlab.cern.ch/tdr/notes/DN-20-016/blob/master/temp/DN-20-016_temp.pdf. The CCLUT algorithm uses a new
CSCComparatorCodeLUT
object that loads the LUTs in txt format. I do not yet have an actual position offset/slope LUT generator, but plan to add that in a follow-up PR.The PR is the fifth in a series following #29233, #29205, #28846 and #28600. A related PR is this one cms-data/L1Trigger-CSCTriggerPrimitives#1 where the LUTs are introduced for position offset and slope.
To be clear: the code is not enabled yet - and won't be for quite some time as it requires precise coordination between EMTF, OMTF, DQM, packer/unpacker etc. There should be no differences in any of the workflows (and I didn't see any in local tests).
PR validation:
Tested with WF 27434.0
if this PR is a backport please specify the original PR and why you need to backport that PR:
N/A
@tahuang1991