AURORA operations¶
I start with JASMIN, check Operations, and then follow the affected stream from its source to the displayed observation. Data-ocean is the development mirror. A page response or a recent transfer stamp is not enough to call a stream healthy.
Start here¶
| I need to… | Guide |
|---|---|
| Check the system and collect useful evidence | Operator quickstart |
| Understand host ownership and app routing | Production and development |
| Merge and release reviewed work | Releases from main |
| Recover service or transfer writer ownership | Failover |
| Commission the read-only app fallback | Operational mobile mirror |
| Find raw data, products and archive evidence | Data locations |
| Interpret or repair archive status | Archive services and recovery |
| Check what was actually verified | Dated recovery records |
Keep the boundaries clear¶
JASMIN owns normal ingestion, products, archives and alerts. Data-ocean mirrors those products and keeps its experiments in separate paths. A client using the mirror does not transfer those responsibilities.
The production raw area is /project/aurora/raw, with products under
/data/aurora/products. Check the actual mounts and quotas: on data-ocean,
/project and /data share storage. Archives are separate additive copies on
JASMIN GWS and the object store. The development mirror is not retention proof.
Use the stream guides in the navigation for source-specific details, including BLE enclosure sensors, AURORACam, Power and Menapia flights. Development experiments describes isolated science and presentation work. The original rebuild plan and dated recovery records are history, not evidence of the current host state.
This documentation is built by GAMB2LE/mkdocs-portal. A local strict build
checks links and navigation; a successful portal deployment and a rendered page
check establish publication.