Using DiabaticCombustionChamber with BICUBIC/TTSE backend

[NilsBarner]

Good morning,

I would like to integrate the tespy DiabaticCombustionChamber module into another python library, for which the default implementation using the HEOS backend is prohibitively slow. From my own experience, switching to the BICUBIC/TTSE backend should do the trick, however, the simple example below returns ValueError: inputs are not in range, p=6340.41 Pa, T=298.15 K, because the tabular backends in CoolProp do not extend below the triple-point (of nitrogen in this particular case).

As none of the partial pressures should actually be below the triple-point pressure of nitrogen, I suspect this is due to some tespy-internal solver being out of bounds. Could you either suggest a fix to this approach of speeding up the below example, or propose an alternative? Interestingly, the PyromatWrapper with ideal gas backend is even slower than HEOS...

Finally, because I want to integrate the tespy DiabaticCombustionChamber module into another python library, I would like to turn off all printouts, both the console and to any log files. Is there a top-level command for this or do I have to uncomment all instances of logger in the tespy src folder (as I have done)?

Thank you for your help, best wishes,
Nils

from tespy.networks import Network
from tespy.components import (
    DiabaticCombustionChamber, Turbine, Source, Sink, Compressor
)
from tespy.connections import Connection, Ref, Bus
from tespy.tools.fluid_properties.wrappers import PyromatWrapper

nw = Network(p_unit="bar", T_unit="C")
cc = DiabaticCombustionChamber("combustion chamber")
air = Source("air source")
fuel = Source("fuel source")
fg = Sink("flue gas sink")

#%%

c2 = Connection(air, "out1", cc, "in1", label="2")
c3 = Connection(cc, "out1", fg, "in1", label="3")
c5 = Connection(fuel, "out1", cc, "in2", label="5")
nw.add_conns(c2, c3, c5)

#%%

c2.set_attr(
    p=1, T=20, m=1,
    fluid={"HEOS::N2": 0.78, "HEOS::O2": 0.21, "HEOS::H2O": 0.01},  # OR
    # fluid={"BICUBIC&HEOS::N2": 0.78, "BICUBIC&HEOS::O2": 0.21, "BICUBIC&HEOS::H2O": 0.01},  # OR
    # fluid={"ig::N2": 0.78, "ig::O2": 0.22},#, "ig::H2O": 0.01},  # AND
    # fluid_engines={"N2": PyromatWrapper, "O2": PyromatWrapper}#, "H2O": PyromatWrapper}
)
c5.set_attr(p=1, T=20,
    fluid={"HEOS::H2": 1},  # OR
    # fluid={"BICUBIC&HEOS::H2": 1},  # OR
    # fluid={"ig::H2": 1},  # AND
    # fluid_engines={"H2": PyromatWrapper}
)

#%%

cc.set_attr(pr=0.97, eta=0.98, lamb=None)
c3.set_attr(T=1250)
nw.solve(mode="design")

[fwitte]

Good morning @NilsBarner

you can import the logger and change the file and screen log levels:

from tespy.tools.logger import define_logging
Import logging


define_logging(screen_level=logging.ERROR, file_level=logging.ERROR)

Would that help? I have to check myself, how to entirely shut it down...

To your other question: pyromat is slower because its backwards methods are super slow (ph calls, which are the one most often accessed by tespy). I was not aware before implementing it. Maybe thermopack could be of help, but we need to implement a wrapper for that first (may not be too difficult). Or you could generate the lookup tables yourself from HEOS and then use lookup tables in a custom wrapper? We can talk about this topic and make a meeting, if you want.

Best

Francesco

[NilsBarner]

Good morning Francesco,

Thank you for your prompt reply and suggestions. Turning off all printouts via the logger should work. I will give some thought as to how to combine the BICUBIC/TTSE backends with a custom lookup table of HEOS/REFPROP results below the triple-point.

Best wishes,
Nils