Should we remove species properties (ex. diffusivity) from Phase object? #2685
ma-sadeghi
started this conversation in
Development
Replies: 1 comment
-
|
I agree completely, but the solution results in the code being significantly more confusing to use, so we remove one source of confusion, but add another. This is why we're stuck with what we have. Incidentally, the new 'Phase properties' functions and classes to support your proposed approach. But this would require everyone using mixtures, which is more complicated. Anyway, definitely worth discussion, and I'd love to hear from active users their thoughts on this thread too. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I think we should remove species properties such as
pore.diffusivityfromPhaseobjects. The reason is that it's very ambiguous. Of course, for binary mixtures, D12 = D21, but still, it's ambiguous forPhaseobject to have such property. It might make sense for aBinaryMixtureclass to havepore.diffusivityas a compromise.I propose the following:
Phaseobjects altogether, and by default useMixtureclass for mass transport problems.pore.propnamefor species properties altogether, and usepore.propname.Xinstead where X is the species name.PS. For backwards compatibility, we could still support
pore.diffusivity, and eventually get rid of it in v4.Beta Was this translation helpful? Give feedback.
All reactions