1 / 9

Upgrading Control Software at Rothney Astrophysical Observatory

Learn about the upgrade initiative at the RAO, challenges faced, and progress made in transitioning to ACS for remote telescope control. Contributions, planned usage, and the rationale behind using ACS are discussed.

cain-gibson
Télécharger la présentation

Upgrading Control Software at Rothney Astrophysical Observatory

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Background • The Rothney Astrophysical Observatory (RAO) is operated by the Department of Physics & Astronomy of the University of Calgary • The RAO was inaugurated on Jan. 7, 1972 • 0.4, 0.5 and 1.8 meter optical telescopes • The RAO is located near Priddis (Alberta), about 30km southwest of the Calgary city center • Current control software is broken

  2. Overall Status • Decision to use ACS • U of C grad student hired • Began porting RAO control software ~May 2005 • Upgrade plagued by numerous problems: • Lack of Linux Port IO driver • Kernel module problems with OSes supported by ACS • Infrastructure and sys admin issues • Not enough man-power • Still, we are making progress

  3. Why Use ACS? • Existing control system coupled too tightly with the Windows-only GUI • A very strong desire to control the telescope(s) remotely • Need to have semi-permanent support

  4. Planned Usage of ACS • Present control system being converted from Windows-only GUI to (non-ACS) C++ classes • 3rd party libraries distributed with ACS will be used by these classes • Eventually ACSComponent-derived components will use these platform independent C++ objects as proxies to control the telescope • Extensive usage of the CDB

  5. Usage to Date • 3rd party libraries distributed with ACS • ACS logging system • Tool for Automated Tests

  6. Contributions to ACS • Kernel module to control Linux ports (September) • Security mechanism (sometime in the near future?)

  7. Questions???

More Related