Agenda:
- Do we want to ask for a deployment?
- Discuss and Record Unit and Coordinate System Conventions
- (at some point)
What units the Capability Request displays - is it what the user inputs? (user/interval view)- for v0.1, default coordinate is RA/Dec in Degrees in CR
- File upload defaults to the units the UI defaults to.
- Define Units for Review Document
- What coordinate/ unit transformations are we responsible for in the Capability Request?
- v0.1 - Transform Units. Do not transform Coordinate Systems
- What are the standard units/coordinate system that the backend takes (and thus are given to the algorithm)?
- Backend keeps RA/DEC; AzEl in degrees.
- What units/coordinate system are standard in Observation Specification?
- We likely need a configurable precision on displayed units.
- Precision decided by GMVA usecase - 10 micro arcseconds
- Display full precision for v0.1
- Motivate display precision for Review Document
Upcoming Events:
- When do we hit TRR: Target 27th
- QA Release on 13th
- QA Process for tickets 13-20th
- Sprint 38 is
13-27 Sept. 9/21 – 10/4 : Includes production Deployment and Configuration- Backlog Sept 19, Sept 26
- Faux Sprint Review of STT-801 tickets Sept 20
- Sprint Planning Sept 21
- Starting
27 Sept. Oct 4 we are ready to do ORR - Next planned meeting is Sept 30 (call meetings as needed between here and there)
{"serverDuration": 104, "requestCorrelationId": "e3bc12669f889be8"}
