Quote:
Originally Posted by Bassnut
Ive been wondering about that. Tpoint makes a map and compensates for all alignment errors for pointing, but I dont think it compensates RA/DEC tracking, would seem a logical extention and not that hard. Perhaps it does, havent tested drift with an out-of-alignment mount after a Tpoint map.
|
Hi Fred,
I can answer that for you.
TPoint, on its own, is a pointing analysis system. As you are aware, it provides
the parameters for a pointing model.
In order to get the most benefit from a system such as TPoint, the same pointing
models need to be implemented in the telescope's control system kernel. The
control system kernel is then responsible for pointing and tracking in
real time.
Apart from the corrections provided by the pointing model, the control system is
also factoring in effects such as Earth rotation, refraction, etc.
Since tracking is the differential of pointing, good pointing performance is a prerequisite
for good tracking performance if the system is tracking "blind", that is, without the
benefit of guiding on a guide star.
So for telescope's such as the AAT and the Gemini's the operators perform a TPoint
pointing analysis and the parameters extracted from that analysis are then fed into
the scope's control system kernel. Software Bisque with their TheSky and TPoint
offerings also provide a system called ProTrack which they use with their ME mounts
that provides these type of real-time tracking corrections. Our own Argo Navis
has an integrated pointing analysis system called TPAS, the outputted parameters
of which are then used in integrated models in its own pointing and tracking kernel.
So, for example, if you interface a slew and track system to it like a ServoCAT
or SiTech, it feeds them tracking rate data that is being continually corrected
in real time.
To give you an example of the 'static' behavior of a system such as TPoint
and the 'dynamic' real-time behavior of the control system kernel, consider
for one moment refraction. When inputting data into TPoint, the user has
entered their latitude as well as the current atmospheric pressure, temperature
and the computer's system has to have its time accurately set to compute the
current Hour Angle of stars. These parameters are then used to correct the apparent
position of each star owing to the effects of refraction. The control system
kernel, on the other hand, needs to be making corrections owing to refraction
to both the pointing and tracking on a continuous basis. If the temperature or
pressure are different on that night compared to the night of the TPoint run, then
the correction made for refraction at any given elevation will also be different.
As you are aware, polar alignment error in systems such as TPoint and our
own TPAS are treated just like any other source of systematic mount error.
The advantage of this approach, is that unlike a drift test, polar misalignment is
considered simultaneously with all the other errors in the system. Since the
errors are entwined in a complex and knotty way, unraveling the polar misalignment
parameters requires reasonably complex analysis techniques.
Of course, there is also no magic point in the sky to which one can align the
mount's RA axis and achieve a 'perfect polar alignment' that is then valid for all
points in the sky to which the scope can point. In other words, the best place
to align the RA axis of the scope depends on where the scope is tracking at
any one instant. A good compromise is to align the RA axis with the refracted
pole.
Best Regards
Gary Kopff
Managing Director
Wildcard Innovations Pty. Ltd.
20 Kilmory Place, Mount Kuring-Gai
NSW. 2080. Australia
Phone +61-2-9457-9049
Fax +61-2-9457-9593
sales@wildcard-innovations.com.au
http://www.wildcard-innovations.com.au