Page History

• 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?

  • Jira
    server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-709

  • What can be modified in the TOM (front end)?

  • Jira
    server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-693

• 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 one or more Observation Specifications. Two ; two Capability Requests, if in a single Allocation Request, can also just generation one or more 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 I think this section muddled a bit the meanings of Capability Request Parameters and Capability Request Specifications .(understandably & sympathies).
      
    • The April versions of RDIn addition to determining the configuration, receiver, backend, pointing pattern, and integration time, the Observing Strategy selects a Calibration Strategy and Scheduling Strategy, which are defined in the April 7th version of RD2 and discussed in the April 8th version of RD4. (S 2.1.3 discusses a ngVLA Observing Strategy too)
      
  • Generally, TTA has uses 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.