GIPSY operating hardware architecture system release class platform processor type sol4 SunOS 5.6 sun4u sparc SUNW,UltraSPARC-IIi-Engine sol4 SunOS 5.7 sun4c sparc SUNW,Sun_4_65 sun386i SunOS 5.7 i86pc i386 i86pc sun4 SunOS 4.1.3 .... .... linux linux 2.2.5 i86pc .... i86pc hp9000s300 HP-UX B.09.00 9000/300 .... .... hp9000s700_A.09.01 HP-UX A.09.01 .... .... .... hp9000s700_B.10.01 HP-UX B.10.01 .... .... .... hp9000s700_B.10.20 HP-UX B.10.20 9000/780 .... .... aix AIX 3.2 IBM/RS6000 .... .... sgi IRIX 4.0.5 .... .... .... convex ConvexOS 10.0 .... .... .... alpha OSF1 2.0 .... .... ....The requirements to run GIPSY on one of the above systems are:
setenv gip_root `\pwd`
You can now decide how to install GIPSY. You can either (1) obtain the source (gipsy-src.tar.gz) from anonymous ftp or install via the sysgen.csh script (2) which uses the gftp program (for your architecture). We usually follow procedure (1) to obtain and install the sources.
1) If you want to download tarred/gzipped GIPSY sources:
cd $gip_root mkdir import cd import mkdir src cd src
Download alternative:
ftp ftp.astro.rug.nl (or ftp 129.125.6.204)
Name: anonymous
Password: <your email address>
ftp> cd gipsy
ftp> cd src
ftp> bin
ftp> get gipsy_src.tar.gz
ftp> quit
cd ../.. gunzip < import/src/gipsy_src.tar.gz | tar xvf -
Download alternative:
>ftp ftp.astro.rug.nl
Name: anonymous
Password: <your email address>
ftp> cd gipsy
ftp> get sysgen.csh
ftp> binary
ftp> cd <architecture>
ftp> get gftp
ftp> quit
chmod +x sysgen.csh chmod +x gftp
sysgen.cshThe sysgen script will retrieve the necessary GIPSY files using gftp If at the end the sysgen script complains that not all files could be retrieved, run it again. It knows which files could not be retrieved in the previous run. After the basic GIPSY sources are obtained from the GIPSY source server, you can go to step 1. In either case (sysgen or tar file) you end up with a GIPSY directory tree with the following subdirectories:
cd $gip_root/sysYou are now in the directory which contains all the GIPSY system files. Make the current host a GIPSY client with:
./mkclient.csh <number><number> denotes the GIPSY client mode and should be one of the following:
<number> What GIPSY client may/can do RUN COMPILE INSTALL SUID GLOCK NOOLD REMOTE GFTP LINK 65 +1 +64 = 65 71 +1 +2 +4 +64 = 71 103 +1 +2 +4 +32 +64 = 103 199 +1 +2 +4 +64 +128 = 199 231 +1 +2 +4 +32 +64 +128 = 231 487 +1 +2 +4 +32 +64 +128 +256 = 487The <number>should be 199, 231 or 487 if you used the sysgen.csh script.
The mkclient.csh script creates an entry in the clients file, which resides in $gip_root/loc. The modified file is in the current directory and is called clients.new. You should check this file and if necessary, modify it. Usually the fields which are modified are the paths to the GIPSY exe, lib and tmp directories.
Requirement: Note that these directories, exe, lib and tmp must be on the same disk partition.
A description of the clients file and the mkclient.csh script can be found in $gip_root/doc/clients.doc and $gip_root/doc/mkclient.doc resp. After inspecting and/or modifying the file client.new type:
mv clients.new $gip_root/loc/clientsNext type:
source cshrc.cshThis should define the necessary environment variables. A description can be found in $gip_root/doc/cshrc.doc. You should also edit the .cshrc (or the .tcshrc) file to contain the following lines:
setenv gip_rootAlso inspect cshrc.csh to find out whether your system needs some special setings. If so, incorporate them into your .cshrc.source $gip_root/sys/gipenv.csh
This will ensure that the GIPSY environment is setup automatically each
time you logon as GIPSY manager. You should try this by logging off and
logging in again and check whether the GIPSY environment variables gip_root
and gip_sys are correctly defined.
Next we have to compile the compile program, the file extractor, the Fortran to C interface program, the GIPSY lock server, the Sheltran compiler, the GIPSY file transporter and install the fonts for PGPLOT. This can be done with the install script. This script will check whether the necessary directories are present and create them if possible and necessary. In principle only the system dependent directories will be created. In order to run install type
cd $gip_sys ./install.cshIf it complains, then probably some variables are not yet set, and running install again might provide the solution. See $gip_doc/install.doc for a description.
If you used the sysgen.csh script, or you want to obtain regular updates of GIPSY sources, you have to read $gip_doc/server.doc and check whether your machine can resolve the address of the GIPSY source server. If not, you must create a file 'server' in $gip_loc with the correct address of the GIPSY source server.
p -sysgen > & p.log &This command will retrieve the GIPSY sources from the GIPSY source server and compile them (Note that you must have the ftp bit on in $gip_loc/clients, i.e. you must have typed mkclient.csh 199 or 231 in Installation step 1). If you obtained the GIPSY sources via anonymous ftp or tape type:
cd $gip_sys ./archreset.csh $gip_arch mv bookkeeper.new bookkeeperIf you have the ftp bit on in $gip_loc/clients (bit 8), turn it off by subtracting 128 from field 3 in $gip_loc/clients. Next type:
p -update > & p.log &This will generate the GIPSY library and the GIPSY applications. You can now turn on the ftp bit again (if you want it). Note that when you kill 'p' there might be some lock files which will not allow 'p' to be restarted. You will have to remove the lock files by typing:
rm -f $gip_sys/.*lock $gip_sys/*.lock $gip_tmp/update.lockYou should inspect the log file p.log for any errors (grep -i error p.log). If there are any, try to find out what caused them. If you can't solve the problem by playing around with compiler switches, contact the GIPSY manager at Groningen (gipsy@astro.rug.nl). If somehow a GIPSY source did not compile correctly because the standard switches in $gip_loc/setup are not suitable (probably because of compiler bugs), create a file 'options' in $gip_loc (see $gip_sys/options.mgr for a list of known problems with compilers).
If you want to obtain regular updates of sources via gftp you should turn on the ftp bit (bit 8) in the $gip_loc/clients file (e.g. put number 199 in the clients file). Then you can run p -update or the update.csh script in $gip_sys whenever suitable. You can also run update.csh automatically at regular intervals (1 week, maybe 1 day) by using the atqueue.csh script or cron. You MUST have permission to use at or cron. See the document in $gip_doc/atqueue.doc. If you have permission to use cron, you should use cron. An example cron command would be:
0 2 * * * /bin/csh /tha3/users/gipsy/sys/update.cshfor updating every day at 200 am, or
0 22 * * 2 /bin/csh /zia/u/gipsy/gipsy/sys/update.cshfor updating every week at tuesday 2200 pm.
File Purpose Documentation grdevices Contains info about graphics devices $gip_doc/grdevices.doc lpdevices Contains info about text printers $gip_doc/lpdevices.doc mtdevices Contains info about tape units $gip_doc/mtdevices.doc tvdevices Contains info about X11 servers $gip_doc/tvdevices.docExamples of files that we use in Groningen can be found in: $gip_loc/grdevices, $gip_loc/lpdevices, $gip_loc/mtdevices and $gip_loc/tvdevices.
setenv gip_rootAlso inspect cshrc.csh to find out whether your system needs some special setings. If so, incorporate them into your .cshrc.source $gip_root/sys/gipenv.csh
cd $gip_sys ./install.cshThis should create the directory. Then (for the second time) type:
./install.cshThis creates some necessary links.
cd $gip_root ftp ftp.astro.rug.nl Name: anonymous Password:ftp> cd gipsy ftp> binary ftp> get GIPSY_HTML.tar.gz ftp> quit
cd $gip_root/htm gunzip < ../GIPSY_HTML.tar.gz | tar xvf -Now GIPSY should be able to access the local html documentation. The message "... Access via Internet" when starting a Web browser from Hermes (ESC-X) should not appear anymore.
GIPSY_HTML.tar.gz
can be deleted:
rm $gip_root/GIPSY_HTML.tar.gz
GIPSY_HTML.tar.gz
on our server is currently
refreshed once a week.
Turn on the ftp bit in the $gip_loc/clients file.
With $gip_sys/atqueue.csh you can queue the update job to run at a specified time and update the gipsy sources. Preferably this is done once a week. You can also use cron for regular updates. A cron command which updates every tuesday would look like:
0 22 * * 2 /bin/csh /zia/u/gipsy/gipsy/sys/update.csh
setenv gip_rootAlso inspect $gip_sys/cshrc.csh for any other system specific settings.source $gip_root/sys/gipenv.csh