Skip to content
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

Open
joshuahansel opened this issue Dec 20, 2024 · 0 comments
Open

No longer require single Closures to be supplied to flow channels #29594

joshuahansel opened this issue Dec 20, 2024 · 0 comments
Assignees
Labels
C: Modules/Thermal Hydraulics Tickets pertaining to the thermal_hydraulics module T: task An enhancement to the software.

Comments

@joshuahansel
Copy link
Contributor

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:

closures = 'my_friction_closures my_heat_transfer_closures'

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 in FlowChannelBase 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.

@joshuahansel joshuahansel added T: task An enhancement to the software. C: Modules/Thermal Hydraulics Tickets pertaining to the thermal_hydraulics module labels Dec 20, 2024
@joshuahansel joshuahansel self-assigned this Dec 20, 2024
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.
Projects
None yet
Development

No branches or pull requests

1 participant