-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Nano consumes alignments #39197
Comments
A new Issue was created by @tvami Tamas Vami. @Dr15Jones, @perrotta, @dpiparo, @rappoccio, @makortel, @smuzaffar, @qliphy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign xpog |
New categories assigned: xpog @mariadalfonso,@gouskos,@swertz,@vlimant you have been requested to review this Pull request/Issue and eventually sign? Thanks |
I also checked |
out of curiosity I tried to run step2 of wf. 136.8523 by using an overridden tracker alignment record with a tag that doesn't have conditions data on the run which is used for the relval, prepared via: $ conddb_import -c sqlite_file:myAlignments.db -f frontier://FrontierProd/CMS_CONDITIONS -i TrackerAlignment_v29_offline -t Alignments -b 345747
$ conddb_import -c sqlite_file:myAlignments.db -f frontier://FrontierProd/CMS_CONDITIONS -i TrackerAlignmentExtendedErrors_v16_offline_IOVs -t AlignmentErrors -b 345747 and then patching the configuration with: # Other statements
from Configuration.AlCa.GlobalTag import GlobalTag
process.GlobalTag = GlobalTag(process.GlobalTag, 'auto:run2_data', '')
process.GlobalTag.toGet = cms.VPSet(
cms.PSet(record = cms.string("TrackerAlignmentRcd"),
tag = cms.string("Alignments"),
connect = cms.string("sqlite_file:myAlignments.db")
),
cms.PSet(record = cms.string("TrackerAlignmentErrorExtendedRcd"),
tag = cms.string("AlignmentErrors"),
connect = cms.string("sqlite_file:myAlignments.db")
)
) in order to see what module would start the crash and I see:
so it seems that the alignment are used because of the |
judging from the table above doesn't seem any PPS condition is used (at least for wf 136.8523) |
The geometry is called here. |
geometry is not alignment (which is the topic of the issue...).
|
ok, this is Run2 and we explicitly re-run the tagger since wasn't in UL-mini.
|
Right but you are asking us to provide you GTs for Run-2 data as well
Ok that sounds reassuring, can you please post the cmsDriver command to reproduce the Run-3 wf? is there a runTheMatrix wf too for that? I'll check that too. But even if that's the true, it's just half the solution to the problem. |
Tracking and pf-candidate is already done in mini, so I do not expect re-running the particlenet for the b-tagging should really use the alignment; I asked the expert to see if something can be cleanup @hqucms |
a consumes statement to cmssw/RecoBTag/FeatureTools/plugins/DeepBoostedJetTagInfoProducer.cc Lines 197 to 198 in 24e9501
it should be consumed here:
|
Isnt that Or this |
it's not in the stack trace I posted above... |
Right, in that stack trace I also didnt find anything, I found this other thing instead, and now I'm asking if that's relevant or not. |
I think I pointed already to the exact point in which there is the consumes statement :) |
this pointed to use of |
The TSOS(state on surface) built from TrackExtra may not be meaningful though if the surface derived from the DetId and new geometry is different from the free state. 🤔 |
So I ran in
Indeed for Run-3 in master, we dont have the alignment dependency, so this issue is about Run-2 only (which is anyway the era that triggered the discussion). |
for completeness: can you list the Record Label used here ? |
|
@tvami I am a bit confused looking at the Rcd report in a recent nano workflows
it seems to pull in a very very large number of records. I have done something wrong ? |
hi @vlimant sorry, I was on vacation until now. It does give a huge list all the time, but then when the record is accessed it also shows which IOV is accessed. It's true that it's not very user friendly to read the output. |
ok, thanks for confirming. having filtered the record with no payload I somehow still have a larger set than in your latest comment. |
latest I got is under https://cernbox.cern.ch/s/JqTmbbfQSjdtyDc |
interesting, so I was looking at
No, not that I know of |
If you run a single threaded job and add in
you will see a module do a prefetch request and then see which EventSetup modules are triggered. |
please close we can reopen if ever this becomes a problem again ; point at which we will need a valid tool to investigate the dependency |
The following table was produced to see what records are consumed in which step:
https://twiki.cern.ch/twiki/bin/view/CMS/AlCaDBHLT2019#Table_of_conditions_for_2018_MC
As you can see the following records are consumed in the Nano step
From this the JEC + JER + Geometry + RunInfo are expected, however the Muon + tracker + global alignment records are not.
The results can be reproduced by
(inspired by 136.8523)
The text was updated successfully, but these errors were encountered: