Skip to navigation

Performance in OpenFold3 NIM

View as Markdown

NIM Accuracy

OpenFold3 is an all-atom biomolecular complex structure prediction model from the OpenFold Consortium and the AlQuraishi Laboratory. OpenFold3 is a PyTorch implementation of the JAX-based AlphaFold3 reported in Accurate structure prediction of biomolecular interactions with AlphaFold 3. Like AlphaFold3, OpenFold3 extends protein structure prediction capabilities to model complete biomolecular complexes including proteins, DNA, RNA, and small molecule ligands.

The OpenFold3 NIM’s accuracy should match that of the AlQuraishi Laboratory implementation of OpenFold3, when using equivalent parameters and inputs.

Running on hardware that is not listed in the Support Matrix might produce results that deviate from the expected accuracy.

The accuracy of the NIM is measured by structural quality metrics such as lddt (local distance difference test). These scores help assess the reliability of the predicted structures.

Factors Affecting NIM Performance

The performance of the OpenFold3 NIM is determined by several key factors:

Hardware Factors

  • GPU type and memory: Different GPU architectures provide different performance levels
  • System RAM: Larger proteins and complexes require more system memory
  • Storage speed: Fast NVMe SSD storage improves model loading and caching performance

Input Complexity

  • Sequence length: Runtime increases with total sequence length
  • Number of chains: Multi-chain complexes require more computation than single chains
  • MSA size: Larger MSAs can improve accuracy but increase memory usage and computation time
  • Ligands, DNA, RNA: Additional molecular components increase computational cost

Model Configuration

  • Diffusion samples: Multiple samples provide diversity but multiply computational cost

Performance Characteristics

Typical Runtimes

For reference, approximate runtimes on high-end hardware (NVIDIA H100 80GB):

Structure Prediction (OpenFold3 NIM v1.6.0 on NVIDIA H100 80GB):

  • ~200 residues: 2.9-3.6 seconds
  • ~300-400 residues: 4.5-12.6 seconds
  • ~500-600 residues: 11.6-26.8 seconds
  • ~800-900 residues: 20.6 seconds
  • ~1300-1500 residues: 30.5-53.1 seconds
  • ~1700-1900 residues: 56.5-72.5 seconds
  • Memory usage: Varies with sequence length, typically 40–80 GB GPU memory

Short sequences improved substantially in 1.6.0. In earlier releases, runtime below roughly 400 residues was dominated by fixed per-request overhead rather than by the model itself, so a 186-residue input cost almost as much as a 600-residue one. CUDA graph capture removes most of that overhead, so runtime now tracks sequence length across the whole range.

The total runtime for structure prediction depends on:

  • Total number of residues in the complex
  • Total number of atoms in the complex
  • Number of molecules and chains
  • Number of sequences in the MSAs
  • Number of diffusion samples requested

Performance Results on H100

The following table shows OpenFold3 NIM runtime on NVIDIA H100 80GB, with and without structural template processing.

Structural template support is available in version 1.1.0 and later.

Test IDSeq LengthWithout structural templates (s)With structural templates (s)
8eil1862.934.62
7r6r2033.644.94
1a3n28712.6322.54
8c4d3314.555.01
7qsj3755.806.57
8cpk3849.2110.98
8are53011.5612.47
8owf57512.6812.94
8aw359026.8428.34
7tpu6169.7610.66
7ylz62317.5418.80
8gpp62815.2821.33
8clz68416.3617.96
8k7x85820.6222.30
8ibx128630.4632.26
8gi1146443.9346.70
8sm6149653.1258.54
8pso149942.7245.76
8jue165756.5261.74
8bsh176263.1968.27
5xgo186972.5287.65

All runtimes are in seconds for end-to-end structure prediction with a single diffusion sample. The template measurements include an average of 4 CIF template files per protein chain. The additional time is primarily attributed to CIF parsing.

Performance Analysis

