1 Introduction

This page is part of the ING document INS-DAS-23 Architecture for UltraDAS.

1.1 Purpose of this document

The division of UltraDAS into sub-systems and packages is described, with emphasis on the definition of formal interfaces and the allocation of the system responsibilities to packages. Technologies for building and linking the sub-systems are prescribed. In this issue, the intended form of the system is described, even where the description is in the present tense. Later issues may change to a description of the system as built.

1.2 History of the document

Issue 1.1, 1998-11-20

Original document. The design and components sections have some material missing.

Issue 2.1, 2000-08-28

Reissued after the system was delivered. Some features of the original design have been dropped and others modified. The hardware components are no longer considered as "packages" of the design, but more software packages are listed, including those on the boundary that interact with UltraDAS.The design diagrams are now in UML.

1.3 Scope of the product

UltraDAS controls ING's detectors, both optical and IR, through SDSU detector controllers. It provides these services:

Operation of detector controllers.
Saving of images to disk.
Assembly of a FITS header for each run.
Status reporting.
Automatic display of observations.

UltraDAS does not log observations: that is done by the ING Data Manager to which UltraDAS is interfaced.

UltraDAS consists in the server and controller software, the client software and the user interfaces. All are parts of the the overall observing system, and the client software and UIs are specifically part of the central intelligence of the observing system. The shorthand term DAS is used below to mean the server and controller software since those parts are associated with a DAS computer.