-
Notifications
You must be signed in to change notification settings - Fork 3
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
Need for a more generic distance information class #47
Comments
Thank you for raising this issue. We recently discussed this issue in one of our weekly meetings (please refer to the meeting summary here). As you can see in the meeting summary, the discussion was focused on whether we can decouple the method-specific details from the interpretation of the distance restraints. It was not possible to do that with the crosslinking examples that we had at the time and therefore, the crosslinking categories are specific. |
A simple distance definition would work, e.g. like: (selection 1) (selection 2) Note that the selection can be a single atom, but also a group of atoms to allow for ambiguity. Some categories might be more specific, probably assuming some kind of (gaussian) distribution of distances and requiring a target distance and some standard deviation. But in first instance I would keep things simple. |
And in principle there is nothing special about MS cross-links... These seems to me rather generic distances. |
Preliminary definitions for generic distance restraints are available in a separate file and will be merged with the IHM dictionary, once finalized. |
The model now allows for cross-link data to be stored. But this is rather specific. In principle any kind of distance should be store, coming from MS or any other experimental method providing such information (e.g. FRET, DEER, ...)
The text was updated successfully, but these errors were encountered: