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

ZDC unpacker, cleaner commit #12497

Merged
merged 3 commits into from Nov 20, 2015
Merged

Conversation

cferraio
Copy link
Contributor

Hi all,

I'm started a new commit with the ZDC unpacker that is much cleaner. Hopefully this helps.

Chris

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @cferraio (Chris Ferraioli) for CMSSW_7_5_X.

It involves the following packages:

Configuration/StandardSequences
EventFilter/CastorRawToDigi

@cmsbuild, @cvuosalo, @franzoni, @davidlange6, @slava77 can you please review it and eventually sign? Thanks.
@ghellwig, @makortel, @GiacomoSguazzoni, @rovere, @VinInn, @Martin-Grunewald, @cerati, @dgulhan 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

@cferraio cferraio mentioned this pull request Nov 19, 2015
@mmusich
Copy link
Contributor

mmusich commented Nov 19, 2015

-1
@cferraio you're still proposing to remove the changes I recently introduce in #12491. A further rebase is needed

@mmusich
Copy link
Contributor

mmusich commented Nov 19, 2015

hold

@cmsbuild
Copy link
Contributor

Pull request has been put on hold by @mmusich
They need to issue an unhold command to remove the hold state or L1 can unhold it for all

@cmsbuild cmsbuild added the hold label Nov 19, 2015
@cferraio
Copy link
Contributor Author

Hi @mmusich, how do I do this? I thought I had taken the most recent release.

Sorry...first time going through this progress...

@abdoulline
Copy link

The most recent IB is usually as good way to proceed...
scram list -a CMSSW | grep 7_5_X
-> CMSSW_7_5_X_2015-11-19-1100

@cferraio
Copy link
Contributor Author

Ok, that's the one I used, however it looks like i DID add in AlCaReco...py
"git add Configuration/StandardSequences/python/AlCaRecoStreamsHeavyIons_cff.py"

I think I understand what happened now, I copied over a folder instead of an individual file, and then committed what git picked up as modified. If I change that file to what Marco committed, then recommit, would that work, or should I start over again and be more careful when copying files?

Thanks,
Chris

On Nov 19, 2015, at 15:38, Salavat Abdullin notifications@github.com wrote:

The most recent IB is usually as good way to proceed...
scramv1 list -a CMSSW | grep 7_5_X
-> CMSSW_7_5_X_2015-11-19-1100


Reply to this email directly or view it on GitHub.

@mmusich
Copy link
Contributor

mmusich commented Nov 19, 2015

@cferraio you can edit the file and remove the changes you didn't mean to include. After that you can commit again with the --amend option (that will make your history look good).

@cferraio
Copy link
Contributor Author

hi @mmusich, i'm having some issues. i made the change and committed with amend, but i receive an error message when i push:
git push my-cmssw ZdcUnpacker_HI75X
Enter passphrase for key '/afs/cern.ch/user/c/cferraio/.ssh/id_rsa':
To git@github.com:cferraio/cmssw.git
! [rejected] ZdcUnpacker_HI75X -> ZdcUnpacker_HI75X (non-fast-forward)
error: failed to push some refs to 'git@github.com:cferraio/cmssw.git'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Merge the remote changes (e.g. 'git pull')
hint: before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

thanks again...

@mmusich
Copy link
Contributor

mmusich commented Nov 19, 2015

git push my-cmssw +HEAD:ZdcUnpacker_HI75X

@cferraio
Copy link
Contributor Author

great, that did it, thanks!

fingers crossed everything looks good...

On Nov 19, 2015, at 16:10, Marco Musich notifications@github.com wrote:

git push my-cmssw +HEAD:ZdcUnpacker_HI75X

@mmusich
Copy link
Contributor

mmusich commented Nov 19, 2015

there is still one line difference, but should be harmless enough :)

@mmusich
Copy link
Contributor

mmusich commented Nov 19, 2015

unhold

