Next: OTFMAP /DEFAULTS
Up: PAKO Language Internal Help
Previous: ONOFF EXAMPLES
Contents
Index
OTFMAP
OTFMAP xStart yStart xEnd yEnd
Specify an On-The-Fly (OTF) map with linear OTF subscans.
Real :: xStart ! x-offset of start of first OTF subscan
Real :: yStart ! y-offset of start of first OTF subscan
Real :: xEnd ! x-offset of end of first OTF subscan
Real :: yEnd ! y-offset of end of first OTF subscan
The sequence of subscans is determined by:
/croLoop /nOtf /reference /step /zigzag
/croLoop sequence of:
R off-source Reference
O on-source OTF
/nOtf number of OTF subscans
/reference off-source reference position
/step step in x and y between OTF subscans
= translation of one OTF subscans to the next
/zigzag option to scan back-and-forth
The scan analysis loops through the letter codes in croLoop until nOtf
OTF subscans have been generated, starting with first letter in the
croLoop.
IF THE CROCODE LETTER IS "R" AND /REFERENCE IS TRUE:
1 subscan tracking the fixed off-source reference position
is generated
IF THE CROCODE LETTER IS "O":
1 linear OTF subscan is generated.
- The start and end positions of the first OTF subscan are:
parameters xStart yStart xEnd yEnd of the OTFMAP command
- For the second and all following OTF subscans:
xStart yStart xEnd yEnd of the previous OTF subscan are
incremented by parameters dx and dy of option /step.
If /zigzag is true, xStart yStart and xEnd yEnd are
interchanged.
Then the next letter code in the croLoop is considered
in the same way.
If /reference is true, a croCode ending in "R" will ensure that an
off-source reference subscan follows the last OTF subscan.
/CROLOOP croLoop
sequence of R = off-source Reference
O = On-source subscans
Character :: croLoop
Example:
/croLoop ROOR
/NOTF nOtf
Integer :: nOtf ! number of OTF (on-the-fly) subscans
/REFERENCE xOffsetR yOffsetR [systemNameRef]
or
/REFERENCE NO ! no reference
position of off-source reference subscans
Real :: xOffsetR ! x-offset
Real :: yOffsetR ! y-offset
Character :: systemNameRef ! name of system
! see /SYSTEM for choices
NOTE: with the usage /REFERENCE xOffsetR yOffsetR, both parameters are requi
but you can replace either parameter with * to leave it unchanged.
/STEP dx dy
Step (shift or translation) between lines in a map.
Real :: dx ! shift in x-offsets
Real :: dy ! shift in y-offsets
/SYSTEM systemName
Name of system for offsets.
Character :: systemName ! name of system, one of:
! PROJECTION
! TRUEHORIZON
! NASMYTH
<<TBD: ! DESCRIPTIVE>>
<<TBD: ! BASIS>>
<<TBD: ! EQUATORIAL>>
<<TBD: ! HADECL>>
<<TBD: ! HORIZONTAL>>
PROJECTION for now means only the standard simple "radio" projection
offsets in the chosen coordinate system. This is normally the
astronomical system of offsets in which point-by-point (TRACK, ONOFF)
or on-the-fly (OTFMAP) maps are made.
TRUEHORIZON means the horizontal system with a factor 1/cos(elevation)
applied to the azimuth offset.
NASMYTH are special offsets to point an off-center pixel of a
focal-plane array receiver (bolometer, HERA) to the commanded
astronomical position, e.g., to use an off-center pixel for pointing,
focus, ONOFF.
IMPORTANT NOTE: projection, trueHorizon
If the observing mode (LISSAJOUS, ONOFF, OTFMAP, ...)
is in /SYSTEM projection,
OFFSETS ... /SYSTEM projection is ignored (not used).
If the observing mode (LISSAJOUS, ONOFF, OTFMAP, ...)
is in /SYSTEM trueHorizon,
OFFSETS ... /SYSTEM trueHorizon is ignored (not used).
IMPORTANT NOTE: OFFSETS /SYSTEM Nasmyth
If OFFSETS xOffset yOffset /SYSTEM Nasmyth are specified in pako,
the values xOffset yOffset are used during the observations.
(this inludes the case that they are explicitly set to 0.0).
It is up to the observer to make sure that they are "correct".
(in pakoDisplay /SYS Nasmyth will be highlighted as yellow alert.)
If OFFSETS xOffset yOffset /SYSTEM Nasmyth are not specified
(cleared), for the MAMBO bolometer, Nasmyth offsets are used
automatically according to the selected bolometer channel (pixel).
Subsections
Gildas manager
2023-06-01