-
Notifications
You must be signed in to change notification settings - Fork 0
Handle scenario JSON with no point inputs and missing node/baseline data in IWFM output generation #16
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
Merged
Merged
Handle scenario JSON with no point inputs and missing node/baseline data in IWFM output generation #16
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
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.
Not addressing in this PR, but the mechanism is correct and worth recording.
GetIWFMHeadAllOutputFileresolves the file withDirectory.EnumerateFiles(resultsPath).Single(...), which throws when nothing matches, so a non-differential run with no*HeadAll.Baseline.outinResults/would throw here before any of the new guards run.Two qualifications:
developtoday; this PR only moved it inside the newifblock, which if anything narrows the exposure — a run with no point inputs now skips the baseline parse entirely.IsDifferential = trueon every run it submits, and GETEngine defaultsdata.IsDifferential ?? true(Functions.cs:278), so the baseline file is always expected on that path. This is only reachable for a non-differential run submitted from elsewhere.Leaving it out because it can't be verified from here: this repo has no CI, and restore needs the private
esadatatechnology/sitkatechfeed, which I can't reach — so a change to a path with no test coverage and no way to exercise it locally isn't one to land on top of a hand-off PR.The fix, for whoever picks it up:
That also avoids parsing a large head-all file on non-differential runs.