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
ZDC unpacker, cleaner commit #12497
Conversation
A new Pull Request was created by @cferraio (Chris Ferraioli) for CMSSW_7_5_X. It involves the following packages: Configuration/StandardSequences @cmsbuild, @cvuosalo, @franzoni, @davidlange6, @slava77 can you please review it and eventually sign? Thanks. Following commands in first line of a comment are recognized
|
hold |
Pull request has been put on hold by @mmusich |
Hi @mmusich, how do I do this? I thought I had taken the most recent release. Sorry...first time going through this progress... |
The most recent IB is usually as good way to proceed... |
Ok, that's the one I used, however it looks like i DID add in AlCaReco...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,
|
@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). |
hi @mmusich, i'm having some issues. i made the change and committed with amend, but i receive an error message when i push: thanks again... |
|
3aca95b
to
8156022
Compare
great, that did it, thanks! fingers crossed everything looks good...
|
there is still one line difference, but should be harmless enough :) |
unhold |
unless I'm missing something, this is still working only up to digi. The issue with rechits is still to be addressed, right? |
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?
|
Chris, |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
|
||
////////////////////////////////////////////// | ||
qie_begin=(const HcalQIESample*)daq_first; | ||
qie_end=(HcalQIESample*)(daq_last+1); // one beyond last.. |
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.
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.
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.
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#EndPaththe 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.
I'm confused now: I was expecting that after we move to castor raw2digi, only one ZDC FED will be unpacked (the 693). 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. |
sorry, I meant
|
Slava, 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 |
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.
|
@cmsbuild please test |
The tests are being triggered in jenkins. |
+1
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. |
merge compilation is OK from the console in jenkins |
Hi all,
I'm started a new commit with the ZDC unpacker that is much cleaner. Hopefully this helps.
Chris