PlanetPlots: Difference between revisions

From CASA Guides
Jump to navigationJump to search
Thunter (talk | contribs)
Thunter (talk | contribs)
No edit summary
Line 3: Line 3:
This page documents the '''planetPlots''' function of Python module [[Analysis Utilities|analysisUtils]].
This page documents the '''planetPlots''' function of Python module [[Analysis Utilities|analysisUtils]].


This function will create uv amplitude vs. uvdistance visibility plots
By calling [http://casa.nrao.edu/stable/docs/TaskRef/predictcomp-task.html predictcomp],
for the specified objects, date, frequencies and ALMA configurations using
this function will create uv amplitude vs. uvdistance visibility plots for a specified date
[http://casa.nrao.edu/stable/docs/TaskRef/predictcomp-task.html predictcomp]. The
for the specified objects, frequencies and ALMA configurations. The
output is a multipage collection of a grid of plots, one
output is a multipage collection of a grid of plots, one
page per object, where rows are configurations and columns are frequencies.
page per object, where rows are configurations and columns are frequencies.


==Usage==
==Usage==

Revision as of 21:46, 8 October 2012

Return to Analysis Utilities

This page documents the planetPlots function of Python module analysisUtils.

By calling predictcomp, this function will create uv amplitude vs. uvdistance visibility plots for a specified date for the specified objects, frequencies and ALMA configurations. The output is a multipage collection of a grid of plots, one page per object, where rows are configurations and columns are frequencies.

Usage

au.planetPlots(objects='Venus,Ceres,Vesta,Pallas,Juno,Jupiter,Callisto,Europa,Ganymede,Io,Titan,Uranus,Neptune', 
               date='2013-01-01', freqs = [100,230,345,690], standard = 'Butler-JPL-Horizons 2012', 
               alma_cycle=1,configs=None)

objects: comma-delimited string of planetary bodies 
date: observing date, all plots are a 1-second snapshot at transit 
freqs: a list of frequencies, in GHz
standard: the model in casa to use
alma_cycle: 0 or 1 (will automatically fill in the configs offered)
configs: alternative to alma_cycle, specify a list of configurations, such as: ['alma_cycle1_1.cfg','alma_cycle1_2.cfg']

See setjy for a list of bodies.

Examples

CASA <3>: au.planetPlots(date='2012-11-20')

complete PDF

Single page extracted for Neptune:

generated by casa-4.0.0