Our most current notion of how to install is captured [here](https://github.com/usnistgov/fipy/blob/develop/.travis.yml)
In short, on Mac OS: conda create --name <MYFIPYENV> --channel guyer --channel conda-forge python=2.7 fipy weave and on linux: conda create --name <MYFIPYENV> --channel guyer --channel conda-forge python=2.7 numpy scipy gmsh pysparse mpi4py matplotlib mayavi fipytrilinos weave and then for both: source activate <MYFIPYENV> pip install scikit-fmm Windows installations are covered [here](https://github.com/usnistgov/fipy/blob/develop/appveyor.yml), but basically you should be able to do the same as on Mac. > On Jul 20, 2018, at 10:21 AM, Carsten Langrock <langr...@stanford.edu> wrote: > > Ok, thanks for the information. I’ll try this again using python 2.7. > > _____________________________________ > Dipl.-Phys. Carsten Langrock, Ph.D. > > Senior Research Scientist > Edward L. Ginzton Laboratory, Rm. 202 > Stanford University > > 348 Via Pueblo Mall > 94305 Stanford, CA > > Tel. (650) 723-0464 > Fax (650) 723-2666 > > Ginzton Lab Shipping Address: > Astro-Physics Building, Rm. 148 > 452 Lomita Mall > > Ginzton Lab Freight Deliveries: > 491 South Service Road > _____________________________________ > > >> On Jul 20, 2018 at 06:38, <Jonathan E. Dr. (Fed) Guyer> wrote: >> >> FiPy should be installed with Python 2.7. We are aware that the >> documentation doesn't say this right now; getting the installation working >> smoothly and ensuring that all of the documentation describes the process >> completely and accurately is a non-trivial task. >> >> >> > On Jul 19, 2018, at 8:02 PM, Carsten Langrock <langr...@stanford.edu> >> > wrote: >> > >> > Hi, >> > >> > It’s been a while since I tried using the FiPy package. I followed the >> > installation directions and used miniconda to generate a Python >> > environment for FiPy. Running the fipy.test() function lists a large >> > number of not installed packages, some of which I was able to install >> > manually; not sure why packages tested by FiPy in this function aren’t >> > part of the vanilla install … Other packages like pysparse don’t seem to >> > want to installed possibly due to a conflict between Python 2 and 3; I am >> > using the Python 3.6 version of minconda. There are two references to >> > mpi4py in the test script. I installed mpi4py, but … >> > >> > gist version not available >> > mpi4py version 3.0.0 >> > mpi4py is not installed >> > >> > Not sure what’s going on here and what the difference may be. >> > >> > The test() function also crashes the Python interpreter. >> > >> > ====================================================================== >> > ERROR: testFiPy (unittest.loader._FailedTest) >> > ---------------------------------------------------------------------- >> > ImportError: Failed to import test module: testFiPy >> > Traceback (most recent call last): >> > File >> > "/Users/langrock/miniconda3/envs/FiPyEnv/lib/python3.6/unittest/loader.py", >> > line 153, in loadTestsFromName >> > module = __import__(module_name) >> > ModuleNotFoundError: No module named ‘fipy.testFiPy' >> > >> > Trying to run the first diffusion example >> > >> > python examples/diffusion/mesh1D.py >> > >> > gives the following error >> > >> > Traceback (most recent call last): >> > File "examples/diffusion/mesh1D.py", line 794, in <module> >> > exec(fipy.tests.doctestPlus._getScript()) >> > File "<string>", line 139 >> > the transient diffusion equation" >> > ^ >> > SyntaxError: Missing parentheses in call to 'print'. Did you mean >> > print("The SciPy library is not available to test the solution to \ >> > the transient diffusion equation”)? >> > >> > I am not familiar with restructured text and how such commented code is >> > supposed to be run using the ipy.tests.doctestPlus._getScript() function, >> > but there’s apparently some issue. >> > >> > The second example fails differently, which seems to indicate a problem in >> > the call to splu() >> > >> > python examples/diffusion/coupled.py >> > >> > /Users/langrock/miniconda3/envs/FiPyEnv/lib/python3.6/site-packages/fipy/viewers/matplotlibViewer/__init__.py:113: >> > UserWarning: Matplotlib1DViewer efficiency is improved by setting the >> > 'datamax' and 'datamin' keys >> > return Matplotlib1DViewer(vars=vars, title=title, axes=axes, **kwlimits) >> > Traceback (most recent call last): >> > File "examples/diffusion/coupled.py", line 153, in <module> >> > exec(fipy.tests.doctestPlus._getScript()) >> > File "<string>", line 66, in <module> >> > File >> > "/Users/langrock/miniconda3/envs/FiPyEnv/lib/python3.6/site-packages/fipy/terms/term.py", >> > line 254, in sweep >> > solver._solve() >> > File >> > "/Users/langrock/miniconda3/envs/FiPyEnv/lib/python3.6/site-packages/fipy/solvers/scipy/scipySolver.py", >> > line 61, in _solve >> > self.var[:] = numerix.reshape(self._solve_(self.matrix, >> > self.var.ravel(), numerix.array(self.RHSvector)), self.var.shape) >> > File >> > "/Users/langrock/miniconda3/envs/FiPyEnv/lib/python3.6/site-packages/fipy/solvers/scipy/linearLUSolver.py", >> > line 64, in _solve_ >> > permc_spec=3) >> > TypeError: splu() got an unexpected keyword argument ‘drop_tol' >> > >> > >> > Anyhow, it’d be nice to at least get the simplest examples to work on my >> > machine (macOS 10.13.6). Even following the mesh1D.py example by hand >> > resulted in errors at >> > >> > eqX.solve(var=phi, dt=timeStepDuration) >> > >> > The error was the same as the one above referencing the splu() call with >> > an unexpected keyword argument ‘drop_tol’. >> > >> > Thanks, >> > Carsten >> > >> > _____________________________________ >> > Dipl.-Phys. Carsten Langrock, Ph.D. >> > >> > Senior Research Scientist >> > Edward L. Ginzton Laboratory, Rm. 202 >> > Stanford University >> > >> > 348 Via Pueblo Mall >> > 94305 Stanford, CA >> > >> > Tel. (650) 723-0464 >> > Fax (650) 723-2666 >> > >> > Ginzton Lab Shipping Address: >> > James and Anna Marie Spilker Engineering and Applied Sciences Building >> > 04-040 >> > 348 Via Pueblo Mall >> > 94305 Stanford, CA >> > _____________________________________ >> > _______________________________________________ >> > fipy mailing list >> > fipy@nist.gov >> > http://www.ctcms.nist.gov/fipy >> > [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ] >> >> >> _______________________________________________ >> fipy mailing list >> fipy@nist.gov >> http://www.ctcms.nist.gov/fipy >> [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ] >> > _______________________________________________ > fipy mailing list > fipy@nist.gov > http://www.ctcms.nist.gov/fipy > [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ] _______________________________________________ fipy mailing list fipy@nist.gov http://www.ctcms.nist.gov/fipy [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ]
