Pewarta Proxy

📋 Server Request & Proxy Logs

Loading active proxy settings...
Developed by Khairul Adha (adhexa.id)
Mengambil log server...

⚙️ Pengaturan Proxy Target

Skip to content

Getting ResidueIdentifier without aligned SEQRES #456

Open

Description

@sbliven

Creating a new contact.ResidueIdentifier (not to be confused with ResidueNumber) requires that the Group have a valid alignedResIndex in the corresponding Compound. Is there a reasonable way to handle missing seqres (e.g. if the structure came from a default AtomCache (see #455))?

Would it be better to do contact matching by ResidueNumber instead of seqres index?

Activity

  1. added this to the BioJava 5.0.0 milestone on Apr 21, 2016
  2. josemduarte commented on Apr 21, 2016

    @josemduarte
    Contributor

    Contact matching based on seqres indices is a way to be able to compare residues in different chains of same entity when their numbering is inconsistent between chains. A good example of this is 3ddo where there's one entity with 6 chains. Each of those chains uses a different numbering: chain A starting at 1001, B at 2001, C at 3001 and so on... These cases can only be covered by doing residue comparisons based on seqres indices.

    See test TestInterfaceClustering.test3DDO() that checks this.

  3. sbliven commented on Apr 22, 2016

    @sbliven
    MemberAuthor

    It seems like the problem of aligning structures comes up often enough that we should have some utilities for handling this in a flexible way (e.g. use SEQRES if possible, otherwise default to a Smith-Waterman).

  4. josemduarte commented on Mar 7, 2018

    @josemduarte
    Contributor

    Agree @sbliven , I think we should work on making this more general, comparing 2 sets of contacts via an alignment or even in some topologically independent way.

    This is something for after the 5.0 release. I'll move it to the next milestone.

  5. modified the milestones: BioJava 5.0.0, on Mar 7, 2018
  6. josemduarte commented on Mar 11, 2021

    @josemduarte
    Contributor

    I'm going to try to work on this for the 6.0.0 release. It requires some API breaking changes.

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

Metadata

Metadata

Assignees

Labels

bugBugs and bugfixesminor

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions