Installing Developer CASA

Revision as of 11:09, 12 February 2009 by Teuben (Talk | contribs)

Jump to: navigation, search

Installing CASA from a users point of view is trivial. Install the correct binary tar ball, add the correct bin/ directory to your $PATH, and type casapy. At UMD we use astromake, so a command like astroload casa will probably do the job. However, the current user release does not (currently) enable you to develop applications. For this a developer release must be installed, from source.

As of this writing (Feb 2009) the original CASA is being split into casacore and the non-code (code) trees, and I will only describe that new setup.

There are a number of packages that casacore (and in particular casa) needs in order to compile. Since some of them collide or are not recent enough with what you have on your linux distro, it is best to install them in a separate /opt/casa/{bin,lib,include} type of tree. Most open source packages will then be installed as follows:

  ./configure --prefix=/opt/casa
  make install

or for python plugins (using casa's version of python) the typical command will be

  python install

some Java based tools (e.g. ccmtools) are a little different.

Here are some links to help on installing casa/casacore

Some packages you will have to get via the CASA repository. Here are some examples:


The code is under SVN control. There are two versions, and two ways to install:

 svn co 


Method-1 uses a new GNUMakefile approach:

  • edit GNUmakefile and set DESTDIR to the place you want the libraries & includes to end up (defaults to ./build/)
  • run gmake setup
  • run gmake

this last process will take a while. Took 45 mins. on my 2GB 2GHz Core2Duo laptop.

casa (non-core or code)

Same deal, SVN, and two versions to download, but the install method is still the old one:

 svn co


 svn co
Personal tools