You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How to validate such a relation?
In this case, atoms in polymers are expected to have parents in _pdbx_poly_seq_scheme and atoms in non-polymers don't, because pdbx_poly_seq_scheme is for polymers only.
Are there general rules to tell when parent in linked group must exist?
The text was updated successfully, but these errors were encountered:
It says there must be a match between atom_site and pdbx_poly_seq_scheme in which the pairs would match.
This allows the dictionary to say a row in atom_site must match the same in pdbx_poly_seq_scheme.
Otherwise, a simple parent/child relationship limits you to say that for a a value of atom_site.auth_asym_id - there is at least one value in pdbx_poly_seq_schee.pdb_strand_id that matches, which is a pretty low bar. Requiring that all attributes match at one time is useful to have.
It says there must be a match between atom_site and pdbx_poly_seq_scheme in which the pairs would match.
This allows the dictionary to say a row in atom_site must match the same in pdbx_poly_seq_scheme.
As we know, it's not true in general, because rows in atom_site that correspond to non-polymers don't match anything in pdbx_poly_seq.
Are there general rules to tell when parent in linked group must exist?
In theory the rules should apply to all. However, I see that there is some logic in cpp-cif-file/src/CifParentChild that will allow certain ones to be missing.
As an example,
_pdbx_item_linked_group_list
defines a relation between atom_site (child category) and pdbx_poly_seq_scheme (parent category).How to validate such a relation?
In this case, atoms in polymers are expected to have parents in _pdbx_poly_seq_scheme and atoms in non-polymers don't, because pdbx_poly_seq_scheme is for polymers only.
Are there general rules to tell when parent in linked group must exist?
The text was updated successfully, but these errors were encountered: