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

[David Harland]

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=#####')