Give the disc sizes the framing quotes as radii, and the meta columns in the order they are stored

The framing rule works in radii: at 390x844 a giant's disc may take 0.74 - 90/195 = 0.278 of the 195 px half-side, 54 px from the centre, and before e62e2fb it took half of it, 98 px. The comment and the spec called the 98 px a disc, which reads as a width, and a name 70 px from the centre would then have been off it. e62e2fb's message says "54 px wide" and "98 px wide" for the same radii: the discs are about 108 and 195 px across. The stars-meta.bin doc comment still put the photometry byte before the distance error, which f31ffe1 moved ahead of it for alignment; metaColumns, the DISTANCE_ERROR_STEPS comment and the README already had the new order. The scene's 2 883 hosts past the survey edge are all hosts past it: 2 878 are the archive's own stars and 5 are HYG's (HD 81817, HD 102272, HD 158996, HD 208527, HD 220074). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-09-30 19:17:20 +02:00
parent 280159dcd2
commit 4c1e19d635
4 changed files with 10 additions and 10 deletions
@@ -27,8 +27,8 @@ export const BYTES_PER_STAR_POSITION = STAR_POSITION_COMPONENTS * Float32Array.B

 /**
 * Columns in `stars-meta.bin`, in order: catalogue id, apparent magnitude, colour index, an
- * index into the spectral-type dictionary, what those were measured in (see {@link PHOTOMETRY}),
- * and the distance's relative error (see {@link DISTANCE_ERROR_STEPS}). Stored column by column
+ * index into the spectral-type dictionary, the distance's relative error (see
+ * {@link DISTANCE_ERROR_STEPS}), and what those were measured in (see {@link PHOTOMETRY}). Stored column by column
 * rather than record by record so each one is a single typed-array view over the buffer, with no
 * per-record stride or alignment padding.
 */