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

Change of DigiToRaw code to keep SiStrip Error information during data repacking #12674

Merged
merged 15 commits into from
Dec 10, 2015

Conversation

rkunnawa
Copy link
Contributor

@rkunnawa rkunnawa commented Dec 4, 2015

This PR fixes the bug which caused empty histograms for SiStrip FED Errors in the DQM. This is prepared for the HIN data taking period after we saw the aforementioned issues.
thanks!
@abaty @icali

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 4, 2015

A new Pull Request was created by @rkunnawa (Raghav Kunnawalkam Elayavalli) for CMSSW_7_5_X.

It involves the following packages:

EventFilter/SiStripRawToDigi

@cmsbuild, @cvuosalo, @davidlange6, @slava77 can you please review it and eventually sign? Thanks.
@makortel, @Martin-Grunewald, @VinInn this is something you requested to watch as well.
@slava77, @Degano, @smuzaffar you are the release manager for this.

Following commands in first line of a comment are recognized

  • +1|approve[d]|sign[ed]: L1/L2's to approve it
  • -1|reject[ed]: L1/L2's to reject it
  • assign <category>[,<category>[,...]]: L1/L2's to request signatures from other categories
  • unassign <category>[,<category>[,...]]: L1/L2's to remove signatures from other categories
  • hold: L1/all L2's/release manager to mark it as on hold
  • unhold: L1/user who put this PR on hold
  • merge: L1/release managers to merge this request
  • [@cmsbuild,] please test: L1/L2 and selected users to start jenkins tests
  • [@cmsbuild,] please test with cms-sw/cmsdist#<PR>: L1/L2 and selected users to start jenkins tests using externals from cmsdist

@abaty
Copy link
Contributor

abaty commented Dec 4, 2015

Some elaboration about this PR. This code adds to the DigiToRaw repacking code the ability to copy the header of another rawDataCollector. This is important for Heavy Ion data taking, as nearly all our data stored on disk is run through the repacker. Without this fix we lose the information stored in the header about the error status of the SiStrips, and also are unable to fill some of the SiStrip FED DQM plots.

