Rule-based advisor
A 23-row decision table maps the data profile and study design to a test — and cites the source behind the rule.
Final Year Project · DI240016
StatNavigator takes a raw CSV and walks a non-expert researcher to a defensible result — recommended test, checked assumptions, effect sizes, and an APA-style citation — inside one guided workspace.
Shapiro–Wilk failed on one group, so the parametric path is closed and a rank-based test is recommended.
01 — The problem
For a non-expert, the failure happens before any numbers appear: choosing the test. Running a t-test on skewed data, ignoring a failed normality check, or re-running tests until a p-value appears are all easy mistakes — and none of them announce themselves in the output.
02 — The approach
Every recommendation names the rule that produced it, shows the assumption checks behind it, and blocks the run until the prerequisites actually exist. The result reads like a method section, not a black box.
03 — The pipeline
Each step writes to a server-side pipeline state, so a project resumes exactly where it was left — on any device, in any session.
Drop a CSV and every column is profiled — type, missingness, outliers, distribution — before anything is changed.
Imputation, outlier handling, scaling, and encoding: applied per feature, with the effect of each choice shown first.
Register the hypothesis, answer the study-design questions, then run the test the advisor routes you to. Multiple hypotheses stay isolated in their own tabs.
Audit trail, plain-language narrative, charts, adjusted p-values, post-hoc comparisons, and a copyable APA-style citation.
A separate supervised-learning track — target selection, algorithm choice, and a leakage guard between training and scoring.
04 — What is inside
A 23-row decision table maps the data profile and study design to a test — and cites the source behind the rule.
Normality is tested per group. When it fails, the parametric option is closed and the rank-based alternative is recommended — with the reason attached.
The hypothesis is written and locked before results exist. Modifying it is possible, deliberate, and visible in the record.
One tab per hypothesis, each with its own setup, results, and history — so a second test never overwrites the first.
Run stays blocked until the study setup and measurement levels are confirmed — the gate explains what is missing and links to the fix.
Choose IQR or z-score detection and a per-feature action, then see the before/after record of every transformation applied.
Staff accounts get a dedicated dashboard to review student projects, findings, and advisor events.
scikit-learn models with duplicate removal, training-only transforms, and identifiers or label-derived columns excluded up front.
Report export, APA-style citation with effect size and confidence interval, and a session that survives logout or a reload.
05 — Screens
Captured from the deployed build. Select any screen to enlarge.
06 — Under the hood
TypeScript · Vite · Tailwind CSS 4 · Radix UI · Plotly
JWT / Google Sign-In · routers · async SQLAlchemy 2 · Alembic
23-row table · gates · assumption rules · findings
SciPy · statsmodels · pingouin · scikit-learn
Routing is benchmarked against IBM SPSS menu equivalents, so the recommended test matches what a statistician would pick there.
Scripted sessions against the deployed build, with friction and jargon logged and remediated rather than explained away.
The statistical core was audited independently and corrected in phases — test selection, effect sizes, and multiple-comparison handling.
Upload a dataset, answer a handful of questions about your design, and watch the advisor explain which test is defensible — and why.