Skip to content
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

Added handling of special case of OTMB corrupted data to the CSC binary examiner #7829

Merged

Conversation

barvic
Copy link
Contributor

@barvic barvic commented Feb 18, 2015

Added handling of special case of OTMB corrupted data to the CSC binary Examiner as part of the CSC Unpacker.

  • The issue was reported by RECO developers during processing of PromptReco MinimumBias job with the release CMSSW_7_3_2_patch1
  • The assertion was triggered in CSC unpacker code for Run 234107 MinimumBias data
  • Was caused by special case of corrupted data from OTMB board, which wasn't marked as bad by the CSC examiner
  • Current fix is to detect and mark such data as bad and then reject such bad events from further unpacking

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @barvic for CMSSW_7_3_X.

Added handling of special case of OTMB corrupted data to the CSC binary examiner

It involves the following packages:

EventFilter/CSCRawToDigi

@cmsbuild, @cvuosalo, @nclopezo, @slava77 can you please review it and eventually sign? Thanks.
@Martin-Grunewald this is something you requested to watch as well.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
If you are a L2 or a release manager you can ask for tests by saying 'please test' in the first line of a comment.
@nclopezo you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

@cvuosalo
Copy link
Contributor

+1

For #7829 e79619c

This PR fixes a rare assertion failure in the CSC unpacker that occurs due to corruption in the data stream that occurs under unusual circumstances.

The code change is satisfactory, and all Jenkins tests show no differences, as expected.

A test case that reproduced the assertion failure in CMSSW_7_3_2_patch1 worked correctly without failure with the new code.

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_3_X IBs unless changes (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @nclopezo, @ktf, @smuzaffar

@davidlange6
Copy link
Contributor

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants