-
Notifications
You must be signed in to change notification settings - Fork 106
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
Equilibrium fails to calculate, resulting in an IndexError #62
Comments
I received the TDB out-of-band since the OP cannot distribute it publicly. |
With
|
It looks like the problem may be with some code that implicitly assumes that |
Minimal test case which fails with the same error on develop: def test_eq_issue62_last_component_not_va():
"""
VA is not last when components are sorted alphabetically.
"""
test_tdb = """
ELEMENT VA VACUUM 0.0000E+00 0.0000E+00 0.0000E+00!
ELEMENT AL FCC_A1 2.6982E+01 4.5773E+03 2.8322E+01!
ELEMENT CO HCP_A3 5.8933E+01 4.7656E+03 3.0040E+00!
ELEMENT CR BCC_A2 5.1996E+01 4.0500E+03 2.3560E+01!
ELEMENT W BCC_A2 1.8385E+02 4.9700E+03 3.2620E+01!
PHASE FCC_A1 % 2 1 1 !
CONSTITUENT FCC_A1 :AL,CO,CR,W : VA% : !
"""
equilibrium(Database(test_tdb), ['AL', 'CO', 'CR', 'W', 'VA'], ['FCC_A1'],
{"T": 1248, "P": 101325, v.X("AL"): 0.081, v.X("CR"): 0.020, v.X("W"): 0.094}) |
richardotis
added a commit
that referenced
this issue
Jan 7, 2017
bocklund
added a commit
to bocklund/pycalphad
that referenced
this issue
Aug 17, 2021
* FIX: Fix incorrectly sized pycalphad P/T/points arrays for MCMC thermochemical error * TST: Includes tests for 3 datasets with varying X, T, T and X * FIX: Fix error where SymPy NaNs in calculate_activity_error would raise in emcee (convert them the NumPy NaNs)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following code example fails to calculate with the given database. The database is known to work as tested in other software.
The traceback for this is as follows
This was also confirmed using each phase individually and in another database and the same conditions, so it does not seem to be a problem with how any one specific model is represented.
This is on the develop branch, commit a518e1a
The text was updated successfully, but these errors were encountered: