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
Add warning for NaN values in DeepFlavourJetTagsProducer for DeepCSV #23640
Add warning for NaN values in DeepFlavourJetTagsProducer for DeepCSV #23640
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-23640/5291 |
//warn if the input is nan | ||
if(std::isnan(inputs_[var.name])) { | ||
edm::LogWarning("ValueError") << "The required output, " | ||
<< var.name << ", encountered an nan value during TagInfo processing." << endl; |
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.
endl is not necessary.
Also the second line indent better be aligned with the first line <<
A new Pull Request was created by @eacoleman (Evan Coleman) for master. It involves the following packages: RecoBTag/Combined @perrotta, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-23640/5292 |
@cmsbuild please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-23640/5822 |
please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
See #23618.