@cmsbuild cmsbuild removed the hold label Nov 19, 2015
@cmsbuild
Copy link
Contributor

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

@slava77
Copy link
Contributor

slava77 commented Nov 19, 2015

unless I'm missing something, this is still working only up to digi. The issue with rechits is still to be addressed, right?

@cferraio
Copy link
Contributor Author

Hi Slava,

Sorry, maybe I was confused, I thought this was something we were to work on after we got this up and running and into the digi level. Is it necessary to fix through reco at this stage?

On Nov 19, 2015, at 16:37, Slava Krutelyov notifications@github.com wrote:

unless I'm missing something, this is still working only up to digi. The issue with rechits is still to be addressed, right?


Reply to this email directly or view it on GitHub.

@slava77
Copy link
Contributor

slava77 commented Nov 19, 2015

Chris,
up to your last message and the PR updates just recently I was anticipating the local reco is going to be updated.
High hopes, I guess.

@cmsbuild
Copy link
Contributor


//////////////////////////////////////////////
qie_begin=(const HcalQIESample*)daq_first;
qie_end=(HcalQIESample*)(daq_last+1); // one beyond last..
Copy link
Contributor

Choose a reason for hiding this comment

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

this generates a complaint from the static analyzer as well
(you can see it in the link next to "Tested at: " after automated test report is produced, they come out in "Static checks outputs")
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-12497/9866/llvm-analysis/report-5dee98.html#EndPath

the code in fact doesn't use these casted non-consts, no harm.
Still, better fix it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ah, ok, I missed the const on the second line. Fixed.

On Nov 19, 2015, at 23:54, Slava Krutelyov notifications@github.com wrote:

In EventFilter/CastorRawToDigi/src/ZdcUnpacker.cc:

  •  if (!silent) edm::LogWarning("ZdcUnpacker") << "Skipping data on spigot " << spigot << " of DCC with source id " << dccHeader->getSourceId() << " which is of unknown flavor " << htr.getFirmwareFlavor();
    
  •  continue;
    
  • }
  • // calculate "real" number of presamples
  • //int nps=htr.getNPS()-startSample_;
  • // get pointers
  • htr.dataPointers(&daq_first,&daq_last,&tp_first,&tp_last);
  • unsigned int smid=htr.getSubmodule();
  • int htr_tb=smid&0x1;
  • int htr_slot=(smid>>1)&0x1F;
  • int htr_cr=(smid>>6)&0x1F;
  • //////////////////////////////////////////////
  • qie_begin=(const HcalQIESample*)daq_first;
  • qie_end=(HcalQIESample*)(daq_last+1); // one beyond last..

this generates a complaint from the static analyzer as well
(you can see it in the link next to "Tested at: " after automated test report is produced, they come out in "Static checks outputs")
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-12497/9866/llvm-analysis/report-5dee98.html#EndPath

the code in fact doesn't use these casted non-consts, no harm.
Still, better fix it.


Reply to this email directly or view it on GitHub.

@slava77
Copy link
Contributor

slava77 commented Nov 19, 2015

