The Monitoring Service collects, persists and propagates the Telescope and Instrument telemetry, for the Gran Telescopio CANARIAS (GTC), an optical-infrared 10-meter segmented mirror telescope at the ORM observatory in Canary Islands (Spain). A new version of the Monitoring Service has been developed in order to improve performance, provide high availability, guarantee fault tolerance and scalability to cope with high volume of data. The architecture is based on a distributed in-memory data store with a Product/Consumer pattern design. The producer generates the data samples. The consumers either persists the samples to a database for further analysis or propagates them to the consoles in the control room to monitorize the state of the whole system.
The "Gran Telescopio Canarias" (GTC) is an optical-infrared 10-meter segmented mirror telescope at the Observatorio del Roque de los Muchachos (ORM) observatory in Canary Islands (Spain). The GTC Control System (GCS) is continuously evolving to enhance the operational efficiency. In this work we present the new GCS subsystem to automatize the guiding setup process, both for Fast Guiding and for Slow Guiding. A set of restrictions (including vignetting and photometric computations) is used to select the stars appropriate for guiding, and a merit function is used to choose the best one. Then, the system computes the optical configuration that fits best the selected star, automatically performs the guide star acquisition process and it closes the guide loop.
The “Gran Telescopio de Canarias” (GTC<sup>1</sup>) is an optical-infrared 10-meter segmented mirror telescope at the ORM
observatory in Canary Islands (Spain). The GTC control system (GCS), the brain of the telescope, is is a distributed
object & component oriented system based on RT-CORBA and it is responsible for the management and operation of the
telescope, including its instrumentation. On the other hand, the Human motor cortex (HMC) is a region of the cerebrum
responsible for the coordination of planning, control, and executing voluntary movements. If we analyze both systems, as
far as the movement control of their mechanisms and body parts is concerned, we can find extraordinary similarities in
their architectures. Both are structured in layers, and their functionalities are comparable from the movement conception
until the movement action itself: In the GCS we can enumerate the Sequencer high level components, the Coordination
libraries, the Control Kit library and the Device Driver library as the subsystems involved in the telescope movement
control. If we look at the motor cortex, we can also enumerate the primary motor cortex, the secondary motor cortices,
which include the posterior parietal cortex, the premotor cortex, and the supplementary motor area (SMA), the motor
units, the sensory organs and the basal ganglia. From all these components/areas we will analyze in depth the several
subcortical regions, of the the motor cortex, that are involved in organizing motor programs for complex movements and
the GCS coordination framework, which is composed by a set of classes that allow to the high level components to
transparently control a group of mechanisms simultaneously.
The GTC1 is an optical-infrared 10-meter segmented mirror telescope at the ORM observatory in Canary Islands (Spain).
First light was at 13/07/2007 and since them it is in the operation phase.
The GTC control system (GCS) is a distributed object & component oriented system based on RT-CORBA<sup>8</sup> and it is
responsible for the management and operation of the telescope, including its instrumentation.
GCS has used the Rational Unified process (RUP<sup>9</sup>) in its development. RUP is an iterative software development process
After analysing (use cases) and designing (UML<sup>10</sup>) any of GCS subsystems, an initial component description of its
interface is obtained and from that information a component specification is written. In order to improve the code
productivity, GCS has adopted the code generation to transform this component specification into the skeleton of
component classes based on a software framework, called Device Component Framework.
Using the GCS development tools, based on javadoc and gcc, in only one step, the component is generated, compiled
and deployed to be tested for the first time through our GUI inspector.
The main advantages of this approach are the following: It reduces the learning curve of new developers and the
development error rate, allows a systematic use of design patterns in the development and software reuse, speeds up the
deliverables of the software product and massively increase the timescale, design consistency and design quality, and
eliminates the future refactoring process required for the code.
The Inspector is the graphical user interface of the GTC Control System. It is implemented in Java and gives a unified
view of the whole system by representing it as hierarchical browser of distributed objects.
The ability to resolve at runtime the domain objects running distributed on the real time systems and use that domain
information to dynamically generate different views of the system.
Using the exact same set of tools and edition capabilities, it is as simple to create an engineering view of the GCS as it is
to create a science view. Such flexibility and simplicity, have made the Inspector be, not only the interface of the final
system, but also one of the most important tools used by the engineers from very early in the development process to test
the functionality of their respective components.
Persistency of dynamically created views, commands execution flows, visualization of system alarms and logs, are also
important aspects of the Inspector which will be explained in this paper.