2022-05-20 TTA Requirements Meeting

• Date: //date
• Time: 9:00 ET
• Location: nraozoom04 

Attendance:

• Jeff Kern
• Dana Balser
• Mark Whitehead 
• Allison Costa

Agenda:

• ngVLA Documents
  • ngVLA Gap Analysis
• Product Owner Discussions
  • What field source elements are required for each capability?
  • STT-709 - Getting issue details... STATUS
  • What can be modified in the TOM (front end)?
  • STT-693 - Getting issue details... STATUS
• sprint Review page

ngVLA gap analysis comments

• Allie: Generally, I do not see any significant misunderstandings reflected in the document. There are a few minor discrepancies, which may be a result of older documentation being used as source material.
  • Section 1.1.2 and 2.1.3
    • The language in reference to the Observation Specification implies a singular mapping between an Allocation Request/ Capability Request to Observation Specification. This is not the case however: an Allocation Request can have multiple Observation Specifications associated with it. A Capability Request also can generate multiple Observation Specifications. Two Capability Requests in a single Allocation Request can also just one Observation Specifications.
    • Future drafts of the document should refer to the definitions in RD4 as well for more functional and descriptive definitions of the Capability Request Specifications, which are noted in the footnote in 1.1.2  ("These inputs are first introduced and described in the context of TTA in RD3...")
  • Section 1.1.3
    • This section has inverted the use of Capability Request Parameters and Capability Request Specifications.
    • The April versions of RD
  • Generally, TTA has Field Source, not Field Setup; Spectral Specification, not Spectral Setup; and Performance Parameters, not Control and Performance Parameters.

Open Actions:

• Add comments on ngVLA gap analysis document to 2022-05-20 meeting notes.