Key Observations:

  • Scaling Behavior: Runtime increases with total sequence length and with the number of chains and atoms in the complex.
  • Change from 1.5.0: CUDA graph capture removed a fixed per-request cost of roughly 7-8 seconds on H100, so comparing these numbers with the 1.5.0 table shows a ratio that shrinks as inputs grow, from about 3.5x at 186 residues to about 1.15x at 1869, even though the same amount of time was saved in both cases. Read the difference between the two releases, not the ratio.
  • Hardware range: The fastest SKUs (GB200, GB300) complete typical predictions in roughly 75% of the H100 time, with B200, H200 and GH200 at 88–91%. A100-class parts take 1.4–1.7x the H100 time. Refer to Table 1 for per-SKU numbers.
  • Small proteins (fewer than 400 residues): Complete in ~3-13 seconds on H100.
  • Large proteins (more than 1,500 residues): Complete in ~43–73 seconds on H100.

Template Processing Impact:

  • Template overhead: Structural templates add modest overhead (typically 1-9 seconds) depending on sequence length and chain count.
  • Primary cost: The additional time is mostly attributed to CIF parsing (average 4 templates per chain).
  • Overall impact: Templates provide structural guidance with minimal performance cost.

Recommended Configuration:

  • For large proteins (more than 1,800 residues): Prefer high-memory GPUs; actual requirements depend on workload (MSA depth, templates, and molecule composition). Refer to Table 1 for measured per-SKU results.
  • For template-guided predictions: Structural templates add minimal performance overhead.

Configuration

The benchmarks use the following configuration:

ParameterSetting
diffusion_samples1
output_formatpdb
GPUH100 80GB
structural_templatesAverage 4 CIF files per chain

Performance Metrics

The following table contains end-to-end runtime (seconds) for the OpenFold3 NIM across supported NVIDIA hardware units. Inputs are the same 21 benchmark cases, arranged by sequence length and annotated with PDB ID and sequence length.

Table 1: Performance Across the Supported NVIDIA Hardware Units

The table shows the prediction times for tests with varying sequence lengths for hardware units. It features the following:

  • Hardware: Nineteen supported GPU SKUs (NVIDIA H100 80GB HBM3, H100 NVL, H100 PCIe, H200, H200 NVL, B200, B300, GB200, GB300, GH200, A100 SXM4 80GB, A100 80GB PCIe, A100 SXM4 40GB, A100 40GB PCIe, L40S, RTX PRO 6000 Blackwell Server Edition, RTX PRO 6000 Blackwell Workstation Edition, RTX 6000 Ada Generation, and DGX Spark GB10). One tab per SKU.
  • Metric: End-to-end predict time (seconds).
  • Configuration: Default model; no structural templates. Inputs sorted by sequence length and annotated with PDB ID and sequence length.

A dash (—) means the case was not measured on that SKU. The benchmark suite caps input length on memory-constrained parts: 1500 residues on the 40-48 GB GPUs (L40S, RTX 6000 Ada, A100 SXM4 40GB, A100 40GB PCIe) and 1800 residues on GB10. These are benchmark limits, not limits the NIM enforces. The NIM itself imposes no maximum sequence length. Longer inputs on those GPUs may still run, but are not covered by these measurements.

Test IDSeq Lengthpredict_time (s)
8eil1862.93
7r6r2033.64
1a3n28712.63
8c4d3314.55
7qsj3755.80
8cpk3849.21
8are53011.56
8owf57512.68
8aw359026.84
7tpu6169.76
7ylz62317.54
8gpp62815.28
8clz68416.36
8k7x85820.62
8ibx128630.46
8gi1146443.93
8sm6149653.12
8pso149942.72
8jue165756.52
8bsh176263.19
5xgo186972.52

