Attendance:

Agenda:

  • Behavior around Comments for PI from TAC - state model or no?
  • Closeout requirements
    • Versioning on Disposition Letters (e.g., sending an updated Disposition Letter) no, last truth is only truth;
    • Just checking - not preventing modification of comments to PI until Disposition Letters are sent
      • "A TTA Group member shall be able to edit the disposition text"  Section 3.8.2, point 1 of System Description
      • "Once the disposition letters are sent, however, the TAC disposition comments cannot be edited" Section 3.6.1, point 7 of System Description we want the disposition letters, once generated from templates, to be completely isolated from the Proposal Reviews and Proposal Dispositions. these entities would be locked down once Disposition Letters are generated. Note, the Proposal Review is already in a "Finalized" state, which prevents TTA members from Editing it.
    • Expand on
      • "There shall be a mechanism for a TTA Group member to make the approved Allocation Dispositions public in the archive." Section 3.8.2, point 2 of System Description We do not want Allocation Dispositions public - they contain source lists. we want in the "Proposal" ui to show the abstract, title, PIs only for Approved ones. This is the functionality PFT - filtering, search capabilities. build a service that would for ttat and archive – Allie will send Dana text to update System Description
    • Assume PIs can see Disposition Letters in TTAT? No explicit requirement on this in System Description yes we want this, see above point
  • Project Creation requirements
    • "The system shall allow the creation of observing Projects for each Allocation Request with a positive dis-position in a format appropriate for each Facility." Section 3.9.2 point 1 of System Description Allie will send Dana text to update System Description
    • Is TTAT's "Project Creation" only the Anti-Corruption Layer, or does TTAT make something in between AD/OSD and Project Data Models? Pick this conversation up on April 11th
  • EVLA Project Creation
    • Discussion with DF, MB, Phobos team
      • Three databases - Scheduling Block, Source Catalog, Resource Catalog
      • Like to have rest APIs to interact but not all have rest APIs (only Scheduling Block has one).
      • We need to authenticate
      • Currently the API serves XML, we would like json
    • Broadly speaking, this suggests
      • Work done by NM-OPs to create rest APIs when needed
      • NM-OPs Modify current API for json
      • Iterate with NM-OPs to define API signatures and understand payload
    • Goal of v0.4 project creation
      • Minimally: Create a stub service and a frontend UI button that calls a REST API and handles the response
      • Service transforms the TTAT Source into the right structure of a Source Catalog Source
      • Send transformed Source to API
  • Interface between TTAT and Archive, Workspaces (Organize meeting with John Tobin, Amy Kimball, Mark Lacey?)

Open Actions:

DescriptionDue dateAssigneeTask appears on
  • draft requirements for TTA Tools and discuss with group Allison Costa 
Allison Costa2025-01-10 TTA Requirements Meeting
  • Contact Patrick Brandt about interfacing with RCT_2 and developing hardware configuration algorithms for VLA Allison Costa 
Allison Costa2025-01-10 TTA Requirements Meeting
  • Contact Dane Sizemore for interfacing with GBO's sensitivity calculator, Mapping calculator, Hardware Mapping Allison Costa 
Allison Costa2025-01-10 TTA Requirements Meeting
  • Talk to Robert M about EVN and inspect EVN to understand how to interface with
2025-01-10 TTA Requirements Meeting
  • Discussion on F2F parking lot items
2022-09-02 TTA Requirements Meeting
  • Establish who is Telescope Subsystem Scientist for GBT & VLBA.
2021-12-17 TTA Requirements Meeting

  • No labels