math-modeling-pipeline/phase-3.5

Automate MATLAB unit testing against physical reference values and generate pass/fail reports.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/SOGERSEN/math-modeling-pipeline --skill math-modeling-pipeline-phase-3-5
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: math-modeling-pipeline/phase-3.5
Source: https://github.com/SOGERSEN/math-modeling-pipeline/tree/main/phases/phase-3.5
Command: npx skills add https://github.com/SOGERSEN/math-modeling-pipeline --skill math-modeling-pipeline-phase-3-5

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates rigorous unit testing for Phase 3.5 MATLAB code with physical reference values to ensure correctness beyond mere execution.

Core Features & Use Cases

  • Validates core MATLAB modeling functions and Q*_solver.m scripts against physical reference values or analytical solutions.
  • Generates a dedicated unit test script at 3-modeling/unit_tests.m and an audit-ready report at 3-modeling/unit_test_report.md.
  • Integrates into the 19-phase pipeline, enforcing repeatable, auditable quality gates for Phase 3.5.

Quick Start

Create 3-modeling/unit_tests.m to exercise all core functions and produce 3-modeling/unit_test_report.md with physical-reference validations.

Frequently Asked Questions about math-modeling-pipeline/phase-3.5

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate unit testing for MATLAB code with physical reference values?

MATLAB unit testing validates core modeling functions and Q*_solver.m scripts against analytical solutions. It ensures calculation correctness beyond mere execution by comparing outputs against expected physical reference values within a structured pipeline.

What is the best way to generate an audit-ready unit test report for MATLAB solvers?

Generating a unit test report requires a working directory with 3-modeling/core/*.m, Q*_solver.m, and unit_tests.m files. The testing process validates core functions and solver scripts, outputting a pass/fail markdown report at unit_test_report.md.

How do I validate Q*_solver.m scripts against analytical solutions in MATLAB?

You validate Q*_solver.m scripts by running automated unit tests that compare script outputs against analytical solutions or physical reference values. This verifies the mathematical modeling logic executes correctly and produces accurate physical results.

What directory structure do I need to run automated unit tests for MATLAB modeling?

You need a working directory containing 3-modeling/core/*.m files, 3-modeling/Q*_solver.m, and a 3-modeling/unit_tests.m script. This structure allows the testing framework to validate functions and output the markdown report correctly.

Why does my MATLAB code execute but fail physical reference value checks?

MATLAB code may execute but fail physical reference value checks because the mathematical modeling logic produces incorrect physical results. Rigorous unit testing identifies these discrepancies by comparing solver outputs against expected analytical solutions.