-
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
Fix tracked nEvents parameter in ExternalLHEProducer (73x) #5818
Conversation
…purious run transitions in production samples
+1 |
Fix tracked nEvents parameter in ExternalLHEProducer (73x)
Hello @bendavid , since we don't have an ETA yet for the changes in wmagent which will allow this transition on the CMSSW side (https://hypernews.cern.ch/HyperNews/CMS/get/wmDevelopment/642/1/1/1/1/1.html) While there's no plans of GEN-SIM with 73x, Ciao, |
Things have been actually set in motion on the wma side: https://hypernews.cern.ch/HyperNews/CMS/get/wmDevelopment/642/1/1/1/1/1/1.html At some point (~ next week) we'll receive a call from @amaltaro /ops to place a request with nEvents set to untracked. @bendavid, @srimanob @boudoul : can we think of using 73x for a GEN-SIM test request injection ? |
@franzoni, since we said we wanted this fixed before we start the 71x wmlhe campaign, an alternative could be to backport it to 71x, and create the RunIIFall14wmLHE campaign which will anyways be needed. It is sufficient to test this with only a wmLHE request btw, so we can also just create the dummy campaign (or move one of the existing wmlhe test campaigns to 7_3_0_pre1). wmLHE production has been privately tested in 73x with existing gridpacks, so we could quickly submit a test request there. |
We should also tested an old/unfixed release on the testbed to make sure it is really working with both the tracked and untracked parameter. |
nEvents changes were applied to ReqMgr in cmsweb-testbed, could you guys please inject a couple of requests? Should we follow up it here or in the HN thread? Thanks |
This is the proper solution for the issue discussed in
https://hypernews.cern.ch/HyperNews/CMS/get/dataopsrequests/5669.html
By making the nEvents paramter untracked, the spurious run transitions should be avoided.