-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to model mixtures of gases and liquids as well as CoolProp mixture back-end #472
Comments
Hi, enthalpy is a quantity with arbitrary reference point (there is no natural zero point). That means, if you want to compare enthalpies from different libraries, you should always use enthalpy differences subtracting a common reference point (temperature and pressure) from your enthalpy. Then these values should be roughly the same. TESPy uses simplfied ideal gas mixture rules for mixing different gases, CoolProp has more elborate routines, but they are quite fragile. Best |
Hi Francesco, thank you for the quick reply. I agree with you, the difference is what matters. As the enthalpies are identical between CoolProp and Tespy for the pure components, I assumed that Tespy was also using CoolProp for mixtures, which is then not the case. Back to the issue mentioned above. When comparing CoolProp and Tespy for a 50/50 propane/methane mixture defined above, the enthalpy difference is 63 kJ/kg with CoolProp and 39 kJ/kg with Tespy. That's far from a small difference (38 % less). |
Hmmm, that's unfortunate... Two thoughts towards CoolProp
Appart from that: I think the issue is, that the saturation temperature of ethane at those pressures is very likely higher than the actual temperature. TESPy will account for only liquid or only gaseous phase, a condensation correction is currently only available for water (for performance reasons I do not want to check all mixture species by default). We can create a new mixture routine, which can account for condensation for all species of a mixture. Once I find the time for it, I will have a look and try to figure something out. Slightly OT, but still relevant I think: We have validated mixture properties vs. Ebsilon Professional software, see https://github.com/KarimHShawky/Chemical-Exergy-in-TESPy/tree/main/validation/ebsilon. Those did match very good, also for higher pressure values at combustion, so I am wondering if they use the same property functions for mixtures as they are available through tespy. In that application condensation of water was relevant iirc. Finally, I suggest you upgrade to the latest version of TESPy soon, because the implementation with the condensation check for generic mixtures will not happen in the older version, and the latest version also has a lot of other improvements, which you might benefit from :). Have a nice weekend |
Thanks for the feedback. Here some additional elements regarding your comments.
Concerning your last remark regarding upgrading TESPy, I actually tried the latest version (0.7.1.post1), to check if maybe the problem was corrected there. But then I got an error on line 47, so I switched back to 0.6.3 (the error is linked to CoolProp). Here is the error message:
Code used for the calculations: from tespy.components import Sink, Source, HeatExchanger
from tespy.connections import Connection
from tespy.networks import Network
from neqsim.thermo import fluid, fluid_df, TPflash, PSflash, PHflash
import CoolProp.CoolProp as CP
nw = Network(fluids=['water', 'methane', 'propane'], T_unit='C', p_unit='bar', m_unit='t / h', v_unit='m3 / h', h_unit='kJ / kg', iterinfo=False)
# Defining components
pri_in = Source('Primary side inlet')
pri_out = Sink('Primary side outlet')
sec_in = Source('Secondary side inlet')
sec_out = Sink('Secondary side outlet')
he = HeatExchanger('heat exchanger')
# Defining connections
pri_he = Connection(pri_in, 'out1', he, 'in1')
he_pri = Connection(he, 'out1', pri_out, 'in1')
sec_he = Connection(sec_in, 'out1', he, 'in2')
he_sec = Connection(he, 'out2', sec_out, 'in1')
nw.add_conns(pri_he, he_pri, sec_he, he_sec)
#Gas side
pu = 80 #bara
Tu = 5 #°C
Td = 20 #°C
dpg = 0 # bar
#Water side
pin = 2.5 #bara
Tin = 55 #°C
Tout = 45 #°C
dpw = 0 #bar
Vdot = 50
# set design attributes
he.set_attr(pr1=(pin-dpw)/pin, pr2=(pu-dpg)/pu, ttd_u=Tin-Td, design=['pr1', 'pr2', 'ttd_u'], offdesign=['zeta1', 'zeta2', 'kA_char'])
pri_he.set_attr(fluid={'water': 1, 'methane':0, 'propane':0}, p=pin, T=Tin, design=['v'])
sec_he.set_attr(fluid={'water': 0, 'methane':0.2668, 'propane':0.7332}, T=Tu, v=Vdot, p=pu)
he_pri.set_attr(T=Tout, design=['T'])
nw.solve(mode='design')
nw.save('design_test')
print('Design: \nVdot (gas): {a:0.1f} m³/h'.format(a=sec_he.v.val), '\nT (gas), in: {a:0.1f} °C, out: {b:0.1f} °C'.format(a=sec_he.T.val, b=he_sec.T.val), '\nVdot (water): {a:0.1f} m³/h'.format(a=pri_he.v.val), '\nT (water), in: {a:0.1f} °C, out: {b:0.1f} °C'.format(a=pri_he.T.val, b=he_pri.T.val), '\nkA: {a:0.1f} W/K'.format(a=he.kA.val))
fluid_CP="methane[0.5]&propane[0.5]"
h_5_CP = CP.PropsSI('H','T', 5 + 273.15, 'P', pu * 10**5, fluid_CP)
h_20_CP = CP.PropsSI('H','T', 20 + 273.15, 'P', pu * 10**5, fluid_CP)
print('CoolProp: \nEnthalpy difference: {a:0.2f} kJ/kg'.format(a=h_20_CP/1000 - h_5_CP/1000))
dic_fluid_NS = {'methane':0.5, 'propane':0.5}
fluid_NS = fluid("srk")
for key in dic_fluid_NS.keys():
fluid_NS.addComponent(key, dic_fluid_NS[key], "mol/sec")
fluid_NS.setMixingRule("classic")
fluid_NS.setMultiPhaseCheck(True)
fluid_NS.setPressure(pu, "bara")
fluid_NS.setTemperature(5, "C")
TPflash(fluid_NS)
fluid_NS.initPhysicalProperties()
h_5_NS = fluid_NS.getEnthalpy("kJ/kg")
fluid_NS.setTemperature(20, "C")
TPflash(fluid_NS)
fluid_NS.initPhysicalProperties()
h_20_NS = fluid_NS.getEnthalpy("kJ/kg")
print('NeqSim: \nEnthalpy difference: {a:0.2f} kJ/kg'.format(a=h_20_NS - h_5_NS)) Have a nice weekend too! |
Okay, thank you for that example. That seems to actually be a bug in the software, I found a fix but have to make sure, it does not interfere with other things. I'll open a pull request for the fix and I'll let you know, when it is available. For the mixture properties: ethane is actually liquid at that pressure and that temperature, therefore the CoolProp and neqsim mxitures correctly take into consideration the partial evaporation when heating, tespy can only consider full or no evaporation in the mixture (the mixture properties are not built for liquid/gas mixtures for non pure fluids except water). I will also add a caution box to this section about it: https://tespy.readthedocs.io/en/main/modules/fluid_properties.html#tespy-fluid-properties-label. With the latest version of tespy it might however be possible to directly integrate the CoolProp mixture backend into your models, I will create a separate pull request for that as well. Another idea could be to creat the custom functions for generic liquid/gas mixtures, but this might take a little bit more time. Finally, if you are interested, you could look into integrating neqsim into tespy. The new fluid property wrapper classes allow to integrate your own fluid property databases... You might also want to look into that, if you want to put a little bit of time and effort in :). Thanks again for reporting! Best Francesco |
Dear Francesco, Thank you for the feedback. I appreciate the quick help! I'm not quite sure why you mentioned ethane. In the mixture I defined there is only methane and propane. But independently from that I agree, integrating neqsim into tespy would probably be the way. I looked into the page you linked, and it will require some time to get into the code of tespy. I was actually looking for a quick way to characterize my heat exchanger and that's how I came to tespy. As my heat exchanger is however not exactly the same as the one defined in tespy (mine is a mix of counter and cross flow, while in tespy it is a pure counter flow) I will invest the time I currently have in building a short model corresponding more precisely to my heat exchanger rather than in adding neqsim to tespy, for an approximate result in the end. However in the medium term I will come back to your suggestion (integration of neqsim) and give it a try! All the best! |
Hi @YoannUniKS, I misread that, thank you for clarifying! If you are running more detailed calculations on heat exchangers, we could try to see, if those calculations could be integrated in tespy's heat exchanger models (or add new models repsectively). It is not that difficult to add new components actually :). Have a nice weekend |
Issue with staring values for temperature (T0=0 Kelvin) resolved by #477 |
Dear Francesco, dear all,
I'm using Tespy to calculate a heat exchanger and I'm running into a strange behaviour. I'm using version 0.6.3 of Tespy. Below a code example which should reproduce the problem.
The heat exchanger has water on the one side, and gas on the other side. I'm checking the result of the specific enthalpy calculation in the output "connections" csv file. When the gas is pure the specific enthalpy is consistent with the results of CoolProp. When the gas is a mixture, then the results differ.
As examples of the specific enthalpy calculations of the gas (secondary side) from the code below:
I was wondering if I'm missing something or if the problem comes from Tespy.
I thank you in advance for the feedback.
The text was updated successfully, but these errors were encountered: