chemistry-interaction-inventory-of-the-modelled-complex

Solid

Use at study design, analysis and writing when the result is a modelled or predicted molecular complex — a docked pose, a co-folded assembly, a binding interface — and RMSD, DockQ or lDDT is about to be the whole answer. Covers the reference-versus-prediction contact inventory per interaction class, the pocket-cropped figure with the interactions drawn, and the mechanism sentence.

AI & Automation 804 stars 25 forks Updated today NOASSERTION

Install

View on GitHub

Quality Score: 85/100

Stars 20%
97
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Interaction inventory of the modelled complex ## What goes wrong When the deliverable is a modelled molecular complex — a docked pose, a co-folded assembly, a predicted interface — the report stops at aggregate distances: RMSD, DockQ, lDDT, "fraction under the accepted cut". Those say how far the partner is from where it belongs. None of them says whether the model found the right pocket, reproduced the recognition chemistry, or kept the specific contacts that hold the complex together. A reader who wants to know what the model got right about the chemistry finds nothing to read. Three symptoms: - **The only structural figure is a whole-complex superposition.** The interface is 10–15 Å across inside a 60–80 Å frame, so it occupies a few percent of the canvas. No residue is labelled and no contact is drawn. The figure shows that two clouds overlap. - **The contact-level number was computed and dropped.** The fraction of native contacts is a term inside DockQ, so any run reporting DockQ already has it, and burial counts fall out of any interface routine. This is `publish-what-the-run-already-computed`'s sweep, applied to the interface. - **The prose says the partner is "placed correctly but imprecisely".** That is an eyeball claim about a picture with no measurement under it. A figure list generated from your own hypotheses will not contain this slot, because no hypothesis asks for it. Reserve it at study design as a deliverable of the subject matter, not o...

Details

Author
tangxiangru
Repository
tangxiangru/AutoR
Created
5 months ago
Last Updated
today
Language
Python
License
NOASSERTION

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Solid

review-clinical-ddi-study

Reviews clinical drug-interaction study reports for design adequacy, result integrity and coverage against in-vitro triggers. It records the mechanism and index drug and flags mismatches, assesses whether the design could detect the effect it sought, extracts every geometric mean ratio with its confidence interval and classifies it against magnitude bands transcribed from the guidance in force, and separates inconclusive studies from negative ones. Use it to review a dedicated interaction study, check which triggered signals received a study, or reconcile a reported ratio against a summary or label. Example: "Review a dedicated interaction study, check which triggered signals received a study." Do not use for in-vitro package review, for management strategy or label wording, for re-analysing individual data, or to judge whether an exposure change is clinically significant.

6 Updated 6 days ago
malekokour
Code & Development Featured

diffdock

DiffDock and DiffDock-L molecular docking. Use for protein-small-molecule pose prediction from PDB or sequence plus SMILES/SDF/MOL2, batch docking, virtual screening, and pose-confidence interpretation. Not for binding affinity prediction.

34,028 Updated yesterday
K-Dense-AI
Code & Development Listed

diffdock

DiffDock and DiffDock-L molecular docking. Use for protein-small-molecule pose prediction from PDB or sequence plus SMILES/SDF/MOL2, batch docking, virtual screening, and pose-confidence interpretation. Not for binding affinity prediction.

13 Updated 3 weeks ago
tassiovale