As of 2006-12-01, the 3.5m has three guiders, each with fairly different cameras and underlying control software but with a unified interface:
Note: all object coordinates are entered and returned in terms of an image's binned subframe, where the lower-left corner of the lower-left pixel is 0,0.
Returns: camFile, files
Returns: maskFile
The following commands are obsolete and no longer work:
Returns: camFile
Returns: darkFile
A number of variables affecting the PyGuide and guiding algorithms can be configured. If they are adjusted via the guide tweak command while guiding, they only affect the active guiding run. If they should be kept across guiding runs, they need to be changed with the set command.
Returns: TBD.
The guider simply makes calls to the PyGuide package, and it can be instructive to call into PyGuide directly. Or useful: seeing measurements can be used for focus loops, etc. This needs to be fleshed out with all the possible PyGuide tweaks. I.e. bias, gain, read noise for the centroider, etc.
Returns: star, files, centActRadius
Returns: star, files, fsActThresh, fsActRadMult
The guider is based on the PyGuide centroider, which is designed to centroid symmetric objects in fields with possibly large masked out regions. This allows it to usefully centroid on stars whose wings are their only visible part, by interpolating over, say, a slit mask. Obviously, there are limits to this technique, so it is also possible to guide on field stars, regardless of any field rotation.
Guiding can be broken down into several stages, each of which can be controlled to some extent:
Returns: guiding
The GUIDING-ARGS specify the basic guiding mode. If boresight and/or centerOn is specified, the "nearest" centroid to the boresight will be moved to the boresight with each iteration of the guide loop. Otherwise, whatever is at the boresight when guiding starts will be kept at the boresight. The default is for the guider to find what it believes is the best guide star and guide on that.
The TWEAK-ARGS are the same as for the guide tweak and set commands.
Returns: guiding, star, , files
The absolute minimum set of commands that the TCC requires to guide via a GImCtrl controller has been implemented. Sorry, no details. OK, maybe one detail: init, setcam, showstatus, doread, and findstars have been implemented. All require all their arguments, just like the TCC always sends. It is not possible to call these commands directly: they are only called when the command source is the TCC.
Many commands require an exposure or a subframe. These commands all accept the same set of arguments to get their image. Basically, they can request that a disk file be loaded, or that a new exposure be taken.
So either:
or:
The following two items are only present for guide stars (type = "g"):
2008-01-31 ROwen:
2007-09-12 ROwen:
2006-12-01 ROwen:
2006-11-07 ROwen: