Update link for correct DV versions in rerun-stripping.md - #329
Merged
Conversation
…erun-stripping.md
mick-mulder
marked this pull request as ready for review
November 20, 2025 09:40
Contributor
|
as discussed probably there is a cleaner solution as LbMCSubmit changes various things from stage0 to stage6 on the fly and this may not be the full truth in this file, but at least this is an improvement for now until we find a better way. Just brainstorming, but one could add a test at https://gitlab.cern.ch/lhcb-simulation/lbmcsubmit/-/tree/main/tests/references so one could have a sim10/sim09 which runs on every stripping version available so one could point directly to a stage6 that includes the current versions. Then one could add some curl+grep command to output immediately what an analyst is looking for. but maybe this is also overkill. |
mick-mulder
changed the title
Contributor
|
ping @AndyLHCb |
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As figured out by @jpwgnr and @chrisburr, the previous link to processing passes was technically correct in that it refers to the DV version used for each stripping campaign. However, to currently rerun a stripping (e.g. in AnalysisProductions), the patched DV version should be used, as updated in the LbMCSubmit repository.