Pointing

We have a licensed and copyrighted copy of Patrick Wallace's TPoint software to determine the pointing coefficients for the telescope. It lives in the directory ~$TELESCOPE/etc/tpoint This directory also contains his star catalogs and the manual. Here is a graph with some TPoint terms.

The TPoint data file has a header with site information, followed by data for each star. Each star has three groups of information.

Where raw position means without any telescope corrections, just what the ha and dec encoders read with the correction for local sidereal time.

Procedure

Determining the telescope pointing corrections involve six steps:

The Programs

Several scripts have been written to do most of the above: Traditionally the steps had been:
makepointing - generate pointing coordinate file
dopointing - point telescope and align each star and generate TPoint file.
More recently this has been replaced by a simpler procedure using the align procedure to take a bunch of images, these are then processed to generate the TPoint file.
fitsfix - converts images to WCS with Gaia stars 
fitstotpoint - generate TPoint file from fixed images

Converting FITs files to TPoint Run file

The dopointing program has an option of generating FITs images of sky fields that are properly annotated and converting them to a TPoint data file. This has to be done in several steps.

Either images that are deep enough to have enough stars to be recognized must be taken or if the FK5 star lists are used having an identifiable brightest star available. If the former can be done they can be analyzed by the wcsfix.html>wcsfix program which will update the header with accurate coordinates. If the latter can be done, they can be analyzed by the onefix script which updates the header using the one bright star.

These header then can be run through the fitstotpoint script which will pull out the timing, location, and meterological data along with the raw and corrrected coordinates to generate a TPoint file.

TPoint Data file

The dopointing script generates a file: run.dat. This file is in the format required by TPoint. I am using the 'Observation Record Format 1' described on page 39 of the TPoint manual. After you run the file, rename the file to a unique name of your convenience. Here is an example.

Analyzing the Observations

The output file from the above is then entered using the following comands for an equatorial telescope:
indat Nov18.dat
use IE IA   #remove encoder offsets
use PEE     #scale errors which I think are:
fit         #returns IE/IA values and rms 
call e9     #plot
comands for an altazimuth telescope:
indat Nov18.dat
use IE IA   #remove encoder offsets
use PEE     #scale errors which I think are:
fit         #returns IE/IA values and rms 
call a9     #plot

Testing

BUGS

You may hit a limit do to bad wrap testing.
Program index