Development overview

Current App V2Reviewed casesNot official

A live research tool for road-risk modelling

Road Risk combines a public research site with a live app for selected-road modelling, scenario testing, graphing, saving, and exporting case evidence.

Open App V2 Judge Route Authorship

Reviewer route

Start Here for Reviewers

This page now acts as the short public entry point for judges and reviewers. Use it to understand the question, then move into Method, Results, and App V2.

Page Purpose

Start Here for Judges and Reviewers

The Project page is the overview layer: question, hypothesis, variables, tested evidence, limits, and next work.

Research question: Can public geometry and explicit assumptions produce transparent comparative road-risk outputs before formal calibration?
Hypothesis: Greater geometric and scenario demand should increase the comparative model output under the same assumptions.
Read first: Use this page for the overview, then Method for formulas and Results for reviewed public evidence.
Boundary: The project does not certify road danger, set legal speeds, or replace professional assessment.

Judge Route

Use the five-minute public review path for judging and live demo preparation.

Project

Understand the question, hypothesis, review boundary, and what was built.

Method

Check how observed inputs, derived geometry, assumptions, and outputs are separated.

Results

Inspect reviewed public cases and the public/private evidence boundary.

App V2

Test the live workspace, change one assumption, and export a reviewable record.

Competition summary

The project at a glance

Research question

Can public geometry support a prospective signal?

Road Risk tests whether public road geometry, physics-informed calculations, and controlled assumptions can support comparative road-risk modelling before collision-history calibration is introduced.

Title	R.I.S.K. - Roadway Infrastructure Safety Kinematics.
Question	Can public road geometry, physics-informed calculations, and controlled assumptions support prospective relative-risk comparison?
Hypothesis	Geometry plus kinematic reasoning can produce useful comparative signals before collision-history calibration is introduced.
Built	A public research site and live analytical app for selected-road modelling, scenario testing, graphing, saving, and exporting case records.
Tested	Internal model behaviour across curvature, radius, friction, speed, stopping distance, assumptions, and comparative statistics.
Boundary	Outputs are comparative model indicators, not official safety ratings or crash predictions.

Variables and Controls

Competition Summary: question, hypothesis, variables, and outputs

The project should be judged on whether the variables, assumptions, and outputs are visible enough to inspect.

Research question

Can public road geometry, physics-informed calculations, and explicit scenario assumptions produce transparent comparative road-risk outputs before formal collision-history calibration?

Hypothesis

Under the same assumptions, tighter curvature, greater speed demand, longer stopping distance, and weaker data confidence should increase the comparative model output.

Independent variables

Selected road geometry plus scenario controls such as speed, weather, surface, visibility, lighting, vehicle profile, fatigue, and overspeed.

Dependent outputs

Annual model output, local-bin output, safe-speed estimate, stopping distance, confidence label, graph position, and exportable evidence.

What Was Tested

Evidence currently available for review

Pipeline behaviour

The public site and App V2 expose a chain from selected road geometry to derived physics checks, scenario assumptions, graphs, and exports.

Reviewed public cases

The committed Results dataset contains reviewed public model-output examples. Source inspection found no pending or filler case markers.

Live scenario sensitivity

A reviewer can change one assumption in App V2 and inspect whether the same selected road changes in an explainable direction.

Observed context boundary

RSA Recorded Collisions can provide historical context where configured, but they are not used as proof of the model.

Interpretation

What the Results Mean and What the Results Do Not Mean

What the results mean

They show Phase 1 model behaviour under explicit assumptions and support review of whether the calculation chain is coherent.

What the results do not mean

They do not prove observed crash probability, certify road danger, set legal speeds, or replace engineering assessment.

Next Work

What I Would Do Next

Aggregate validation

Compare many modelled road bins against observed RSA collision density and severity-weighted context.

Demo mode

Prepare one resettable judge demo route with fallback screenshots and a short explanation script.

Authorship detail

Complete named help-received details before final judging if the competition requires individual attribution.

Evidence trail

What the project evidence is built from

Public data

Open road geometry

The project starts with inspectable public road data rather than hidden proprietary inputs.

Physics chain

Kinematic interpretation

Curvature, radius, safe-speed, and stopping-distance relationships are exposed as part of the explanation.

Sensitivity

Scenario-based modelling

Rain, fog, fatigue, overspeed, BAC, vehicle type, surface, lighting, and traffic-proxy assumptions can be varied deliberately.

Statistics

Comparative context

Distribution views and percentiles help prevent one raw model value from being read in isolation.

Live app

Inspectable research tool

The app lets judges test a selected road, inspect the method, and export a case record.

Review boundary

Reviewed public cases

Local browser saves are not global evidence until exported, checked, and committed to the reviewed public dataset.

Public resource boundary

The Next.js site now routes public review through the Project, Method, Results, References, Assumptions, Validation, Glossary, Live App, and Licensing pages instead of a separate resource hub.

Physical display materials

SciFest booklet and poster materials are treated as physical display materials for the project stand, not public PDF downloads on the website.

Suggested demo path

A five-minute path through the current platform

Open App V2

Start in the live app rather than the preserved legacy route.

Select a road

Click a road and inspect modelled bins, safe-speed context, and confidence notes.

Open Maths & Method

Show formulas, substituted values, assumptions, and interpretation boundaries.

Enable RSA Recorded Collisions

Compare nearby historical records as observed context, not model proof.

Export Evidence Package

Save a reviewable package with source metadata and limitation wording.

Review questions

Questions the project is ready to answer

Meaning

What does the output mean?

It is a comparative model output under defined assumptions, not a measured crash rate.

Data choice

Why not use crash data yet?

The project first tests whether geometry and physics can produce a transparent prospective signal before calibration.

Sensitivity

How do assumptions affect results?

Change one factor at a time, such as rain, fog, fatigue, vehicle type, or overspeed, and compare the same selected road.

Mechanism

How does curvature influence the model?

Tighter curvature and smaller radius increase lateral demand and can reduce the friction-limited safe-speed estimate.

Next validation

How could this be validated next?

Compare exported cases with official collision records, engineering audits, field inspection, and expert review.

Responsible use

What the project does and does not claim

What Road Risk does

It lets users inspect a road, understand the geometry and assumptions behind a model output, and compare scenarios in a visible evidence trail.

What Road Risk does not do

It does not replace official collision statistics, engineering audits, field inspection, or professional road-safety assessment.

Build summary

How the public site, App V2, and private workspace fit together

Public site

Explains the project, method, reviewed public cases, sources, assumptions, validation boundary, glossary, and licensing.

Live workspace

App V2 handles selected roads, scenario controls, local bins, RSA context, graphs, Maths, imports, exports, and project saves.

Private workspace

Account and Dashboard organise private projects, imports, datasets, and evidence records for signed-in users.

Preserved access

Legacy App remains available for continuity, but App V2 is the current live workspace.