Skip to content

Only consider standard residues in consecutive CA filter#576

Open
bcm49 wants to merge 1 commit intojwohlwend:mainfrom
bcm49:processing-consecutive-ca-filter-standard-residues-only
Open

Only consider standard residues in consecutive CA filter#576
bcm49 wants to merge 1 commit intojwohlwend:mainfrom
bcm49:processing-consecutive-ca-filter-standard-residues-only

Conversation

@bcm49
Copy link
Copy Markdown

@bcm49 bcm49 commented Sep 17, 2025

The consecutive CA filter marks a protein chain as invalid if it has two consecutive residues that are too far apart. I have CIF files where a few zinc and calcium ions are included in the protein chain. Since the ions are far apart, this chain would previously have been marked invalid by the filter. After this small change, the ions are ignored by the filter and the protein chain is marked as valid during processing.

The consecutive CA filter marks a protein chain as invalid if it has two consecutive residues that are too far apart. I recently found a CIF file where a few zinc and calcium ions were included in the protein chain. Since the ions are far apart, this chain would previously have been marked invalid by the filter. After this small change, the ions are ignored by the filter and the protein chain is marked as valid during processing.
volgin added a commit to Novel-Therapeutics/boltz-community that referenced this pull request Mar 8, 2026
…hlwend#576)

Non-standard residues (e.g. Zn, Ca ions) embedded in protein chains
caused the CA distance filter to see huge gaps and reject the chain.
Filter now only considers standard residues.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@volgin
Copy link
Copy Markdown

volgin commented Mar 8, 2026

We applied this fix in boltz-community, a community-maintained fork with 20+ upstream bug fixes, broader hardware compatibility (MPS, ROCm), expanded test coverage, and CI. Thanks for the contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants