Migrate from HHR-based Templates to Explicit mmCIF Templates
Purposes of 2.0.0 Changes
OpenFold2 version 2.0.0 removes support for an internal search for structural templates based on HHR-format input, but maintains support for explicitly provided mmCIF template structures. The functionality to search a database of structure files will be moved to the NVIDIA MSA-NIM, and supported in the MSA-NIM in future releases. This change consolidates the management of sequence and structure databases to the MSA-NIM. This change provides several benefits for the OpenFold2:
- Simpler dependency set: No bundled PDB70 database required
- Lower startup time & disk footprint: Reduced container size and faster initialization
- Greater flexibility: Direct control over template structures without database limitations
Removed Features
The following features have been removed in version 2.0.0:
- All request fields named
templatesor sub-keys expecting HHSearch (HHR) data - Environment variables and NIM cache content for PDB70 are ignored
- CLI flags or examples that mentioned
use_templates=truewith HHR format - Database-driven template processing pipeline
Step-by-Step Migration
Follow the steps below to migrate the HHR-based template to explicit mmCIF templates.
1. Prepare Your Local mmCIF Template Structure
This guide assumes you already have mmCIF template files available locally. If you need to convert existing PDB files to mmCIF format, you can use tools like BioPython:
2. Update Your JSON Request Format
Replace the old JSON request format to the new format. Old format (≤1.2.0):
New format (2.0.0):
format: bothmmcif(uncompressed) andmmcif.gz(gzip-compressed) are supported. Use a compressed format for large template files to reduce request payload size. For detailed information about supported formats, refer to the Template Processing.rank:-1is the default value for the OpenFold2 monomer use-case.
3. Update Python Code Examples
Update your Python code examples as follows: Complete Python example:
4. Clean Cached Data (Optional)
Remove old PDB70 cache data that is no longer needed:
Common Issues and Solutions
Performance Considerations
Ensure you consider the following improvements and impact when migrating.
Expected Improvements in 2.0.0:
- Faster startup: No database loading required
- Reduced memory usage: No PDB70 database in memory
- Simplified confidence scoring: Fixed maximum confidence instead of HHR scores
- Direct processing: Single-step template feature extraction
Accuracy Impact
The following are ways 2.0.0 impacts accuracy:
- Empirical tests show less than 1% RMSD change in most cases
- pLDDT scores may vary slightly due to different confidence weighting
- Overall structure quality remains comparable
Advanced Usage Patterns
This section explores other usage patterns.
Multiple Templates
Programmatic Template Management
Helpful Resources
- Refer to the updated Template Processing documentation for technical details
- Review Example Requests for complete working examples
- Contact NVIDIA support for migration assistance
Migration Checklist
- Identify all HHR-based template usage in your code
- Ensure you have template structures in mmCIF format locally available
- Update JSON request format to use
explicit_templates - Test with a small example to verify functionality
- Update any automated pipelines or scripts
- Clean up old PDB70 cache directories
- Validate that structure prediction quality meets your requirements