psModule Image Processing Library

0.9.1

Introduction

This library contains the Pan-STARRS Image Processing Pipeline (IPP) modules (psModule). These modules use the functionality of the Pan-STARRS Library (psLib) to perform more complex tasks associated with image processing. Modules were constructed to support each of the required processing stages and are listed according to the particular processing stage for which they will primarily be used. To preserve namespace, globally-visible structures and functions are prefixed with pm, an abbreviation for Pan-STARRS Modules.

The capabilities provided by psModule are grouped into the following areas which are also reflected in the file system directory structure:

The installed code for psModule consists of header files and a binary library.

Required external Libraries

Before building psLib from source, several external software libraries must be installed. These include:

We recommend using the particular versions listed as compatibility tested, as that is the only versions of the external libraries tested to work well with psLib and psModule. Though it is quite possible that later versions of the libraries listed will also work, care must be taken when upgrading these libraries to verify that its functionality is compatible with the tested version.

How to Build from Source

Tested versions of psModule are put into a tar file and can be downloaded from:

https://mhpcc.pan-starrs.org/code/releases

If one has a login account on mhpcc.pan-starrs.org, direct CVS access is possible. Example of the commands required for direct CVS retrieval are as follows:

$ cvs -d:ext:USERNAME@mhpcc.pan-starrs.org:/data/panstarrs/cvsroot co -r RELEASEBRANCH psModule
where:

How to Build and Test the psModule Library.

The psModule library and associated tests are made via the GNU autoconf/automake system.

The source should build using the configure script in the psModule directory. The recommended steps are:

$ cd psModule
$ ./configure
$ make
$ make check
$ make install
Unless otherwise specified, the library is installed with PREFIX of the current directory.

If the code was retrieved from CVS, you will need to substitute 'autogen.sh' for 'configure' in above example.

Other configuration options, such as location of external libraries, are also available. To get a list of options, type the following in the top psModule directory.

$ configure --help
A likely option needed is '--with-pslib-config', which specifies the location of the configuration script for psLib. By default, configure searches for it using PATH, but that is not always sufficient.

How to Build from Source

To install the library using the prefix given in the configure step, execute in the top build directory:
$ make install

Building and Linking your code to the psModule library

To assist the use of the library with your own code, a configuration tool is part of the psModule library package. This tool, psmodule-config, is installed in the BIN directory, according to the options given to the configure script.

The required CFLAG options for the compiler stage of code that uses psModule can be obtained via 'psmodule-config --cflags'. This outputs the cc options that supplies include path(s) required to find the psModule headers.

The required linking options, can be obtained via 'psmodule-config --libs'. This outputs the ld options that supplies the library paths and files required to link to the psModule library.

Note: psmodule-config usage above refers to the install locations of the library.

How to Create Code Documentation

Both HTML and man page documentation may be generated from the inline documentation embedded in the code using the following commands:
$ cd psModule
$ make docs
This places documentation in PREFIX/docs.

Also, a prebuilt set of code documentation for both the releases and last CVS snapshot can be found at:

https://mhpcc.pan-starrs.org/docs/


Generated on Tue Dec 13 13:38:22 2005 for Pan-STARRS Module Library by  doxygen 1.4.5