On May 6, 2011, at 10:55 AM, Julien Derr wrote:
> I was trying to run on a cluster, a program which is running fine on my
> computer.
> and I get the following error (see full error at the end)
>
> return self.distanceVar._cellInterfaceFlag * 1e+20
> AttributeError: 'DistanceVaria
Hi Everyone,
I am restarting an old question . I remind you, I was trying to run on a
cluster, a program which is running fine on my computer.
and I get the following error (see full error at the end)
return self.distanceVar._cellInterfaceFlag * 1e+20
AttributeError: 'DistanceVariable' objec
On Fri, Apr 1, 2011 at 5:57 AM, Julien Derr wrote:
> by test suite, which test do you mean ?
> i went on the "different computer" (a cluster)
I just mean running "python setup.py test" in the base fipy directory.
If you have an installed only version of FiPy then you obviously can't
do this.
>
On Apr 1, 2011, at 5:57 AM, Julien Derr wrote:
> by test suite, which test do you mean ?
I assume that Daniel meant `python setup.py test` on the entire installation,
but what you've done is probably enough information.
> i went on the "different computer" (a cluster)
>
> I went into the i
by test suite, which test do you mean ?
i went on the "different computer" (a cluster)
I went into the installation directory, in models/levelset, and I run the
test.py file , here is the result :
[jderr@iliadaccess02 electroChem]$ ls
gapFillMesh.py gapFillMesh.pyc __init__.py __init__.pyc
met
On Thu, Mar 31, 2011 at 12:14 PM, Julien Derr wrote:
> 1. If I understand well, the line you suggested to add, is setting a
> infinite (1E20) out flux at the phi=0 interface. this source term shouldn't
> be negative ??
It should have the right sign. Whatever that is. The wrong choice
should be
Hi Daniel,
thanks a lot, it seems to behave very well !!!
just two additional questions : the frist one to uderstand what is going on,
the second one more pragmatical
1. If I understand well, the line you suggested to add, is setting a
infinite (1E20) out flux at the phi=0 interface. this source
On Mon, Mar 28, 2011 at 1:38 PM, Julien Derr wrote:
> Hi Daniel,
>
> I was also thinking about two conditions :
>
> condition 1 : for the boundary of the diffusion of C
> instead of a condition on grad(c) like in the example, I was thinking of a
> condition on c directly : c=0 at the interface;
Hi Daniel,
I was also thinking about two conditions :
condition 1 : for the boundary of the diffusion of C
instead of a condition on grad(c) like in the example, I was thinking of a
condition on c directly : c=0 at the interface;
condition 2 : definition of the speed of the interface
instead of
On Mon, Mar 28, 2011 at 5:31 AM, Julien Derr wrote:
> Thanks Daniel for the fast answer as always.
>
> I am a bit confused :
> if I understood correctly, in this example, the boundary condition is that
> the normal component of the gradient of c is equal the velocity of the
> interface.
> and as
Thanks Daniel for the fast answer as always.
I am a bit confused :
if I understood correctly, in this example, the boundary condition is that
the normal component of the gradient of c is equal the velocity of the
interface.
and as you know the velocity of the interface (supposed to be propotional
On Tue, Mar 22, 2011 at 1:23 PM, Julien Derr wrote:
> Hi everyone!
> I didn't bother you for a long time! I am back!
Good to have you back.
> in the simpletrenchsystem.py example, I have a question about the boundary
> condition :
>
> metalEquation.solve(metalVar, dt = dt,
>
Hi everyone!
I didn't bother you for a long time! I am back!
in the simpletrenchsystem.py example, I have a question about the boundary
condition :
metalEquation.solve(metalVar, dt = dt,
boundaryConditions = metalEquationBCs)
metalequation BCs defines the boundary co
13 matches
Mail list logo
