frame_velocity.pro

NRAO GBTIDL
Produced by IDL 6.1
User Documentation

prev file | next file view single page | view frames

SUMMARY: fields | routine DETAILS: routine

./toolbox
File frame_velocity.pro

Last modification date:: Tue Nov 30 10:42:58 2004

frame_velocity

function frame_velocity(data, toframe[, fromframe], [/bootstrap])

Toolbox front-end to chdoppler. Get the velocity of a given frame relative to another frame.

Recognized frames:

TOPO - topocentric. The observed (sky) frame.
GEO - geocentric.
HEL - heliocentric.
BAR - barycentric.
LSR - Local standard of rest (kinematic).
LSD - Dynamic LSR.
GAL - galactocentric.

Uses: chdoppler decode_veldef
Version: $Id: frame_velocity.pro,v 1.1 2004/11/30 15:42:58 bgarwood Exp $

Parameters

data
in, required
spectrum Data container to get pointing direction, time, and telescope location from.

toframe
in, required
string The desired frame.

fromframe
in, optional
string The originating frame. Defaults to "TOPO".

Keywords

bootstrap
in, optional
boolean If set, the data.frame_velocity will be used to get to the frame given in data.velocity_definition. The other data header information will only be used to get to other frames. Bootstraping is desirable because the sdfits tool may not be getting the correct times and positions for each integration - early versions didn't. However, the frame_velocity is correct and can be relied on.

Produced by IDLdoc 1.5 on Wed Dec 8 13:08:16 2004

Parameters
data in, required spectrum	Data container to get pointing direction, time, and telescope location from.
toframe in, required string	The desired frame.
fromframe in, optional string	The originating frame. Defaults to "TOPO".

Keywords
bootstrap in, optional boolean	If set, the data.frame_velocity will be used to get to the frame given in data.velocity_definition. The other data header information will only be used to get to other frames. Bootstraping is desirable because the sdfits tool may not be getting the correct times and positions for each integration - early versions didn't. However, the frame_velocity is correct and can be relied on.