Zodiac issueshttps://gitlab.multiscale.utah.edu/common/Zodiac/-/issues2017-11-20T14:28:56Zhttps://gitlab.multiscale.utah.edu/common/Zodiac/-/issues/3Add GPU configure flag to build system2017-11-20T14:28:56ZJames SutherlandAdd GPU configure flag to build systemWhen auto-building upstream libs, we need to allow GPU-enabled builds.When auto-building upstream libs, we need to allow GPU-enabled builds.James SutherlandJames Sutherlandhttps://gitlab.multiscale.utah.edu/common/Zodiac/-/issues/19Transport coefficients in new cantera are wrong2021-12-16T21:44:32ZJames SutherlandTransport coefficients in new cantera are wrong## Description of the problem
Transport coefficients (viscosity, thermal conductivity) calculated via PoKiTT are wrong. I've tracked this down to the `polyfit` function inside cantera where the species viscosities and thermal conductiv...## Description of the problem
Transport coefficients (viscosity, thermal conductivity) calculated via PoKiTT are wrong. I've tracked this down to the `polyfit` function inside cantera where the species viscosities and thermal conductivities are fit to polynomials. The inputs to that function are all consistent, but the function returns different polynomial coefficients in Zodiac and PoKiTT.
Strangely, `PoKiTT` doesn't show this problem. It gets the expected result.
I suspect that other downstream usage (Wasatch, ODT) will have the same problem.
Note that the `polyfit` function calls through to the `Eigen` library, which Cantera builds internally. `SpatialOps` also builds `Eigen` internally. However, since it is a header-only library, I don't see how we could get a clash there...James SutherlandJames Sutherland