Details
-
Architectural Decision
-
Resolution: Done
-
None
-
None
Description
Reasoning about the telescope requires maintaining models of how it is set up and behaves. By nature, these models are going to involve quite a bit of data in various data formats, and will continously evolve - and possibly in a non-linear fashion.
Telescope configuration / models will also have a very varied group of users: Operators will want to be able to maintain an update them, whereas many sub-systems will need to be able to query their information (in an efficient fashion). In communication between the two groups, it is important we can always be clear about what piece of information (especially what version) is applicable in every situation - without getting too verbose about it either.
Why now? For SPO-944 we now have different parts of the system that need to agree on more detailed aspects of the telescope such as antenna positions
Scope: All software
Qualities: Modifiability, portability, reliability, usability, performance
Attachments
Issue Links
- relates to
-
SP-1546 Design and implement telescope model for visibility receive
- Done
-
SP-1755 Development of minimal telescope configuration data interface for visibility receive
- Done
-
SP-1577 Provide a test data manager component
- Done
-
SP-1784 CLONE - Provide a test data manager component
- Discarded
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- Wiki Page
-
Wiki Page Loading...