Details
-
Architectural Decision
-
Resolution: Done
-
None
-
None
Description
Right now, the per-scan configuration SDP gets is fairly limited - as of https://developer.skatelescope.org/projects/ska-telmodel/en/latest/ska_sdp_configure.html#scan-type-0-3Â it only allows setting a target and a channel map.
This leaves a number of blind spots:
- How do we indicate the intent of a scan, for instance (pointing) calibration? This is the kind of metadata that we should make sure gets put into the output measurement set.
- What happens if we have multiple beams? Currently SDP has no way to reason about this, neither in its input configuration nor for receive addresses. The latter is important, as we will want to have the possibility of ingesting different beams on separate ingest nodes.
- What if we have a non-standard beam, like for holography scans? How do we specify this - presumably as scan types?
- How precisely are zoom windows handled? The ICD states that channels "include" zoom channels, but what exactly does this look like?
Attachments
Issue Links
- informs
-
SP-2483 Visibility Receive Multiple Scan Support (ADR-54)
- Done
- relates to
-
SP-1889 Revise SDP execution control data models & schemas
- Discarded
-
ADR-63 Sky direction representation
- decided
-
ADR-59 How to handle "non-trivial" scans
- decided
- mentioned in
-
Page Loading...
- mentioned on
- Wiki Page
-
Wiki Page Loading...