-
Notifications
You must be signed in to change notification settings - Fork 238
We should replace cantera.Species.fromCti() calls with cantera.Species.from_yaml() calls #2676
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Would this also require setting a new lower limit to the supported Cantera version inside the environment file? I assume that this new function has not been backported to all previous versions, and there would be some new cutoff. |
For a year now we have required Cantera 2.6, and |
This issue is being automatically marked as stale because it has not received any interaction in the last 90 days. Please leave a comment if this is still a relevant issue, otherwise it will automatically be closed in 30 days. |
The Python 3.9 upgrade is running into a challenge with Arm-Based Macs that could be solved by resolving this issue. The juliacall overhaul required with Python 3.9 does not work when running in x86 emulation mode on Apple Silicon, so we would rather run in ARM native. Cantera 2.6 does not have arm-osx builds, but the latest versions of cantera do. |
This issue is being automatically marked as stale because it has not received any interaction in the last 90 days. Please leave a comment if this is still a relevant issue, otherwise it will automatically be closed in 30 days. |
Updating the above comment - we can do the Python 3.9 upgrade w/o incrementing cantera, but not vice versa. Will try and get the Python 3.9 upgrade in first. What I previously said about the missing builds was wrong, we were looking in the wrong channel. Also important is that cantera 3.1.0 has a bug with reading surface files used in RMG. It has been resolved (Cantera/cantera#1845 (comment)) but not yet released (as of writing). |
Bug Description
The unit tests include the warning:
The relevant part of
RMG-Py/test/rmgpy/speciesTest.py
isWe should replace the
fromCti
block with afrom_yaml
block with a syntax a bit like this (this example is obviously a different species)Note the transportDataTest.py also has a fromCti call.
How To Reproduce
Run the unit tests, specifically
test/rmgpy/speciesTest.py
Expected Behavior
We wouldn't get deprecation warnings from Cantera.
The text was updated successfully, but these errors were encountered: