You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

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)
    • 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" p.42 of System Description
      • "Once the disposition letters are sent, however, the TAC disposition comments cannot be edited" p. 39
    • Expand on
      • "There shall be a mechanism for a TTA Group member to make the approved Allocation Dispositions public in the archive." p. 42 of System Description
    • Assume PIs can see Disposition Letters in TTAT? No explicit requirement on this in System Description
  • 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." p. 43 of System Description
    • Unclear what this means:
      • STT-141 - Getting issue details... STATUS
    • Only TTA Member access to Project Creation Views?
    • What visibility to Projects in TTAT is desired for PIs at this time?
  • 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

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