Performance Optimization Tips

  • GPU Selection: Use any of the supported GPUs listed in Table 1. For best throughput, prefer higher-performance SKUs such as B200, H100, and H200.
  • Sequence Length: Performance scales with sequence length.
  • Multiple Samples: Setting diffusion_samples > 1 increases runtime in affine fashion (input featurization time is independent of diffusion_samples).
  • MSA Size: While larger MSAs can improve accuracy, they also increase memory usage and computation time. Consider filtering MSAs for very large proteins.
  • Structural Templates: Templates add modest overhead (1-10 seconds) but can significantly improve prediction accuracy. Refer to Template Processing for guidance.
  • Batch Processing: Requests are not batched. For multiple independent predictions, process them sequentially, serve them from a container with several GPUs (refer to Serve Requests on Multiple GPUs), or use multiple NIM instances.
  • Memory Management: Ensure adequate GPU memory for your target sequence lengths. Very long sequences (more than 1,800 residues) are memory-intensive, and actual requirements depend on workload characteristics (MSA depth, templates, and molecule composition). Refer to Table 1 for measured per-SKU results.

Reproduce Performance Benchmarks

Overview

This section provides scripts and instructions for reproducing the performance metrics reported above. The benchmarking process is as follows:

  1. Run inference with OpenFold3 NIM to generate predicted structures
  2. Use OpenStructure (OST) to compare predictions against reference structures
  3. Extract accuracy metrics like lDDT (local Distance Difference Test)

Prerequisites

Run the OpenFold3 NIM

Before running benchmarks, ensure that OpenFold3 NIM is deployed and running. The benchmarking scripts send inference requests to the NIM service.

Verify NIM is Running:

# Check if NIM is accessible and ready
curl http://localhost:8000/v1/health/ready
# Expected response:
# {"object":"health.response","message":"ready","status":"ready"}

The default NIM URL is http://localhost:8000. If your NIM is running on a different host or port, specify it using the --nim-url parameter when running benchmarks. For detailed deployment instructions and configuration options, refer to the Getting Started guide.

Install the OpenStructure Docker Image

OpenStructure is a computational structural biology framework that provides tools for structure comparison and validation. You need the OpenStructure Docker image for running benchmarks:

# Pull the latest OpenStructure image from the OST registry
docker pull registry.scicore.unibas.ch/schwede/openstructure:latest
# Verify the installation
docker run --rm -v $(pwd):/home registry.scicore.unibas.ch/schwede/openstructure:latest --version
# Expected response:
# OpenStructure 2.11.1

Download Reference Structures

You need reference structures (ground truth) in CIF format for comparison. These are experimentally determined structures from the Protein Data Bank (PDB):

  • CIF (Crystallographic Information File): A standard format for representing molecular structures, including atomic coordinates, experimental metadata, and structural annotations
  • Obtaining reference structures: Download from RCSB PDB using the PDB IDs from the performance table (for example, 8eil, 7r6r, 1a3n)

Example:

# Create directories
mkdir -p references
# Download a reference structure (for example, 8eil) to references folder
wget https://files.rcsb.org/download/8eil.cif -O references/8eil.cif

Prepare Input JSON Files

What are Input JSON Files?

Input JSON files contain the sequence information needed for OpenFold3 NIM to make predictions. They are an intermediate format: benchmark_openfold3.py converts each file into a NIM API request. Each file specifies:

  • Protein sequences (amino acid chains)
  • Chain IDs
  • Optional: DNA, RNA, ligands, MSAs, templates

Example Input JSON Structure

{
"name": "8eil",
"sequences": [
{
"protein": {
"id": "A",
"sequence": "MKQHKAMIVALIVICITAVVAALVTRKDLCEVHIRTGQTEVAVF..."
}
}
]
}

Create Input JSON Files

You can create input JSON files by extracting sequences from PDB structures. Save this script as generate_inputs.py:

