[evla-sw-discuss] OSRO python scripting: RestFreqX and VelocityX Intents

[Michael Rupen]

> rest frequencies and velocities go in the Source table.

Yes.

>  the following
> optional elements are the ones of interest:
>
> Name           Type               Comment
> numLines       int                Nlines, the number of line transitions
> transition     string[Nlines]     the names of the transitions
> restFrequency  Frequency[Nlines]  the rest frequencies
> sysVel         Speed[Nlines]      the systemic velocity
> rangeVel       Speed[2]           the velocity range
>
> numLines : Number of line transitions for which information is given.
> transition : The line of each spectral line transition.
> restFrequency : The rest frequency for each transition considered. LABREST
> sysVel : The source radial velocity in each of the line transitions. LSR
> rangeVel : Range of radial velocities present in the source (for
> spectroscopy).
>
> so, as far as i can tell, MCAF should just collect up the unique values
> of the RestFreq.... quantities and stuff them into Source.restFrequency,
> and do the same with the Velocity... quantities into sysVel.  i don't
> know what happens if there is not the same number of unique RestFreq....
> and Velocity.... quantities.

There must be the same number of each.

Note that the Source Table is also indexed by spectralWindowId.  Supposedly
you store the observe line(s) in the entry corresponding to the SpW in
which those line(s) occur.  I believe this is a really a result of
over-loading this table, which is also used to store a model of the source as 
a function of frequency.

Note that the MS Table of the same name duplicated the above elements.

Note too that we have tentatively agreed that the transition name should
match Splatalog.  Joy.

Cheers,

         Michael