| Version 43 (modified by , 19 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 the tape drive setup/share)
Changed AIPS directory ownership to root:
sudo chown -R root:root aips
Data, Tape, and Other Configuration Files
Configuration files are located under /opt/aips/31DEC06/DA00
- Note: A link from the NFS shared aips directory, to an 'aips' group writable location was created.
DA00 -> /home/cal/groups/aips/DA0
PRDEVS.LIST
#----------------------------------------------------------------------- # printer type AIPS options Description firefly PS NONE HP LaserJet 2300 duplex in 1008 cricket PS NONE HP 4500 Color plain paper in 1008 cricket-film PS NONE HP 4500 Color transparencies in 1008 dragonfly PS NONE HP 4100 duplex in 1328 monarch PS NONE Brother HL-1870N duplex in 1210 moth PS NONE Lexmark T420 duplex in 1407
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 Configuration
For sharing the aips installation , modifications to several configuration files were required:
All new workstations (hosts) must be added to the /opt/aips/current/HOSTS.LIST file:
+ IO LINUX CAL NONE CAL Configured Workstation + RHEA LINUX CAL NONE CAL Configured Workstation + TETHYS LINUX CAL NONE CAL Configured Workstation + TRITON LINUX CAL NONE CAL Configured Workstation + CALLISTO LINUX CAL NONE CAL Configured Workstation + TITAN LINUX CAL NONE CAL Configured Workstation + EUROPA LINUX CAL NONE CAL Configured Workstation + DIONE LINUX CAL NONE CAL Configured Workstation + ENCELADUS LINUX CAL NONE CAL Configured Workstation + IAPETUS LINUX CAL NONE CAL Configured Workstation + ARIEL LINUX CAL NONE CAL Configured Workstation
Add entries to the /home/cal/groups/aips/DA00/DADEVS.LIST, this file specifies the location of the data disk areas:
- /scratch/aips/data/IO_1 - /opt/aips/current/DA00/DATA/TETHYS_1 - /opt/aips/current/DA00/DATA/TETHYS_2 - /opt/aips/current/DA00/DATA/TETHYS_3 - /opt/aips/current/DA00/DATA/TETHYS_4 - /opt/aips/current/DA00/DATA/TETHYS_5 - /opt/aips/current/DA00/DATA/TITAN_1 . . . - /opt/aips/current/DA00/DATA/TITAN_20 - /opt/aips/current/DA00/DATA/TRITON_1 - /opt/aips/current/DA00/DATA/TRITON_2 - /opt/aips/current/DA00/DATA/TRITON_3 - /opt/aips/current/DA00/DATA/TRITON_4 - /opt/aips/current/DA00/DATA/TRITON_5 . . . - /opt/aips/current/DA00/DATA/TRITON_20 - /opt/aips/current/DA00/DATA/RHEA_1 - /opt/aips/current/DA00/DATA/CALLISTO_1 - /opt/aips/current/DA00/DATA/EUROPA_1 - /opt/aips/current/DA00/DATA/DIONE_1 - /opt/aips/current/DA00/DATA/ENCELADUS_1 - /opt/aips/current/DA00/DATA/IAPETUS_1 - /opt/aips/current/DA00/DATA/ARIEL_1
Add disk locations to the/home/cal/groups/aips/DA00/NETSP file:
# Disk name TIMDEST --------------Allowed Users----------- /scratch/aips/data/IO_1 365.0 0 0 0 0 0 0 0 0 /opt/aips/current/DA00/DATA/TITAN_1 365.0 0 0 0 0 0 0 0 0 . . . /opt/aips/current/DA00/DATA/TITAN_20 365.0 0 0 0 0 0 0 0 0 /opt/aips/current/DA00/DATA/TRITON_1 365.0 0 0 0 0 0 0 0 0 . . . /opt/aips/current/DA00/DATA/TRITON_20 365.0 0 0 0 0 0 0 0 0 /opt/aips/current/DA00/DATA/RHEA_1 365.0 0 0 0 0 0 0 0 0 /opt/aips/current/DA00/DATA/CALLISTO_1 365.0 0 0 0 0 0 0 0 0 /opt/aips/current/DA00/DATA/EUROPA_1 365.0 0 0 0 0 0 0 0 0 /opt/aips/current/DA00/DATA/DIONE_1 365.0 0 0 0 0 0 0 0 0 /opt/aips/current/DA00/DATA/ENCELADUS_1 365.0 0 0 0 0 0 0 0 0 /opt/aips/current/DA00/DATA/IAPETUS_1 365.0 0 0 0 0 0 0 0 0 /opt/aips/current/DA00/DATA/ARIEL_1 365.0 0 0 0 0 0 0 0 0 *Note: these files allow for the creation of multiple disks (data sets). In general, I've added the max of 32 for all aips users (CWs).
Physical creation of disk/data areas:
The following simple script can be used to create the AIPS data folders:
#!/bin/bash
printf "Name of Aips Host:"
read AIPS_HOST
COUNTER=1
while [ $COUNTER -lt 34 ];do
mkdir ${AIPS_HOST}_$COUNTER
touch ./${AIPS_HOST}_$COUNTER/SPACE
let COUNTER=COUNTER+1
done
* Each created data folder must contain a 'SPACE' (created using: touch SPACE) file for it
to be available as a disk; **the aips data folders should be created in the /scratch/aips/data folder.
The share folder /opt/aips/current/DA00/DATA requires links to all of the CW data folders:
for foo in /scratch/aips/data/*;do ln -s $foo /opt/aips/current/DA00/DATA/$(basename $foo);done
(1) Modified the /opt/aips/current/AIPSASSN.SH so that the $DATA_ROOT variable points to the /opt/aips/current/DA00/DATA. (2) All CWs (hosts) must be added through an AIPS script: (a) export AIPS_ROOT=/opt/aips/current (b) . $AIPS_ROOT/LOGIN.SH (c) cd /opt/aips/current/31DEC06/SYSTEM/UNIX and run ./SYSETUP 'CW' cdelacruz@io:/opt/aips/current/31DEC06/SYSTEM/UNIX$ ./SYSETUP TETHYS SYSETUP: Enter the AIPS manager account name [aipsmgr]: cdelacruz SYSETUP: Enter the AIPS user group name [aipsuser]: aips SYSETUP: Enter the "master" host name [io]: SYSETUP: master = IO SYSETUP: Operating on 1 hosts: TETHYS SYSETUP: Is this acceptable? (yes/no) yes SYSETUP: Processing TETHYS... SYSETUP: Creating ERRORS directory for TETHYS mkdir: cannot create directory `TETHYS': Permission denied chgrp: cannot access `TETHYS': No such file or directory chmod: cannot access `TETHYS': No such file or directory chmod: cannot access `TETHYS': No such file or directory SYSETUP: Creating DA00 directory for TETHYS SYSETUP: Copying /opt/aips/31DEC06/31DEC06/LINUX/TEMPLATE/ACD000000; to DA00/TETHYS . . . SYSETUP: Copying /opt/aips/31DEC06/31DEC06/LINUX/TEMPLATE/TPD00100A; to DA00/TETHYS SYSETUP: Make symbolic link to /opt/aips/31DEC06/DA00/IO/GRD000000; SYSETUP: Make symbolic link to /opt/aips/31DEC06/DA00/IO/PWD000000; cdelacruz@io:/opt/aips/current/31DEC06/SYSTEM/UNIX$ **************************************************************************************
Related reference notes. The following was referenced from here (pg. 51)
"If you see messages about file MSD001000.001; inparticular something like "File MSD001000.001; not found", you can safely ignore them. This is referring to the message file for user number 1."
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.
