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
This is somehow similar to the film field (= wave + base film) in the four-field solver. More generally, a liquid field could be added to the three and four-field solver. Then, a generic mixture field could be applied to any of the multi-field solver.
An AbstractMixture is now the superclass of Mixture.Mixture and the new ThreeField.Mixture. Many of the Mixture.Mixture methods are transfrerred over to AbstractMixture, but @lecorrejm should take a look if there are mistakes in the process. ThreeField.Mixture is constructed using a Mixture.Mixture and a new class, ThreeField.Liquid. ThreeField.Liquid acts as an interface that represents the film and drop fields in the ThreeFieldSolver.
Main comment: At this point, there should not be any dependency between the new mixture field and the solver solution.
Hence, the solver should still rely on the solution from the mixture solver when needed. Use of this new mixture field in the solution will be done later case by case.
Additional comments:
New commit updated the new liquid class within the three-field solver. Correct definitions of VF, U, H, etc have been included.
The flowrate of the liquid in the three-field solver at node 1 is initialized with a a very large value.
The new abstract mixture class does not need to include properties and methods that are exclusively related to the mixture solver, that is, Properties: TRELAX, relaxtevap, relaxtcond, Methods: RELAXEVAP, RELAXTCOND, WWALL, MINT, MINTEVAP, MINTCOND, MTRANSV, WALEVAPRATIO, MWALEVAP, MTOT, HINT, HINTEAP, HINTCOND, HWALEVAP.
Activity
lecorrejm commentedon May 6, 2025
This is somehow similar to the film field (= wave + base film) in the four-field solver. More generally, a liquid field could be added to the three and four-field solver. Then, a generic mixture field could be applied to any of the multi-field solver.
feat(#79): create abstractMixture class
feat(#79): add ThreeField.Liquid to combine drop and film
feat(#79): start implementing ThreeFieldSolver Mixture
feat(#79): implement threefield solver-specific mixture for solver.solve
jasonjan2003 commentedon Jul 15, 2025
An
AbstractMixtureis now the superclass ofMixture.Mixtureand the newThreeField.Mixture. Many of theMixture.Mixturemethods are transfrerred over toAbstractMixture, but @lecorrejm should take a look if there are mistakes in the process.ThreeField.Mixtureis constructed using aMixture.Mixtureand a new class,ThreeField.Liquid.ThreeField.Liquidacts as an interface that represents the film and drop fields in theThreeFieldSolver.lecorrejm commentedon Jul 16, 2025
Thanks! I will have a look the week of August 4.
Note that the same Mixture class should also be available for the twofluid and fourfield solvers.
lecorrejm commentedon Oct 10, 2025
Main comment: At this point, there should not be any dependency between the new mixture field and the solver solution.
Hence, the solver should still rely on the solution from the mixture solver when needed. Use of this new mixture field in the solution will be done later case by case.
Additional comments:
fix(#79): move mixture solver-specific properties and methods back to…
jasonjan2003 commentedon Oct 14, 2025
Is this something that should be changed?
fix(#79): revert use of tfSolver.mixture to re-eval initialization issue
fix(#79): move mixture for multi-field solver to smix property