On Jan 22, 2014, at 1:42 AM, Phillip Feldman <[email protected]>
wrote:
> `python mesh2D.py --scipy` seems to be doing something. (At least, it is
> burning a lot of CPU). It would be very helpful if this code displayed an
> iteration counter or some other progress indicator.
The Cahn Hilliard problem runs a huge mesh when run directly; it will be slow.
Have you run any of FiPy's other examples? I would start with
examples/diffusion/mesh1D.py
> I patched my local copy of gmshMesh.py to make it display the offending
> version number:
>
> if gmshVersion < 2.0:
> raise EnvironmentError("Gmsh version must be >= 2.0. Actual version "
> "is %s." % str(gmshVersion))
>
> The above code reports version 0.
What does "gmsh --version" report at the command line? Alternatively, launch
the Gmsh GUI application and select "About Gmsh" from its menus.
_______________________________________________
fipy mailing list
[email protected]
http://www.ctcms.nist.gov/fipy
[ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ]
