Download and Installation Guide
Download and Installation Guide
pip install "cython<3"If you fulfilled all requirements (see also next section for a specific OS), then the installation can be done with a script. You need the TC-shell to execute the script.
chmod +x gipsy_install.pypython gipsy_install.py of if you made it executable: ./gipsy_install.py
chmod +x gipsy_install.csh
./gipsy_install.csh
install.log which can be consulted in case of problems. You can follow the
installation results in detail in a separate terminal with:
tail -f install.log
+++ FINISHED +++
.cshrc or .bashrc:
setenv gip_root <PATH_TO_GIPSY_ROOT_DIRECTORY>
source $gip_root/sys/gipenv.csh
.bashrc:
export gip_root="<PATH_TO_GIPSY_ROOT_DIRECTORY>"
source $gip_root/sys/gipenv.sh
and after sourcing the relevant file (or after opening a new terminal) you can start the system with:
gipsy
The GIPSY environment defines a number of commands to start tasks on the command line:
p Shortcut to compile for local compilationsngipsy The command line version of the Hermes interface (e.g. nhermes pyblot)skycalq A sky coordinate converter with graphical interfacevisions GIPSY's data(cube) viewerBelow is a list of requirements to install GIPSY's core system. Please note that depending on the operating system distribution, some software may already be provided and other software can be installed from repositories belonging to that distribution. Separate pages with preparation instructions are available for
Below a description of common requirements.csh or tcsh is required.
You can run the install script under Bash, but still need the TC-shell to process
essential TC-shell scripts in the installation process.make which compiles executables.http://www.astro.rug.nl/software/kapteyn/.
The package may be installed afterwards. See also the document<gipsy root>/doc/kapteynpackage.doc
Installation step 0: Download the source
First create a directory gipsy in the tree where you want to keep the
GIPSY source files. It is advisable to create a user gipsy,
but this is not really necessary. When you have a user
gipsy on your system, the GIPSY root directory should be the HOME
directory of user gipsy. Do not install GIPSY as root to avoid problems with ownership of
downloaded files.
setenv gip_root `\pwd`
cd $gip_root
mkdir import
cd import
mkdir src
cd src
cd ../..
gunzip < import/src/gipsy_src.tar.gz | tar xvf -
You will end up with a GIPSY directory tree with the following subdirectories:
Installation step 1: Clients file
cd $gip_root/sys
You 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 = 487
It should be 71 or 103
If your machine does not allow set owner and set
group ID on the disk where the GIPSY sources are stored, you may have to add
8 to the GIPSY client code.
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.
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 clients.new type:
mv clients.new $gip_root/loc/clients
Next type:
source cshrc.csh
This should define the necessary environment variables. A description
can be found in
$gip_root/doc/cshrc.doc.
Installation step 2: Compiler setup$gip_loc directory ($gip_loc is defined as
$gip_root/loc by the gipenv.csh script).
You can check the
$gip_sys/setup.mgr file for
entries which match your local situation. Now copy the file with:
cd $gip_loc
cp $gip_sys/setup.mgr setup
For standard installations, usually no editing is necessary.
Otherwise, delete all the lines that are not relevant and do
NOT delete the last (comment) line! (see also
$gip_doc/setup.doc).
Mac with X11 installed with MacPorts-I/usr/X11R6/include -I/usr/X11R6/include/X11:\ -L/usr/X11R6/lib/ -lX11:\ -L/usr/X11R6/lib -lXaw3d -lXmu -lXt -lXext -lSM -lICE -lX11into:
-I/opt/local/include -I/usr/X11R6/include/X11:\ -L/opt/local/lib/ -lX11:\ -L/opt/local/lib -lXaw3d -lXmu -lXt -lXext -lSM -lICE -lX11
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.csh
If 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. Note that the install script
tries to send a mail with registration information to the GIPSY server.
If you don't want that, then comment out the calls to 'register.sh' in
the scripts 'install.csh' and 'gipsy.csh' (both in $gip_sys).
Installation step 3: Building the sources
cd $gip_sys
./mkbookkeeper.csh
mv bookkeeper.new bookkeeper
If 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 > & install.log &
This will generate the GIPSY library and the GIPSY applications. It is the most
time consuming part of the installation. Use command: tail -f install.log
in a separate terminal to check
the compilation.
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.lock
You should inspect the log file install.log for any errors.
If there are any, try to find out what caused them. If you can't solve
the problem by adjusting setup parameters or installing missing software
components, such as libraries or header files, you can contact the GIPSY
manager at Groningen
(gipsy@astro.rug.nl).
Installation step 4: Local system setup
In order to get the system running properly, you may have to edit the
following setup files in the $gip_loc directory:
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.doc
Installation step 5: Set the environment$gip_loc/setup to enable correct compiling.gipsy!create and press <esc> eA command line editor will be started (see remark about this editor below if you want to change the default). Paste the list with keywords below. Save the file and exit. Task CREATE will start with these keywords and a dummy set 'test' will be created which can be viewed with task VISIONS.
BUNIT= CDELT1= -0.01 CDELT2= 0.01 CDELT3= 1000000 CROTA2= CRPIX1= 150 CRPIX2= 100 CRPIX3= 1 CRVAL1= 45 CRVAL2= 30 CRVAL3= 1401000000 CTYPE1= RA---NCP CTYPE2= DEC--NCP CTYPE3= FREQ-OHEL CTYPE4= CUNIT1= CUNIT2= CUNIT3= DRVAL3= 400 DUNIT3= FREQ0= 1400000000 FUNCTION= RA*DEC*FREQ INSTRUME= WSRT NAXIS1= 300 NAXIS2= 200 NAXIS3= 60 OUTSET= test
.cshrc is given below.
#============== TCSH template .cshrc ===============
set filec # enable file completion
#
# History
#
set history = 2000 # length of history
set histfile=$HOME/.tcshHistory/history.$HOST
set savehist=(2000 merge)
history -L
if ($shell:t == tcsh) then # we are running tcsh
bindkey -k up history-search-backward
bindkey -k down history-search-forward
endif
if ($?autologout) then # if autologout is enable
unset autologout # do not logout automatically
endif # done
#set prompt = "$HOST>" # prompt is machine name
set prompt="%U$HOST%u\:%/ >"
setenv gip_root /home/kapteyn/gipsy64 # !! Replace this with your GIPSY home !!
source $gip_root/sys/gipenv.csh
# This can be useful if you want to override the default editor 'vi'
set EDITOR = nano
setenv EDITOR nano
#===================================================
