docs(readme): state reduction pipeline status per stage (fmvqxv3cf1d)
ci / lint (pull_request) Successful in 12s
ci / client (pull_request) Successful in 35s
ci / nox (pull_request) Successful in 13s
ci / server (mysql) (pull_request) Successful in 16s
ci / server (sqlite) (pull_request) Successful in 16s
ci / sidecar (pull_request) Successful in 42s
ci / image (pull_request) Successful in 4m8s
ci / sourcemaps (pull_request) Skipped
ci / deploy (pull_request) Skipped

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1
2026-11-06 14:50:43 -05:00
co-authored by Claude Opus 5.5
parent b88176c9e6
commit f76fc1f7cb
+6 -3
View File
@@ -195,9 +195,12 @@ These dumps live locally only (gitignored) so they never end up in the public re
## Reduction pipeline
Frames that land in the archive go through a reduction pipeline: header
ingest, calibration against master bias/dark/flat frames, plate solving into a
stored WCS, source extraction, photometry, and barycentric time correction.
Frames that land in the archive go through a reduction pipeline. Header
ingest, source extraction and barycentric time correction run today.
Calibration against master bias/dark/flat frames and aperture photometry are
built and not yet wired into runs, so no frame carries a magnitude yet. Plate
solving into a stored WCS is in progress. The landing page pipeline table
(client/src/views/Landing.vue) holds the same status per stage.
Node owns the job queue, the rules deciding which calibration masters apply to
which frame, and the provenance record. A Python sidecar