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
Is GenXSecAnalyzer still useful? #29098
Comments
assign generators |
New categories assigned: generators @alberto-sanchez,@SiewYan,@qliphy,@efeyazgan,@mkirsano,@agrohsje you have been requested to review this Pull request/Issue and eventually sign? Thanks |
A new Issue was created by @makortel Matti Kortelainen. @Dr15Jones, @smuzaffar, @silviodonato, @makortel, @davidlange6, @fabiocos can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
GenXSecAnalyzer is used to gather cross section and filter informations from each luminosityBlock, and then combine them to reach high accuracy with larger statistics. This is needed in MC production, especially for MC Contacts who make McM requests and need to input these information (especially on Filter/Matching efficiency which affect the job submission ) based on the print out. |
@qliphy Thanks. Is it needed in every GEN job (notably in RelVal and production)? Or would it be sufficient if it could be easily included in a GEN job when needed, but it would not be run by default? |
@makortel Yes, I think for RelVal and Production, this is not needed to be run . |
How are the configurations for the MC contacts created? Is there perhaps a template, a recipe for cmsDriver command, or generation by a web service? I'm just thinking if a modifier (e.g. |
The cmsDriver commands for MC contacts are got from McM automatically: |
Thanks. So in principle it could be sufficient to modify McM to add an extra parameter to Who should be contacted to get such change in McM? |
adding @justinasr and @pgunnell |
Made obsolete by GenXSecAnalyzer getting migrated to be thread efficient in #29328. |
The
GenXSecAnalyzer
is anedm::one::EDAnalyzer<edm::one::WatchRuns, edm::one::WatchLuminosityBlocks>
that prevents efficient use of concurrent luminosity blocks (#25090 (comment)). By quick look it aggregates various information inendLuminosityBlock()
andendRun()
, and prints out the result inendJob()
.Is this behavior needed in MC production (or RelVals)? Are these printouts looked at systematically?
The text was updated successfully, but these errors were encountered: