code:telescope_poiniting
Differences
This shows you the differences between two versions of the page.
Previous revision | |||
— | code:telescope_poiniting [Unknown date] (current) – external edit (Unknown date) 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Telescope pointing algorithm ====== | ||
+ | All coordinates entered to telescope control are in J2000. Using [[http:// | ||
+ | |||
+ | Calculating coordinates on which telescope will be sent is a complex process. It is make more transparent by those variables, which are displayed in // | ||
+ | |||
+ | Those values are important: | ||
+ | |||
+ | * **ORIRA**, **ORIDEC** contains original, J2000 coordinates. Those area usually entered by observing program (rts2-executor). | ||
+ | * **OFFSRA**, **OFFSDEC** contains offsets applied to ORI coordinates. | ||
+ | * **OBJRA**, **OBJDEC** contains offseted coordinates. //OBJRA = ORIRA + OFFSRA, OBJDEC = ORIDEC + OFFSDEC//. | ||
+ | * **TARRA**, **TARDEC** contains precessed etc. coordinates. Those coordinates do not contain modelling, which is stored in MODRA and MODDEC. | ||
+ | * **CORR_RA**, | ||
+ | * **TELRA**, **TELDEC** contains coordinates read from telescope driver. In ideal word, they should equal to //TARRA - CORR_RA - MORA//, //TARDEC - CORR_DEC - MODEC//. But they might differ. The two major sources of differences are: telescope do not finish movement as expected and small deviations due to rounding errors in mount or driver. | ||
+ | * **MORA**, **MODEC** contains offsets coming from pointing model. They are shown only if this information is available from the mount (OpenTpl) or when they are calculated by RTS2 (Paramount). | ||
+ | |||
+ | Following auxiliary values are used to track telescope offsets. Due to their transient nature, they are visible only in // | ||
+ | |||
+ | * **woffs** contains offsets which weren' | ||
+ | * **wcorr** contains corrections which weren' | ||
+ | |||
+ | They are two algorithms worth mentioning. First is how OFFSets are handled, so telescope offseting do not cause observatory to move telescope during exposures. Second, similar algorithm is used for applying corrections (wcorr and CORR_ variables). | ||
+ | |||
+ | If you are interested to see how the code works, please see startResync() documentation for functions available to retrieve various coordinates. startResync is the routine which is called each time coordinates written as target should be matched to physical telescope coordinates. Using various methods in the class, driver can get various coordinates which will be put to telescope. You can also see [[code: |
code/telescope_poiniting.txt · Last modified: 2009/10/07 00:00 (external edit)