Using Recipes and Validating

Build the smallest scenario that proves the mission concept, then add one capability at a time.

Recipe: basic communications checkout

Use:

• metadata and a short brief
• a 600-second simulation
• GPS enabled
• Madrid and Singapore
• one enabled team
• one collection named Main
• one spacecraft with Computer, Receiver, Transmitter, Storage, Solar Panel, Battery, and Reaction Wheels
• one Number question
• one Low Bit Rate event
• one Select question about that event

The earlier pages provide each block:

• Configuring Metadata Simulation and Universe
• Configuring Ground Stations
• Defining Spacecraft
• Defining Components
• Assigning Collections and Teams
• Writing Questions in JSON
• Writing Spacecraft Events

Recipe: imagery and object detection

Start from the communications checkout, then:

1. add a Camera and suitable attitude control
2. add ground vessels or labels
3. choose an orbit and epoch that provide visibility
4. write Number or Select questions about observable targets
5. test the image from the operator workflow

See Creating Ground and Space Objects.

Recipe: component-fault assessment

1. choose one tested error-model preset
2. add the required component and model
3. schedule one non-repeating event
4. write a question about observable telemetry
5. provide a recovery path only when the learning objective requires it

Do not begin with cascading failures.

Recipe: docking or shared-resource exercise

1. define the two spacecraft
2. add and place compatible Docking Adapters
3. enable rendezvous software only on the intended craft
4. test local power and fuel buses
5. add interconnects
6. add initial docking only after dynamic docking works

See Using Neutral Assets and Docking and Configuring Power and Fuel Networks.

Validating the source file

Before loading:

• parse the JSON with a JSON-aware editor
• remove comments and trailing commas
• confirm all IDs are unique
• confirm all reference capitalization is consistent
• confirm every team explicitly sets enabled
• confirm end_time is explicit
• confirm question option indices
• confirm event times fit the duration

Validating after load

After Load Scenario:

• inspect Script
• confirm the expected team, asset, event, and question counts
• inspect the Console

After Construct Scenario:

• confirm every station exists
• confirm every enabled team exists
• confirm each team receives the intended spacecraft
• confirm component names and counts
• confirm neutral assets exist once
• confirm docking and interconnects

Running the operator test

For each team:

1. join with the team password
2. list and inspect the spacecraft
3. send a basic command
4. verify telemetry and ground access
5. open the brief
6. verify every question

Run past every event and verify its resulting behavior.

Diagnosing common failures

Symptom	Likely cause
Team missing	Disabled team or duplicate numeric ID
Team has no spacecraft	Broken team → collection → asset chain
Component missing	Unsupported class or construction failure
Question missing	Invalid type or missing required answer value
Event marker with no effect	Wrong target, model, asset, or Data key
No communications	Missing station, Receiver, Transmitter, or matching team configuration
Docking skipped	Missing endpoint asset or incompatible target components
Power or fuel link absent	Component name or terminal mismatch

Preserving the brief and source

Keep the authored JSON in version control. Studio may flatten nested values to dotted keys when exporting, and scenario JSON export omits metadata.brief.

For facilitator delivery:

1. construct and test the source JSON
2. save the Studio project
3. export the tested project as .zen
4. import that .zen into a clean Studio library
5. repeat the connection test

Give the facilitator the .zen, Studio version, credentials through a secure channel, private event timeline, and reset instructions.

The facilitator continues with Hosting a Space Range.