#!/usr/bin/env python3
"""Generate input JSON files from PDB structures."""
import argparse
import json
import requests
import sys
from pathlib import Path
def fetch_sequences_from_pdb(pdb_id):
"""Fetch protein sequences from RCSB PDB FASTA endpoint."""
url = f"https://www.rcsb.org/fasta/entry/{pdb_id}"
response = requests.get(url)
if response.status_code != 200:
raise Exception(f"Failed to fetch FASTA for {pdb_id}")
sequences = []
current_seq = []
chain_index = 0
for line in response.text.strip().split('\n'):
if line.startswith('>'):
if current_seq:
# Use sequential chain IDs: A, B, C, D, ...
chain_id = chr(65 + chain_index)
sequences.append({
"protein": {
"id": chain_id,
"sequence": ''.join(current_seq)
}
})
chain_index += 1
current_seq = []
else:
current_seq.append(line.strip())
# Don't forget the last sequence
if current_seq:
chain_id = chr(65 + chain_index)
sequences.append({
"protein": {
"id": chain_id,
"sequence": ''.join(current_seq)
}
})
return sequences
def create_input_json(pdb_id):
"""Create OpenFold3 input JSON file for a PDB structure."""
output_dir = Path("inputs")
output_dir.mkdir(parents=True, exist_ok=True)
print(f"Fetching sequences for {pdb_id}...")
sequences = fetch_sequences_from_pdb(pdb_id)
input_data = {
"name": pdb_id,
"sequences": sequences
}
output_path = output_dir / f"{pdb_id}_input.json"
with open(output_path, 'w') as f:
json.dump(input_data, f, indent=2)
print(f"Created {output_path} ({len(sequences)} chain(s))")
return output_path
if __name__ == "__main__":
# All benchmark PDB IDs from performance table
benchmark_pdbs = [
"8eil", "7r6r", "1a3n", "8c4d", "7qsj", "8cpk",
"8are", "8owf", "8aw3", "7tpu", "7ylz", "8gpp",
"8clz", "8k7x", "8ibx", "8gi1", "8sm6", "8pso",
"8jue", "8bsh", "5xgo"
]
parser = argparse.ArgumentParser(
description='Generate OpenFold3 input JSON files from PDB structures',
epilog='Example: python generate_inputs.py --pdb 8eil'
)
parser.add_argument('--pdb', type=str,
help='Specific PDB ID to generate input for (e.g., 8eil)')
parser.add_argument('--all', action='store_true',
help='Generate input files for all benchmark PDB IDs')
args = parser.parse_args()
# For backwards compatibility: if no arguments provided, generate all
if not args.pdb and not args.all:
args.all = True
if args.pdb:
# Generate input for specific PDB ID
try:
create_input_json(args.pdb)
except Exception as e:
print(f"Error processing {args.pdb}: {e}", file=sys.stderr)
sys.exit(1)
elif args.all:
# Generate all benchmark inputs
print("Generating input files for all benchmark cases...")
failed = []
for pdb_id in benchmark_pdbs:
try:
create_input_json(pdb_id)
except Exception as e:
print(f"Error processing {pdb_id}: {e}")
failed.append(pdb_id)
if failed:
print(f"\nFailed to generate inputs for: {', '.join(failed)}", file=sys.stderr)
sys.exit(1)

Benchmarking Script

The following is a complete script to benchmark OpenFold3 NIM predictions. Save this as benchmark_openfold3.py:

