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
introduce MINIGEN step and output to replace GenOnly workflows #19853
Conversation
A new Pull Request was created by @perrozzi for master. It involves the following packages: Configuration/Applications @perrotta, @monttj, @cmsbuild, @franzoni, @slava77, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
@perrozzi |
@slava77 I am not sure where to find a cmsDriver example for master/93X.
do you have suggestions? |
Comparison is ready Comparison Summary:
|
made its worth a bit of thought to first agree on the concept being proposed? [I say without really looking at this]
… On Jul 21, 2017, at 2:28 PM, Slava Krutelyov ***@***.***> wrote:
@fabozzi
please take a look at the new steps in cmsDriver and advise @perrozzi on how to add a matrix workflow for it.
Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
if not semi-blandly to ignore the diffs, need to rerun this after another IB. |
@davidlange6 sure, I can try to summarize here then we can discuss at the ORP meeting or else. In GEN we are often using GenOnly workflows (i.e. GEN step without SIM) to provide high statistics alternative samples to compare unfolded data and mc or validate new versions of the MC, for instance. Since we foresee very soon one of these such quick validation turn around to validate the latest and greatest GEN updates before to launch the 2017 v2 MC campaign, to count on central production GENOnly+MINIAODSIM workflows (saving only reduced MINIAODSIM output) will be very beneficial, I think. The validation can be carried on using the current 2016 MC campaign (71X+80X) so this feature is quite more urgent in 80X than master/93X, somehow. Let me know if you want to discuss more or would like to have further input. [*] https://hypernews.cern.ch/HyperNews/CMS/get/comp-ops/3623/1/1/1.html [**] The HepMC collection can be produced on the fly starting from the GenParticle collection, but in MINIAOD it is splitted and slimmed into PackedGenParticles and PrunedGenParticles to reduce disk space. |
@perrozzi the output data tier better be named MINIGEN or something like that, because "AOD" in the name seems inappropriate. |
please test |
The tests are being triggered in jenkins. |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
Hello, may I kindly ask to review this on time for tomorrow's ORP? I would really like to close this... |
+1 for #19853 3781f11
|
@perozzi : his PR only mosses the "analysis" signature; I can only sign for reco, and @slava77 already did six days ago |
merge |
created a new eventcontent
--eventcontent MINIAODGEN
and a new step
--step PATGEN
to allow MINIAODSIM from GenOnly datasets.
Useful for GEN validation and creation of alternative samples in central production with small event size.