Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Residue-mapping error because of sequence change in UniProt #1

Closed
HrishiDhondge opened this issue Nov 22, 2022 · 0 comments
Closed
Labels
bug Something isn't working

Comments

@HrishiDhondge
Copy link
Owner

The sequence of PTBP1_HUMAN (P26599) has changed in UniProt. It has 4 RRM domains, 2 each from RRM_1 (PF00076) and RRM_5 (PF13893).

  • RRM_5:
    • (38, 152),
    • (309, 433) --> This Structural InstancStI is causing the error
  • RRM_1:
    • (186, 252),
    • (456, 521)

The above sequence numbering matches with UniProt sequence versions=238, but the sequence changed in versions=239.
With the change in UniProt version, the corresponding SIFTS file has also changed accordingly, but not Pfam (v35.0).
This sequence change is causing workflow errors during the residue-mapping step of P26599_A (309, 433), recognizing only the domain end residue.
According to the new sequence, the RRM domain starts at 335, and the corresponding PDB (2EVZ) starts from the 350th amino acid residue of the UniProt sequence.

The issue can be replicated with the current version of the workflow (v1.0.0) by using the CWL tool Tools/resmapping_pfam_instances_subwf.cwl (sub-workflow for residue-mapping of Pfam StIs).
Query this tool for RRM_5 (PF13893) Pfam family.

@HrishiDhondge HrishiDhondge added the bug Something isn't working label Nov 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant