Skip to content

SATCOM products

The SATCOM platform separates physical receiver, configured target, broadcast profile, decoded spacecraft identity, original product source, and product family. GOES-19 is the documented reception target, not a generic source identity.

The workspace also consumes validated appliance records or optional Server archives through shared C++ memory64 reconstruction. See browser record sources for explicit source selection, scoped credentials, fallback, gaps and local recovery. The direct-IQ path described below remains available independently of any Server.

Acquisition ownership

Validated HRIT CADUs go directly from the decoder manager to a dedicated product coordinator, satcom.worker.ts. It owns virtual-channel state, packet/file assemblies, counters, compact progress, parsing, archive indexing and persistence. It does not own a receiver connection. SatcomProductService dispatches raster requests to separate imagery workers without interpreting pixels on the main thread. React gets batched keyed summaries a few times per second, not one update per CADU.

flowchart TB
    C[Validated CADUs] --> W[SATCOM product worker]
    W --> ACTIVE[Bounded active assemblies]
    W --> DECODE[Segment raster workers]
    W --> MOSAIC[Mosaic render workers]
    W --> COLOR[Derived color worker]
    DECODE --> W
    MOSAIC --> W
    COLOR --> W
    W --> META[(IndexedDB metadata/indexes)]
    W --> FILES[(OPFS originals/derivatives)]
    ACTIVE --> PROGRESS[Compact activity deltas]
    META --> GALLERY[Product catalog/gallery]
    FILES --> VIEWER[Viewer/export/playback]

Segment decode, progressive/final mosaic rendering, derived color and interactive enhancement use distinct bounded queues. Thumbnail preparation and native playback decoding also have dedicated workers. Cancellation or recycling of optional presentation work must not terminate reception or take ownership of its buffers. A single product coordinator is not a single worker doing every expensive image operation.

In Direct IQ mode, keep the owning browser session and decoder job open. You can hide the product view while file reconstruction and storage continue. For unattended reception, enable a continuous HRIT job on the Pi. With Server products, the browser displays revisions built by the paired Server. Choose a source

Product model

RF Sentry distinguishes:

  • original reconstructed received file;
  • segment belonging to a logical observation;
  • complete or incomplete logical image/product;
  • derived preview, enhancement, or composite;
  • compatible temporal sequence; and
  • rebroadcast/reception history.

A complete strip is not a complete full-disk image. Sixteen attractive strips in a trench coat are still sixteen strips until protocol geometry says otherwise.

Every record can carry source spacecraft, relay/broadcast service, instrument or channel, sector/coverage, observation/issue/reception times, completeness, quality, original inputs, recipe revision, processing version, and archive identity. Unknown facts stay unknown.

Configured target is operator intent, decoded relay identity is transport evidence, and source spacecraft belongs to the product headers/metadata. Receiving a relayed image from another spacecraft does not change the selected target. Service profile and product family likewise remain distinct. Observation/issue time describes the represented scene or bulletin; reception time describes when it was captured; processing time is not either of them.

Overview's Latest received content cards label original product evidence by family. Imagery shows originating spacecraft and Observed scan time; weather shows the parsed issuing office and Issued time. Environmental/DCS files show platform addresses, or a platform count for multi-platform files. Their compact platform timestamps describe Message time (DCS message reception), not a sensor measurement. When product time is absent, Received explicitly denotes original reception time and the card identifies the missing field. The appliance or Server delivering a product is not substituted for its original source.

Live appliance reception with record sources

With an appliance or Server record source selected, Reception can show the originating appliance's live decoder statistics through the browser's existing authorized appliance control connection. Both producer UUID and stream UUID must match a configured GOES job. A Server connection by itself cannot provide this live telemetry; an unavailable or different appliance is explained explicitly. Configured anonymous access and protected access keep their existing policies.

The compact header and reception panel distinguish running/acquisition state, frame synchronization, freshness, validation/correction counts, rates, continuity and faults. Expand the diagnostic groups for individual RS lanes, Viterbi, carrier/timing measurements, power/DC estimates, receiver commands, handoff, processing lag and memory/CPU usage. Definitions, units, availability and reset rules come from the appliance's capabilities. Large counters remain exact. Unavailable measurements are distinct from zero; stale values do not establish current lock. Independent carrier/timing lock, calibrated SNR, RF BER and packet CRC are not inferred from other measurements.

Live trends retain up to 120 snapshots / two minutes in browser memory for the selected source and decoder run. Multiple views share the control connection's single job watch; other simultaneously monitored jobs use bounded status reads. Monitoring does not start jobs, acquire hardware, request IQ, retune or change gain. These are live appliance reception statistics even during reconstruction of older Server records. They are not historical telemetry. Direct-IQ diagnostics remain available separately.

Assembly lifecycle

