Credentials. Keep the model parameters and their terms of use in mind when copying files between machines.
Who it is forA lab sharing one GPU across many predictions.
The problemThe data pipeline is slow and does not need the GPU, so it wastes GPU hours.
The outcomeA split workflow where the expensive search runs where it is cheap.
What you need first
- The model parameters, which you may only use if received directly from Google, under the weights terms of use
- Docker and an NVIDIA GPU for the inference step
- The genetic and template databases for the data pipeline, mounted into the container
- A fold_input.json describing your sequences, model seeds, dialect and version
Steps
- Install AlphaFold 3 as described in docs/installation.md
- Run
python run_alphafold.py --helpto list all the available flags - Run the data pipeline alone with
--run_data_pipelineset to true and--run_inferenceset to false on a machine without a GPU - Run inference alone on the GPU machine with
--run_data_pipelinefalse and--run_inferencetrue, reading docs/performance.md for tuning
Prompt for your agent
With google-deepmind/alphafold3, show me how to run the data pipeline on my CPU server and inference on my GPU server using --run_data_pipeline and --run_inference, and what to copy between them.
Caveat. The data pipeline needs the genetic and template databases, which are large.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for google-deepmind/alphafold3 and "Run the CPU search and the GPU fold on different machines"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer