HENSYNTH requirements run report: metrics and help modals

What appears after Run screening

When a requirements-oriented analysis completes, HENSYNTH renders the Requirements run panel on the Requirements page. The subtitle states the scope: screening result for the requirements just saved, conceptual analysis, not a wind-tunnel or certification report. Solver status from the engine is shown when the API returns it.

Only metrics the engine actually calculated appear in the grid. If a value is missing from predictions, there is no tile for it — the UI does not interpolate.

The metric tiles and ? help

Each shown metric has a label, unit, monospace value, and a ? button. The modal is structured in four sections the product uses consistently:

• Purpose — why this number exists in the requirement loop.
• Meaning — what the symbol represents in plain language.
• Why it is calculated — which requirement or downstream check depends on it.
• Formula used — the handbook-style relationship the C++ path applied at screening fidelity.

Typical tiles include MTOW, empty mass, range, endurance, stall speed, takeoff distance, landing distance, climb rate, L/D max, and static margin. Open the modal when you need to explain a row in a design review — the text is copied into the zip report package as well.

Compliance table on the same panel

Below the metric grid, the compliance matrix lists Requirement, Target, Predicted, Margin, Status, and Confidence for each row the engine emitted. PASS and FAIL chips come from comparing predicted performance to the saved caps. Confidence is metadata from the analysis path, not a tunnel uncertainty band.

Reasoning findings

When the engine returns reasoning findings, up to twelve lines appear with severity, topic, and detail. They are advisory strings tied to the stored result — read them as screening notes, not as automated certification findings.

Download and share icons

The top-right icons mirror the candidate cards:

• Download builds hensynth-requirements-run.zip with PDF, figures, and stored numbers from the current panel state.
• Share by email opens CC and BCC fields (maximum two addresses), optional note, and attaches the same zip. If the mailer is not configured, HENSYNTH saves a local mail copy and tells you sending was not live.

How this differs from validation

The help modals teach the screening math HENSYNTH used. They do not assert that your aircraft matched experiment. For agreement with measured polars or flight data, use your own validation process outside this panel — HENSYNTH does not stamp tunnel validation on the requirements run.

In simple words: what this page is for

After Run screening, the Requirements run report lists MTOW, range, endurance, stall, field lengths, climb, L/D max, static margin, compliance rows, and ? modals with formulas.

This lesson exists because aircraft teams often jump to heavy CFD before the mission is even closed. HENSYNTH requirements run report: metrics and help modals keeps the focus on conceptual screening you can explain in review.

Why the topic matters

Engineers lose time when a title sounds clear but the page only sketches the idea. This article expands HENSYNTH requirements run report: metrics and help modals so you can answer three questions without jargon: what is the idea, when do you use it, and how do you check it in a HENDOI product.

Read the sections above for the core definitions. Use the steps below to move from reading into a real project trail you can share with a teammate.

How to apply this in HENDOI

In practice: open HENSYNTH after you sign in, set or confirm geometry, write mission targets on Requirements, Run screening, then read PASS / FAIL with margins. Use Mission, Performance, Trades, Optimize and Reports only after the screening snapshot exists. Numbers come from stored runs — the product does not invent missing values.

If you still need the wing section itself, finish that work in HENFOIL first, then continue the aircraft in HENSYNTH. One HENDOI account covers both. Plans stay Student USD 9, Professional USD 29 and Team USD 89.

What this page will not claim: HENSYNTH is conceptual and preliminary screening. It is not wind-tunnel data, not certification CFD, and not a compliance certificate for an authority. PASS / FAIL means requirement-versus-prediction inside the product.

Checklist before you leave this page

• Can you state the idea of HENSYNTH requirements run report: metrics and help modals in one sentence?
• Do you know which product owns the next action — HENSYNTH or HENFOIL?
• Will every number you keep carry a method label or a stored-run source?
• If you are new here, have you opened Register or Login?

Related reading on this site

• HENSYNTH candidate cards, Use this aircraft, and CAD
• HENSYNTH compliance matrix: PASS, FAIL, and margin
• HENSYNTH download and share technical reports
• HENSYNTH Geometry page: wing, fuselage, and tails
• All HENDOI blog articles
• HENSYNTH product page
• HENFOIL product page
• Pricing — Student, Professional & Team
• FAQ
• Login · Register now