-
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
Relval matrix updates #14839
Relval matrix updates #14839
Conversation
- added 2016 relvals
- same steps for all 2015 relvals
- updated gensim recycling for 2017 relvals
A new Pull Request was created by @fabozzi for CMSSW_8_1_X. It involves the following packages: Configuration/PyReleaseValidation @cmsbuild, @srimanob, @davidlange6, @hengne, @fabozzi can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
please test |
The tests are being triggered in jenkins. |
Comparison is ready The workflows 134.911 have different files in step1_dasquery.log than the ones found in the baseline. You may want to check and retrigger the tests if necessary. You can check it in the "files" directory in the results of the comparisons |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_1_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar |
+1 |
@fabozzi, the discussion with @Martin-Grunewald at #13819 made me realise that due to the snapshot features the 2016 data relvals will consume wrong conditions. |
@fabozzi @hengne @davidlange6 would it be possible to wait for a refresh of the GT snasphots before sending the RelVals production for this cycle? @franzoni |
hopefully working includes also the GT:)
|
@davidlange6 technically speaking already works, but yields wrong results. |
we have a different meaning of “works” then… but good if at least the prompt conditions are already about read to merge
|
@@ -183,6 +183,22 @@ | |||
steps['RunSinglePh2015D']={'INPUT':InputInfo(dataSet='/SinglePhoton/Run2015D-v1/RAW',label='sigPh2015D',events=100000,location='STD', ls=Run2015D)} | |||
steps['RunZeroBias2015D']={'INPUT':InputInfo(dataSet='/ZeroBias/Run2015D-v1/RAW',label='zb2015D',events=100000,location='STD',ib_block='38d4cab6-5d5f-11e5-824b-001e67ac06a0',ls=Run2015D)} | |||
|
|||
#### run2 2016B #### | |||
# Run2016B, 25ns: 274160 | |||
Run2016B=selectedLS([274160],l_json=data_json2016) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it possible to pick a run with CTPPS included?
274094 LS>151 or 274199 full
@davidlange6 #14842 is a temporary solution to avoid crazy output in relvals, @franzoni and I will take care of removing the keys once the standard re-reco GT is fully up-to-date. Is this a reasonable solution? |
@slava77 run 274199 contains more than double statistics w.r.t. what we usually run with data relvals. What about to run only on a subset of it? For instance, the first 250 lumisections? |
On 6/10/16 8:33 AM, fabozzi wrote:
A fraction of it is fine. Once this settles, can you please add one 2016 workflow to the short matrix? Thanks
|
Il 10/06/16 17:50, Slava Krutelyov ha scritto:
Yes, sure
|