← Back to the architecture page
MoCSI · thermophysical model

How a simulation run flows

The big picture: the five stages every MoCSI run passes through, from your configuration to temperature output. For the class-level view, see the detailed diagram in the docs.

Inputs → setup builds the grid & picks modules → modules fill the field map → the time loop solves the heat equation each step → results stream out.

📥

1 · Inputs

What you provide to describe a run

ConfigurationThe .ini files that fully describe a run.
Shape modelOptional surface mesh of the body.
SPICE kernelsOptional orbit/ephemeris data.
SnapshotOptional — restart from a saved state.
↓
⚙️

2 · Setup

Runs once, before the time loop

Read the configParse the .ini files into settings.
Build the gridSurface + depth discretization.
Pick the modulesLoad just the physics you asked for.
↓
🧩

3 · Physics modules

Each module owns one property and keeps it current

Albedo & emissivitySurface optical properties.
Density & heat capacityHow much heat the material stores.
Heat conductivityHow heat moves through the body.
Solar geometrySun–target distance, solar vector and heat sources.

These are just examples — MoCSI ships more modules (and you can add your own). See the full list in the docs.

↓
🔁

4 · Time loop

Repeats every time step until the run completes

⟳ each step: assemble → apply boundary conditions → solve → update temperature
AssembleBuild the equations from the grid and module values.
Boundary conditionsDefault: surface energy balance — sunlight in, radiation out.
SolveCompute the new temperature field for this step.

The default is the surface energy balance shown here — MoCSI ships other boundary conditions too (e.g. fixed-temperature, constant-heat-flux). See the full list in the docs.

↓
📤

5 · Outputs

What you get back

SnapshotA full restore point — final field plus the exact configuration.
CSV resultsField values streamed during the run.
Inputs & setup Physics modules Time loop (repeats) Outputs