Closed henryefranks closed 3 years ago
thermo module just got updated yesterday - they seem to have revamped the whole thing. That's likely what's causing the issue.
Ok, had a quick go at some drop-in replacements (ie using set_chemical_TP
instead of calculate
) but no dice. This might be a slightly more involved bug.
There is a note in Thermo.mixture Docs recommending switching to Thermo.flash but this seems to be not a straightforward transition. It needs to be decided whether it's worth doing, currently, the temporary fix is forcing Thermo to version 0.1.40
Updated bamboo so it no longer relies on thermo - the user needs to decide what they want to use to model transport properties.
I seem to get this error on two different machines, both running linux. It comes from the calls to
self.thermo_object.calculate
in cooling.py whenthermo_object
is an instance ofthermo.mixture.Mixture
, I think it's something to do with the thermo module installation but I'm not sure.