[go: up one dir, main page]

Skip to content
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

Merged
merged 5 commits into from
Jun 10, 2016
Merged

Conversation

fabozzi
Copy link
Contributor
@fabozzi fabozzi commented Jun 9, 2016
  • added 2016 relvals
  • same steps for all 2015 relvals
  • updated gensim recycling for 2017 relvals

@cmsbuild
Copy link
Contributor
cmsbuild commented Jun 9, 2016

A new Pull Request was created by @fabozzi for CMSSW_8_1_X.

It involves the following packages:

Configuration/PyReleaseValidation
DPGAnalysis/Skims

@cmsbuild, @srimanob, @davidlange6, @hengne, @fabozzi can you please review it and eventually sign? Thanks.
@ghellwig, @Martin-Grunewald this is something you requested to watch as well.
@slava77, @Degano, @smuzaffar you are the release manager for this.

cms-bot commands are list here #13028

@fabozzi
Copy link
Contributor Author
fabozzi commented Jun 9, 2016

please test

@cmsbuild
Copy link
Contributor
cmsbuild commented Jun 9, 2016

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/13452/console

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-14839/13452/summary.html

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

@fabozzi
Copy link
Contributor Author
fabozzi commented Jun 10, 2016

+1

@cmsbuild
Copy link
Contributor

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

@davidlange6
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit 949434f into cms-sw:CMSSW_8_1_X Jun 10, 2016
@mmusich
Copy link
Contributor
mmusich commented Jun 10, 2016

@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.

@mmusich
Copy link
Contributor
mmusich commented Jun 10, 2016

@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

@fabozzi
Copy link
Contributor Author
fabozzi commented Jun 10, 2016

@mmusich @franzoni I think it is good to have a working 2016 relval infrastructure merged in the release. We will handshake with Alca before submitting relvals to be provided to validators

@davidlange6
Copy link
Contributor

hopefully working includes also the GT:)

On Jun 10, 2016, at 11:08 AM, fabozzi notifications@github.com wrote:

@mmusich @franzoni I think it is good to have a working 2016 relval infrastructure merged in the release. We will handshake with Alca before submitting relvals to be provided to validators


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@mmusich
Copy link
Contributor
mmusich commented Jun 10, 2016

@davidlange6 technically speaking already works, but yields wrong results.
Incidentally when #14820 will be merge the problem is going to be mitigated, but I would definitely wait for the DPGs to udpate the 2016 IOVs (due in any case for the data re-reco) before releasing for validation.

@davidlange6
Copy link
Contributor

we have a different meaning of “works” then… but good if at least the prompt conditions are already about read to merge

On Jun 10, 2016, at 11:36 AM, Marco Musich notifications@github.com wrote:

@davidlange6 technically speaking already works, but yields wrong results.
Incidentally when #14820 will be merge the problem is going to be mitigated, but I would definitely wait for the DPGs to udpate the 2016 IOVs (due in any case for the data re-reco) before releasing for validation.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@@ -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)
Copy link
Contributor

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

@mmusich
Copy link
Contributor
mmusich commented Jun 10, 2016

@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?

@fabozzi
Copy link
Contributor Author
fabozzi commented Jun 10, 2016

@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?

@slava77
Copy link
Contributor
slava77 commented Jun 10, 2016

On 6/10/16 8:33 AM, fabozzi wrote:

@slava77 https://github.com/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?

A fraction of it is fine.
I just wanted to make sure that we exercise the CTPPS software with
realistic inputs in the matrix.

Once this settles, can you please add one 2016 workflow to the short matrix?

Thanks


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#14839 (comment), or
mute the thread
https://github.com/notifications/unsubscribe/AEdcblHf9WcYhoeX3BpzDKKrf9ucoE9Pks5qKYO_gaJpZM4IyfwO.

@fabozzi
Copy link
Contributor Author
fabozzi commented Jun 10, 2016

Il 10/06/16 17:50, Slava Krutelyov ha scritto:

On 6/10/16 8:33 AM, fabozzi wrote:

@slava77 https://github.com/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?

A fraction of it is fine.
I just wanted to make sure that we exercise the CTPPS software with
realistic inputs in the matrix.

Once this settles, can you please add one 2016 workflow to the short matrix?

Yes, sure

Francesco

Thanks


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#14839 (comment), or
mute the thread

https://github.com/notifications/unsubscribe/AEdcblHf9WcYhoeX3BpzDKKrf9ucoE9Pks5qKYO_gaJpZM4IyfwO.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#14839 (comment), or
mute the thread
https://github.com/notifications/unsubscribe/AEo3uyIoxdpGilBlOCHtIUxsB3L5xzmTks5qKYfMgaJpZM4IyfwO.

@fabozzi fabozzi mentioned this pull request Jun 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants