faq
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
faq [2009/11/08 13:25] – When is selector called? pkubanek | faq [Unknown date] (current) – external edit (Unknown date) 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== When is selector called to select next target? ===== | + | ===== Is RTS2 an open standard? ===== |
- | Selector (// | + | Yes, it is. RTS2 defines TCP/IP interfaces between devices found at the observatory, |
- | * When observatory | + | ===== Who is using RTS2? ===== |
- | * during last exposure on last exposing camera in script, so the // | + | |
- | * every // | + | |
+ | RTS2 is used on more than 20 observatories around the world, ranging in diameter from 10cm to almost 2m. RTS2 was selected by ESA in an open bid for environment to control its space monitoring telescopes. | ||
+ | ===== Will RTS2 run on Windows? ===== | ||
+ | Yes. If you don't want to change anything, please use cygwin environment and compile RTS2 in it. If you want native Windows interface, please consider providing Windows port or get in touch with us for negotiation details. We don't need Windows, and as long as nobody will pay us to provide direct support for Windows, Microsoft Windows (or any other closed source operation system) will remain unsupported. | ||
+ | ===== Why there aren't precompiled binary packages? ===== | ||
+ | |||
+ | Because we are not funded for providing binary packages. If you want them, please consider either providing them, or get in contact with us regarding funding necessary to have binary packages. | ||
+ | |||
+ | ===== Why I should use RTS2 instead of ASCOM? ===== | ||
+ | |||
+ | ASCOM is a standard tightly coupled with Windows closed source COM/DCOM model, now being depreciated by its backing company in favour of .NET and other marketing tricks. We are not interested in upgrading our environment every few years. | ||
+ | |||
+ | ASCOM has following bottlenecks, | ||
+ | |||
+ | * it is strictly typed, it is not possible to extend devices with additional information - consider switching on/off hydraulics, or various variables RTS2 image processor can output to signal current observation conditions | ||
+ | |||
+ | * it hardly scales over network | ||
+ | |||
+ | * it does not provide in our sense reasonable weather reaction subsystem - in RTS2, every device can signal bad weather and block operations of the observatory | ||
+ | |||
+ | ===== How do I add and schedule a new target? ===== | ||
+ | |||
+ | There is a [[howto: | ||
+ | < | ||
+ | |||
+ | ===== Which images consider rts2-imgproc as good and which as bad? ===== | ||
+ | |||
+ | // | ||
+ | - **bad**, when imgproc is unable to read the image. This means that the image FITS header is screwed or that something else failed. Then this image is moved to //bad// directory in directory from which the image was taken | ||
+ | - **trash**, when image processing routine do not output string with astrometry informations to standard output. | ||
+ | - **good**, when image processing routine (defined in /// | ||
+ | < | ||
+ | %li %lf %lf (%lf,%lf) | ||
+ | </ | ||
+ | for the scanf. The format is defined in // | ||
+ | < | ||
+ | 1 180.0 5.0 (.2499999990 .0166666666) | ||
+ | </ | ||
+ | |||
+ | ===== When is selector called to select next target? ===== | ||
+ | |||
+ | Selector (// | ||
+ | |||
+ | * When observatory is switched to ON state, so the // | ||
+ | * during last exposure on last exposing camera in script, so the // | ||
+ | * every // |
faq.1257683151.txt.gz · Last modified: 2009/11/08 00:00 (external edit)