Astronomical Observing Conditions
Cloud cover, sky transparency, seeing, dew point, and moon phase — the specific combination of conditions an imaging session actually depends on.
Project / EDS
EDS is MDNT's sensing-to-alerting pipeline for environmental conditions: it ingests environmental telemetry, models near-term change, and turns the result into structured forecasts, alerts, and operational awareness for the teams that need to act on them.
System Overview
EDS started as a practical problem, not an abstract one: deciding whether a night is actually worth setting up for astrophotography, and keeping optics clear of dew once a session is running. That recurring, concrete decision — cloud cover, sky transparency, seeing, and dew point, all changing hour to hour — shaped the system's core sense-forecast-alert loop well before it was generalized into a broader environmental decision-support pipeline.
EDS is built as a layered pipeline rather than a single monolithic tool. Sensing sources feed a normalization and modeling layer, which produces forecasts and evaluates them against configurable thresholds, which in turn drives alerting and awareness outputs. Each layer is designed to evolve on its own schedule — new sensing sources, refined models, and additional output channels can be added without reworking the system end to end.
The goal is continuous, structured visibility into changing environmental conditions, not a one-off report or a static map. EDS is designed for teams that need to track conditions over time and respond when they change — environmental monitoring groups, infrastructure operators, and field research teams — rather than for a single fixed use case. It is currently an active prototype: core ingestion and modeling are running against real test data, and the surrounding system is still being shaped around that foundation.
Sensing Inputs
EDS treats sensing as a plural, extensible layer rather than a dependency on any single feed. Sources are normalized into a common schema so the modeling layer can reason over them consistently, regardless of where a given signal originates.
Cloud cover, sky transparency, seeing, dew point, and moon phase — the specific combination of conditions an imaging session actually depends on.
Wind, precipitation, temperature, humidity, and pressure readings from ground stations and public weather feeds.
River, reservoir, and coastal water-level sensors used to track hydrological change over time.
Satellite and aerial imagery layers used to contextualize and cross-check ground-level sensor readings.
Distributed, IoT-class sensor nodes reporting localized environmental conditions from fixed or mobile deployments.
Long-run historical datasets used to establish baselines, seasonal patterns, and anomaly thresholds.
Public and institutional environmental datasets integrated as supplementary context around primary sensing sources.
Forecasting & Alerting Model
Between sensing and awareness sits a modeling pipeline that turns unstructured signal into evaluated, actionable state. Each stage narrows the data down — from raw readings to a small number of alerts that actually warrant attention.
Raw sensor and feed data is collected, timestamped, and queued for processing.
Inputs are cleaned, aligned to a common schema, and checked for gaps or sensor faults.
Statistical and machine-learning models estimate near-term environmental conditions.
Forecasts are compared against configurable thresholds and historical baselines.
Qualifying conditions generate structured alerts routed to the relevant channel.
Operational Awareness Outputs
The output layer is designed around how conditions actually get used day to day: quick situational read, spatial context, timely notification, and a record to look back on.
Condensed, human-readable summaries of current and forecasted environmental state.
Map-based views that place sensor data, forecasts, and alerts in spatial context.
Configurable notification channels for qualifying conditions and threshold breaches.
Time-series views for tracking how conditions evolve against baseline patterns.
Structured exports for downstream analysis, recordkeeping, or integration with other systems.
Closed-loop outputs that act directly on hardware — such as automated dew-heater regulation — not just notifications for a person to read.
Prototype Status
EDS is under active development. The system is being built layer by layer, with each stage validated against real test data before the next is added — rather than shipped as a single fixed release.
Core ingestion and normalization for initial sensing sources is in place and running against live test data.
Baseline statistical forecasting is operational; machine-learning model refinement is ongoing.
Threshold-based alert generation exists; delivery channels are being expanded and hardened.
Awareness outputs are being designed as structured views rather than a fixed dashboard product.
Structured pilot integrations with real sensing sites are the next milestone.
Note Interface captures and system diagrams will be published here as the prototype matures.
Collaboration
MDNT is open to focused collaboration on EDS: sensing integrations, forecasting model design, environmental data partnerships, and structured field pilots. If your work touches environmental monitoring, infrastructure operations, or applied environmental research, get in touch.
20F4 1435 3E7E A1A6 7EC0
EA11 8DFF F119 FF5B 8464
-----BEGIN PGP PUBLIC KEY BLOCK----- xjMEalDKCRYJKwYBBAHaRw8BAQdAgNOFm8pBHMT/aRdKjxiGKat9yaTZQV0B jtic3+tSzvzNG2xhYnNAbWRudC5wdCA8bGFic0BtZG50LnB0PsLAEQQTFgoA gwWCalDKCQMLCQcJEI3/8Rn/W4RkRRQAAAAAABwAIHNhbHRAbm90YXRpb25z Lm9wZW5wZ3Bqcy5vcmckEPEU0W1M01ix+48GvMHDz07lTXtJZ2ZP7vr8QTU/ 9QMVCggEFgACAQIZAQKbAwIeARYhBCD0FDU+fqGmfsDqEY3/8Rn/W4RkAAAN lwD/Qq5jmcu9TiEyNexgqRAb4hWSEHxBJIdEkMWIxeeRuYkA/0yZzdoxKuUl OrvWQr6YaJZkxlh/dzc6d1L6mLvnH5wBzjgEalDKCRIKKwYBBAGXVQEFAQEH QLvXLPszOZ6egFG8N3wRJ6h5blm164WpNfTJviOrYEp4AwEIB8K+BBgWCgBw BYJqUMoJCRCN//EZ/1uEZEUUAAAAAAAcACBzYWx0QG5vdGF0aW9ucy5vcGVu cGdwanMub3JnMH+xpvowDplsJoB2TZeF2V4tKCmgfj4RX5635Q1nVwwCmwwW IQQg9BQ1Pn6hpn7A6hGN//EZ/1uEZAAAEzIBANhXi4zG/UyEFcvhWE8EAnFI nKIiXzVeCGype1l2/12tAP9Cyekpb4NStGIPCUfPZ87v7YMWCssDXkQaxv74 sqpyCQ== =zuPU -----END PGP PUBLIC KEY BLOCK-----