Ian Bell
Ian Bell
In principle it is only a few minutes of work, if all goes to plan. > Message ID: ***@***.***> >
That's right, but the true Python interface does. I'm frankly surprised that the array inputs are not automatically converted. > Message ID: ***@***.***> >
You need to figure out how MATLAB goes the conversion; it seems it is converting to ``array.array`` but you want it to convert to ``numpy.array``.
Nope, this is a MATLAB "problem"; it should be converting to numpy arrays. Nothing we can do in CoolProp land. Already handling too many array conversion cases
Only thing I can think of is to use python
Does density work at that statepoint? Can you reproduce that failure outside the table generator?
You'll have to take it up with Mathworks then if it cannot be reproduced outside of the table generator
See information about loading the tables: http://www.coolprop.org/coolprop/Tabular.html#more-information I regret to inform that I don't have time to look into this, but you are welcomed to
You can use f strings, like this: ``f'REFPROP::R134a[{a}]&R245fa[{b}]')``. But this is a very(!) bad solution for speed because REFPROP will constantly get reloaded and the fluids initialized at each call...
I'm guessing you did not do a recursive clone? It is ok, because you can now do a: git submodule init --recursive