On Apr 7, 2014, at 8:53 AM, Joakim Odqvist wrote:
> This is a real problem we have at the moment, and the "coeff" doesn't (as far
> as we can see) update itself.
> No, you are right, the specific solver shouldn't have any bearing on this
> problem I guess.
I apologize that it's taken me this
Från: fipy-boun...@nist.gov [mailto:fipy-boun...@nist.gov] För Guyer, Jonathan
E. Dr.
Skickat: den 7 april 2014 14:43
Till: FIPY
Ämne: Re: Solving the Cahn-Hilliard equation
On Apr 7, 2014, at 4:42 AM, Joakim Odqvist wrote:
> If the default solver (trilinos LinearGMRESSolver) is used we fi
On Apr 7, 2014, at 4:42 AM, Joakim Odqvist wrote:
> If the default solver (trilinos LinearGMRESSolver) is used we find that the
> mobility/diffusion coefficient and the thermodynamic factor is only evaluated
> at the beginning of the time-step which causes numerical instabilities if
> these ha
-Ursprungligt meddelande-
Från: fipy-boun...@nist.gov [mailto:fipy-boun...@nist.gov] För Guyer, Jonathan
E. Dr.
Skickat: den 24 mars 2014 20:40
Till: FIPY
Ämne: Re: Solving the Cahn-Hilliard equation
Hi Joakim -
On Mar 23, 2014, at 7:16 PM, Joakim Odqvist wrote:
> All these samples prod
Hi Joakim -
On Mar 23, 2014, at 7:16 PM, Joakim Odqvist wrote:
> All these samples produce different results (where code1.py is the correct).
> In order to get the coupling with the external thermodynamics package we need
> to use an approach that is shown in code3.py.
Are you sure code1.py
Hello all,
This question is related to the one posed by Thomas Barkar last week.
We are trying to solve the Cahn-Hilliard problem using thermodynamics and
mobilities obtained from external routines.
To illustrate the problem 3 sample codes are included.
In code1.py the expression for the thermo