I'm confused now: I was expecting that after we move to castor raw2digi, only one ZDC FED will be unpacked (the 693).
[this picture doesn't quite match the slides from today. What I see in the code now is that both FED 693 and FED 722 are unpacked in one place]

What's FED 722? it's the old ZDC VME FED index, when it was "attached" to HF, right?

I have a feeling I understand even less now.

Let me start with "basic" questions:

Looking at the HcalUnpacker and HcalRawToDigi, it wouldn't care which VME FED number it is as long as it's in the list to try.
@abdoulline ?

@slava77
Copy link
Contributor

slava77 commented Nov 19, 2015

sorry, I meant

  • can the hcal raw2digi unpack new ZDC data if it was coming from the FED 693? (was it a mere FED number change or was there really a change in the format?)

@abdoulline
Copy link

Slava,
it was HCAL request to start "phasing out" ZDC from HCAL ("a la" CASTOR), as new ZDC is sitting in CASTOR crate/FED
http://cmslxr.fnal.gov/source/DataFormats/FEDRawData/interface/FEDNumbering.h

ZDC entries were removed from HCAL emap since April. This was no-return point unpacking-wise.

NB: in principle, HCAL unpacker still could have managed new ZDC in-CASTOR FED
(693) , but HCAL OPS didn't want to maintain ZDC emap and insisted on its
removal from HCAL emap early in 2015.
More so, the request was made about ZDC QIE electronics properties to be
removed from HCAL DB table in particular , and possibly other ZDC conditions from HCAL ones in general (like in conditions-self-consistent CASTOR).
But this was unrealistic to accomplish given very limited manpower on ZDC
side (and HCAL overwhelmed by many HCAL-specific issues). So at the moment
ZDC is still in HCAL DIGI/RECO code (even ZDC snippets in HCAL
packer/unpacker), but not in new (2015) data e-map.

@cferraio
Copy link
Contributor Author

Hi Slava,

Unfortunately Hcal has kicked out the Zdc :-).

That's correct, 722 is the Fed used for old datasets, and I'm using it to distinguish between pre- and post- April data sets. As Salavat mentioned, Hcal can't simply unpack Zdc with a change of fed id for run 2 data. I've set up the code so that when it has info in fed 722 it uses different electronics and detectors ids than when it unpacks info in fed 693.

On Nov 20, 2015, at 00:31, Slava Krutelyov notifications@github.com wrote:

I'm confused now: I was expecting that after we move to castor raw2digi, only one ZDC FED will be unpacked (the 693).
[this picture doesn't quite match the slides from today. What I see in the code now is that both FED 693 and FED 722 are unpacked in one place]

What's FED 722? it's the old ZDC VME FED index, when it was "attached" to HF, right?

I have a feeling I understand even less now.

Let me start with "basic" questions:

• can the hcal raw2digi unpack new ZDC data if it was coming from the FED 722? (was it a mere FED number change or was there really a change in the format?)
• if it's just a FED numbering, can't you just add FED 693 to https://github.com/cms-sw/cmssw/blob/CMSSW_7_5_6/EventFilter/HcalRawToDigi/plugins/HcalRawToDigi.cc#L39 and be done?
Looking at the HcalUnpacker and HcalRawToDigi, it wouldn't care which VME FED number it is as long as it's in the list to try.
@abdoulline ?


Reply to this email directly or view it on GitHub.

@cmsbuild
Copy link
Contributor

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

@slava77
Copy link
Contributor

slava77 commented Nov 20, 2015

@cmsbuild please test
[will just check up to compilation]

@cmsbuild
Copy link
Contributor

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

@slava77
Copy link
Contributor

slava77 commented Nov 20, 2015

+1

for #12497 1b2649d

  • code changes are OK for this emergency 75X situation (and I'd prefer not to forward port and instead to solve this appropriately; even better still I'd rather see the ZDC unpacking go back to hcalDigis where it was fitting well and will still fit OK from the code perspective)
  • jenkins tests pass and comparisons with baseline show no relevant differences
  • local tests with CMSSW_7_5_6 and run2 pp data and also recent runs (262163)
    • show only a change in HcalUnpackerReport castorDigis errorFree among the monitored quantities (expected)
    • zdc digis are not empty with a manual inspection in 262163
      Tests were done with ZDC unpacker, cleaner commit #12497 8156022

For post-75X perspective. If I understood the plans correctly, the 722 and 693 FED unpacking (now both in castorDigis) will be moved out to a separate zdcRawToDigi and also outputs of it will be picked up by the local reconstruction.

@slava77
Copy link
Contributor

slava77 commented Nov 20, 2015

merge

compilation is OK from the console in jenkins

cmsbuild added a commit that referenced this pull request Nov 20, 2015
@cmsbuild cmsbuild merged commit f590afb into cms-sw:CMSSW_7_5_X Nov 20, 2015
@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

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

5 participants