Studio quickstart
Open a published lab on the Hub, run your own copy in Studio, then compare two runs. Nothing to install.
Some buttons on the Hub say “Chat”. They open Studio.
Before you start
- Time: about 5 minutes.
- Requirements: a browser and a Biosimulant account. You can browse the Hub without one.
- Outcome: two completed runs of the Lotka-Volterra lab, compared side by side.
Step 1: open a lab on the Hub
Open the Lotka-Volterra System Lab. You don’t need an account for this part.
The lab page has four tabs:
- About: what the model is, how to read its plots, and its inputs and outputs.
- Compose: the models in the lab and how they’re wired together.
- Results: public runs of the lab, if anyone has shared one.
- Experiments: experiments people have run against the lab.
The Hub is read-only. To run a lab or change it, you open it in Studio.
Step 2: open it in Studio
- Click Actions, then Run from Chat. Studio opens in a new tab with the lab’s Runs panel showing.
- Click Log in at the top right. Studio brings you back to the same lab.
Studio gives you a private draft copy of the lab, so nothing you do here changes the published version.
If you want to change the model itself rather than its settings, pick Edit as copy in Chat instead. That opens the lab on the Canvas.
Step 3: change a parameter and run
- In the Runs panel, click Run current revision.
- The Run immutable Draft Lab revision dialog opens. Under Runtime, check Duration (250 by default) and Comms Step (0.01 by default).
- Inputs and Component Parameters hold the model’s values. Leave them alone for this first run.
- Click Queue run.
The run appears in the list, and its status moves from queued to running to completed. You can close the tab while it runs and find it later under Runs in the left sidebar.
Step 4: run again and compare
- Click Run current revision again. This time open Inputs and raise
prey_growth_rate. - Click Queue run and wait for it to finish.
- Tick both runs in the list and click Compare.
The comparison puts each run’s Effective configuration next to its Visuals, so you can see what you changed and what it did. Copy Link gives you a URL you can send to someone.
Verify the result
- Both runs show
completed. - Select the first run. Results and Visualizations show the population trajectory and the phase portrait. Prey rise first, predators follow a little later, and the phase portrait traces a closed loop.
- Artifacts lists the files you can download, and Execution log shows the run’s log output.
- In the comparison, the run with the higher
prey_growth_ratecycles around a higher predator count.
Troubleshooting
- “Create a runnable revision first”: there’s no revision selected to run. Pick one from the revision menu next to Run current revision, or reopen the lab from the Hub.
- “This Lab is not available to your account”: the lab is private or no longer published. Go back to the Hub and choose a public lab.
- The run stays
queued: give it a minute. Runs keep going after you close the tab, so check back under Runs in the left sidebar. - You want a script instead of clicks: the Developer API quickstart runs a lab from Python.
Next steps
- Developer API quickstart: run a pinned lab from your own code and get the results back.
- Use Biosimulant from Codex or Claude: have an agent find and run labs for you.
- Library quickstart (Python): write a simulation and run it on your own machine.