-
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
Run-3 ALCT and LCT data formats #29456
Run-3 ALCT and LCT data formats #29456
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29456/14646
|
A new Pull Request was created by @dildick (Sven Dildick) for master. It involves the following packages: DataFormats/CSCDigi @cmsbuild, @rekovic, @benkrikler, @civanch, @mdhildreth can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@civanch I think I still need to add a member in order to distinguish Run-1/2 from Run-3 ALCTs and LCTs. I was able to do this for CLCTs in #29205 with the comparator code value. For ALCTs and LCTs, there is no obvious choice with the existing members. Some CSC folks suggested to add a flag |
please test |
The tests are being triggered in jenkins. |
@dildick , addition of an extra flag seems to be a working solution. However, it is not the first case when in a sub-detector we have to modify data structure, let us discuss with experts what is optimal in the case of a minor change as you have. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@silviodonato Do you have a suggestion I can implement? |
Glad to see that the unit test passed this time. Other than that, the comparisons look good; no failures in the CSC system that I can tell. |
@@ -81,7 +84,7 @@ void CSCCLCTDigi::clear() { | |||
} | |||
} | |||
|
|||
int CSCCLCTDigi::getKeyStrip(int n) const { | |||
uint16_t CSCCLCTDigi::getKeyStrip(const uint16_t n) const { | |||
// 10-bit case for strip data word | |||
if (compCode_ != -1 and n == 8) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is for Run 3 only, I guess? Just to confirm: the "compCode" has never been used in Run 2, i.e. it was unused in firmware, and was always set to -1 in software? (See getCompCode() function above.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, correct. I suppose we can update this function so that for Run-1/2 it always returns the half-strip, whatever the argument.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that's already what it does, no? See below, "// 8-bit case for strip data word (all other cases)"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it does.
Looks like there were 0 changes in any of the DQM histograms, including L1T:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_11_1_X_2020-04-16-2300+4c06e6/35939/1330.0_ZMM_13+ZMM_13+DIGIUP15+RECOUP15_L1TMuDQM+HARVESTUP15_L1TMuDQM+NANOUP15/
…On Fri, Apr 17, 2020 at 11:10 AM Sven Dildick ***@***.***> wrote:
Glad to see that the unit test passed this time. Other than that, the
comparisons look good; no failures in the CSC system that I can tell.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#29456 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABHVOUHKT3FKJEUST3FYXPDRNB5L3ANCNFSM4MFR6A6Q>
.
|
Hi, are there more comments on this PR? |
+1
|
+1 |
@rekovic do you have any comments? |
Hi, can this PR be integrated? |
Reminder @rekovic (CMSSW_11_1_0_pre7 is scheduled for tomorrow) |
@dildick +1 |
+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 |
@rekovic I see. I'll need to remove the "get" from each getter function... Is there a chance this introduces an issue with reading old MC/data with newer code? |
PR description:
This PR extends the ALCT and LCT data formats for Run-3. Detailed information can be found in this note: https://gitlab.cern.ch/tdr/notes/DN-20-016/blob/master/temp/DN-20-016_temp.pdf
Edited Summary:
ALCT changes (section 3.1 in DN-20-016)
hmt_
was addedversion_
that indicates Run3 or Legacy was addedCLCT changes
version_
that indicates Run3 or Legacy was addedLCT changes (section 3.2 in DN-20-016)
hmt
was addedversion_
that indicates Run3 or Legacy was addedPR validation:
Tested with WF 22034.0
if this PR is a backport please specify the original PR and why you need to backport that PR:
N/A