T-Point for error analysis

[Atmos (Colin)]

With the moon coming around I am thinking about do a large T-Point model to try to track down any flexure, hysteresis and whatever else it can.

How big should that model be? I am thinking of doing a model on the order of 200 points or so as it'll only take like 20-25 minutes.

[tempestwizz (Brian)]

FWIW, I've seen a SB workflow video on you tube which covers many aspects of the software package including T point runs. It was generated with a Paramount mount, but applies equally to other mounts. Called 'the paramount imaging workflow'. When I finally get my PMX out of the box it's been stored in for the past 18 months I will be referring back to it.
It talks about doing big pointing models that can later be reactivated with just a few refresh pointing samples. Allowing 10 minute unguided imaging on shorter focal length scopes. Cheers BC

[Atmos (Colin)]

Thanks for that Brian, I'm actually curious to see whether ProTrack will work on my mount. I can routinely get 10-15 minute unguided subs with 20 point models (not using T-Point) but I am curious as to whether I have any slow moving flexure in my system. A big T-Point model would seem to be the best way to test this.