#!/usr/bin/env python3
"""
Benchmark OpenFold3 NIM predictions against reference structures.
"""
import argparse
import json
import subprocess
import time
from pathlib import Path
import requests
def run_inference(nim_url, input_json, output_dir):
"""
Run OpenFold3 NIM inference and save the predicted structure.
Args:
nim_url: URL of the OpenFold3 NIM service (e.g., http://localhost:8000)
input_json: Path to input JSON file with sequence information
output_dir: Directory to save predicted structures
Returns:
tuple: (predicted_pdb_path, inference_time_seconds)
"""
output_dir = Path(output_dir)
output_dir.mkdir(parents=True, exist_ok=True)
# Read input configuration
with open(input_json, 'r') as f:
input_data = json.load(f)
# Convert to NIM API format
molecules = []
for seq in input_data.get("sequences", []):
if "protein" in seq:
protein = seq["protein"]
# Create minimal MSA with just the query sequence
msa_csv = f"key,sequence\n-1,{protein['sequence']}"
molecules.append({
"type": "protein",
"id": [protein["id"]],
"sequence": protein["sequence"],
"msa": {
"main_db": {
"csv": {
"alignment": msa_csv,
"format": "csv"
}
}
}
})
nim_request = {
"inputs": [{
"input_id": input_data.get("name", "prediction"),
"molecules": molecules,
"output_format": "pdb"
}]
}
# Start timing
start_time = time.time()
# Run inference
response = requests.post(
f"{nim_url}/biology/openfold/openfold3/predict",
json=nim_request,
headers={"Content-Type": "application/json"}
)
# End timing
inference_time = time.time() - start_time
if response.status_code != 200:
raise Exception(f"Inference failed: {response.text}")
# Extract PDB data from response
result = response.json()
outputs = result.get('outputs', [])
if not outputs:
raise Exception(f"No outputs in response")
structures = outputs[0].get('structures_with_scores', [])
if not structures:
raise Exception(f"No structures in response")
# Get the first (best) structure
pdb_content = structures[0].get('structure', '')
if not pdb_content:
raise Exception(f"No structure content in response")
# Save predicted structure
pdb_id = input_data.get('name', 'prediction')
pred_path = output_dir / f"{pdb_id}_pred.pdb"
with open(pred_path, 'w') as f:
f.write(pdb_content)
return pred_path, inference_time
def compare_structures(pred_pdb, reference_cif, output_dir):
"""
Compare predicted structure against reference using OpenStructure.
Args:
pred_pdb: Path to predicted structure (PDB format)
reference_cif: Path to reference structure (CIF format)
output_dir: Directory to save comparison results
Returns:
dict: Comparison metrics including lDDT score
"""
output_dir = Path(output_dir)
output_dir.mkdir(parents=True, exist_ok=True)
out_path = output_dir / "comparison_results.json"
# Build OpenStructure comparison command
cmd = [
"compare-structures",
"-m", str(pred_pdb), # Model (predicted structure)
"-r", str(reference_cif), # Reference (ground truth)
"--fault-tolerant", # Handle minor structural differences
"--min-pep-length", "4", # Minimum peptide chain length
"--min-nuc-length", "4", # Minimum nucleotide chain length
"-o", str(out_path), # Output JSON file
"--lddt", # Calculate lDDT metric
]
# Run comparison using OpenStructure Docker container
docker_cmd = [
"docker", "run", "--rm",
"-v", f"{Path.cwd()}:/home",
"registry.scicore.unibas.ch/schwede/openstructure:latest"
] + cmd
result = subprocess.run(
docker_cmd,
capture_output=True,
text=True
)
if result.returncode != 0:
raise Exception(f"Structure comparison failed: {result.stderr}")
# Read comparison results
with open(out_path, 'r') as f:
metrics = json.load(f)
return metrics
def extract_lddt(comparison_results):
"""
Extract lDDT score from comparison results.
Args:
comparison_results: Dictionary containing comparison metrics
Returns:
float: lDDT score (0.0 to 1.0, higher is better)
"""
# lDDT is directly a float value in the comparison results
lddt_score = comparison_results.get('lddt', 0.0)
return lddt_score
def benchmark_structure(nim_url, input_json, reference_cif, output_dir):
"""
Complete benchmark pipeline for a single structure.
Args:
nim_url: URL of OpenFold3 NIM service
input_json: Input configuration for prediction
reference_cif: Reference structure for validation
output_dir: Output directory for results
Returns:
dict: Benchmark results including timing and accuracy
"""
output_dir = Path(output_dir)
print(f"Running inference...")
pred_path, inference_time = run_inference(nim_url, input_json, output_dir)
print(f"Inference completed in {inference_time:.2f} seconds")
print(f"Comparing structures...")
metrics = compare_structures(pred_path, reference_cif, output_dir)
lddt_score = extract_lddt(metrics)
print(f"lDDT score: {lddt_score:.4f}")
return {
'inference_time': inference_time,
'lddt_score': lddt_score,
'predicted_structure': str(pred_path),
'full_metrics': metrics
}
if __name__ == "__main__":
parser = argparse.ArgumentParser(description='Benchmark OpenFold3 NIM predictions')
parser.add_argument('--nim-url', default='http://localhost:8000',
help='URL of the OpenFold3 NIM service')
parser.add_argument('--input', required=True,
help='Path to input JSON file')
parser.add_argument('--reference', required=True,
help='Path to reference CIF file')
parser.add_argument('--output', required=True,
help='Output directory for results')
args = parser.parse_args()
results = benchmark_structure(args.nim_url, args.input, args.reference, args.output)
print("\nBenchmark Results:")
print(f" Inference Time: {results['inference_time']:.2f}s")
print(f" lDDT Score: {results['lddt_score']:.4f}")
print(f" Predicted Structure: {results['predicted_structure']}")

