Diabetes research overview
One workspace for data preparation, experiment training and exploratory prediction.
From raw measurements
to reproducible experiments.
Cleaning, leakage-aware preprocessing and model evaluation are handled by a single repeatable training pipeline.
Dataset snapshot
Generated PIMA + laboratory composite cohort
Target distribution
Class balance in synthetic labels
Quick actions
Continue your workflow
Leakage-aware setup — target columns, source row identifiers and synthetic type-marker fields are excluded from model inputs.
Training metrics measure whether the pipeline can learn patterns in this generated cohort. They are not evidence of performance on real patients. Validate later using independent, clinically labeled data.
Prediction studio
Explore the two-stage status and conditional type workflow with synthetic training labels.
Batch predictions
Upload a CSV to score up to 100,000 rows and export a new file with model outputs.
Upload dataset
Model uses an allowlist of feature columns. Target and provenance columns are ignored.
What happens to your file?
Preprocessing applied before inference
This local demo does not intentionally save uploaded files. Avoid uploading identifiable health records; no production security review has been completed.
Model laboratory
Four saved pipelines compare clinical-only inputs with Ayurveda-inspired synthetic proxies.
Evaluation snapshot
Grouped synthetic holdout · not clinical validation
Top feature importance
Choose a trained model
Evaluation guardrails
Read before interpreting a score
Model performance measures recovery of generated scenarios, not true diabetes status or type.
The cohort reuses PIMA and lab donors. Splits hold out PIMA source rows, but lab donors may recur.
Simulated autoantibodies and C-peptide are not model inputs, preventing direct access to generated type rules.
Use separate patient-level clinical records and verified labels before any real-world claim.
Confusion matrix
Rows = actual synthetic labels · columns = predicted synthetic labels
Data quality
Review the cohort schema, source provenance and cleaning steps used by the training pipeline.
The two source CSVs did not contain a common patient key. The 100,000 rows were generated through donor resampling and jitter. The data cannot establish clinical type labels or real Ayurveda assessments.
Feature missingness
Highest missing percentage after basic normalization
Cleaning pipeline
What the system does automatically
Field groups
How the main dataset columns are interpreted
PIMA measures and lab markers that can be entered as model features. Lab units must be verified.
Synthetic Prakriti/Vikriti scores and symptom flags. Not measured by either original source dataset.
Simulated autoantibodies, C-peptide and clinical clues. Excluded from all prediction feature sets.
Generated status and type scenarios. Used only as training targets; not verified patient labels.