SShortSingh.
Back to feed

Probabilistic graph neural inference aims to improve satellite anomaly response with built-in auditability

0
·2 views

A developer working on satellite anomaly triage found that a temporal autoencoder and threshold rules missed a reaction wheel fault that appeared as correlated, sub-threshold drift across several subsystems. Seeking a fix, they explored graph neural networks, where subsystems are nodes and their physical and functional dependencies are edges, so each subsystem's score can reflect its neighbors' states. They argue that operators need calibrated probability distributions over failure modes, not binary verdicts, and that the reasoning behind each output must be traceable for later review. The write-up walks through the graph construction, probabilistic inference method, audit trail design, and lessons from a prototype tested on simulated data.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Developer shares standalone GitHub editions of open source tools he uses daily

A full-stack developer has published standalone editions of several well-known open source projects in his own GitHub account. The projects include public-apis, free-for-dev, markitdown, and ui-ux-pro-max-skill, each credited to its upstream source. He says he maintains these copies so his workflow keeps working if upstream repositories change, lets him pin specific versions, and applies consistent docs, dependency updates, CI, and linting. He encourages readers to star the original projects first and invites feedback on how others handle upstream updates.

0
ProgrammingDEV Community ·

Developer Uses Regex Whitelist Before LLM to Safely Run Voice Commands

A developer built a voice-controlled home automation server for their website that lets users trigger actions like turning lights on or off or starting backups. To prevent spoken input from being turned into arbitrary shell commands, the system first checks the transcribed text against a strict regular-expression whitelist, rejecting anything that doesn't match a known pattern with a 400 error. Browser speech recognition via the Web Speech API sends the transcript to a Node.js server, where validated inputs are mapped to hardware parameters. A language model then generates the final command using a static prompt that never includes the raw user text, which guards against prompt injection. The author argues the regex gate adds negligible overhead while providing deterministic protection.

0
ProgrammingDEV Community ·

Tenant-Aware Batch Processing for Document Summarization With Usage Accounting

The article argues that summarizing multiple documents should be treated as a small data pipeline rather than a simple loop over an API endpoint. It recommends tenant-aware batches with bounded inputs, idempotency keys, and usage recorded before results are shown, so each document maps to one accountable record. Usage should be a measured or deliberately estimated value tied to the amount of text processed rather than the document count. Manifests and usage events are kept longer than raw text, subject to privacy and contractual rules, and item-level failures should not halt the rest of a batch. Retries are permitted only when the previous attempt is known to have ended without a committed result or when an idempotency key protects the operation.

0
ProgrammingDEV Community ·

Previewing a Site on a New Server Without Editing the Hosts File

Migrating a website typically involves editing the local hosts file to test it on a new server before changing DNS records. This works because browsers still send the real domain name in the HTTP Host header and TLS SNI, so the server responds as it would after a live DNS change. Visiting the server's bare IP address instead fails because the server cannot tell which site is requested. The approach has practical drawbacks: entries are local and hard to share with colleagues, wildcard subdomains are unsupported, and stock mobile devices cannot be edited. Firefox's DNS over HTTPS can also bypass the hosts file entirely, while Chrome generally still respects it.