Ian,
I have CoolProp and the low level interface working on Mac OS X 10.11. Haven't figured out the issue in the Windows environment yet, but will keep working on that.
One reason I want to go to this method was due to computation errors in the saturation region where the internal CoolProp solver was failing because it was iterating internally to a value below the saturation temperature causing an error to a temperature which was too low. The input temperature was at the saturation condition, but when solving, the internal routine was iterating to solve for enthalpy from and input of Q and T.
To ensure I benefit most from the low level tabular interpolation, I want to ensure I am properly using it.
The Tabular Interpolation page says:
"It is critical that you try to only initialize one AbstractState instance and then call its methods. The overhead for generating an AbstractState instance when using TTSE or BICUBIC is not too punitive..."
For the Matlab example provided on CoolProp's website which you pointed me to earlier, the script loads the library if not loaded, initializes points, uses the AbstractState_factory to set the handle, and then calls the library function to calculate the values.
Is the AbstractState_factory the instance to call only once or is there some other aspect to this I am missing?
For instance, are you saying to avoid the scenario where I put that entire Matlab example code into a function and then call that function 10000 times thereby checking for library, setting AbstactState_factory, and calling the library function 10000?
Instead, the AbstractState_factory would be called outside of the function and only the library function is called in the function 10000 times? Does that method work when you have many functions and functions of functions calling the same Coolprop library function?
Regards,