-
Notifications
You must be signed in to change notification settings - Fork 94
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
Expose tight coupling to OperatorSnapshots
#1113
Expose tight coupling to OperatorSnapshots
#1113
Conversation
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 haven't been involved in this feature add, but this PR looks good to me!
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.
It's a small change. And I see its value.
I'd like the change more if it broke a test. Or we added a test to cover it.
I totally agree... Let me see if I can add/modify one. |
@albeanth Any progress? Or just thoughts on testing? |
Getting a decent test in is slightly tricky since |
You could just subclass You could also use |
…30/assembly-1d-parent-class * terrapower/main: Updating B4C docstring for assumed TD frac (terrapower#1117) bug fix for xsGroup manager w/ coupling (terrapower#1118) Add neutronics category to linPow parameter (terrapower#1119) Refactoring Material to not subclass Composite (terrapower#1062) Exposing tight coupling to `OperatorSnapshots` (terrapower#1113)
Description
PR #1033 introduced the capability to measure the convergence of tight coupling and removed the
looseCoupling
setting. However, its exposure to the snapshot operator was missed. This PR serves to resolve that.Checklist
doc/release/0.X.rst
) are up-to-date with any bug fixes or new features.doc
folder.setup.py
.