Run a Single Benchmark

To run a benchmark for a single structure, follow these steps in order:

# Step 1: Install dependencies
pip3 install requests
# Step 2: Create directories
mkdir -p inputs results
# Step 3: Generate the input JSON file
python3 generate_inputs.py --pdb 8eil
# Step 4: Verify files exist before running benchmark
ls -l inputs/8eil_input.json references/8eil.cif
# Step 5: Run the benchmark (requires OpenFold3 NIM to be running)
python3 benchmark_openfold3.py \
--nim-url http://localhost:8000 \
--input inputs/8eil_input.json \
--reference references/8eil.cif \
--output results/8eil

Each step must complete successfully before proceeding to the next. Verify that input and reference files exist (Step 4) before running the benchmark (Step 5).

Understand the lDDT Metric

lDDT (local Distance Difference Test) is a metric for assessing the quality of predicted protein structures:

  • Score Range: 0.0 to 1.0 (or 0 to 100 when expressed as percentage)
  • Interpretation:
    • lDDT above 0.90: Very high accuracy, very high confidence
    • lDDT 0.70-0.90: Good accuracy, reliable predictions
    • lDDT 0.50-0.70: Moderate accuracy, some structural features correct
    • lDDT below 0.50: Low accuracy, limited reliability

How lDDT Works:

  • Measures local geometric agreement between predicted and reference structures
  • Evaluates distances between atoms within local neighborhoods (typically 15 Å radius)
  • Less sensitive to domain movements and mobile regions than global metrics like RMSD
  • Focuses on local structural correctness rather than global superposition

Why lDDT for OpenFold3:

  • AlphaFold3 and OpenFold3 models are trained to optimize lDDT during the training process
  • Well-suited for evaluating multi-chain complexes and structures with mobile regions
  • Provides per-residue metrics in addition to global metrics
  • Standard metric used in CASP (Critical Assessment of protein Structure Prediction) competitions

Run Benchmarks for the Performance Table

To reproduce the performance metrics from the table above, follow these steps in order:

Complete Steps 1 and 2 before running Step 3. The benchmark workflow requires:

  1. Both Python scripts (generate_inputs.py and benchmark_openfold3.py) saved as files
  2. The bash script (run_benchmarks.sh) saved as a file
  3. All scripts must be in the same directory before execution

Running steps out of order results in “File Not Found” errors.

Step 1: Prepare the Python Scripts

Save the two Python scripts provided earlier in this document:

Step 2: Create the Benchmark Workflow Script

Save the following as run_benchmarks.sh:

