You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ionic two-sublattice model (I2SL) exists in the DAT format with the code SUBI. I believe this model is supported already for TDB databases, so I'm hopeful that adding support for DAT databases wouldn't be too much work.
I2SL (SUBI) support was added to Thermochimica recently, I should be able to help answer any questions about DAT formatting for this model.
The text was updated successfully, but these errors were encountered:
A couple of things here. These were written by the OpenCalphad TDB->DAT converter, which inserts comments after phase names. I had trouble parsing those comments in pycalphad, so I just manually deleted them when using these files.
More relevant to this issue, you will notice that endmembers corresponding to the neutral constituents in I2SL phases get repeated in the DAT. There are #cations copies of each neutral. I suspect that FactSage couldn't handle unpaired constituents on the second sublattice, so made copies of the neutrals such that they could be paired to cations. Note also that the stoichiometry of the neutral endmember is scaled by the charge of the cation it is paired with.
In Thermochimica I discard all the redundant neutral endmembers, and divide the stoichiometry of the one I keep by the cation charge, so that I2SL can be used as written in Bosse's paper. I'd guess you want to do the same.
The ionic two-sublattice model (I2SL) exists in the DAT format with the code SUBI. I believe this model is supported already for TDB databases, so I'm hopeful that adding support for DAT databases wouldn't be too much work.
I2SL (SUBI) support was added to Thermochimica recently, I should be able to help answer any questions about DAT formatting for this model.
The text was updated successfully, but these errors were encountered: