MultiApps problems with Subchannel Solver #30328
-
|
Hello, I am attempting to create a multiphysics model for a hexagonal lattice liquid-metal cooled microeactor, using BISON for heat conduction and Subchannel for the thermal hydraulics. I have been having issues with Subchannel not solving and throwing out errors when attempting to couple the two. For debugging purposes I have: 1) ensured that the linear heat rate (LHR) in BISON is identical to what is being sent to in Subchannel 2) successfully ran standalone Subchannel cases with constant and non-constant LHR and 3) ensured that the solutions in the standalone Subchannel make sense. At this point I believed it might have been a transfer issue but then attempted to run a multiapp but have no transfers done. This is to say that I had the working standalone subchannel model run as the child app of the BISON model. From what I understand this should effectively amount to having two physics modules run one after the other but with no transfers they are not connected. Since the standalone SC model works when not in MultiApp I figured it should work here as well but I run into the same error being thrown. This to me points to their being an issue with the timing of execution of some process within subchannel. I would appreciate any insight on this! Below are my inputs for the BISON model and the SC model. Note that for the SC model, I've also attempted to not use AuxKernels and set the initial conditions manually but it yielded the same error. Below is the error I get when attempting to run MultiApps: Below are my models for Bison and SC. Bison Model: SC Model |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 14 replies
-
We should let the solver survive this in hopes it recovers. Depending on the fluid properties and the enthalpy value at the reference temperature, negative does not always mean completely wrong |
Beta Was this translation helpful? Give feedback.
-
|
some initial comments:
3)Your solution tolerances (1.0e-2) are quite high. Try lowering them to 1e-4 or less.
Errors such as the one you are getting usually happen when we have very high power and relatively low mass-flow rate. Regarding Guillaume's suggestions. You have access to the source code, you can track these error messages and deactivate them, but I suspect that you will get some seg fault error when the solver tries to calculate FPs with negative enthalpy. |
Beta Was this translation helpful? Give feedback.
-
|
Can you check that the q_prime is what you would expect? |
Beta Was this translation helpful? Give feedback.
-
|
"m_dot is showing up to be zero after the first node when I run the MultiApp with no transfers": Thats correct. You set the boundary condition of massflow correctly and the initial massflow to zero. What's not good is that the solver doesn't solve so these values don't get updated by the solution. So when you are looking at the exodus file you see the initial values. Maybe you can compare the two versions of the problem (multiapp, standalone) to see if the BCs an ICs are the same? |
Beta Was this translation helpful? Give feedback.
-
|
ok so the petsc options are contaminating from the main app to the subapp. We'll fix this very soon, I'll have the patch ready this morning. For now you can only solve subchannel problems either:
|
Beta Was this translation helpful? Give feedback.


ok so the petsc options are contaminating from the main app to the subapp. We'll fix this very soon, I'll have the patch ready this morning. For now you can only solve subchannel problems either: