-
Notifications
You must be signed in to change notification settings - Fork 235
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
Diagnostic tool to look for potential evaluation errors #1268
Merged
Merged
Changes from 8 commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
80fabcc
diagnostic tool to look for potential evaluation errors
michaelbynum 368b063
merge main into eval_error_detection
michaelbynum 8fb3b33
working on diagnostic tool to detect possible evaluation errors
michaelbynum 8b52c20
working on diagnostic tool to detect possible evaluation errors
michaelbynum 048dfd3
run black
michaelbynum 09bc21b
working on tests for evaluation error detection
michaelbynum 6f3cae0
working on tests for evaluation error detection
michaelbynum 2a135a1
run black
michaelbynum e9e8fc8
evaluation error detection
michaelbynum 246b92a
evaluation error detection
michaelbynum 2c5b36b
Merge branch 'main' into eval_error_detection
michaelbynum df094c5
fix pylint issues
michaelbynum 261b29e
run black
michaelbynum 6a1b57e
fix pylint issues
michaelbynum a8c0e0e
fix tests
michaelbynum 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 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.
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.
_collect_structural_warnings
and_collect_structural_cautions
methods? It looks like you did this for efficiency so you only need to walk the model once. However, there is anassert_no_structural_issues
method as well (that only checks for warnings) which could not include this as written (although the solution might be to just add this code there as well). I am also working on adding diagnostics to the convergence tester (parameter sweep) tool, and I am looking at using these methods there too (which would mean they need to become public).next_steps
as well pointing users to the associateddisplay
method.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.
I think I have addressed both of these now. I realized I was being silly with the cautions. They were completely unnecessary/wrong.