Skip to content

Latest commit

 

History

History
32 lines (22 loc) · 2.04 KB

methodology.md

File metadata and controls

32 lines (22 loc) · 2.04 KB

Methodology

Analytical question

Can a reproducible, uncertainty-aware workflow rank scaffold-held-out HIV-1 protease compounds for follow-up while making its validation limits visible?

Workflow

  1. Curate activity records — retain standardized ChEMBL IC50 measurements reported as exact nanomolar values and aggregate repeated measurements by median pActivity.
  2. Standardize structures — parse SMILES with RDKit, select the largest fragment, remove explicit hydrogens and canonicalize the result.
  3. Create a scaffold split — assign Bemis–Murcko scaffolds wholly to train or test data to reduce analogue leakage.
  4. Build baselines — compare an Extra Trees regressor using Morgan fingerprints with a mean-prediction baseline.
  5. Quantify uncertainty — use variation across individual trees as a pragmatic model-uncertainty indicator.
  6. Check applicability — report each candidate's maximum Tanimoto similarity to the training set and penalize low-similarity predictions.
  7. Prioritize transparently — combine potency, uncertainty, domain similarity and a broad molecular-weight screen in a documented score.
  8. Simulate learning — reveal labels for selected held-out compounds over repeated retrospective rounds. This is not experimental validation.

Validation design

The holdout is scaffold-based, never a random row split. Model and baseline are evaluated on the same unseen scaffold set using MAE, RMSE and R². The small, bounded sample makes these diagnostic estimates, not claims of clinical or discovery performance.

Reproducibility

  • Fixed random seed: 42
  • Versioned dependency ranges in pyproject.toml
  • One-command demo: hiv-protease-discovery demo
  • Executed notebook with saved outputs
  • Unit tests and automated lint/test workflow

What is intentionally excluded

No wet-lab assay, docking result, binding claim, de novo molecule claim or clinical conclusion is presented. The optional Transformer module defines an inspectable architecture only; it does not ship a pretrained checkpoint.