Appearance
Choose a Simulation Mode
Review the mode before starting. A completed simulation demonstrates the recorded path within its supported scope; it does not establish a physical or biological result.
Device validation and workflow simulation
| Mode | What it does |
|---|---|
| Device validation | Uses the selected workstation's supported device path and rejects unsupported operations. This is the default. |
| Workflow simulation | Keeps device actions on the selected workstation and allows explicitly registered internal model operations. Supported synthetic readouts are labeled in the result. |
Workflow simulation is off by default. In 0.2.0 its internal readout model supports fluorescence img without a custom schema, instrument program or raw-data export. It does not supply every missing operation, measurement type or instrument.
With your AI agent
Read the current simulation policy and revision. Explain which steps in this experiment would use device simulation and which would use an internal model. Do not change the setting yet.
After reviewing the difference, explicitly request the setting change. The agent uses the current revision, reads back the result and repeats the experiment check before starting.
In the interface
- Open System Settings → Simulation.
- Review Enable workflow simulation and change it only for the intended simulation.
- Check and preview the experiment again, then review the displayed mode before Run simulation.
The policy is saved for the workstation. A reviewed start must match the current settings revision; existing runs retain their saved plans. Disabling workflow simulation restores strict device capability checking for new runs.
Read results in the correct scope
Synthetic workflow observations are identified separately from device receipts. A remote official simulator provides different evidence from the local workflow model. Accelerated waiting times must be reported as simulation settings; they do not change the scientific protocol or prove physical timing.
The desktop simulation starts with a fresh declared load. Physical loading still requires a person in a separately verified execution path; the 0.2.0 hardware-run button is disabled.
Next: Start and Monitor or Results and History.