-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
No longer require single Closures to be supplied to flow channels #29594
Labels
C: Modules/Thermal Hydraulics
Tickets pertaining to the thermal_hydraulics module
T: task
An enhancement to the software.
Comments
joshuahansel
added a commit
to joshuahansel/moose
that referenced
this issue
Jan 10, 2025
joshuahansel
added a commit
to joshuahansel/moose
that referenced
this issue
Jan 23, 2025
joshuahansel
added a commit
to joshuahansel/moose
that referenced
this issue
Jan 27, 2025
joshuahansel
added a commit
to joshuahansel/moose
that referenced
this issue
Jan 27, 2025
The average wall temperature material required an average wall heat transfer coefficient material, but this quantity can be computed directly from the other parameters, so the parameter was removed to ease requirements of the material. Refs idaholab#29594
joshuahansel
added a commit
to joshuahansel/moose
that referenced
this issue
Jan 27, 2025
joshuahansel
added a commit
to joshuahansel/moose
that referenced
this issue
Jan 27, 2025
joshuahansel
added a commit
to joshuahansel/moose
that referenced
this issue
Jan 28, 2025
Re-opening until |
joshuahansel
added a commit
to joshuahansel/moose
that referenced
this issue
Jan 31, 2025
joshuahansel
added a commit
to joshuahansel/moose
that referenced
this issue
Jan 31, 2025
5 tasks
tophmatthews
pushed a commit
to tophmatthews/moose
that referenced
this issue
Mar 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C: Modules/Thermal Hydraulics
Tickets pertaining to the thermal_hydraulics module
T: task
An enhancement to the software.
Motivation
The flexibility of the Closures system could be increased by not requiring each Closures object to supply all of the necessary closures. For example, one could do this:
This allows Closures classes to be more natural, since they don't need to have a combination of types of closure relations.
Design
The
closures
parameter inFlowChannelBase
will now correspond to a vector of Closures names, and it will be optional, defaulting to empty. Then all of the places using it will loop over the provided closures.Closures1PhaseNone
Impact
Enhanced flexibility.
The text was updated successfully, but these errors were encountered: