The Transformation Catalog - tc
-------------------------------
The transformation catalog lists where application executables are
located on execution sites.

By default, the site catalog is stored in etc/tc.data. This path can
be overridden with the tc.file configuration property, either in the
Swift configuration file or on the command line.

The format is one line per executable per site, with fields separated by space or tab.

Some example entries:
----
localhost  cat  /bin/cat null null null 
localhost  vasp  /home/ketan/runvasp.sh null null null
fusion  echo  /bin/echo INSTALLED INTEL32::LINUX  null
TGUC touch /usr/bin/touch INSTALLED INTEL32::LINUX GLOBUS::maxwalltime="0:1"
----

The fields are: site, transformation name, executable path, installation
status, platform, and profile entries.

The site field should correspond to a site name listed in the sites catalog.

The transformation name should correspond to the transformation name
used in a Swift script app procedure.

The executable path should specify where the executable is
located on that site.

The installation status and platform fields are not used. Set them to
INSTALLED and INTEL32::LINUX respectively. Alternatively, they could be set to null.

The profiles field should be set to null if no profile entries are to
be specified.

Setting Environment Variables
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
It is often useful to set environment variables when running an application.
This can be accomplished using *env* in the profile entry. For example,
the following application sets an environment variable called R_LIBS to
/home/user/R_libs.

-----
localhost R /usr/bin/R INSTALLED INTEL32::LINUX	env::R_LIBS=/home/user/r_libs
-----

Setting Multiple Profiles
~~~~~~~~~~~~~~~~~~~~~~~~~
Multiple profile entries can be added by using a semicolon. The example below
sets two environment variables: R_LIBS and R_HOME.

-----
localhost R /usr/bin/R INSTALLED INTEL32::LINUX env::R_LIBS=/home/user/r_libs;env::R_HOME=/home/user/r
-----