Hi Ram,
If you look here:
http://www.ctcms.nist.gov/fipy/INSTALLATION.html
you can see the requirements for installation. Gmsh is under
"optional".
On the mac you need to ensure that gmsh can be run from the command line
and that means making some minor modifications to your PATH environment
variable.
For example, I have my "Gmsh Application (Gmsh.app)" installed under
my FiPy directory, so,
I need to explicitly call out the path to the binary file: ./FiPy/
gmsh-2.2.0/Gmsh.app/Contents/MacOS
I would imagine that it is a very similar problem on Windows.
To test pysparse, however, all you need is a simple script and since
you already got
so many "OK"'s from the FiPy test, it looks like pysparse is probably
working.
Good luck!
Best,
Dan Lewis
On Nov 10, 2010, at 6:28 PM, Ram Balachandran wrote:
Thanks for the help Dan.
Ok. So I installed pysparse using the exe file and fipy using the
exe file again. I then tested fipy and found 8 failures among the
488 tests. The error message for all the failures was 'gmsh' is not
recognized as an internal or external command. I suppose this has
something to do with the gmsh module and relates to irregular
meshing. Is there a way to fix it? Is it absolutely essential to fix
it?
Thanks
Ram Balachandran.
On Wed, Nov 10, 2010 at 2:36 PM, Daniel Wheeler <[email protected]
> wrote:
On Wed, Nov 10, 2010 at 11:08 AM, Ram Balachandran
<[email protected]> wrote:
> Hello,
>
> I am new to python and hence pardon me if the questions are too
elementary.
> I have EPD 6.3.1 installed on my windows-32 bit machine.
Nothing wrong with your questions.
> I am trying to install PySparse (on my windows 32-bit) and I
downloaded the
> pysparse-1.1_rc1.win32-py2.6.exe file and ran it. I don't
understand how the
> exe file works. How is this different from running the setup.py
file that
> comes with unzipping the tar.gz files in the sourceforge.net
website.
It is similar to running "python setup.py install", but the the ".exe"
installer has prebuilt binaries so that you don't have to compile from
source, which is generally involved process. The end result should be
the same, a working copy of pysparse in site-packages.
> I
> tried 'import pysparse' at the interpreter command line and it
worked fine.
> Does that mean that I am good to go and can start using Pysparse.
Well, that is definitely a good sign. Try running the fipy tests and
see. When you unpack fipy go into to the directory in which you
unpacked it and run "python setup.py test". You will get some errors,
because of some missing dependencies, but most of the examples should
pass. If pysparse isn't working then virtually all the examples will
fail. Or simply write a toy 1D diffusion problem in FiPy and run it
and see if it solves.
> If not,
> how do I test pysparse to make sure that everything is alright.
>
> When I download the pysparse-1.1.1.tar.gz file and unzip it I see
a ton of
> folders that don't get generated when I run the executable. The
instructions
> for installation appear complex too. Can someone throw some light
on it.
> Your help will be greatly appreciated.
See if FiPy works, probably the best way to know. Don't worry about
the "tar.gz" if you have already installed with the the ".exe".
Cheers
--
Daniel Wheeler
Dan Lewis
Assistant Professor
Materials Research Center, Room 110
Rensselaer Polytechnic Institute
110 8th Street
Troy, NY 12180
[email protected]
518-276-2297
http://www.rpi.edu/~lewisd2
Skype: dan_lewis_at_rpi
Mobile: 518-321-4799
