Details
-
Architectural Decision
-
Resolution: Unresolved
-
None
-
None
Description
Why now? We are working towards integrating PSS LMC into the system, so this is going to become relevant very soon.
Scope: (OET?) TMC, CSP LMC, PSS LMC
Qualities: Maintainability, Controllability, Reliability
Processing in PSS happens in "near" realtime right after the scan or observation completes. The way the subarray state machine has been defined (see ADR-8) this is neither observable nor controllable.
There is especially no way for PSS to communicate to OET that certain sequences of scans might cause resource conflicts within this process (see explanation by c.baffa here: https://confluence.skatelescope.org/pages/viewpage.action?pageId=105416556&focusedCommentId=110793645#comment-110793645).
We should especially consider how all of this relates to commensal observing.
Attachments
Issue Links
- relates to
-
SP-1248 Review design of pulsar and single pulse candidate sift pipeline as SDP workflow.
- Done
-
SP-997 Requirements for instantiating and terminating PSS subarrays.
- Done
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...