antibody-protenix-pipeline

Submit and monitor RFdiffusion-ProteinMPNN-Protenix antibody design jobs through the ScienceDiscovery NPU Broker.

64|15|Updated Aug 14, 2026
One-click install
npx skills add https://github.com/openJiuwen-ai/sciencediscovery --skill antibody-protenix-pipeline-openjiuwen-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: antibody-protenix-pipeline
Source: https://github.com/openJiuwen-ai/sciencediscovery/tree/main/skills/antibody-protenix-pipeline
Command: npx skills add https://github.com/openJiuwen-ai/sciencediscovery --skill antibody-protenix-pipeline-openjiuwen-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mindspore, numpy, pandas, biopython, scipy, scikit-learn, pyyaml, hydra-core, omegaconf, ml-collections, dm-tree, optree, tqdm, attrs, decorator, matplotlib, safetensors, sympy, rdkit, biotite, and includes scripts (resource) components.

What problem does it solve? Running a real antibody design pipeline (RFdiffusion backbone generation, ProteinMPNN sequence design, Protenix structure prediction, and epitope screening) on Ascend NPUs requires careful environment setup, correct config authoring, and disciplined job monitoring. This Skill orchestrates that entire workflow through the ScienceDiscovery Runner NPU Broker so jobs are submitted once, monitored to a terminal state, and their artifacts registered correctly. ## Core Features & Use Cases - Broker-only job lifecycle: Lists workloads, submits antibody.protenix.v1 jobs with a workspace-local config.json, checkpoints the job ID, and polls status/logs until the job reaches a terminal state. - Managed environment validation: Probes ScienceDiscovery scientific environments for pinned dependencies (mindspore 2.7.2, numpy 1.26.4, biotite 1.4.0, rdkit 2024.3.5) and creates or updates environments before submission. - Custom antigen support: Accepts user-provided target antigen PDBs, antibody framework PDBs, and chain-labelled hotspot epitopes (e.g. [B45,B46,B49]) with strict validation of run names, NPU lists, and diffuser schedules. - Use Case: A researcher uploads a custom antigen PDB and antibody framework PDB, specifies epitope residues on chain B, and requests 4 designs across NPUs 0-3; the Skill prepares the config, submits the Broker job, monitors each stage, and returns declared Project Artifacts with screening results. ## Quick Start Run the Protenix antibody pipeline with my uploaded target antigen PDB and framework PDB, using hotspots B45,B46,B49, 4 designs on NPUs 0,1,2,3, and monitor the job until it finishes.

Frequently Asked Questions about antibody-protenix-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run the Protenix antibody design pipeline on Ascend NPUs?▼

Create an antibody_pipeline/config.json with workspace-local target and framework PDB paths, hotspots, design count, and NPU list, then submit via run_npu_job with workload antibody.protenix.v1 and a probed managed environment ID. Monitor with status and logs until the job reaches a terminal state, then call result to declare artifacts.

What inputs does the antibody Protenix pipeline require?▼

The pipeline requires a workspace-local target antigen PDB, an antibody framework PDB, and one chain-labelled hotspot list such as [B45,B46,B49] using the original PDB chain and residue numbers. There is no default example PDB; missing inputs mean the run must stop and ask the user.

Which Python dependencies does the Protenix antibody environment need?▼

The managed environment needs mindspore 2.7.2, numpy 1.26.4, biopython 1.83, dm-tree 0.1.8, rdkit 2024.3.5, biotite 1.4.0, matplotlib 3.9.2, plus pandas, scipy, scikit-learn, hydra-core, omegaconf, ml-collections, optree, and others. A probe must print MANAGED_ENV_OK before submission.

Why does the antibody pipeline job fail with a hotspot mapping error?▼

A hotspot_mapping_error means the requested original PDB residue cannot be mapped to the Protenix sequence, usually due to an absent residue or ambiguous insertion code. The correct action is to ask the user to fix the chain/residue list, not to guess replacement residues or report zero contacts.

Can I launch the Protenix pipeline with run_shell or nohup instead of the Broker?▼

No. All model and NPU execution must go through run_npu_job with workload antibody.protenix.v1; host_bridge, nohup, device passthrough, and shell-launched model runs are forbidden. run_shell is only allowed for small file operations, import probes, and a single sleep TICK per monitoring cycle.

What happens if the Broker job creates more than 50 files?▼

The result call declares only the first 50 createdFiles as Project Artifacts. The remaining files stay in the Session workspace under antibody_pipeline/runs/<run_name>/, and antibody_pipeline/artifact_manifest.txt lists them, which the final response must tell the user.