SDK-compliant module type
Basilisk-Backed Simulation
Basilisk-backed modules package simulation models, messages, and control loops behind the same SDK-compliant boundary used by smaller numerical modules.
What it can do
Run spacecraft simulation components, attitude and orbit dynamics, flight software loops, sensor models, and Basilisk-derived message pipelines as OrbPro2-callable modules.
Reference modules
space-data-network-modules/simulation/basiliskrepos/ancillary-packages/basilisk
Contract shape
Inputs include scenario configuration, initial state, message definitions, time step policy, and requested outputs. Outputs include sampled states, messages, logs, and deterministic status records.
Authoring checklist
- Keep Basilisk message schemas mapped to SDS-backed module ports.
- Make simulation step size, event ordering, and stop conditions explicit.
- Validate against Basilisk native runs before packaging for OrbPro2.
- Keep large scenario assets outside the module unless the manifest declares them.