Analysis Utilities

From CASA Guides
Revision as of 16:37, 4 January 2012 by Thunter (talk | contribs) (Getting Started)
Jump to: navigation, search

This page is under development.

Analysis Utilities (or analysisUtils for short) is a small set of Python source code files that provide a number of analysis and plotting utilities. The utilities were developed for ALMA data reduction and are, in many cases, also useful for EVLA data reduction. This CASA Guide documents some of the most useful functions contained in the analysisUtils Python module.

Getting Started

First, download Analysis Utilities from here and extract the tar ball. From a Unix command line this can be done with

$ tar xvf analysis_scripts.tar

Seven files will be extracted -- a README file, and six python scripts. The README file contains the time and date that the tar ball was generated, which can be useful for reporting bugs.

Next, edit your casapy init file in $HOME/.casa/, and add the following

import sys
import analysisUtils as au

where /PATH_TO_ANALYSIS_SCRIPTS is the path to the directory you just extracted from the tar ball. When this is done, start casapy and you will have access to all the functions contained in the analysisUtils module.

Key Functions

a faster version of plotcal for bandpass tables, with useful overlay capabilities

Other Functions

change the intents for a specified field in an ms (based on John Lightfoot's pipeline script)
returns a dictionary of the baseline lengths in your ms, by default sorted by length
lists the range of LST, UT, MJD for the whole ms, and for scans with ON_SOURCE intent (including the elevation range)
prints the antenna station coordinates in local offsets from the Center of Array, and computes longest/shortest baselines
plot any standard telescope configuration of observatories known to casa
shows relative location of pointings in an .ms
plot weather conditions vs. time for your ms
smooths an existing bandpass table with options for window length and type (Ed Fomalont)
compute the total time spent integrating on-source for each specified field