Appendix D: Installing and configuring the PHT Interactive Analysis System

Purpose

Prerequisites

[Users with an IDL runtime license can use PIA as a standalone package (without the IDL environment). The installation has to be performed in the same manner, but an extra package has to be installed. Please see the PIA Homepage for details. ]

Distribution package

The central directory contains the following files:

1. PIA: A UNIX shell script defining the main PIA location and all environment variables (UNIX) needed for setting all the necessary paths, and for starting the PIA package. The environment variables / logical names are divided into a system wide part (localization of the executable file, calibration files directories, etc), and an individual user part (data, print and save directories) which can be redefined by each user (s. pia_envi / pia_logdef.com). Some of these last directories require write access.


Please NOTE that VMS is not further supported. The distribution of a VMS command file PIA.COM does not imply that PIA has been tested under VMS but is only to give the possibility of using it at the user's own (high) risk.
 

2. pia_envi (UNIX) and pia_logdef.com (VMS): example for user PIA environment variables / logicals setting.
3. ia_init_sysv.pro: it contains the main IDL initialisation of system variables according to PIA(.com).
4. pia_start.scr: the IDL startfile for running PIA. Only the default printer definition given here should be changed individually by users.
5. pia_export.sav (or pia_export_IDL5.1.sav in the IDL5.1/5.2 version): the PIA executable file. No need to be copied to individual users.

1. calg: all the official PHT-Cal G files containing the calibration parameters used by the data reduction.
2. calg_not_off: alternative PHT-Cal G files, which are not officially approved.
3. calu: all the official PHT-Cal U files used for uplinking commands derivation. Not used by the data reduction.
4. html: the central directory for the html structure, containing all the hypertext help files, images, etc.
5. help: the IDL help directories containing information on every PIA routine, accessible under the IDL "old" help system ('widget_olh').
6. incl: all the include files containing common block definitions as used in PIA. They allow direct access from IDL to all the internal PIA buffers.
7. support: several routines from the IDL astronomical library as used by PIA.

PIA Installation

System wide installation

1. uncompress (if necessary) pia_fexp.tar.gz
2. untar ('tar xvf pia_fexp.tar') the tarfile from a filesystem created for accomodating PIA.
3. if the ISO products (FITS files) have to be accessed by several users, create a directory for them.
4. changing the line giving the main PIA directory in the file PIA IS NOT  necessary anymore from V8.0 on.
5. (optional) define an alias systemwide / logical PIA pointing to PIA

Individual configuration (optional)

However, if you want to have user-defined places for data, save and printfiles from the very beginning of your session, you can create a PIA directory to place a file giving all the addresses you might redefine for running PIA. The general command file will run this cshell script / command file if it is found. The default places in which it will look for it are

• under your start directory
• under your root directory/pia (root directory:[.pia] for VMS).

1. create a 'PIA directory' (default your root/pia), a 'print directory' and a 'save' directory -
2. copy from the general installation to the your individual PIA directory the file pia_envi (UNIX)/ pia_logdef.com (VMS)
3. change the file setting the variables PIA_PRINT, PIA_SAVE to the print and save directories. If you are going to manage yourself FITS files containing products, change the variable FITDIR to the directory you are going to use.

Default: the place from which you send the command PIA for all three is used for PIA_PRINT.
4. put under the printer variable PIA_PRINTER your favourite printer (should be at least black/white Postscript capable).

Default: $PRINTER (UNIX), SYS$PRINT (VMS).
5. change the environment variable / logical W3NET to your favourite html browser.

Default: netscape