-
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
add ak4 gen and PF jets to corresponding sequences #6907
Conversation
A new Pull Request was created by @fratnikov (Fedor Ratnikov) for CMSSW_6_2_X_SLHC. add ak4 gen and PF jets to corresponding sequences It involves the following packages: RecoJets/Configuration @cmsbuild, @nclopezo, @StoyanStoynev, @slava77 can you please review it and eventually sign? Thanks. |
Pull request #6907 was updated. @cmsbuild, @nclopezo, @StoyanStoynev, @slava77 can you please check and sign again. |
merge |
add ak4 gen and PF jets to corresponding sequences
Hi @fratnikov , do we know the impact of the ressources (memory , timing) at high PU ? I'm worried because for HGCal we are trying to reduce the reco step , and also we are just about to send big digi-reco prodcution for Shaslik, so i'm worried that this is inducing resosurces while we are already at the limit (or even already above..) . |
@boudoul: we currently produce 35 Jet collections in RECO (see below), Very conservative estimation is that adding 3 more Jet collections to 35 already available However, if resources is big an issue requiring action, we can safely drop all jet collections recoPFJets_kt4PFJets__RECO. |
indeed, there are memory problems.. perhaps removing some of the unneeded jets would benefit everyone On Dec 16, 2014, at 4:41 PM, Fedor Ratnikov notifications@github.com
|
@davidlange6 If you talk about RAM shortage, then reducing number of jet collections won't help: jet reconstruction memory consumption is driven by number of input objects, which is pretty the same for all used jet algorithms of given flavor. So I expect no difference in peak RAM consumption between running one jet algorithm and running many of them sequentially. |
No description provided.