Add two drafts for humid air handling#1
Open
fwitte wants to merge 79 commits into
Open
Conversation
…ty and heat capacity
…suming constant temperature
…f there is nothing from the previous simulation
…in a multiprocess environment and avoids having to handle temporary files.
…in a multiprocess environment and avoids having to handle temporary files.
…to feature/humid-air-connection
… for droplets in pipe flow or for condensate removal and frost formation.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This implements two different possibilities of handling the
HAPropsSIinterface of CoolProp.HumidAirConnectionwith the humidity ratiowas additional variable and handling the fluid property calls on the connection instance. While it is nice, that the humidity ratio is explicitly exposed the main problem is, that the fluid property calls which do not go through aConnectioninstance (e.g. callingT_mix_phfrom inside a component like theMovingBoundaryHeatExchanger) need to be handled separately and not really in a nice way.mixing_rule"humidair"that callsHAPropsSIby calculating the humidity ratiowfrom the given fluid mass fractions in the fluid vector of a connection. With this the user has to calculate the mass fraction dictionary for the fluid specification before specifying it to the connection, but that could also be done through a method I think. So I do much prefer this solution.Given, that 2 is the preferred solution, there are two relevant changes:
An example is available in https://github.com/CHPApS/tespy/blob/cd17f164ac9f3020d99f5311c95a3638f8a98498/tests/test_tools/test_fluid_properties/humidair.ipynb