Skip to content

Update selectors.py for CYSP residue#755

Closed
alexsodt wants to merge 1 commit intomarrink-lab:masterfrom
alexsodt:patch-1
Closed

Update selectors.py for CYSP residue#755
alexsodt wants to merge 1 commit intomarrink-lab:masterfrom
alexsodt:patch-1

Conversation

@alexsodt
Copy link
Copy Markdown

CYSP residue was not previously detected and would trigger the molecule to not be recognized as a protein. There may be other modified residues that would lead to the same behavior. Ideally it would detect if a molecule is likely a protein, rather than this stringent test that every residue should be known.

CYSP residue was not previously detected and would trigger the molecule to not be recognized as a protein. There may be other modified residues that would lead to the same behavior. Ideally it would detect if a molecule is likely a protein, rather than this stringent test that every residue should be known.
@pckroon
Copy link
Copy Markdown
Member

pckroon commented Feb 12, 2026

Ideally it would detect if a molecule is likely a protein, rather than this stringent test that every residue should be known.

I am inclined to agree here, except that DSSP refuses to give any output if your molecule contains any residue that is not in its list of approved residue names. And this causes chaos on our side of things. Maybe we need to change the selector to "is_known_to_dssp" rather than "is_protein". Problem for later as far as I'm concerned.

@pckroon
Copy link
Copy Markdown
Member

pckroon commented Feb 12, 2026

There's also some unrelated test failures, seemingly due to the removal of pkg_resources. I'll take a look at that soon

@pckroon
Copy link
Copy Markdown
Member

pckroon commented Feb 24, 2026

Superseded by #756

@pckroon pckroon closed this Feb 24, 2026
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