Reading the outputs

Two statuses

The run status says whether the job ran: queued, running, completed, failed, cancelled or timed out. The solver status is MADETOOL’s own verdict for a completed run:

• OK - every stage finished without errors or warnings.
• WARN - finished, with warnings to read.
• INCOMPLETE - a module is not implemented for this case, or the sizing loop did not converge.
• FAIL - a stage failed. When reading, validation or the capability check fails, the run stops there and the report explains why.

Stage table

One row per stage of main.m (read, validate, capabilities, registry, mission, design init, iteration, performance, trade, verification, report) with status, time, error and warning counts and a note.

Compliance statuses

• PASS / FAIL - hard limits and minimum capabilities.
• MARGINAL - the margin is within the method uncertainty.
• DEVIATION - a target outside its tolerance, or an unmet preference.
• NOT EVALUATED / UNSUPPORTED - no model result for that requirement.
• INFO - requirement given as NONE.

Files

• *_report.txt - the complete text report. Every number carries its unit; missing values print as --.
• *_compliance.csv - one row per requirement: required and achieved values in SI, margin, status and evidence.
• *_checks.csv - engineering checks of all modules. A check without a pass/fail judgement is reported as “not demonstrated”, never as a pass.
• *_constraints.csv - constraint diagram: W/S grid, each constraint line and the envelope.
• *_results.mat - the full results structure (MAT v7) for Octave or MATLAB.
• input_prd.txt and octave.log - the exact PRD the run used and the solver console output (added by the website).

Placeholders and validation needs

The report lists every PRD value marked as a placeholder and what needs higher-fidelity analysis or physical testing. Treat a converged sizing loop as a numerical result, not as evidence that the aircraft is safe or flight-ready.