Published research / software

RC flexural-capacity prediction.

Repeat flexural-capacity screening across candidate beam parameters.

Supplied application interface; collaborative research context. An image is not proof of current deployment. Publication · 10.1002/suco.70332

Role: Research co-author · credited developer
Period: 2025
Methods: Regression · Python GUI
Status: Published research / software

Engineering software / Desktop interface

A defined input.
An inspectable decision.

For reinforced-concrete designers

Repeat flexural-capacity screening across candidate beam parameters.

01 / INPUT

Set the engineering case

Section, concrete and stainless-reinforcement variables

02 / OUTPUT

Inspect the result

Predicted ultimate flexural capacity (kNm) and comparison history

03 / DECISION

Compare the next options

Compare beam alternatives before detailed analysis.

Technical basis

Regression · Python GUI

Validation evidence

Personally credited GUI, sensitivity results and published research.

Current scope

Literature-derived data and a bounded prediction domain; code compliance requires separate verification.

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

Engineering record

Scope, method and evidence.

Journal article first published online in 2025, issue in 2026. Beam experiments and collaborative contributions retain their own attribution.

01Engineering question

Repeat flexural-capacity screening across candidate beam parameters.

Context: Reinforced concrete.

02Role and documented scope

Research co-author · credited developer

03Methods and evidence

Regression models use literature-derived stainless-reinforced concrete beam data to predict ultimate flexural capacity. Sensitivity outputs and a personally credited GUI support interpretation and repeated prediction, within the reference-data domain.

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.

Publication record · 10.1002/suco.70332

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.

Research supporting this project