Requirement:
- Store the way the user enters the value to display it back in the same format
- Store in "canonical" units for calculations where canonical units are SI units unless explicitly specified.
In Scheduler Tools, we need a common display output regardless of the OSD's unit
https://www.roe.ac.uk/ukatc/projects/alma/APDM-Cycle7/Indexs/indexLeft.html
Chapter 25 of the Algorithms Document details Proposal Creation unit requirements.
| Entities affected | Attribute | Data Type | Stored Unit | Supported Conversions for UI display | Note |
|---|---|---|---|---|---|
| ATM, Time Reservation, OSD, OS | start_date | UTC | (LST, GST, UTC)↔ (LST, GST, UTC); YYYY-MM-DD | astropy stores a split Julian Date where JD1 is integer portion of the date and JD2 is the fractional portion for precision. Postgres stores datetime as 64-bit integer in UTC. | |
| ATM | end_date | UTC | (LST, GST, UTC)↔ (LST, GST, UTC); YYYY-MM-DD | ||
| Time Reservation, OSD, OS | repeat_count | integer | None | None | |
| Time Reservation, OSD, OS | cadence | None | there's a definition of cadence in older conceptual doc; Dana promised to find | ||
| Time Reservation, OSD, OS | start_time | UTC | HH:MM:SS | ||
| Time Reservation, OSD, OS | stop_time | UTC | HH:MM:SS | ||
| Time Reservation, OSD, OS | duration | (d,h,m,s,ms,micros,ns) ↔ (d,h,m,s,ms,micros,ns) | |||
| Time Reservation, OSD, OS | temporal_reference | UTC | (LST, GST, UTC)↔ (LST, GST, UTC) | ||
| ATM, Time Reservation, OSD, OS | facility_configuration | character varying | facility specific | None | |
| OSD, OS | longitude | HH:MM:SS.SS of Equatorial RA | (RA, galactic longitude) ↔ (RA, galactic longitude) | ||
| OSD, OS | latitude | DD:MM:SS.SS of Equatorial DEC | (DEC, galactic latitude) ↔ (DEC, galactic latitude) |