IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changes between Initial Version and Version 1 of IPPInstallStepByStep-2.6.1-RHEL5.1-Odyssey


Ignore:
Timestamp:
Feb 24, 2009, 4:23:55 PM (17 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • IPPInstallStepByStep-2.6.1-RHEL5.1-Odyssey

    v1 v1  
     1== Warning: this installation is not yet complete! ==
     2
     3 * MySQL is still pending, so there is no pantasks support.
     4
     5== IPP User Setup on Odyssey ==
     6
     7 * The general description of Odyssey is here: [wiki:Odyssey_Cluster_Configuration Odyssey_Cluster_Configuration]
     8 * The binaries for ipp-2.6.1 reside in /odyssey/apps/ipp/ipp-2.6.1/psconfig, with source in /odyssey/apps/src/ipp/ipp-2.6.1 .
     9 * This system uses [http://www.ece.utexas.edu/it/modules/ Modules] for environment management, so there is a small change in setup compared to most IPP installations.  Instead of the usual modification to .bashrc or .cshrc, for which the .cshrc version looks like:
     10
     11   if (-e /path/to/psconfig.csh) then
     12      alias psconfig "source /path/to/psconfig.csh"
     13   else
     14      alias psconfig "echo psconfig not available"
     15   endif
     16
     17the following code suffices for both .bashrc and .cshrc:
     18
     19   module load hpc/ipp
     20   
     21 * To finish setting up the shell environment, the usual 'psconfig default' command is needed.  In addition, libcfitsio doesn't seem to work properly unless the environment variable CFITSIO points to the library itself.  Thus the user's .bashrc should include:
     22
     23   module load hpc/ipp
     24   psconfig default
     25   export CFITSIO=${PSCONFDIR}/default.linrh64/lib/libcfitsio.a
     26
     27.cshrc should include:
     28
     29   module load hpc/ipp
     30   psconfig default
     31   setenv CFITSIO ${PSCONFDIR}/default.linrh64/lib/libcfitsio.a
     32
     33 * Users must set up several config files in their home directories:
     34
     35   cd ${HOME}
     36   cp /odyssey/apps/src/ipp/ipp-2.6.1/ippconfig/ipprc.config ./.ipprc
     37   cp /odyssey/apps/src/ipp/ipp-2.6.1/ippconfig/dvo.site ./.ptolemyrc
     38
     39Edit ${HOME}/.ipprc to uncomment the line near the top of the file which includes $HOME/.ipp in the config search path.  These files can be customized to implement your preferred config options.
     40
     41<b>DO NOT</b> set the environment variable PSCONFIG in your ${HOME}/.psconfigrc file.  The <em>module load</em> command handles that for you; setting it separately in ${HOME}/.psconfigrc will interfere with the function of the <em>module</em> commands.
     42
     43== Build Notes ==
     44
     45 * The modulefile /odyssey/apps/modules-3.2.6/Modules/modulefiles/hpc/ipp is used to implement the 'module load' behavior described above.
     46 * Except for the substitution of 'module load' for the edits to ${HOME}/.cshrc and ${HOME}/.bashrc, the
     47installation proceeds exactly as described in the INSTALL file in /odyssey/apps/src/ipp/ipp-2.6.1 up through
     48the end of step (3).
     49 * As per [wiki:CFITSIO CFITSIO], do:
     50
     51   export LDFLAGS=-L/odyssey/apps/ipp/ipp-2.6.1/psconfig/default.linrh64/lib
     52
     53before doing the 'psbuild' command of INSTALL step (4).  (Modify this appropriately if LDFLAGS is already defined).
     54
     55 * Errors with messages like:
     56
     57   libtool: link: `/odyssey/apps/ipp/default.linrh64/lib/libgsl.la' is not a valid libtool archive
     58
     59seem to be the result of broken libtool archive (.la) files left over from failed earlier compiles.  The fix is to remove all .la files from both the /odyssey/apps/src/ipp/ipp-2.6.1 and /odyssey/apps/ipp/ipp-2.6.1/psconfig/default.linrh64 trees and do a 'psbuild -clean -rebuild -extbuild'.
     60
     61== Known Problems ==
     62 * There is not yet a MySQL server running, so it is not yet possible to run pantasks or simtest.
     63 * We don't yet have a convention for the naming of user's data directories.
     64 * It's unclear how to integrate pantasks with the queueing system.
     65 * site.config needs to be kept up to date as additional data directories are established.