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

[Bryan Butler]

i've been looking at the SDM, and how they store frequencies, so we can 
figure out where these end up (what rich needs to do with them in MCAF).

as usual i'm confused by what's in there, but i'll put it down here and 
maybe rich or michael will respond and clarify.

rest frequencies and velocities go in the Source table.  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.

	-bryan


David Harland wrote, On 3/5/10 08:50:
> David Harland wrote:
>> David Harland wrote:
>>> I'm modifying the code that turns an OPT-created observation into a 
>>> python script.  Below are some lines i want to address:
>>>
>>>    intents = Intention()
>>>
>>>    intents.addIntent('RestFreqA=26500')
>>>    intents.addIntent('RestFreqC=26500')
>>>
>>>    intents.addIntent('VelocityA=500')
>>>    intents.addIntent('VelocityC=500')
>>>
>>> I want to know if we will be changing the RestFreqX and VelocityX 
>>> strings.
>>>
>>> When we start doing the four 3-bit outputs, will we have RestFreqA1, 
>>> RestFreqA2, ..., RestFreqD2?
>>>
>>> For the 8-bit outputs, will we continue to use RestFreqA, or will it 
>>> be renamed RestFreqA0?
>>>
>>>
>> I received no feedback on the above, so below is how its been coded.
>> Showing RestFreq only below; Velocity uses same pattern.
>>
>> Case 1: Two 8-bit pairs
>>
>>   intents.addIntent('RestFreqA0C0=#####')
>>   intents.addIntent('RestFreqB0D0=#####')
>>
>> Case 2: Four 3-bit pairs
>>
>>   intents.addIntent('RestFreqA1C1=#####')
>>   intents.addIntent('RestFreqA2C2=#####')
>>   intents.addIntent('RestFreqB1D1=#####')
>>   intents.addIntent('RestFreqB2D2=#####')
>>
>> Case 3: One 8-bit pair & Two 3-bit pairs
>>
>>   intents.addIntent('RestFreqA0C0=#####')
>>   intents.addIntent('RestFreqB1D1=#####')
>>   intents.addIntent('RestFreqB2D2=#####')
>>
>>   or
>>
>>   intents.addIntent('RestFreqA1C1=#####')
>>   intents.addIntent('RestFreqA2C2=#####')
>>   intents.addIntent('RestFreqB0D0=#####')
>>
>>
>>
> No replied in October, and  no one objected to the above in November, so 
> upcoming Doppler observations will have the lines as shown above.  
> Furthermore, it was unclear as to what velocity to put in the velocity 
> intent -- that of the source against its rest frame or the total 
> velocity of that source relative to the VLA at the time of observation 
> (which for now is the SB start time).  I am providing the latter.
> _______________________________________________
> evla-sw-discuss mailing list
> evla-sw-discuss at listmgr.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/evla-sw-discuss