forked from E3SM-Project/E3SM
-
Notifications
You must be signed in to change notification settings - Fork 7
Omega/add eos clamp #293
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
Open
alicebarthel
wants to merge
7
commits into
E3SM-Project:develop
Choose a base branch
from
alicebarthel:omega/add-eos-clamp
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+403
−17
Open
Omega/add eos clamp #293
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
13b1d61
added p,T,S limits (with CtFreezing calc) to eos Poly75t with a check…
alicebarthel 645f108
adds test for eos clamping
katsmith133 30c5666
adds lower bounds clamping test for temperature
katsmith133 3f00564
switched clamping to an option, and eos limits has 2 options
alicebarthel 4ee8e9a
added a setClamping method to toggle the Clamping option for the rele…
alicebarthel 0ab6d7c
updated the documentation and added T,S warnings
alicebarthel 3a84e53
added documentation on internal helper functions for developers
alicebarthel 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
Some comments aren't visible on the classic Files Changed page.
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
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
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
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
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.
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.
Change to ABORT_ERROR
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.
Thanks. Out of curiosity, is the use case for LOG_ERROR when it's an error but we don't want to exit? Can you think of a use case for it?
I understand that ABORT_ERROR is the most appropriate to exit when encountering a critical error?
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.
Yes, once we created the Error handler, some of the LOG macros are superseded (though the Error handler uses the LOG macros underneath). You can still use LOG_ERROR to write a message with an error prefix to the log and not abort/return. A possible use case might be when you have a lot of information to write and multiple messages might be cleaner than a single large message with multiple lines. And yes, ABORT_ERROR is preferred for critical errors. I've been going through and replacing LOG macros with ERROR macros when I can but haven't made it up to the ocn directory yet and just happened to see these.