Mercurys

Part of the Celestial project.

Mercurys is a Rust Mercury-system simulation core.

It computes state, evolves that state over time, and exposes simulation-ready data for downstream consumers. It is meant to sit behind endpoints, IPC, or another orchestrating runtime. It is not a UI crate, not a viewer, and not a frontend.

Scope

Mercurys currently ships as:

• a Cargo package named mercurys
• a Rust library crate imported as mercurys
• a runtime binary named mercurys

The project combines scientific subsystems for:

• atmosphere
• biosphere
• geodata
• geology
• hydrology
• lighting
• physics
• rendering-oriented physical state
• satellites
• temporal systems
• terrain

The library exposes reusable domain modules. The binary assembles them into a continuously ticking Mercury runtime.

What This Crate Is For

Use Mercurys when you need one of these:

• a Rust dependency for Mercury-system simulation logic
• a runtime process that advances Mercury state continuously
• a backend core behind REST, gRPC, WebSocket, CLI, or custom IPC endpoints
• an orchestrated Mercury node inside a larger multi-body simulation system
• a downstream consumer of scientific primitives provided by sciforge

What This Crate Will Not Do

Mercurys does not provide:

• any UI
• any viewer
• any frontend
• any visualization layer
• any render window or presentation loop
• any bundled large datasets
• any hardcoded dependency on sibling repositories

Key Physical Parameters

Key Features

• Exosphere with species column densities and Jeans escape modeling
• 3:2 spin-orbit resonance (solar day = 176 Earth days)
• Extreme temperature range (100 K nightside — 700 K subsolar)
• Giant iron core (> 60 % of planet mass)
• Lobate scarps and tectonic contraction seismicity
• MESSENGER and BepiColombo mission orbital parameters
• Caloris basin impact modeling
• Permanently shadowed crater polar ice deposits

Current Status

• version: 0.0.1
• edition: 2024
• license: MIT
• validation gates: cargo fmt, cargo clippy, cargo test

Architecture

Mercurys is split into domain modules plus a runtime binary.

Package Name, Library Name, Binary Name

• Cargo package name: mercurys
• Rust library import path: mercurys
• binary name: mercurys

Dependency declaration:

[dependencies]
mercurys = "0.0.1"

Rust import path:

use mercurys::physics::orbit;

Runtime Binary

The binary in src/main.rs is a long-running simulation process. It constructs a full Mercury state object, advances simulation time continuously, and keeps running until externally stopped. It does not open a window, draw frames, or embed any visual dashboard.

Why There Is a rendering Module

The rendering module provides physically meaningful data structures for atmospheric scattering (null on Mercury), PBR material parameters for the dark regolith surface, and shader-oriented uniforms. It does not make this crate a visual application.

Examples

• cargo run --example climate_sim
• cargo run --example earthquake_sim
• cargo run --example tidal_sim

Validation

cargo fmt --check
cargo clippy
cargo test

sciforge Strategy

Mercurys is intentionally downstream from sciforge. Mercury-specific orchestration belongs here; reusable scientific primitives should move upstream into sciforge when appropriate.

Related Project Files

• CHANGELOG.md: current implemented state
• ComingSoon.md: detailed roadmap and blocked items
• LICENSE: MIT license text