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
Mostly changes related to handling TDC info #14920
Conversation
A new Pull Request was created by @igv4321 (Igor Volobouev) for CMSSW_8_1_X. It involves the following packages: DataFormats/HcalRecHit @cmsbuild, @cvuosalo, @slava77, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
|
||
// Special value for the rise time used in case the QIE10 pulse | ||
// is always above the discriminator | ||
static constexpr float UNKNOWN_T_OVERSHOOT = -101.f; |
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.
overshoot is smaller than undershoot?
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.
These are just technical numbers. The only requirements
for them is that they are exactly representable floats, and
that they can not be encountered during normal readouts.
It is also nice to define them in such a way that, if desired,
they can be seen in plots together with "normal" readouts.
On 06/19/2016 11:17 AM, Slava Krutelyov wrote:
In DataFormats/HcalRecHit/interface/HFQIE10Info.h #14920 (comment):
@@ -21,6 +21,14 @@ class HFQIE10Info
static const unsigned N_RAW_MAX = 5;
static const raw_type INVALID_RAW = std::numeric_limits<raw_type>::max();
- // Special value for the rise time used in case the QIE10 pulse
- // is always below the discriminator
- static constexpr float UNKNOWN_T_UNDERSHOOT = -100.f;
- // Special value for the rise time used in case the QIE10 pulse
- // is always above the discriminator
- static constexpr float UNKNOWN_T_OVERSHOOT = -101.f;
overshoot is smaller than undershoot?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/cms-sw/cmssw/pull/14920/files/0b14bc4b41a8878079e1ed29025e58c078e6f68a#r67619481, or mute the thread
https://github.com/notifications/unsubscribe/AFS4-Ypcq6z48vojFrUR7sY5QkcmfNaEks5qNWu0gaJpZM4I5Mg7.
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.
thanks for the explanation
( just magic numbers )
@cmsbuild please test |
The tests are being triggered in jenkins. |
Pull request #14920 was updated. @cmsbuild, @cvuosalo, @slava77, @davidlange6 can you please check and sign again. |
@cmsbuild please test |
The tests are being triggered in jenkins. |
Maybe, but with negative magic numbers there can be no On 06/22/2016 12:06 PM, Slava Krutelyov wrote:
|
Pull request #14920 was updated. @cmsbuild, @cvuosalo, @slava77, @davidlange6 can you please check and sign again. |
@cmsbuild please test |
The tests are being triggered in jenkins. |
hardwareOK = false; | ||
} | ||
} | ||
if (!hardwareOK) |
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.
Code duplication can be avoided here, starting at line 39:
unsigned startSample = sampleToCheck, endSample = sampleToCheck + 1;
if (sampleToCheck >= nRaw)
{
startSample = 0;
endSample = nRaw;
}
for (sampleToCheck = startSample; sampleToCheck < endSample; ++sampleToCheck)
{
const QIE10DataFrame::Sample s(anode.getRaw(sampleToCheck));
if (!s.ok())
hardwareOK = false;
}
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.
Sorry, which code duplication? I prefer to write my code
so that the least possible amount of work is performed
in the branch that is encountered most often.
On 06/27/2016 07:17 AM, Carl Vuosalo wrote:
In RecoLocalCalo/HcalRecAlgos/src/HFSimpleTimeCheck.cc #14920 (comment):
{
const QIE10DataFrame::Sample s(anode.getRaw(sampleToCheck));
hardwareOK = s.ok();
}
else
{
// This should not normally happen, but we still
// need to do something reasonable here
for (sampleToCheck = 0; sampleToCheck < nRaw; ++sampleToCheck)
{
const QIE10DataFrame::Sample s(anode.getRaw(sampleToCheck));
if (!s.ok())
hardwareOK = false;
}
}
if (!hardwareOK)
Code duplication can be avoided here, starting at line 39:
|unsigned startSample = sampleToCheck, endSample = sampleToCheck + 1; if (sampleToCheck >= nRaw) { startSample = 0; endSample = nRaw; } for (sampleToCheck = startSample; sampleToCheck < endSample;
++sampleToCheck) { const QIE10DataFrame::Sample s(anode.getRaw(sampleToCheck)); if (!s.ok()) hardwareOK = false; } |—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/cms-sw/cmssw/pull/14920/files/d69aae5b5dd9e76e1ba10f46e8ed58dd93044926#r68566046, or mute the thread
https://github.com/notifications/unsubscribe/AFS4-S7Y0LuphBdB-mu-lOI5IQC3_rpDks5qP79IgaJpZM4I5Mg7.
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.
@igv4321: OK. I was just making a suggestion. If this method is called at very high frequency, then performance considerations take priority.
@igv4321: What option to |
No, use either -m 2 or -m 3. On 06/27/2016 08:42 AM, Carl Vuosalo wrote:
|
+1 Revising usage of TDC info for Phase 1 HF. There should be no change in monitored quantities. The code changes are satisfactory, and Jenkins tests against baseline CMSSW_8_1_X_2016-06-25-1100 show no significant differences, as expected. A custom Phase 1 HCAL test was performed (using
RECO and Mini-AOD event content increases in size somewhat:
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_1_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar |
+1 |
HFQIE10Info and rechit timing is now in ns instead of TDC units.
Correct handling of special QIE10 TDC values 62 and 63.
Made provisions for proper handing of single-anode PMTs in the mixed-readout scenario.
Use "sample-of-interest" time slice for setting "HARDWARE_ERROR" algorithm status.
The code is checked with the Phase 1 recipe described at
https://twiki.cern.ch/twiki/bin/viewauth/CMS/HcalPhase1SoftwareSimulationRecipe