You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Added
meteor_window — the tool this server exists for. Two grid squares in; the path,
the shower in play, and the hour-by-hour geometry out. Three factors decide a contact
and all three are reported: the path length against single-hop limits, the radiant's
elevation at the path midpoint (where the reflection happens, not at either
station), and the angle between the radiant and the path. That last one decides whether
a reflection is geometrically possible at all — a trail reflects only where it is
tangent to the ellipsoid with both stations at its foci, so a radiant broadside to the
path works and one up-path does not, at the same elevation.
Your own end of the path comes from the station profile.meteor_window takes their_grid and leaves my_grid optional, so a host that knows the operator's station
supplies it — QG Desktop's Station component, carrying ADIF's MY_GRIDSQUARE. Exact MY_LAT/MY_LON coordinates are accepted and preferred over a grid square, because a
square is a rectangle whose centre would otherwise be assumed (about 110 by 160 km of
slack at 4 characters; it moved one real path by 38 km). Home, portable and remote all
work without a special case, because ADIF's location fields describe the transmitting
station rather than where the operator sits. A 2-character locator is refused for a path
with the reason, since ADIF permits it but 1100 km of ambiguity cannot support one.
meteor_showers — which showers are near their published maximum, closest first.
meteor_shower_info — every published solution for one shower, never blended.
meteor_activity — confirmed meteor counts today from the Global Meteor Network,
by shower. A count, not a flux density; named and documented for what it returns.
meteor_fireballs — recent fireballs from NASA CNEOS.
meteor_source_info — provenance, the carried edition's SHA-256, and the MDC's own
requested citations.
113 established showers and 594 published solutions read from the IAU Meteor Data
Center, with the source file's URL, retrieval date, encoding and SHA-256 recorded. The
file is latin-1 and the authors' names carry diacritics, so the encoding is pinned
rather than guessed — a mangled name is a miscredit.
Solar-longitude conversion both ways (Meeus ch. 25), so the catalogue's published
maxima become dates in the year asked about. Checked against the peak dates every
operator knows: Quadrantids, Lyrids, Perseids, Orionids, Leonids, Geminids, Ursids.
Notes
The single-hop call is hedged when the locators cannot decide it. A grid square is a
rectangle and its centre is all a locator gives, so the distance carries slack. This is
computed from the characters each locator actually carried rather than inferred from the
mode — ADIF enumerates modes and submodes but says nothing about payload length, so
there is no authority for such an inference and 4 is the safe floor for every mode. About
±100 km per end at 4 characters, a few km at 6. At the 4-character floor a path length
is within roughly ±200 km — immaterial mid-range, decisive against a threshold, since
2250 km could be 2050 to 2450 and straddle the 2300 km limit. When a limit falls inside
the slack the answer says the call cannot be made at that precision and what would
settle it. The slack is always reported.
The summary leads with the path verdict when the path cannot work. Distance and
radiant geometry are assessed independently, so a path far past single hop can still
have a radiant beautifully placed — and the sentence opened with "workable for 7 of 7
sampled times" on a 2535 km path that is physically unusable, mentioning the distance
only at the end. An operator reading the first clause would have gone and listened.
The verdict is words, not a score. The physics is a tangency condition and what a
station hears also depends on its power, antenna and the sporadic background. A number
out of a hundred would imply a precision none of that supports, so each verdict carries
the reason that decided it.
No network for anything computed. Only the two live tools reach out, and a test
enforces that the other five stay offline.
TLS verification uses a current root set (certifi) rather than whichever store the
running Python was built against. NASA's API chains to a Sectigo root that older system
OpenSSL stores do not carry, so on such a machine the fireball tool failed to connect
while the GMN one worked. Verification is never disabled.