Browser memory ownership follows the presentation and archive lifetimes. Weather loop preparation shares an owner across region changes, accounts for decodes that are still settling, and reuses prepared native frames. Its admission estimate uses two RGBA planes plus encoded bytes within a 2 GiB working-set budget; this matches the native viewer's automatic budget basis and is not a claim of exact GPU/RSS measurement. Timeline history and source resolution are preserved.

Archive eviction also invalidates compact RAM indexes and open presentation state. Product searches retain a page while scanning/counting through the archive index; changing filters cancels obsolete reads. Environmental raw diagnostics are loaded on expansion and return station-specific records; opening the source product still provides full inspection/export. After 60 seconds without progress on a request, the client checks whether its worker can still answer. If it responds, other environmental operations remain available. Retry environmental index in the Environmental pane restarts its local worker and reopens the retained data, keeping the tuner and live reception active.

The imagery viewer keeps a bounded metadata window of two indexed pages, with active/comparison selections retained. Load earlier pages for older observations; Follow new observations returns to the current window. This metadata policy does not reduce native playback quality or the configured texture cache. Obsolete thumbnail requests and projection caches are retired independently of useful hot images. Direct-IQ mosaic rendering waits for capacity before copying pixels, and a terminal error waits for changed input rather than repeatedly rendering the same failed revision.

Active assemblies track unique accepted bytes, expected totals where known, packets/segments, duplicates, gaps, first/last progress, and stage. Waiting for the broadcast to return to a product is not immediately called stalled. Missing starts create bounded orphan/continuation activity when a filename or percentage cannot be known.

Completed files proceed through integrity checks, decompression, segment grouping, rendering/preview, and storage as separate stages. 100% received therefore does not mean successfully rendered.

Each lane, receiver/route, decoder job, live/replay source and DVR source epoch has independent assembly state. Virtual-channel/APID/file and segment geometry operate within that acquisition context. A replay seek or incompatible session change must not let matching protocol identifiers join different captures. Usable partial pixels remain partial evidence; a completed segment cannot make its parent observation complete.

Record reconstruction keeps these boundaries in shared C++, including separate live and historical instances. Exact repeated radio frames/initial packets do not create another product; a genuinely different original reception remains distinct. Scan grouping uses common frame-start evidence when available, not each strip's changing observation timestamp. Overlapping historical ranges can therefore improve the same scan without merging different capture/run epochs. The processor revision is rfsentry-hrit-records-3; its versioned recovery state preserves sparse strips, quality and expiry clocks.

Known missing record ranges discard unsafe partial packet assembly while keeping validated file chunks and scan-identified strips with explicit unknown-loss evidence. Completion requires actual coverage and constituent quality. Conflicting pixels preserve the prior validated image and the conflicting original/evidence; they do not stop unrelated products. Files expire after 15 minutes without progress and images after two hours. Missing portions remain partial/abandoned, not fabricated reception. Reconstruction activity and original strip links are available through the existing workspace.

Imagery

The gallery groups compatible observations by verified source/channel/sector/ navigation geometry. Temporal animations use observations, never spatial segments. Complete frames are preferred; partial frames show missing regions without borrowing pixels from another time.

The expanded viewer supports native-resolution pan/zoom, fit/100%, fullscreen, playback, comparison, enhancement, and export. Native playback uses bounded prefetch and an explicit memory budget. Lightweight thumbnails do not cap the native product.

Natural-looking C02+C13 false color is a documented derived product, not received true color. It retains source links and recipe revision. Infrared palettes remain qualitative unless verified calibration supports physical temperature units.

Day/Night Color is a separate derived treatment: C02+C13 daytime false color blends with calibrated C07+C13 infrared nighttime structure using received navigation and scan time. It requires matching spacecraft, scan, sector and coverage, plus the broadcast brightness-temperature tables. It is not true color or exact GeoColor; a nearby scan must not fill a missing channel. See the decoder's color requirements.

The main imagery browser distinguishes the frame currently displayed, the latest complete frame and the latest retained frame. Its automatic thumbnail and loop eligibility uses a persisted minimum segment-coverage threshold, default 90%, plus a persisted observation-time window and pace. Qualifying partials are labeled with their percentage and segment counts; below-threshold partials remain available in the detailed viewer and are never discarded or filled from another scan. The viewer always includes retained partials within its selected window and persists window/pacing preferences without restoring an active playhead. Natural-looking false color and Day/Night Color remain separate named treatments.

Individual adapter-validation failures are recorded with the product revision and field diagnostic; compatible downloads continue. Retry now deliberately rechecks deferred imports. DCS payload control characters are displayed as escape sequences without changing retained evidence. Browser archive metadata upgrades preserve products; if an older tab blocks an upgrade, close the other rfSentry tab and reload the updated application.

In Server products mode, color generation belongs to the Server. The color panel reports imported observations, retained thumbnails and native images available offline for the loaded window. Partial products can be available while remaining incomplete; the display coverage threshold still applies. Opening a native image uses the configured download policy. Local preparation counts apply to local processing modes, and switching sources cancels obsolete preparation requests. Server production health and download progress remain visible in the source controls.

