Research prototype

Strength-targeted concrete mix design.

Explore strength-targeted binder combinations through a repeatable inverse workflow.

Supplied inverse-concrete interface screenshot; personal contact details masked. This is not a live application.

Role: Research author · credited developer
Period: 2025
Methods: ANN · GWO · Streamlit
Status: Research prototype

Engineering software / Streamlit

A defined input.
An inspectable decision.

For concrete materials engineers

Explore strength-targeted binder combinations through a repeatable inverse workflow.

01 / INPUT

Set the engineering case

Target strength, age, water and aggregate contents

02 / OUTPUT

Inspect the result

Candidate cement, slag, fly-ash and admixture quantities

03 / DECISION

Compare the next options

Select candidate mixes for subsequent qualification.

Technical basis

ANN · GWO · Streamlit

Validation evidence

Personally credited application source, model outputs and a research manuscript.

Current scope

Research prototype; literature-derived data and predicted candidates require laboratory qualification.

Public deployment has not been verified. The supplied interface and source establish the implementation shown.

Engineering record

Scope, method and evidence.

A distinct implemented inverse-prediction tool. Physical mix validation and production carbon or cost reductions are not established.

01Engineering question

Explore strength-targeted binder combinations through a repeatable inverse workflow.

Context: Concrete/materials.

02Role and documented scope

Research author · credited developer

03Methods and evidence

The inverse workflow predicts cement, slag, fly-ash and superplasticiser quantities using a literature-derived mix dataset and a GWO-optimised ANN lineage. It remains distinct from the later generative Stage09 workflow; outputs are research candidates requiring physical qualification.

Supplied research files support the scope shown. Authorship is distinguished from personal ownership of every dataset, test or model; an interface is not proof of current deployment.

04Interpretation and limitations

No universal accuracy, engineering approval or field benefit is inferred from a selected output. Model domains and independent checks must be established for a new assignment.