Docs tagged “concepts”

Heavy scientific compute such as folding, docking, ADMET, generative design and omics, which runs as tracked jobs, produces artifacts, and uses credits.

Every platform concept, grouped into five clusters. Each cluster answers one question about how work moves through the platform.

Instant, inline lookups against external databases — compounds, targets, literature, and trials — that return directly in the canvas with no job to track.

Close-cousin concepts, side by side — pick the right surface, work unit, and organizational container for the task in front of you.

Every platform term in one place — grouped by concept cluster, then listed A–Z for lookup.

You describe a goal in plain language and the orchestrator maps it to tools and chains them. This page covers what happens in between and how to steer it.

Every tool runs as a tracked compute job, an instant lookup, or code in the chat's workspace, and that decides its latency and cost.

Bench-automation bridges and data-processing utilities — protocol generation for lab robots and server-side data transforms.

How the platform fits together in 90 seconds — one request becomes tools, a recorded run, and an artifact you can keep.

What a predicted structure, pose or property score has been shown to agree with experimentally, how that agreement is measured, and where the figures stop.

A bridge to a hosted Galaxy bioinformatics server that adds sequencing and genomics tools as an HTTP-async execution class, separate from GPU jobs.

A passport aggregates several tools into one profile. Here is the model behind it, how it differs from running tools yourself, and when to reach for one.

Start from the outcome, not the tool. Most goals are served by more than one tool that does roughly the same thing — here's the capability and which tool fits.