You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Allow variations in coolant area in mixture solver #59
The geometry input should allow the definition of any axial variations in coolant area and perimeters.
Area and perimeters must then be considered as axially non constant in conservations equations solved in the solve method of the mixture solver class.
Extension to other solvers can be considered as a future step. However, one must think of how the liquid film is treated within the three and four-field solvers.
Thinking further about it, this is quite challenging to do it right.
I am reassigning to Jason and myself for now. Jason will allow the solver to handle geometrical arrays (area and perimeters), similar to how the heat fluxes are handled, and I will implement the new discretized equations.
How the film behaves at transitions should be user-specified. Perhaps a 0-1 coefficient to denote how much stays on the wall and how much becomes droplets, for example.
The more I think about this, the more I think we need to develop a more thorough plan before I implement the Geometry definition. I've move it to the v2026.1 project for now.
Activity
lecorrejm commentedon Nov 12, 2024
Thinking further about it, this is quite challenging to do it right.
I am reassigning to Jason and myself for now. Jason will allow the solver to handle geometrical arrays (area and perimeters), similar to how the heat fluxes are handled, and I will implement the new discretized equations.
jasonjan2003 commentedon Aug 31, 2026
I'll see about implementing geometrical arrays today
jasonjan2003 commentedon Aug 31, 2026
How the film behaves at transitions should be user-specified. Perhaps a 0-1 coefficient to denote how much stays on the wall and how much becomes droplets, for example.
jasonjan2003 commentedon Aug 31, 2026
The more I think about this, the more I think we need to develop a more thorough plan before I implement the Geometry definition. I've move it to the v2026.1 project for now.