-
Notifications
You must be signed in to change notification settings - Fork 68
Era by run #5026
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
Era by run #5026
Conversation
5414b15 to
dfbc29f
Compare
|
Deployed a replay with this patch and runs 380128, 382686, 386925. See ReplayOfflineConfiguration.py Era @germanfgv @jeyserma what do you guys think of this solution? |
95d6866 to
6000877
Compare
6000877 to
2174a75
Compare
be23ddf to
21cd35a
Compare
|
Hello @jeyserma this patch has correctly changed era provided a specific limit run. Could you please have a look at the code? |
| thresholdRuns = list(tier0Config.Global.AcquisitionEra['maxRun']) | ||
| caseRun = max(thresholdRuns) | ||
|
|
||
| if run <= caseRun: |
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.
caseRun is not defined when maxRun is not defined. I suggest setting a default for caseRun to 999999; or take the default acquisition era when maxRun does not exist.
|
Thanks Antonio. Apart from 1 comment, the PR looks good to me. Can you also add in the prod/replay some comments on how it should be used? I.e., you can only append new ERAs, and the one with the maximum run will be taken into account; the rests gets ignored but kept for bookkeeping reasons. I also think it will affect ERA extraction on the nodeSummary page? |
6df6881 to
71ffd88
Compare
|
Hello @jeyserma I have updated the changes and tested them successfully. Please review and merge when ready |
|
Looks good, merging now |
Proposal to change era after a specified run value.