Opening workspace…
Read-only snapshot — run the workbench locally for the full interactive version. Get vivarium-workbench on GitHub →

Loading…

Vivarium Workbench

A local, git-backed workspace for building, running, and sharing multi-scale simulations of cells and other living systems.

What is Vivarium?

Vivarium is a framework for integrative, multi-scale modeling. Instead of one monolithic model, you write small, self-contained Processes — each describing one mechanism (metabolism, gene expression, physics, transport) — and wire them together into Composites that share state through a typed bigraph. Processes advance in time (Temporal) or transform state as dataflow (Steps), and any composite can itself be used as a process inside a larger one. This makes models modular, reusable, and composable across scales — from molecules to whole cells to colonies.

Built on process-bigraph and bigraph-schema.

What is the Workbench?

The Workbench is a web UI over a Vivarium workspace — a directory of composites, studies, investigations, and data. It reads and writes that workspace, committing every action to a git branch so you get a full audit trail. From here you can browse the registry, configure and run simulations, explore a composite's wiring, organize work into studies and investigations, and view the resulting reports and visualizations.

How to use it

  • Resources — the datasets, references, and expert notes your work draws on.
  • Catalog / Processes — browse every Composite and Process. Open a card to Configure its parameters, choose Observables and an emitter, Explore its bigraph, and Run it — the run's progress and figures appear under Outputs.
  • Studies — organize runs into investigations that pose a question and gate on an expected result.
  • Runs — every simulation you've launched, with its results and artifacts.
  • Analysis — tools and viewers matched to what your runs produced.

Tip: start on Catalog → Composites, open ecoli_baseline (or any composite), set Steps, and hit ▶ Run.

Loading audit…

Source

Loading…

Sort

Loading…

Loading…

Loading…

How this page works

This page controls where this workspace runs and how your work syncs with GitHub — two separate jobs, one per card below.

Source — where this workspace runs

  • Local is a workspace checked out on this machine; Cloud is a build registered on the GovCloud sms-api server.
  • Pick a Repo / Branch / Commit (or build), then Open ↗ to open it in a new tab (instant, non-destructive), or Use this environment to re-point this tab to it — that downloads the cloud environment's workspace the first time (a minute or two; cached builds are instant). You don't need to use the cloud environment to view results.
  • Build via sms-api registers a branch's current HEAD as a new cloud environment. Run locally gives you a command to recreate this exact source on your own machine.
  • In the build list, chips flag which build is in workspace ✓, on your workspace commit, or the latest.

GitHub — sync & collaborate

  • Account — the GitHub identity used to push (your gh session, or a pasted token).
  • Branch & sync — the workspace's git state: the branch vs its base, uncommitted Changes + push state, and any open pull request.
  • Commit + Push commits every change on the branch and pushes it; Open PR starts a pull request from it.

GitHub

Sync this workspace with GitHub — sign in, commit & push, open a PR.

Account

Signed in as
Uses your gh session, or paste a token for browser-based push.

Branch & sync

Branch
loading…
Changes
—
Pull request
—

Actions

Sync

Studies

Browse every study in the workspace — filter, sort, and open any of them (each belongs to an investigation).

Loading studies…

Loading…
Loading composite…