Enable turning convective heat transfer on/off for big coupled runs #15421
Assignees
Labels
C: Modules
P: normal
A defect affecting operation with a low possibility of significantly affects.
T: task
An enhancement to the software.
Comments
andrsd
added
T: task
andrsd
added a commit
to andrsd/moose
that referenced
this issue
Jun 8, 2020
By default, the scale factor is 1. But a sub-app can transfer the scale factor as a field variable and then the total heat flux would be multipled by it. This can be used for turning the BC on/off based on geometrical location. Closes idaholab#15421
andrsd
added a commit
to andrsd/moose
that referenced
this issue
Sep 9, 2020
By default, the scale factor is 1. But a sub-app can transfer the scale factor as a field variable and then the BC can be turned on/off based on geometrical location. Refs idaholab#15421
andrsd
added a commit
to andrsd/moose
that referenced
this issue
Oct 8, 2020
By default, the scale factor is 1. But a sub-app can transfer the scale factor as a field variable and then the BC can be turned on/off based on geometrical location. Refs idaholab#15421
loganharbour
pushed a commit
to loganharbour/moose
that referenced
this issue
Oct 29, 2020
By default, the scale factor is 1. But a sub-app can transfer the scale factor as a field variable and then the BC can be turned on/off based on geometrical location. Refs idaholab#15421
jain651
pushed a commit
to jain651/moose
that referenced
this issue
Apr 19, 2021
By default, the scale factor is 1. But a sub-app can transfer the scale factor as a field variable and then the BC can be turned on/off based on geometrical location. Refs idaholab#15421
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reason
When running microreactor full core simulations, we have thousands of heat pipes running as sub-apps coupled to the master app running heat conduction in a 3D domain. We want to investigate the effect of a failed heat pipe (or cascading failure of heat pipes) on the full run/final solution. To enable this we, need to be able to turn off heat exchange between a single instance of the heat-pipe simulation and the 3D domain.
Design
Add a new coupled variable to
CoupledConvectiveHeatFluxBCthat will indicate if the BC is operational. Turning 'enable' on/off is not possible, since we want to have just one instance of the BC handling all the heat transfer. Having thousands instances of the BC would be meshing and input file disaster.Impact
Gain capability.
The text was updated successfully, but these errors were encountered: