Checklist for attending FACETS Collaboration Meetings

1. Check PATH, PYTHONPATH, LD_LIBRARY_PATH

Ensure that you can log onto the iter and/or multipole machines (your password is the same on all). On these machines, make sure that your PATH contains

  /contrib/bin:/contrib/mpi/bin:/opt/bin:/usr/local/mpi/bin

Make sure that your PYTHONPATH contains either

  /contrib/lib64/python2.5/site-packages

or

  /contrib/lib/python2.5/site-packages

as appropriate. Make sure that your LD_LIBRARY_PATH contains

   /contrib/gcc-4.3.2/lib64

if you are working on wavelet.

2. If your machine, check your Fortran, MPI, Java

If you want to work on your OSX or Linux laptop, make sure that you have gfortran-4.3.x installed. For OS X, gfortran-4.3.x is available at  http://hpc.sourceforge.net. If you are going to build gcc-4.3.x, keep in mind that this will take a long time. You also need mpi and java.

3. If your machine, build facetspkgs

If you are working on your own laptop, please be sure to

  cd /where/you/work/on/facets
  svn co https://ice.txcorp.com/code/facetspkgs/trunk facetspkgs
  cd facetspkgs/phystools
  env FCPREFIX=/where/to/install ./mkfcphyspkgs.sh

Then

  cd ../graphics
  env FCPREFIX=/where/to/install ./mkfcgrafpkgs.sh

and be sure that your PYTHONPATH and PATH are updated as output by these scripts.

BUILD TIMES on 2.1 GHz Opteron

txbase:         4m
hdf5-serial:    6m
hdf5-parallel:  6m
netcdf:         < 1m
numpy:          2m
Forthon:        < 1m
pytables:       1m
petsc-serial:   10m
petsc-parallel: 15m
babel:          59m
pact:           3m
PyPDB:          < 1m
matplotlib:     ~ 1m

PLEASE note, with the above build times totaling close to 2 hours, waiting until you arrive at the FACETS neeting will not work.

4A. If your machine, build all the development packages

Have all of the development packages on your laptop or in your work area on multipole/quartic/wavelet and build them.

  cd /where/you/work/on/facets
  svn co https://ice.txcorp.com/code/facetsall
  cd facetsall/physics
  ./mkfcphysall.sh -a

This will take a long time due primarily to nubeam.

OR

4B. Build just UEDGE and FACETS

  cd /where/you/work/on/facets
  svn co https://ice.txcorp.com/code/facetsall
  cd facetsall/physics
  ./mkfcphysall.sh

If all goes well, you should be ready to follow along with the demos. If it does not go well, please send us email in advance of the meeting so that we can help you.

Possible errors and fixes

If using your own MPI/openmpi

E.g., may need to set

export FCMPICC=/usr/local/openmpi/bin/mpicc
export FCMPIDIR=/usr/local/openmpi

Make sure that the compiler for building Python modules is the compiler that Python was built with

E.g., for OS X, you may need to do

export CC=/usr/bin/gcc
export CXX=/usr/bin/g++

before building numpy, pytables, matplotlib, and so on.

Make sure that your babel is not openbabel

which comes with some linices, and may end up being chosen according to your path.

Check your java version

with java -version. On OS X, java version "1.5.0_13" works, but java version "1.6.0_05" does not.

matplotlib possible problems

Matplotlibrc file should not use Qt4Agg as backend

As we are not building facetspkgs with Qt this backend will not be supported. Hence Qt4Agg should not be used as a backend for matplotlib.

On OS X, make sure you have the SDK

Under a directory like /Developer/SDKs/MacOSX10.4.sdk.

Look for problems in output file, like missing Gtk+ headers

Then install the appropriate package. In the above case, gtk2-devel on FC9.

When building on Linux, make sure you come in through X

Otherwise the X backend will not be built.