-
Notifications
You must be signed in to change notification settings - Fork 249
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
add option for higher-stat relval tests #937
Comments
A new Issue was created by @kpedro88 Kevin Pedro. @Dr15Jones, @perrotta, @dpiparo, @makortel, @smuzaffar, @qliphy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
@smuzaffar to confirm, if I request (using cms-bot test parameters relvals_opt) more events for standard workflows (that already have 10-event samples generated in IBs and PR tests), will the bot recognize that this is a "different" workflow that needs to be rerun in the IB as well, to provide the comparison? |
@kpedro88 , no , bot does not change the event numbers. We can add a separate test e.g. |
@smuzaffar okay, I think that would resolve this issue. |
we should come up with a list of workflows and default number of events for high-stats tests. Do you have any workflow in mind which I can use to test? |
35034.0 is the current Phase 2 baseline workflow. 11634.0 might be useful to have a Run 3 test for changes proposed with a shorter timescale. @cms-sw/upgrade-l2 should comment if they have other preferences. |
Default number of events, maybe 1000? This could be a configurable parameter of the |
@kpedro88 |
@kpedro88 , PR #1728 should allow to run
Note that as number of events should remain same for both baseline and PR, so it is not possible to change the evnets via Pr comment. |
#1728 has been merged and one should be able to request |
high stats relvals tests and comparisons are now supported |
Request from (cms-sw/cmssw#21701 (comment)):
This seems like a valid request to automate in-depth physics validation when needed for PRs. Most PRs won't need this.
One potential issue is that the high-stat samples would also be needed in the IB baselines. We could run them for all IB baselines, or just run them on-demand (somehow keeping track when they're already available so they don't get rerun unnecessarily).
We might want to limit this option to request high stats for a specific workflow, since most workflows may not need physics validation in any given case.
The text was updated successfully, but these errors were encountered: