PaPCo is intended for use on Windows, Linux, Mac, and Solaris
platforms. The full version runs on IDL 5.6 and newer. IDL 7.0 appears
to work, but it breaks our installer scripts on Windows, and there are
other annoyances. For example, IDL 7.0's workbench loads every code
it compiles, meaning that hundreds of codes will be loaded into the
editor. The software still appears to work in limited testing. It will run
under Runtime (unlicensed) IDL with minor limitations, mainly that only
the core modules can be used since new code cannot be compiled at
Java JRE 1.3 is new requirement that provides unzip and wget
functionality. Java is freely available at http://java.sun.com, and comes
pre-installed on most operating systems. IDL 7.0 has a JRE embedded,
and this is used if detected. Binaries versions of wget and unzip can still
be used when Java is not available, but they are no longer supported.
PaPCo's home on the web is http://www.papco.org, but the source code
and distributions are provided on the website SourceForge.net at
http://sourceforge.net/projects/papco/. From here, tagged versions of the
software can be downloaded as a zip file, or checked out via CVS.
PaPCo is open-source, and it is often the case that developers in distant
time zones are working on different parts of the software, so it is best to
use zip distributions or work off tagged branches. Note a bugs database
exists at SourceForge. Anyone wishing commit access to PaPCo on
SourceForge should contact the author.
For this article, PaPCo is downloaded and installed as a zip file
papco12beta_tenerife_06.zip. PaPCo is installed by unzipping the zip
file in a filesystem such as /usr/local/. PaPCo is about 25MB. Users will
have a area in their home directory where temporary files are staged.
The folder containing the unzipped PaPCo is referred to as
PAPCO_BASE. The user area is PAPCO_USER.
Change directories into PAPCO_BASE/scripts. Run the script for
setting up PAPCO_USER, papco_install.pro. This can be done in two
ways. OS-dependent scripts for running the IDL script are found in the
same folder. Or start IDL, then type “@papco_install.pro.” IDL
Runtime users should invoke “papco_runtime.sav.” This will bring up a
dialog asking for four things: (1) PAPCO_BASE, the location of the
PaPCo software, (2) PAPCO_USER, each users area, typically in their
home directory, (3) PAPCO_DLNK, which is a large writable area for
storing data, and (4) JAVA, which is the location of a Java executable,
JRE 1.3 or greater. This is used to download and uncompress files.
PaPCo will attempt to guess reasonable values for the parameters. Work
groups will typically have PAPCO_BASE be a read-only directory such
as /usr/local/papco_12, and each user will has his or her own
PAPCO_USER folder within their home directory. PAPCO_DLNK may
be a read-only filesystem, in which case downloaded files will be stored
within the PAPCO_USER area.
This will create the PAPCO_USER area where temporary files are
created, configuration stored, etc. This also creates the platform-specific
start-up script which is used to invoke PaPCo. Installation is now
complete, and the analyst can run the software.
PaPCo is launched from the PAPCO_USER area with the script
“papco_start_papco.” IDL Runtime users should use “papco_runtime.”
A dialog is presented showing a list of all the modules that are
distributed as “core” PaPCo modules along with PaPCo. Additional user
modules can be created and installed independently from this set. Select
the Cluster CAA module, as it is the module described in this article.
This module is pre-configured to use the CAA, and will prompt for a
username and password.
Demonstration videos and more complete documentation are available
on the PaPCo website.