-
Notifications
You must be signed in to change notification settings - Fork 105
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
Solver: convergence failure in Cr-Ti-V #427
Comments
On closer inspection, it's not clear whether this is a solver failure or starting point failure. I noticed that we are adding composition sets with positive driving force before even running the solver. I printed out the chemical potentials just before add nearly stable and got: The starting point composition sets are:
These chemical potentials do seem to be correct w.r.t. the composition sets (i.e. |
Reproducing on Windows. |
Looks like
There's some kind of oscillation happening. Details:
|
There was no oscillation problem in the develop branch. I had made a mistake in some debugging code that accidentally changed the behavior. The issue may be a problem in some code that is supposed to accelerate the hyperplane calculation by throwing out metastable points: pycalphad/pycalphad/core/hyperplane.pyx Lines 241 to 247 in 04b870e
If I force that first branch to always be taken (
The assumption made in the accelerator code (that any point metastable at any particular iteration must be metastable at every subsequent iteration, and at the solution) may be incorrect, or maybe the assumption is being implemented incorrectly. Either way, it may be worth it to turn it off since it's counterproductive here. |
This test is a convergence failure for Cr-Ti-V in a three phase region. It seems to be representative of a class of convergence failures where a starting point of 3 or more phases sees one phase removed inside the solver, which gets added back by the global grid minimization, and this loop continues until the maximum number of global iterations are reached.
The test is below. I attached the TDB and the diff to patch this test and TDB directly in.
The output I'm seeing on current develop:
crtiv_fail.patch.txt
crtiv_ghosh.tdb.txt
The text was updated successfully, but these errors were encountered: