Hi Dave,
The script seems to work with the following changes.
4c4
< from fipy.meshes.grid2D import Grid2D
---
> #from fipy.meshes.grid2D import Grid2D
Problem here is that "from fipy import Grid2D" is not the same as "from
fipy.meshes.grid2D import Grid2D", which doesn't work correctly in
parall
On Tue, Jan 8, 2013 at 10:01 AM, dely wrote:
>
> In any case, the problem I described below goes away when I add "from fipy
> import *" to the beginning of my script. If possible, I would prefer to
> import the specific modules necessary to run in parallel rather than
> importing *. Are there spe
Thanks for pointing out the difference between the return types of "x,y =
mesh.cellCenters" and "x,y = mesh.cellCenters[0], mesh.cellCenters[1]". I was
unaware of that. I just realized that I was already using the nomenclature
recommended. In fact, my script fails entirely when using "x,y =
myM
On Dec 7, 2012, at 5:32 PM, dely wrote:
> I am writing to ask how to correctly use setValue with the where argument
> when running fipy in parallel. For example, to set the value of a
> cellVariable in a hemispherical region on the bottom boundary of a mesh, I
> can do the following:
>
> x, y
I am writing to ask how to correctly use setValue with the where argument when
running fipy in parallel. For example, to set the value of a cellVariable in a
hemispherical region on the bottom boundary of a mesh, I can do the following:
x, y = myMesh.cellCenters
myCellVar.setValue(1, where=((x -
