-
Notifications
You must be signed in to change notification settings - Fork 2
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
Update tdr barrel regionizer emulator #116
Update tdr barrel regionizer emulator #116
Conversation
At a quick look it seems ok to me. |
For squashing into a single commit, you mean that when this is merged, you will use the "Squash and Merge" option, or is there something I need to do before? |
I think it's best if you squash the commits locally and force-push the new commit here. |
I may have a solution to the order problem I am still seeing, so I may want to include a few more commits before squashing. It should be within the next few days. |
8f79baf
to
29af0a6
Compare
29af0a6
to
71bc3b9
Compare
I fixed the order issue and squashed this commit. |
I pushed another commit here as requested in the review in cms-sw#41838. If you agree with the response to that request, we should cherry-pick the answer. If not, let me know what is the best way to fix it. |
Yep, I'll cherry-pick it on the other PRs (monday).
Il Sab 3 Giu 2023, 00:24 Jovan Mitrevski ***@***.***> ha
scritto:
… I pushed another commit here as requested in the review in cms-sw#41838
<cms-sw#41838>. If you agree with the
response to that request, we should cherry-pick the answer. If not, let me
know what is the best way to fix it.
—
Reply to this email directly, view it on GitHub
<#116 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABDNWR7MYFRBHBPK6VKSPBLXJJRYDANCNFSM6AAAAAAXXWAK3E>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Ok, the PRs to upstream are not yet merged but they are fully signed so I can merge this. |
effectively merged. |
PR description:
This updates the tdr barrel emulator. It generally matches results with the firmware in:
https://gitlab.cern.ch/cms-cactus/phase2/firmware/correlator-common/-/merge_requests/134
The one issue that remains is that the processing delays are not 100% accurately modeled, so data coming from different fibers can appear in different order in the output between the emulator and the simulation. (The TDR emulator was never 100% accurate on this.) This includes an attempt to model this better, but it's not quite there.
PR validation:
This is mainly tested manually comparing emulator and simulator using scripts in in correlator-layer1. I will comment on the related PR once I make it.