-
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
Fix for handling of extremely rare case of CFEB data corruption #11821
Fix for handling of extremely rare case of CFEB data corruption #11821
Conversation
…ssertion failure in CSC Segment RECO module
A new Pull Request was created by @barvic for CMSSW_7_4_X. Fix for handling of extremely rare case of CFEB data corruption It involves the following packages: EventFilter/CSCRawToDigi @cmsbuild, @cvuosalo, @slava77 can you please review it and eventually sign? Thanks. |
@cmsbuild please test |
@barvic |
The tests are being triggered in jenkins. |
+1 For #11821 9cadc86 The fix is satisfactory, and Jenkins tests against baseline CMSSW_7_4_X_2015-10-15-1100 show no significant differences, as expected. However, the Jenkins comparisons are incomplete. #11824 has complete Jenkins comparisons, and they also show no significant differences. |
This pull request is fully signed and it will be integrated in one of the next CMSSW_7_4_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_7_6_X is complete. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar |
@davidlange6 |
+1 |
Fix for handling of extremely rare case of CFEB data corruption
The CSC Unpacker side fix for handling of rare case CFEB data corruption, which could cause assertion failure in CSC Segment RECO module.
Original issue is described at https://hypernews.cern.ch/HyperNews/CMS/get/recoDevelopment/1391.html
Assertion failure is triggered, when number of expected time bins in CFEB data is not equal to 8.