#!/bin/bash
# Complete benchmark workflow for all test cases
NIM_URL="http://localhost:8000"
PDB_IDS=("8eil" "7r6r" "1a3n" "8c4d" "7qsj" "8cpk" "8are" "8owf" "8aw3" "7tpu" "7ylz" "8gpp" "8clz" "8k7x" "8ibx" "8gi1" "8sm6" "8pso" "8jue" "8bsh" "5xgo")
# Create directories
mkdir -p references inputs results
# Step 1: Generate input JSON files from PDB
echo "Step 1: Generating input JSON files..."
python3 generate_inputs.py
echo "✓ Input files created in inputs/"
# Step 2: Download reference structures
echo "Step 2: Downloading reference structures..."
for pdb_id in "${PDB_IDS[@]}"; do
if [ ! -f "references/${pdb_id}.cif" ]; then
echo " Downloading ${pdb_id}.cif..."
wget -q "https://files.rcsb.org/download/${pdb_id}.cif" -O "references/${pdb_id}.cif"
fi
done
echo "✓ Reference structures downloaded"
# Step 3: Verify NIM is running
echo "Step 3: Checking NIM availability..."
curl -sf "${NIM_URL}/v1/health/ready" > /dev/null || {
echo "Error: NIM not accessible at ${NIM_URL}"
exit 1
}
echo "✓ NIM is ready"
# Step 4: Run benchmarks
echo "Step 4: Running benchmarks..."
for pdb_id in "${PDB_IDS[@]}"; do
echo " Benchmarking ${pdb_id}..."
python3 benchmark_openfold3.py \
--nim-url "$NIM_URL" \
--input "inputs/${pdb_id}_input.json" \
--reference "references/${pdb_id}.cif" \
--output "results/${pdb_id}"
done
echo ""
echo "Benchmarking complete! Results saved in results/"

Step 3: Run the Complete Workflow

# 1. Install dependencies
pip3 install requests
# 2. Make the benchmark script executable
chmod +x run_benchmarks.sh
# 3. Run the complete workflow (generates inputs, downloads references, and runs benchmarks)
./run_benchmarks.sh

The run_benchmarks.sh script handles all steps automatically: generating input files, downloading reference structures, and running benchmarks for all test cases. Make sure the OpenFold3 NIM is running before executing the script.

Expected Output Format

The comparison results JSON file contains detailed metrics:

{
"lddt": 0.9234,
"chain_mapping": {
"A": "A",
"B": "B"
},
"aln": [
">reference:A\nMKQLYGHSTI...",
">model:A\nMKQLYGHSTI..."
],
"model_clashes": [],
"model_bad_bonds": [],
"model_bad_angles": [],
"reference_clashes": [],
"reference_bad_bonds": [],
"reference_bad_angles": [],
"status": "SUCCESS",
"ost_version": "2.11.1"
}

The primary metric of interest is lddt, which is a float value (0.0 to 1.0) representing the overall structural quality of the prediction. Higher values indicate better agreement with the reference structure.

Troubleshooting

General Performance Issues

  • Out of memory errors: Reduce MSA depth, decrease sequence length, or upgrade to GPUs with more memory
  • Slow performance: Ensure fast storage (NVMe SSD), sufficient CPU cores, and adequate system RAM
  • Poor quality predictions: Check input sequence quality, increase MSA depth if available, or request more diffusion samples (diffusion_samples)

Benchmarking Issues

The following are “File not found” errors.

  • “Input file not found”: Generate input JSON files first using generate_inputs.py
    python3 generate_inputs.py --all # Creates all input files
    python3 generate_inputs.py --pdb 8eil # Or for specific PDB
  • “Reference file not found”: Download CIF files from RCSB PDB
    wget https://files.rcsb.org/download/8eil.cif -O references/8eil.cif

The following are structure comparison issues.

  • OpenStructure comparison failures: Ensure both predicted and reference structures have compatible chain IDs and residue numbering
  • Missing atoms in predictions: Use --fault-tolerant flag to handle incomplete structures (already included in script)
  • lDDT score of 0.0: Check that sequences match between prediction and reference; may indicate alignment failure

The following are NIM connection issues.

  • “Connection refused”: Ensure OpenFold3 NIM is running
    curl http://localhost:8000/v1/health/ready # Should return {"object":"health.response","message":"ready","status":"ready"}

For runtime settings that affect performance, such as multi-GPU serving and request size limits, refer to Configuration Alternatives.