Concrete mix design in Indian practice remains chart-and-iteration under IS 10262, and data-driven strength models could support it — but the published machine-learning record on concrete strength is statistically weak: single models, single splits, no baseline anchoring, tuning that leaks into test data, no confidence intervals, and optimisation claims that ignore the model's valid operating range and codal durability constraints. There is no reproducible, declared-protocol study that (a) benchmarks linear and ensemble regressors on the standard public concrete-strength dataset under nested, repeated cross-validation with an untouched holdout, (b) interprets variable importance with fold-level uncertainty rather than intuition, and (c) proposes trial mixes that respect IS 456-consistent constraint envelopes strictly inside the model's trust region with prediction intervals attached. This dissertation fills that gap with a fully scripted pipeline, seed-fixed reproducibility, and honest reporting of where data-driven mix proposals stop being trustworthy.
Abstract
This dissertation benchmarks four regression families — ordinary least squares, ridge, random forest and gradient boosting — for predicting concrete compressive strength from mix proportions and age, on the public UCI Concrete Compressive Strength dataset under a frozen evaluation protocol: repeated 10-fold cross-validation with fixed seeds, nested cross-validation for hyperparameter tuning, an untouched holdout scored once at the end, and metrics reported as mean ± standard deviation (RMSE, MAE, R²). Permutation importance with confidence intervals is checked against water–cement-ratio expectations. A final stage optimises trial mixes for minimum binder at target strength inside declared IS 456-consistent constraint envelopes and the model's trust region, with prediction intervals per proposal. The study quantifies the ensemble advantage over honest baselines, the signal variables, and where mix proposals stop being trustworthy.
Introduction
India's infrastructure programme makes concrete strength prediction a practical economics question: every MPa of over-design is cement cost and embodied carbon, every under-design is structural risk. Mix design under IS 10262 is chart-and-iteration practice, while materials vary by source, so data-driven strength models appeal. Machine-learning regression offers that, but its published record on concrete is weakened by single-split evaluation habits.
Existing system and literature gap
Since Yeh's 1998 study on this very dataset, dozens of papers have applied regression to concrete strength, but accessible ones typically report one model on one split, tune on the test set implicitly, and never state the model's valid operating range. What is missing is a baseline-anchored, leakage-safe, seed-fixed comparison on the field's standard public dataset, with permutation-based interpretation and a codally constrained, trust-region optimisation stage — a study whose numbers regenerate exactly and whose claims carry their limits.
Proposed work
- Ingest the UCI dataset with full provenance (DOI, feature definitions, units); audit ranges, units and the uneven age distribution before modelling.
- Implement the four model families in leakage-safe scikit-learn pipelines (preprocessing inside every fold); tune the ensembles by nested cross-validation; freeze seeds and grids in configuration.
- Evaluate by repeated 10-fold CV plus a single untouched holdout; report RMSE, MAE and R² as mean ± standard deviation; test the ensemble-versus-linear gap across folds.
- Interpret with permutation importance (with fold-level variability) and partial dependence for cement, water and age; contrast against water–cement-ratio expectations.
- Optimise trial mixes: minimise binder subject to target strength and declared IS 456-consistent constraints (w/c bounds, cementitious minimums, volume closure), inside the training data's trust region, with prediction intervals per proposal.
Feasibility
- Technical: everything runs in Python (pandas, NumPy, scikit-learn, SciPy) on a 16 GB laptop; the full nested-CV campaign completes in about an hour.
- Data: the UCI dataset is public, citable and the field's standard benchmark; no lab time is required for the modelling stages.
- Economic: zero licence cost; the optimiser's output is a shortlist for a later lab phase.
- Operational (research): the protocol, seeds and constraint envelopes are frozen before evaluation; every table regenerates from two commands — the audit trail an M.Tech viva demands.
The work follows a quantitative, comparative-experimental research design in six phases over 24 weeks, with the evaluation protocol (folds, repeats, seeds, grids, constraint envelopes) frozen at the end of Phase 1 — before any model is scored.
| Phase | Weeks | Activities | Deliverable |
|---|
| Literature survey & protocol | 1–4 | Survey strength-modelling literature and its evaluation practice; fix the protocol, seeds, grids and constraint envelopes | Survey chapter; pre-declared protocol document |
| Data engineering | 5–8 | Ingest UCI dataset with provenance; audit ranges and units; build the versioned store and data-quality report | Documented dataset + audit report |
| Models & baselines | 9–13 | Implement the four families in leakage-safe pipelines; nested-CV tuning; unit tests on metric and constraint code | Tested model library + tuned configurations |
| Evaluation & interpretation | 14–18 | Repeated-CV campaign; untouched holdout scored once; permutation importance and partial dependence with fold variability | Full results tables and figures |
| Mix optimisation | 19–21 | Implement constraint envelopes and trust-region logic; run the optimiser for target strengths; attach prediction intervals | Constrained mix shortlist + caveat report |
| Writing & defence | 22–24 | Dissertation in VTU format, paper-style results chapter, slides, live pipeline demo | Dissertation, presentation |
Validation inside the study: unit tests for metric implementations against hand-computed examples and for the constraint checker against boundary mixes; a leakage test asserting that no scaling statistic crosses fold boundaries; a trust-region test asserting the optimiser rejects any proposal outside the training support; and a full re-run reproducing every table from fixed seeds.