-- DanielKlopp - 2012-04-24

Installation notes on my installation of the ALMA Pipeline at Charlottesville.

Installation

I chose two nodes to test the setup environment. The nodes chosen were multivac22 (Infrastructure) and multivac21 (compute node). This was only for the purposes of writing this document and providing Jeff Kern and Lindsey Davis a proper environment for their visit.

This document references http://almasw.hq.eso.org/almasw/bin/view/PIPELINE/ChileMarch2012 as well as amalgamating several emails from Lindsey Davis, Ville Suoranta and prior documentation written by the RTOS team (Rodrigo Amestica, J Perez, Rodrigo Araya, Dongshan Guo).

NOTE: You may need to use the CVS checkout tag datapacker-1_1_0-TEMP if none was specified in my notes here due to code refactoring during and since the installation at Charlottesville.

Infrastructure

Standard Red Hat 5 32 bit installation at NRAO. Any one of the three sites should be able to readily procure this.

Create a directory /tmp/installation

From an AOC (New Mexico) machine, such as login.aoc.nrao.edu, please copy the file /home/almaspace/almasw/users/almamgr/archive/ACS-10_1_0-pre-20120312-NO-LGPL.tar.gz to multivac22:/tmp/installation . Next acquire version 18527 of CASA.

cd /tmp/installation
wget https://svn.cv.nrao.edu/casa/linux_distro/stable/casapy-stable-34.0.18527-001-64b.tar.gz
wget https://svn.cv.nrao.edu/casa/linux_distro/stable/casapy-stable-34.0.18527-001.tar.gz

Check out all necessary code. I did this in a directory called /export/data_1/dklopp/alma

cvs co ICD
cvs co -r TRUNK-R9APDMChanges-201203-BeforeMerge ICD/HLA/APDM
cvs co -r PipelineDeployment-2012-04-SCO-KEEP ICD/PIPELINE
cvs co ARCHIVE/Database
cvs co ARCHIVE/DataPacker
cvs co ARCHIVE/AsdmHandler
cvs co -r PipelineDeployment-2012-04-SCO-KEEP PIPELINE/Science

I made a backup of all checked out code before moving on to speed up recovery from mistakes, hopefully you won't need that. Untar the archive

tar -xf /tmp/installation/ACS-10_1_0-pre-20120312-NO-LGPL.tar.gz -C /export/data_1/dklopp/alma/

Set up the symlinks

mkdir /alma
cd /alma
ln -s /export/data_1/dklopp/alma/ACS-10.1
ln -s ACS-10.1 ACS-current

Extract CASA.

cd /alma/ACS-current
tar -xf /export/data_1/dklopp/casapy-stable-34.0.18527-001.tar.gz -C /alma/ACS-current
ln -s casapy-stable-34.0.18527-001 casapy

Configure your environment with something like this:

if [ `hostname` == "multivac22" ]; then
    export CASA_ROOT=/alma/ACS-current/casapy
    export ACSROOT=/alma/ACS-current/ACSSW
    export CASAPATH=/alma/ACS-current/casapy
    source /alma/ACS-current/ACSSW/config/.acs/.bash_profile.acs
fi

.bash_profile.acs references /usr/java/default as the Java home directory. The easiest fix is to add a symlink to the correct version of Java. I did it likeso.

mkdir -p /usr/java
cd /usr/java
ln -s /opt/local/java/jdk1.6.0_20 default

For matter of convenience while building I also created the following functions in my profile:

    function src { 
        ABASEDIR=/export/data_1/dklopp/alma
        case "$1" in 
            icd|ICD) cd $ABASEDIR/ICD
                ;;
            archive|ARCHIVE) cd $ABASEDIR/ARCHIVE
                ;;
            pipeline) cd $ABASEDIR/PIPELINE/Science/src/
                ;;
            *) cd $ABASEDIR
                ;;
        esac
    }

You will need to log in and back out for these changes to take effect.

Start building. If you used my environment suggestions above then you should be able to build everything via:

# Note, in retrospect I should have built ICD after ARCHIVE
src icd
make build
src ARCHIVE
cd DataPacker/src/
make clean && make all && make install
cd ../..
cd Database/src
make clean && make && make install
cd ../..
cd AsdmHandler/src
make clean && make && make install
src pipeline
make clean && make && make install

With the HEAD version I had checked out there was a build error in ARCHIVE. The file Walker.java was renamed to AsdmWalker.java and one of its methods was migrated to DataPackerFileUtils.java . The fix was quite simple. Edit the file ARCHIVE/AsdmHandler/src/alma/archive/pipelineTools/PipelineEntitiesProvider.java by changing the line:

Walker.sanitiseFilename(asdmArchiveUid);

To

DataPackerFileUtils.sanitiseFilename(asdmArchiveUid);

And add an import line near the top of the file reading:

import alma.asdm.action.DataPackerFileUtils;

Infrastructure Build Status

To help me keep track of the current builds here is a semi up to date build overview (this will only make sense for those that have built this before)

############ Clean Build Log File: build.log #################
############ Clean Build Log File: build.log #################
############ Clean Build Log File: build.log #################
############ build ICD Software         #################
############ HLA/Enumerations MAIN
############ HLA/APDM MAIN
############ HLA/ASDM MAIN
############ HLA/ASDMBinaries MAIN
############ CONTROL/TMCDBComponent MAIN
############ CONTROL MAIN
############ CORR MAIN
############ OFFLINE MAIN
############ TELCAL MAIN
############ SCHEDULING MAIN
############ OBSPREP MAIN
############ PIPELINE MAIN
############ EXEC MAIN
############ ACACORR MAIN
############ OBOPS/ObopsUtils MAIN
############ OBOPS/dam MAIN
### ==> FAILED all ! 
### ==> FAILED install ! 
############ OBOPS/userregdam MAIN
### ==> FAILED all ! 
### ==> FAILED install ! 
############ OBOPS/StateSystem MAIN
############ OBOPS/StateSystemWS MAIN
############ build ICD/SharedCode Software         #################
############ build ICD/SharedCode/TMCDB Software         #################
############ Persistence MAIN
############ Utils MAIN
############ Access MAIN
############ gui MAIN
############ LOsolutions MAIN
############ calibratorCatalogue MAIN
############ AlmaJFreeChart MAIN

Compute Node

Create the directory /export/data_1/dklopp/alma and checkout code there as follows:

cvs co -r PipelineDeployment-2012-04-SCO2-KEEP PIPELINE/Heuristics
Topic attachments
I Attachment Action Size Date Who Comment
archiveConfig.propertiesproperties archiveConfig.properties manage 2 K 2012-04-27 - 15:19 DanielKlopp Archive config properties file for CV, no passwords
Topic revision: r5 - 2012-04-27, DanielKlopp
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding NRAO Public Wiki? Send feedback