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
The most obvious way to retrieve model scale (atomic/coarse-grained/multiscale (a mix of atomic and coarse-grained)) is from the _ihm_model_representation_details table. However, the scale is also explicitly defined in _ihm_modeling_protocol_details.multi_scale_flag .
This table is populated during deposition, correct? Seems like the deposition system just needs a consistency check. Or maybe just make this field not editable and automatically populate it for the user?
The most obvious way to retrieve model scale (atomic/coarse-grained/multiscale (a mix of atomic and coarse-grained)) is from the
_ihm_model_representation_details
table. However, the scale is also explicitly defined in_ihm_modeling_protocol_details.multi_scale_flag
.It causes a conflict for PDBDEV_00000093:
According to the representation table, the model is purely atomic:
at the same time
_ihm_modeling_protocol_details.multi_scale_flag
is set toYES
.Thus, on the website it's rendered as 'multiscale' :
)
I think structural model scale should be inferred using only
_ihm_model_representation_details
. @brindakv @jaredsagendorf what do you think?The text was updated successfully, but these errors were encountered: