Repository navigation
Feat/batch skip existing - #155
Merged
Merged
Conversation
The batch runner classifies each case from files already in its folder: cases with a summary file or a live LSF job are skipped, cases staged without results are regenerated, new cases run. --dry-run prints the plan; a changed DesignMatrix row for a skipped case is flagged. The manifest marks skipped cases "existing"; --force still reruns all. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Only workbook cases without a folder are run. An existing folder is skipped: finished when model/<stem>.LOG ends with "Run completed", otherwise listed as unverified for the user to check. Removes the LSF query and the retry path. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
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.
No description provided.