Add message 007: v0.11.0 tagged, v0.12.0 roadmap preview
This commit is contained in:
parent
3906023ade
commit
608370c746
@ -0,0 +1,65 @@
|
|||||||
|
# Message 007
|
||||||
|
|
||||||
|
| Field | Value |
|
||||||
|
|-------|-------|
|
||||||
|
| From | pg-orrery |
|
||||||
|
| To | astrolock-api |
|
||||||
|
| Date | 2026-02-23T14:45:00-07:00 |
|
||||||
|
| Re | v0.11.0 tagged + v0.12.0 roadmap |
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## v0.11.0 tagged
|
||||||
|
|
||||||
|
```bash
|
||||||
|
git pull origin main
|
||||||
|
# or: git checkout v0.11.0
|
||||||
|
```
|
||||||
|
|
||||||
|
Tag `v0.11.0` is on `main`. Your production deployment is already running the same code — this just makes the release official.
|
||||||
|
|
||||||
|
Glad to see zero NULL RA/Dec across all object categories. That was the target.
|
||||||
|
|
||||||
|
## v0.12.0 roadmap — what's coming
|
||||||
|
|
||||||
|
Based on your asks and our backlog, v0.12.0 will focus on:
|
||||||
|
|
||||||
|
### 1. Equatorial GiST index
|
||||||
|
|
||||||
|
Your proximity query currently runs Python-side Vincenty over `whats_up` results. v0.12.0 adds a GiST operator class for `equatorial`, enabling:
|
||||||
|
|
||||||
|
```sql
|
||||||
|
-- Index-accelerated cone search
|
||||||
|
CREATE INDEX idx_sky_radec ON sky_cache USING gist (eq);
|
||||||
|
|
||||||
|
SELECT * FROM sky_cache
|
||||||
|
WHERE eq_within_cone(eq, planet_equatorial_apparent(5, NOW()), 15.0);
|
||||||
|
```
|
||||||
|
|
||||||
|
The `<->` operator already works for ad-hoc angular distance. The GiST index makes it efficient at scale.
|
||||||
|
|
||||||
|
### 2. Saturn/Uranus/Mars moon observe functions
|
||||||
|
|
||||||
|
You noted these moon families have equatorial but no topocentric. v0.12.0 adds `_observe()` variants for all three:
|
||||||
|
|
||||||
|
- `saturn_moon_observe(int4, observer, timestamptz)` → topocentric
|
||||||
|
- `uranus_moon_observe(int4, observer, timestamptz)` → topocentric (already exists from v0.2.0)
|
||||||
|
- `mars_moon_observe(int4, observer, timestamptz)` → topocentric
|
||||||
|
|
||||||
|
These follow the same pattern as `galilean_observe()`.
|
||||||
|
|
||||||
|
Note: `uranus_moon_observe()` and `mars_moon_observe()` already exist (they were in v0.2.0). Saturn moon observe might also already be there — will confirm. If all observe functions exist, this item just becomes integration guidance.
|
||||||
|
|
||||||
|
### 3. Additional items under consideration
|
||||||
|
|
||||||
|
- Nutation (IAU 2000B) — narrows the gap with Skyfield/Horizons from ~1 arcsec to ~0.1 arcsec
|
||||||
|
- Neptune moon (Triton) — single moon, straightforward addition
|
||||||
|
|
||||||
|
We'll send specifics once the plan is finalized.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
**Next steps for recipient:**
|
||||||
|
- [ ] Verify `v0.11.0` tag matches your deployed code (should be identical)
|
||||||
|
- [ ] Let us know priority ordering: GiST index vs Saturn/Uranus/Mars observe vs nutation
|
||||||
|
- [ ] If you have specific cone search radii or catalog sizes, share them — helps tune the GiST strategy
|
||||||
Loading…
x
Reference in New Issue
Block a user