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
Duplicate Species name error when parsing FactSage DAT into Database #425
Comments
I can reproduce this, thanks for the excellent report. For TDB files, it's always been safe to assume In light of this example, it is not obvious to me what My thinking is that we have to make the calling code responsible for managing case. I'm working through the implications of this for the parsers now. The DAT parser will need to work around the assumption that |
This may be a use case for semantic typing, i.e., say |
This is related to #419, with the core issue being that species names are basically cosmetic in DAT files |
#426 should fix the present issue, though it leaves the core issue mentioned above unresolved. It should be enough to move forward with this database, at least. |
When trying to parse in a DAT file which uses Cobalt 'Co' as system component and contains carbon monoxide 'CO' as gas phase, then a ValueError for using duplicate species name will be raised:
This bug has been found while trying to parse exported DAT files from FactSage 6.2.
This has been tested under Python 3.9 and pycalphad 0.10.1.
I've attached a zip file containing a minimal DAT file, a script for reproducing the error and a list of packages versions, in case that's needed.
script.zip
The text was updated successfully, but these errors were encountered: