@zodiacs/engine 1.0.0
    Preparing search index...

    Interface DeclinationRow

    interface DeclinationRow {
        body: string;
        boundMarginArcsec: number;
        dec: number;
        lat: number;
        lon: number;
        outOfBounds: boolean;
        ra: number | null;
        raDefined: boolean;
    }

    Hierarchy (View Summary)

    Index
    body: string
    boundMarginArcsec: number

    |declination| − trueObliquity, in arcseconds: positive beyond the bound, negative inside it. For every row but the exempt Sun, outOfBounds is exactly boundMarginArcsec > 0. The flag describes the ephemeris's position; it agrees with the real sky only where |boundMarginArcsec| exceeds the ephemeris's declination error for that body (see the README).

    dec: number

    Declination in degrees [-90,90], north positive.

    lat: number

    Full ecliptic latitude in degrees [-90,90], not an assumed zero.

    lon: number

    Ecliptic longitude in degrees; finite values wrap into [0,360).

    outOfBounds: boolean

    Strictly |declination| > the supplied true obliquity, with no uncertainty allowance, except for the Sun, by convention. In chartDeclinations the chart's own Sun row is never out of bounds, at any latitude. In declinationsForBodies a row labelled exactly "Sun" is exempt while its ecliptic latitude is within SUN_BOUND_LATITUDE, and flagged by the strict rule beyond it. The real Sun does pass the bound at about half of all solstices, by up to about 1.1″, but the ephemeris's solar declination is off by up to about 2.7″ near the present and its solar latitude by tens of arcseconds far from it (−68″ in year 2, +26″ in 3902), more than the effect, so the flag could not say which.

    ra: number | null

    Right ascension in degrees [0,360), or null at a numerical celestial pole.

    raDefined: boolean

    False exactly when ra is null; consult RA_POLE_TOLERANCE.