- Date:
- Time: 9:00 ET
- Location: nraozoom04
Attendance:
Agenda:
- ngVLA Gap Analysis:
- Clarify:
- Multiple Capabilities and Observation Specifications per Allocation request.
- Section 1.1.3: Capability Request Parameters vs Specifications
- Suggest:
- 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...")
- Adopting consistent nomenclature Field Source, not Field Setup; Spectral Specification, not Spectral Setup; and Performance Parameters, not Control and Performance Parameters.
- Discuss:
- Multiple Capability Requests vs multiple Allocation Requests. We should discuss these concepts and maybe flesh them out. Might be better to do this now than later.
- SRDPs. We should discuss where in the proposal and how these will be specified by the user.
- Simultaneous multi-band observations. Is this a new concept?
- Multiple sensitivities per beam size. Related to multiple sub-arrays. We should discuss if this is an issue or not.
- Clarify:
- Test Planning:
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-800
Open Actions:
| Task report | ||
|---|---|---|
|