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
Save pixel and strip layers in miniAOD #15605
Save pixel and strip layers in miniAOD #15605
Conversation
… layers from HitPattern
…ew miniAOD, but will be zero when reading old ones, so better check both that and packedHits_ (which may be zero on new miniAODs if there's just one hit per layer)
A new Pull Request was created by @gpetruc (Giovanni Petrucciani) for CMSSW_8_1_X. It involves the following packages: DQM/TrackingMonitor @cvuosalo, @dmitrijus, @cmsbuild, @montjj, @slava77, @vanbesien, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
I guess we need an IORULE to correctly fill nHits when reading old files, isn't it? |
As written in the PR description, no iorule should be needed to have the On Thu, Aug 25, 2016 at 2:15 PM, arizzi notifications@github.com wrote:
|
ah right, apologies for reading the code only instead of the description :-) On Thu, Aug 25, 2016 at 2:24 PM, Giovanni Petrucciani <
|
Thanks for updating also the validation code. |
if (numberOfPixelHits_ > trackPixelHitsMask) numberOfPixelHits_ = trackPixelHitsMask; | ||
int numberOfStripHits_ = tk.hitPattern().numberOfValidHits() - numberOfPixelHits_; | ||
int numberOfStripHits_ = tk.hitPattern().numberOfValidHits() - numberOfPixelHits_ - numberOfPixelLayers_ - numberOfStripLayers_; |
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.
some comments about the incremental meaning of values may be useful
@cmsbuild please test |
The tests are being triggered in jenkins. |
ok, I can add some the comments after the tests are done On Thu, Aug 25, 2016 at 4:28 PM, cmsbuild notifications@github.com wrote:
|
Added comments explaining the logic, as per Slava's comment. |
Pull request #15605 was updated. @cvuosalo, @dmitrijus, @cmsbuild, @montjj, @slava77, @vanbesien, @davidlange6 can you please check and sign again. |
@gpetruc |
@cmsbuild please test |
The tests are being triggered in jenkins. |
+1 Adding pixel and strip layers to packed candidates in Mini-AOD. The code changes are satisfactory, and Jenkins tests against baseline CMSSW_8_1_X_2016-08-26-1100 show no significant differences, as expected. The new DQM histograms do appear in the Jenkins output DQM files. An extended test of workflow 136.731_RunSinglePh2016B with 20 events against baseline CMSSW_8_1_0_pre10 shows no significant differences, and the additions to the packed candidates do show up in the Mini-AOD output:
|
+1 |
This was already asked but I have not seen a clear reply. @gpetruc, will there be a 80X backport of this PR? |
Yep, it's #15641 On Tue, Aug 30, 2016 at 11:42 AM, Dinko Ferencek notifications@github.com
|
Perfect, thanks. I was not getting GitHub emails about the backport PR On 08/30/2016 12:49 PM, Giovanni Petrucciani wrote:
|
Save also the strip and pixel layers for packed candidates.
For compactness, instead of saving then also the number of hits we save the number of extra hits (hits - layers).
Disk size cost seems to be ~100 bytes/event, on 8.5k TTbar (PUpmx25ns).
Validation module updated as well, and used to check that there is perfect agreement between the reported number of hits and layers in the strip and pixel detector between the AOD track, the PackedCandidate methods and the PackedCandidate pseudoTrack, on ~1k TTbar events, both for 2016 and 2017 scenarios.
When reading old MiniAODs, the number of layers will be reported as zero, and but the number of hits should still be correct (I didn't put any iorule magic to try to fudge a number of layers).
@arizzi @makortel @ferencek