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

Referencing multiple sources/datasets for ihm_derived_distance_restaints #78

Open
mtrellet opened this issue Feb 18, 2019 · 1 comment

Comments

@mtrellet
Copy link

Distances automatically generated in HADDOCK from several sets of "active" (key) residues can currently reference only a unique dataset as a source of information in the IHM dictionary (_ihm_derived_distance_restraint.dataset_list_id).
However, HADDOCK does not distinguish whether two key residues come from the same source or from two different ones (e.g. mutagenesis, DNA-footprinting, FRET, etc.).

We should try to find a way to reference multiple experiments when defining a distance restraint.

Two solutions were proposed for the moment:

  1. Be able to reference the _ihm_dataset_group.group_id item that is supposed to group datasets used for the same modeling protocol (and referenced in _ihm_modeling_protocol.dataset_group_id)
  2. Allows for comma-separated list of values in _ihm_derived_distance_restraint.dataset_list_id item.
@mtrellet
Copy link
Author

As a side note and following the last discussions we/I had where:

  1. A decision was taken to create a category referencing the interface_residues that would link poly_residue_features to dataset_list_id and/or dataset_group_id
  2. A realisation with Alexandre that, in order for HADDOCK to be able to exactly reproduce a given set of parameters for a HADDOCK run (and then reproduce it only from the mmCIF file information), we should try to integrate the importance/status of a given interface residue (e.g. either active or passive). This could take the form of a boolean flag for instance.
    For the sake of completeness, a short reminder: Active residues are residues that should be at the interface (significant penalty if they are not) and passive residues are residues that can be at the interface (no penalty if not at the interface but favorable score if they are).

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

No branches or pull requests

1 participant