Re: [firedrake] pyOP2 installation
This is correct. Installing PETSc via PiP will install PETSc in the Python subtree. It won't go anywhere near your system PETSc installation. David On 28 January 2014 10:00, Cotter, Colin J <colin.cotter@imperial.ac.uk>wrote:
Dear firedrakers, I'm going to attempt a pyOP2 installation this evening. As I've already mentioned to David and Lawrence, I'm concerned about breaking my build for our quads Fluidity branch which requires Petsc 3.1, which I currently bring in via an environment module.
Do I correctly understand that if I pip install the python Petsc 3.4 module that this will be installed somewhere else and won't cause me any bother when I try to use the quads branch? Please reassure me and let me know if I have to do something other than what is written on the pyOP2 installation page in order to get this right.
all the best --Colin
_______________________________________________ firedrake mailing list firedrake@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/firedrake
-- Dr David Ham Departments of Mathematics and Computing Imperial College London http://www.imperial.ac.uk/people/david.ham
If you pip install PETSc 3.4 it will be installed to your global (or user if you install with --user) site-packages directory. petsc4py will pick up this installation if no PETSC_DIR is set. Since your PETSc 3.1 environment module exports PETSC_DIR that should not conflict. Alternatively you can create a separate environment module for your PETSc 3.4 installation: /usr/share/modules/modulefiles/petsc-gcc4/3.4.3 """ #%Module1.0 proc ModulesHelp { } { puts stderr "\tPETSc Portable, Extensible Toolkit for Scientific Computation" puts stderr "\thttp://www-unix.mcs.anl.gov/petsc/petsc-as/" puts stderr "\t Version 3.4.3" } module-whatis "PETSc Portable, Extensible Toolkit for Scientific Computation, Version 3.4.3" set petscver 3.4.3 set basedir /usr/lib/petscdir/${petscver} setenv PETSC_VERSION ${petscver} setenv PETSC_DIR ${basedir} unsetenv PETSC_ARCH setenv PETSC_CONFIGURE_OPTIONS "--with-fortran-interfaces=1 --with-c++-support --with-fc=/usr/bin/mpif90 --prefix=${basedir}" prepend-path PYTHONPATH ${basedir}/lib/python2.7/site-packages """ If you then `module load petsc-gcc4/3.4.3` you can install PETSc 3.4.3 [1] with: python setup.py build && sudo make install [1]: http://ftp.mcs.anl.gov/pub/petsc/release-snapshots/petsc-lite-3.4.3.tar.gz This is what I use to manage many concurrent PETSc installations on foraker. Florian On 28/01/14 10:16, David Ham wrote:
This is correct. Installing PETSc via PiP will install PETSc in the Python subtree. It won't go anywhere near your system PETSc installation.
David
On 28 January 2014 10:00, Cotter, Colin J <colin.cotter@imperial.ac.uk <mailto:colin.cotter@imperial.ac.uk>> wrote:
Dear firedrakers, I'm going to attempt a pyOP2 installation this evening. As I've already mentioned to David and Lawrence, I'm concerned about breaking my build for our quads Fluidity branch which requires Petsc 3.1, which I currently bring in via an environment module.
Do I correctly understand that if I pip install the python Petsc 3.4 module that this will be installed somewhere else and won't cause me any bother when I try to use the quads branch? Please reassure me and let me know if I have to do something other than what is written on the pyOP2 installation page in order to get this right.
all the best --Colin
participants (2)
-
David Ham
-
Florian Rathgeber