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.
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.Impact
Enhanced flexibility.
The text was updated successfully, but these errors were encountered: