wiki:AIPS

Version 30 (modified by cdelarcuz, 21 years ago) ( diff )

--

AIPS

​AIPS, the NRAO Astronomical Image Processing System is used primarily for reducing data from synthesis radio telescopes. General information is given in the ​AIPS FAQ.

Fernando asked the 'makers' of AIPS whether it should work ok in debian:

Subject: Re: [daip] aips on debian
Date: Wed, 28 Dec 2005 09:59:03 -0700
From: Eric Greisen <egreisen@nrao.edu>
To: Fernando Camilo <fernando@astro.columbia.edu>
CC: daip@nrao.edu
References: <43B2C16B.7010202@astro.columbia.edu>

Fernando Camilo writes:

  > Could you please let me know whether there are any known issues for AIPS
  > running under Linux Debian 3.1 (sarge)?  We are building a new Linux-based
  > computing network here at the Columbia Astrophysics Lab and want to make
  > sure that the key packages will work under our proposed operating system.

So far as I know there are no issues.  But I do not know if it has
been tested properly either.  We offer AIPS in both source-code and
binary versions.  The former mostly has issues with compilers, where
some versions of GNU for example simply make many mistakes in
optimization.  The latter is build with the Intel compiler on a RedHat
9 host.  It is possible that some issues might arise from OS
incompatibilities.  In fact, we are seeing serious degradation of AIPS
TV performance on those machines that have been "upgraded" to RedHat
Enterprise.  Whether Enterprise just does not like standard sockets
especially Inet loopback sockets or whether load modules build with an
Enterprise system would work better, we do not yet know.

Eric Greisen

Preliminary/Dependant packages

AIPS installer requires the installation of the following:

 * make
 * cvs
 * ncurses
 * gcc-g77-3.4.4 (compilers)
 * X-window-system-dev

AIPS Installation

Create the AIPS directory:

sudo mkdir -p /opt/aips/31DEC06  

Modify directory ownership:

sudo chown -R cdelacruz:cdelacruz /opt/aips

Create an AIPS user group

​31DEC06.tar.gz (text) installation file is downloaded as well as the installation script ​install.pl

Make file executable:

chmod a+x install.pl

Run the install.pl script

./install.pl 

The following options (pulled from the .AIPSRC file) were selected:

# AIPSRC created by install.pl on Fri Apr 21 19:11:55 2006
#
LAST_VERSION = 31DEC06
AIPS_ROOT = /opt/aips/31DEC06
GROUP = aips
GROUPWRITE = NO
INSTALL_FROM_CD = NO
INSTALL_FROM_NET = NO
ARCH = LINUX
IS64 = NO
SITE = CAL
THISHOST = IO
HOSTS = "IO"
PRINTERS = ""
DATA_AREAS = "/scratch/aips/data/IO_1:NONE"
TAPE_DRIVES = ""
TPHOSTS = "127.0.0.1"
APSIZE = 80
PRINTMED = A

 * Note: CWs must define a scratch disk for the data area. 
 * Configuaration files are located in:

         /opt/aips/31DEC06/DA00$

(can refer to solaris configuration files if necessary)



===================== AIPS 31DEC06 Install Wizard=====================

Screen 11: FINAL REVIEW before installing!
------------------------------------------
.
.
.
AipsWiz:  =====> We're DONE!  Let's have a nice Banana Split! <======

AipsWiz: Here are the final setup instructions for running AIPS

        1.  Reference the LOGIN.SH file in your .profile file
              (dot it now too, via ". ./LOGIN.SH")

        2.  Check that it works:

                aips notv tpok

              (this will not start a TV or tape servers).
            Try 'print 2 + 2' for a very basic test.

========================================================================
 * Successfully ran above task.
========================================================================


Create a simlink for 'current' software version:

ln -s /opt/aips/31DEC06 /opt/aips/current

Created an 'aips-shell' for launching application:

#!/bin/bash
. /opt/aips/current/LOGIN.SH
exec aips tv=local tpok

 * (tv=local disables network share of aips tv, tpok disables tape drive setup/share)

Changed AIPS directory ownership to root:

 sudo chown -R root:root aips

Testing

The following commands/script was successfully executed:

	(1) launch aips (setup the LOGIN.SH under the user profile)
	(2) # 123 (input a password)
	(3) system will issue an id ?XXX
	(4) > task 'mandl'
	(5) inp
	(6) check outname > outname 'test1'
	(7) > input
	(8) > cparm 0
	(9) > go (look at message server)
	(10) > mc (image catalog, print out file test1 (image file))
	(11) > getn 'cat' (input the cat number from the list)
	(12) tvall
	(13) check for error messages in the msgserv.

User Feedback

Nithyanandan Thyagarajan made a couple of suggestions:

(1) create multiple data areas/sets (approx. 10).
(2) Load all of the printers.
(3) verify the midnight job (cvs update script). This will
ultimately depend on how we will install the program.

Updates

A Cron job can be enabled.

'midnight job' (CVS updates); .cvs pass file in home directory enabling cvs to run without passwords.

              Make a cron entry for the do_daily.METIS file
              that the MAKE.MNJ created, so you can run the
              AIPS 'midnight job'.  This is optional but
              strongly recommended.

*.make.MNJ

UPPCONFIG

edit email/contact: 

ErrorList=root, cdelacruz@astro.columbia.edu

Post-Install Data Configuration

The following was referenced from ​here

How do I configure new AIPS data areas?

 * Move to your $AIPS_ROOT/NET0 area. Edit DADEVS.LIST and add the new data areas. 
Note that these areas must have the name of the host (in upper case) which is to use the areas, 
such as /home/AIPS/DATA/WOOHOO_1 where /home/AIPS is $AIPS_ROOT and the file /home/AIPS/DATA/WOOHOO_1 
is a link to the actual data area on host woohoo.

 * If you are supporting conflicting architectures, such as LINUX and SOLARIS which 
cannot share data due to their opposite byte orders, you must use different $SITE 
names for the separate architectures. DADEVS.LIST then becomes DADEVS.LIST.$SITE with 
separate disk area lists for each architecture.

 * Disk areas in all DADEVS.LIST files in the $NET0 directory should also appear in the 
file NETSP using the identical name and specifying the TIMDEST limit in days and the list 
of allowed user numbers (or 8 0's to allow all users).

 * The data area itself needs to have only one AIPS file before it may be used. 
That file is called SPACE and can be a 0-byte file with write privilege for anyone 
supposed to use that data area. It may be created with the command "touch SPACE" 
Note: See TracWiki for help on using the wiki.