Messages and environmental data

Choose a received DCS station to open its field recorder. Each instrument shows a decoded channel, its reported units and its own observation time. Select an instrument to focus its history. Drag across the trace, step the observation slider, or press Play to step through actual reports. Latest resumes following the station. A shared cursor aligns sensors with different cadences. The smaller traces below the focused chart use the same time axis. Select a trace to examine that channel in detail. The range uses the station's loaded observations; gaps and explicitly missing samples remain visible.

Water-level scales follow the readings in the selected window. Gauge height uses the station reference; reservoir elevation requires its datum to interpret. Reported wind direction and speed are independent. Interval precipitation is shown as bars; a decrease in a cumulative counter is a possible reset. Its accumulation epoch is unknown unless supplied by the source.

In DCS transmissions, select a mark to highlight the samples linked to that message. The strip uses message time, and the trace uses sensor observation time. A message can carry several earlier observations. The strip covers the decoded samples in the loaded window. Expand the transmission diagnostics to inspect available raw messages. Instruments and traces are drawn locally from the readings and work offline.

Radar viewing and region selection work without an analysis location or waiting for the location-based weather dashboard. A location enables local bulletin relevance and prioritizes nearby radar regions.

EMWIN text/graphics parsers extract supported WMO/AWIPS identity, office, issue/valid/expiration time, UGC/VTEC geography and action, revisions, and original text. DCS/environmental transport metadata remains distinct from station-specific sensor meaning; RF Sentry never invents units or coordinates from plausible bytes.

Unsupported content remains downloadable and inspectable with an exact reason. That fallback is evidence preservation, not a substitute for a known-format viewer.

Browser publication replaces superseded partial assets after the new references commit. Pending obsolete transfers move to the current revision without changing asset hashes or deleting an existing local copy. An expired selected download resolves explicitly instead of waiting indefinitely. Startup & activity shows bounded archive cleanup; Server health polling continues independently. Browser archive schema 10 adds asset-reference indexes and preserves existing observations.

While catching up, the product reader drains bounded work turns without a fixed pause after each pair of assets. It refills from a low watermark rather than requesting one catalog item at a time. Local retention and staging accounting use bounded page reads. Verification is reused only during one uninterrupted owned publication; reload still verifies retained bytes. Download limits, independent retention and selected-image priority remain in effect. Retired rows disappear immediately; All products combines matching-count refreshes to at most once per 30 seconds during cleanup so repeated full-index counts do not stall imports.

The reader retains only compact scheduling headers in memory and reloads them from durable pending work after restart. Small assets of the same product share admission checks; large transfers and selected-image requests retain their cancellation boundaries. Publication updates the viewer after commit in the same order as retirement, without rereading just-committed metadata. Age cleanup keeps its known receipt position across passes, resets for older arrivals or settings changes, and rechecks the full index at least once per minute for other tabs. Actual byte pressure still selects the oldest retained entries. No new setting is needed; reload the updated client to use this path.

With Server authentication disabled, an expired internal reader ticket is refreshed through the existing trusted access broker while the product reader keeps its pending work. Simultaneous product/health requests share one refresh; the interrupted read retries once with the same asset revision and byte range. An expected expiry is shown as source-access renewal activity rather than a sign-in failure. Genuine permission errors and rejection after refresh remain visible with the Server error when available. Healthy product operation resets retry backoff. An HTTP 401 can still appear internally before renewal; the broker does not currently provide pre-expiry replacement to this client.

Storage and replay

Bulk originals/native derivatives live in OPFS; compact metadata and indexes live in IndexedDB. Stable derivative identities prevent regeneration loops. Replacement publishes the new asset before deleting an obsolete derivative. Capture/reception/observation times preserve historical semantics during replay.

Derived records track recipe and source revisions/content hashes as well as source links. A source mosaic updated under the same product ID must be distinguished from the old pixels; replacement must not add a duplicate observation to its sequence. Thumbnail/decoded-frame caches are disposable presentation resources, not another authoritative history.

Raw IQ remains the authoritative RF capture. Reconstructed files, interpreted products and rendered pixels carry their reconstruction/processing provenance; retaining an original file is not permission to discard reception occurrences. Worker queries and bounded cache ownership are described in replay/storage architecture and operator storage controls.

Ledger and qualification

docs/roadmap/aviation-satcom.md Phase 11 separates receive/alignment qualification from product and operator acceptance. docs/verification/satcom/goes-hrit/report.md preserves dated receive configuration, independent comparisons, test/report semantics and open gates. The current workspaces, derived color and worker separation extend that initial checkpoint; its earlier optional-enhancement/DCS interpretation backlog is not a complete inventory of today's code.

Only a qualified RF service profile establishes support. Reusing CCSDS file machinery does not qualify another spacecraft/downlink, and representative fixtures do not prove uninterrupted live reception. Preserve the recorded extended reliability, restoration, concurrent-lane and operator gates rather than closing them through a documentation build. See the SATCOM ledger map.