Data and Evaluation

Computational biology evaluation은 대부분 training 전에 결정됩니다. Example definition, label semantics, split unit, leakage control, benchmark design이 성능 claim의 범위를 정합니다. Random split은 molecule, protein, complex-level claim에는 약한 경우가 많습니다.

이 estimate는 test set이 generalization claim과 맞을 때만 의미가 있습니다.

Data Contract Routes

QuestionStartWatch
무엇이 one example인가?Example unit, Dataset construction checklistmolecule, protein, assay, complex identity를 숨기는 row ID
label은 무엇을 뜻하는가?Label semantics, Target-assay-label contract, Bioactivity labelendpoint, unit, censoring, threshold, source mismatch
preprocessing이 object를 어떻게 바꾸는가?Preprocessing contract, Metadata and provenance, Chemical state contractfull data에서 preprocessing 또는 deduplication을 fit하는 경우
어떤 split이 claim을 지지하는가?Split unit, Leakage, Test-set contaminationrandom row split이 generalization을 과장하는 경우

Split and Leakage Routes

Split axisStartUse for
Molecule seriesScaffold splitnew-chemistry claim과 analog leakage check
Protein familyProtein family splitnew-target 또는 sequence generalization claim
Protein-ligand pairProtein-ligand splitinteraction과 docking generalization
Structure templateTemplate leakagestructure prediction, docking, pocket task
Assay/sourceAssay harmonizationmulti-source activity label

Claim to Split Map

Claim더 강한 split약한 split의 risk
Known target 안의 new moleculescaffold 또는 chemical-series splitrandom split이 close analog를 memorize할 수 있음
New protein targetprotein-family 또는 sequence-identity splitrandom target row가 homolog를 공유할 수 있음
New protein-ligand pairpair split + scaffold/protein controlpair split만으로는 ligand와 protein neighborhood가 남을 수 있음
New assay/sourcesource 또는 temporal splitassay-specific artifact가 row 사이로 leak될 수 있음
New structure templatetemplate-aware structure splithomologous structure가 pose task를 너무 쉽게 만들 수 있음

Evaluation Routes

NeedStartCheck
Protocol boundaryEvaluation, Evaluation protocol, Evaluation set designtrain/validation/test role과 final selection rule
Claim supportClaim-evidence boundary, Benchmark claim contract, Benchmark intakereported number가 실제로 증명할 수 있는 것
Metric choiceMetric selection, Objective-metric alignmentoptimized loss와 reported decision metric의 차이
ReliabilityCalibration, Uncertainty estimation, Applicability domaindistribution shift 아래 confidence
Benchmark trapsNegative set, Activity cliff, Boltzmann ceiling analysisfalse negative, cliff, indistinguishable label
Repeated paper patternsComputational Biology paper claim patternsproperty, activity, docking, generation, protein design, genome task

Boundary With AI Evaluation

General evaluation concepts still matter, but computational biology claims often fail because the biological or chemical unit was underspecified.

If the main issue isUseRecord
metric definition, confidence interval, seed variance, calibrationAI Evaluationmetric formula, estimator, uncertainty, selection rule
molecule identity, scaffold, tautomer, protonation, stereoMolecular and Ligand Modelingstandardization policy and split unit
protein family, homolog, residue indexing, structure sourceSequence-Based Modeling, Protein modelingfamily split, sequence identity, structure cleaning
protein-ligand pair, assay row, affinity, selectivityInteraction Modelingtarget, assay, endpoint, unit, censoring, source
pose, docking, pocket, template, coordinate qualityStructure-Based Modeling, Dockingpocket rule, atom mapping, RMSD/alignment, leakage

Computational Biology Evidence Package

Computational biology paper에서는 model score만으로 부족합니다. Metric보다 먼저 modeled object와 measurement context를 기록해야 합니다.

FieldRequired detail
Example unitmolecule, protein, assay record, complex, pose, generated sample, or genomic region
Label semanticsendpoint, direction, unit, threshold, censoring, replicate aggregation, and source
Preprocessingmolecule standardization, protein/structure cleaning, sequence filtering, coordinate source
Chemical statesalt, stereo, tautomer, protonation, charge, conformer, and cache policy
Split unitscaffold, protein family, complex pair, assay/source, time, or template-aware split
Baselinefingerprint/tree model, sequence similarity, docking baseline, or task-specific simple model
Metricprimary decision metric plus diagnostics for calibration, uncertainty, or failure modes
Benchmark claimwhat the reported score can support after split, metric, baseline, and uncertainty are checked
Objective-metric alignmentwhether the optimized loss supports the reported metric and claimed utility
Leakage checkduplicate, scaffold, homolog, template, assay/source, or preprocessing leakage
Benchmark trapsnegative construction, activity cliffs, applicability domain, assay harmonization, and measurement ceiling

Structure-based benchmark에서는 known ligand pose, close analog, template, pocket definition이 inference time에 사용 가능한지도 적어야 합니다.

Baseline Ladder

복잡한 모델은 항상 적절한 단순 baseline과 비교해야 합니다.

TaskUseful baseline
molecule propertyfingerprint + linear/tree model
target-conditioned activityligand-only baseline, target-only baseline, nearest-neighbor baseline
protein sequence taskhomology, family, or sequence-similarity baseline
docking / poseclassical docking, minimized pose, known conformer baseline
virtual screeningsimple similarity, docking score, random/ranked decoy control
generationvalidity/diversity filter plus nearest-neighbor analysis

Benchmark Trap Map

Trap먼저 물을 것Start
assumed negativeinactive가 measured, censored, sampled, missing 중 무엇인가?Negative set
analog cliffsimilar molecule들이 assay-compatible하지만 매우 다른 label을 갖는가?Activity cliff
out-of-domain exampletest object가 relevant axis에서 training support와 먼가?Applicability domain
mixed assaysendpoint, unit, construct, source, censoring이 compatible한가?Assay harmonization
physical or assay ceilingeffect size가 distinguishability 또는 label noise보다 작은가?Boltzmann ceiling analysis

Checks

  • one example은 molecule, protein, assay record, protein-ligand complex, generated pose 중 무엇인가?
  • label direction, unit, censoring rule, assay context는 무엇인가?
  • split construction 전에 어떤 near-duplicate를 분리했는가?
  • metric이 benchmark convenience만이 아니라 intended decision을 반영하는가?