fedbuffer.reset(new sistrip::FEDBuffer(rawfedData.data(),rawfedData.size(),true));
//bufferBase.reset(new sistrip::FEDBufferBase(rawfedData.data(),rawfedData.size()));
} catch (const cms::Exception& e) {
std::cerr << "[sistrip::DigiToRaw::createFedBuffers_]"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use LogError or LogWarning

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

line 143 here has "std::cerr"
please change to LogWarning or LogError

@slava77
Copy link
Contributor

slava77 commented Dec 4, 2015

@rkunnawa
please provide details how to test with a case where two fedRaw are read

@slava77
Copy link
Contributor

slava77 commented Dec 4, 2015

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 4, 2015

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/10154/console

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 4, 2015

Pull request #12674 was updated. @cmsbuild, @cvuosalo, @davidlange6, @slava77 can you please check and sign again.

@rkunnawa
Copy link
Contributor Author

rkunnawa commented Dec 4, 2015

@slava77 we do have the logWarning in the code. can you briefly explain what you wanted done? should we remove the

  • if ( edm::isDebugEnabled() ) {
    
    thanks!

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 4, 2015

Pull request #12674 was updated. @cmsbuild, @cvuosalo, @davidlange6, @slava77 can you please check and sign again.

@rkunnawa
Copy link
Contributor Author

rkunnawa commented Dec 4, 2015

@slava77 thanks for pointing that out. im afraid i need to ask you again what you mean by " please provide details how to test with a case where two fedRaw are read". Do you want a config which we tested with the cout statements for a single fed (which you can find it here ~rkunnawa/public.testSiStripFEDMonitor_cfg.py on lxplus)? or im not sure?

@slava77
Copy link
Contributor

slava77 commented Dec 4, 2015

@rkunnawa
is this config what's supposed to run online or really just a small test setup?
I'd rather check the full setup.

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 4, 2015

@amagnan
Copy link
Contributor

amagnan commented Dec 9, 2015

Just want to add that the exact error classification doesn't matter much in practice, we have checked the raw fed buffer and indeed both types could apply. I still want to understand why exactly they get reclassified but this should not prevent the PR to go ahead: it is much better to have this now than delay it any further.

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 9, 2015

-1
Tested at: 8616a23
When I ran the RelVals I found an error in the following worklfows:
1000.0 step1

DAS Error

you can see the results of the tests here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-12674/10217/summary.html

@slava77
Copy link
Contributor

slava77 commented Dec 9, 2015

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 9, 2015

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/10221/console

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 9, 2015

@cmsbuild
Copy link
Contributor

@slava77
Copy link
Contributor

slava77 commented Dec 10, 2015

+1

for #12674 8616a23

  • code changes are in the packer of sistrip data in the heavy ion data taking.
  • changes introduced up to 73f0c48 are dscussed above; the last commit didn't trigger any additional changes in the monitored quantities (including matrix with 2010 HI data and reHLT-reRECO workflow of 2015 HI data)

@rkunnawa @abaty
Please, make a pull request for 80X and also just in case for 76X.

@rkunnawa please use the "Edit" button at the top of the github page for this PR and update the subject to reflect changes made in the packer (for self-documentation)

@rkunnawa rkunnawa changed the title SiStrip FED DQM error plot fix Change of DigiToRaw code to keep SiStrip Error information during data repacking Dec 10, 2015
@rkunnawa
Copy link
Contributor Author

@slava77 done! hope we can get this now! we will prepare one for 80X and 76X as requested, with all the changes.

davidlange6 added a commit that referenced this pull request Dec 10, 2015
Change of DigiToRaw code to keep SiStrip Error information during data repacking
@davidlange6 davidlange6 merged commit 50c1aa6 into cms-sw:CMSSW_7_5_X Dec 10, 2015
@Martin-Grunewald
Copy link
Contributor

Is this also needed for MC production validation purposes? If so we'd need another PR from HLT as #12735 does not contain the new parameters, so would use the default setting from fillDescriptions for them, while I assume you'd need another setting for the added parameters.
Please advise!
BTW, for data I'd need to parse this and the menu used online needs to be migrated and then changing the added parameters. Please advise as well!

@amagnan
Copy link
Contributor

amagnan commented Dec 10, 2015

Hi, no need to change anything for MC I think, default settings are fine. MC doesn't know anything about fed errors or buffer header as far as I understand....

@icali
Copy link
Contributor

icali commented Dec 10, 2015

@Martin-Grunewald not an expert but I believe that we need to ask the parsing of the menu. This is used in only one module. I also agree with Anne Marie, nothing should be affected in MC.

@Martin-Grunewald
Copy link
Contributor

Hi,

OK, I have patched it into ConfDB - code template CMSSW_7_5_7_patch1_HLT1.
Default migration to this new template leads to these changes in the HIon menu:

-------------------------------------------------------------------------------
Modules (2):
  -> hltSiStripRawDigiToVirginRaw [SiStripDigiToRawModule] CHANGED
       bool CopyBufferHeader = false [ADDED]
       InputTag RawDataTag = rawDataCollector [ADDED]
  -> hltSiStripDigiToZSRaw [SiStripDigiToRawModule] CHANGED
       bool CopyBufferHeader = false [ADDED]
       InputTag RawDataTag = rawDataCollector [ADDED]

Thus, migrate the online menu you have in ConfDBv2, modified since provided by STORM,
and then adjust the new parameters in the two instances above to your liking!
As an example, I have done so starting from the STORM menu in hltdev (ConfDBv1),
/online/collisions/2015/HeavyIons/v1.0/HLT/V6, migrated that and saved it as
/online/collisions/2015/HeavyIons/v1.0/HLT/V7. Simply do the same with the most
recent PbPb menu running online.

@abaty
Copy link
Contributor

abaty commented Dec 11, 2015

@slava77

We managed to run this change online today and it worked well. I have made a PR for 8_0_X (#12762).

I have not made the PR for 7_6_X, as it has some changes that depend on having PR (#12161) merged before, and that PR seems to be held up quite a bit. Should I just wait for that PR to merge first?

cmsbuild added a commit that referenced this pull request Dec 15, 2015
Fix for SiStripErrors in HI repacking (porting PR #12674)
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.

8 participants