Definitions:

The pointing model used by comsoft is very simple and incorporates only two parameters: R.A. and Dec encoder offsets. For this reason, when you point SPARO at a source of known R.A. and Dec, you will need to add empirically-derived "SPARO Pointing Offsets" (SPO's) to the actual coordinates or else you will not be pointed at the source.

Actual Source Coordinates + SPARO Pointing Offsets = SPARO-corrected Source Coordinates

or

ASC + SPO = SSC

What does it mean for SPARO to be pointed at a source that has a certain R.A. and Dec? Does it mean that the left beam is pointed at that source? Or the right beam? Or something else? The convetion will be that SPARO is pointed at a position that would put the source half-way between these two beams. So the SPARO pointing offsets are referenced to the "center position" of the chop. So if you want to put the source in your left beam then you have to move the telescope by half-a-chopper throw towards positive R.A. from these "center-position" pointings.

SSC + 0.5*(chopper throw) = SPARO-corrected left-beam Source Coordinates

More conventions: Unless otherwise stated, (1) all ASC's, SPO's, and SSC's are precessed to the 2000 Epoch, (2) all SPO's and SSC's refer to pixel 5, and (3) all R.A. SPO's are in degrees of azimuth.

Finally, note that there could be two reasons for non-zero SPO for a give source: (1) the Viper pointing is not perfect, and (2) the source coordinates are wrong. Almost always most of the SPO will be due to the first effect, but for a few sources the coordinates are not precisely known.

The bottom line is that it is the SSC, not the ASC that should be put into the tcl scripts.

Table of SPARO Pointing Offsets (azimuth degrees and arcminutes)


Source
Date
Notes
Link to image
RA SPO (avg) (deg)
RA SPO (amp) (arcmin)
RA SPO (1 - phase) (arb-az)
Dec SPO (avg) (deg)
Dec SPO (amp) (arcmin)
Dec SPO (1 - phase) (arb-az)
RCW 57
11/12/99
marginal detection
-
+1.19
-
-
+0.09
-
-
RCW 57
11/13/99
Image on Web
-
+1.35
-
-
+0.09
-
-
Moon
11/11/99
-
-
-0.12
-
-
-0.08
-
-
Moon
11/13/99
-
-
-0.06
-
-
-0.11
-
-
Moon
02/28/00
Greg's
-
-0.19
-
-
+0.21
-
-
Moon
02/28/00
Tom's (assumes right in Mac)
-
-0.20
-
-
+0.25
-
-
RCW 57
03/13/00
On web page
-
-0.40
-
-
+0.26
-
-
RCW 57
03/20/00
Greg's fit
Link
-
-
-
-
1.2
65.7
NGC 6334
04/08/00
Tim's fit, without dip
Link
-0.808
0.40
329.2
+0.274
1.4
63.0
RCW 57
05/08/00
Tim's fit
Link
-0.951
2.54
139.6
+0.319
1.23
43.5
RCW 57
05/08/00
Greg's fit
Link
-
2.2
146.4
-
1.6
42.6
Sgr B2
06/26/00
Greg's fit
Link
-
-
-
-
2.0
42.6
Sgr B2
06/26/00
Tim's fit
Link
-0.84
-
-
+0.257
1.9
31.6
NGC 6334
07/07/00
Tim's
Link
-0.858
0.9
116.0
+0.284
2.1
44.2
Sgr B2
07/08/00
Tim's
-
-0.872
0.5
126.6
+0.262
2.4
29.0
Sgr B2
07/13/00
Tim's
-
~ -0.86
-
-
+0.268
2.3
44.6
Sgr B2
07/17/00
Tim's
-
~ -0.86
-
-
+0.258
2.2
30.3
Sgr B2
07/24/00
Tim's
-
-
-
-
+0.263
2.1
31.4
Sgr B2
07/26/00
Tim's
-
-0.858
-
-
+0.269
1.8
47.6
NGC 6334
07/26/00
Tim's
-
~ -0.84
-
-
+0.303
2.2
49.3


This table is written assuming the equation

SPO = average + amplitude * sin(2*pi*(t + phase))

(note the sign on the phase, which may be opposite what you're used to).

The "(1-phase)" column in the table therefore gives the location in arbitrary-azimuth of the point on the ring where sin = 0 and cos = 1.

A table of pointing targets with RA and dec coordinates can be found here.


Last modified by Tim on 08/10/00