Claude
efa9e4084a
Two things, one verified and one that cannot be. The render budget is now the whole catalogue: 68388 stars, one instanced draw call, which is what a GPU should be asked to do. The budget itself stays, because the catalogue is meant to grow past what any machine should draw at once — Gaia alone could contribute a million — and at that point the selection is what keeps the field legible rather than a grey wash. A `?stars=` override handles the machines that cannot, including the software rasterizer the end-to-end suite runs against, whose frame rate is two orders of magnitude below a real GPU's and which was measuring the rasterizer rather than the app. The aggregation is the second thing, and none of it has run. Every ESA, NOIRLab, SDSS and Euclid endpoint is unreachable from here — only GitHub raw is, which is why HYG and OpenNGC are the current sources. So this is infrastructure and a Gaia query written against the published DR3 schema, not data. What the framework encodes is that these surveys are not interchangeable. The distinction is not size but whether a catalogue knows how far away its objects are, because a 3D map cannot place a star it only has a direction for. Gaia is the only one of the five that can add stars here, because it is the only one that measures parallaxes. DECaPS2 has fifty times Gaia's object count and photometry alone — not one of its 3.32 billion objects can be placed in depth. Euclid's bulge is 8 kpc away, where a parallax is microarcseconds; its contribution would be imagery. SDSS-V and SAGA are keyed to stars something else already places, so they enrich rather than extend. Those roles are recorded as data the ETL prints, not as prose that can drift. Overlapping catalogues are reconciled on direction rather than on 3D proximity, which is the one non-obvious part. Two surveys agree on a star's direction to within an arcsecond and disagree on its distance by tens of per cent, so a star at 200 pc is 50 pc from itself between catalogues while being unmistakably the same object. Matching in 3D would need a tolerance so loose it swallowed real neighbours. The better parallax wins where both reach; where only one does, the star stays. Names become dense-with-holes with a source dictionary, because a survey catalogue has no proper names — writing "Gaia DR3 4472832130942575872" once per star would cost 25 MB per million to repeat what two adjacent fields already say. An empty entry costs three bytes and is regenerated on load. The Sun needed its own case in the merge: it sits at the origin, has no direction to compare, and appears in every catalogue. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WaySiNst4HhDXBHnMy8p5G
46 lines
1.9 KiB
TypeScript
46 lines
1.9 KiB
TypeScript
import { StarRecord } from '../../../src/app/shared/models/star.model';
|
|
|
|
/**
|
|
* The catalogues this map can draw on, and what each of them can actually contribute.
|
|
*
|
|
* The distinction that matters is not size. It is whether a catalogue knows how *far away* its
|
|
* objects are, because a 3D map cannot place a star it only has a direction for. That splits the
|
|
* available surveys into three roles which are not interchangeable, and a survey being enormous
|
|
* says nothing about which role it fills — DECaPS2 has fifty times Gaia's object count and
|
|
* cannot place a single one of them in depth.
|
|
*/
|
|
export type StarSourceRole =
|
|
/** Has a direction *and* a distance, usually from parallax. Can put a star in the scene. */
|
|
| 'positional'
|
|
/** Has stellar parameters keyed to an identifier. Adds knowledge about stars already placed. */
|
|
| 'enrichment'
|
|
/** Has directions but no usable distance. Can only be painted on the backdrop shell. */
|
|
| 'backdrop';
|
|
|
|
export interface StarSource {
|
|
readonly id: string;
|
|
readonly name: string;
|
|
readonly role: StarSourceRole;
|
|
/** Where the data comes from, for the credits and for anyone re-running the pipeline. */
|
|
readonly endpoint: string;
|
|
/** What this source adds that the others do not. */
|
|
readonly contributes: string;
|
|
/**
|
|
* Why it is not yet wired in, or `null` when it is. Kept as data rather than as a comment so
|
|
* the ETL can print an honest summary of what actually ran.
|
|
*/
|
|
readonly unimplementedBecause: string | null;
|
|
/** Fetches this source's stars. Absent for sources that are declared but not implemented. */
|
|
readonly fetch?: () => Promise<StarRecord[]>;
|
|
}
|
|
|
|
/**
|
|
* Precision of the parallax each positional source measures with, in milliarcseconds — which is
|
|
* what decides how far out its distances stay meaningful, and which of two catalogues to believe
|
|
* when both contain the same star.
|
|
*/
|
|
export const PARALLAX_PRECISION_MAS: Readonly<Record<string, number>> = {
|
|
hyg: 1,
|
|
gaia: 0.02
|
|
};
|