Orchestrating molecular design workflows
Protocols let you describe a multi-step molecular design job — chained model calls, gather/aggregation steps, filters, and structured outputs — as a single declarative YAML file. You author and validate the YAML locally, then either run it on your machine (Local Protocol Profile) or submit inputs to a registered slug on the BioLM platform.
This section is split into focused guides:
Choose local vs hosted
Local execution |
Hosted execution |
|
|---|---|---|
Where it runs |
Your machine ( |
BioLM platform servers |
Entry points |
|
|
Input format |
|
JSON file keyed to protocol |
Feature set |
ApiTask DAG, |
Full protocol (gather, foreach, task-output expressions, …) |
Best for |
Fast iteration, offline dev, CI smoke tests |
Long runs, sharing by slug, full platform features |
See Local Protocol Profile v1 for the exact local feature matrix.
Guides in this section
Authoring and Validating Protocols — scaffold, inspect, and validate YAML
Running Protocols Locally —
run-local,Protocol.execute(), outputs selectionRunning Protocols on the Platform — submit, wait, download, MLflow logging
Local Protocol Profile v1 — Local Protocol Profile v1 reference
See also
Orchestrating molecular design workflows — protocols vs pipelines vs model one-offs
Managing datasets — platform datasets for protocol inputs
Protocol Schema Reference — full protocol YAML field reference
biolm.protocols — Python API reference
biolm protocol — CLI command reference