HENSYNTH workflow: dashboard to technical report

Start on the HENSYNTH dashboard

Sign in through HENDOI and open HENSYNTH. The dashboard lists projects and states the two-step headline: define aircraft geometry, set mission requirements, then synthesize candidates. Calculations run in the C++ engine; the UI displays results. Create or open a project to enter the sidebar workflow.

Step 1 — Aircraft geometry

On the Aircraft page, choose type baseline if helpful, edit wing, fuselage, horizontal and vertical tail, and propulsion, inspect 2D views and 3D drag view, and save. Validation badges and geometry checks flag issues before you waste a run. CAD continuity panels note what must refresh after planform edits.

Step 2 — Requirements

Enter the twelve mission fields with units as labelled. Open asterisk help on any unfamiliar cap. Save requirements. Optional: run physical plausibility feasibility, seed HEN-AI review, then Run screening from the project workspace (Requirements participates in save-before-run).

Step 3 — Requirements run report

When analysis completes, read the Requirements run panel: metric grid with ? modals, compliance matrix PASS/FAIL, reasoning findings. Download hensynth-requirements-run.zip or share by mail from the top-right icons. This is the first technical report milestone in the loop — conceptual screening only.

Step 4 — Synthesize (optional)

When feasibility allows, use Then auto-size aircraft candidates → or open Synthesize from the sidebar. Run Synthesize candidates. Compare four styles. Download per-candidate zips or mail them. Apply one geometry with Use this aircraft, return to Aircraft to verify, Run screening again.

Step 5 — Analysis: Mission, Performance, Trades, Optimize, Reports

Open the Analysis group in the HENSYNTH sidebar. Mission shows stored mission metrics, optional battery day scenarios, and mission-opt Run. Performance shows prediction tiles and any mission / section-Cd bridge. Trades sweeps one variable and can run local sensitivity. Optimize runs a conceptual random-search range maximizer. Reports downloads the latest analyze PDF, lists stored runs, and can mail a screening summary. Background jobs apply when runs exceed interactive limits. Conceptual screening only — not certification.

HEN-AI and Help throughout

HEN-AI dock follows the page context. It explains stored results and can propose requirement edits; it does not replace Run screening. In-app Help restates the ordered checklist and support contact. Neither substitutes for engineering judgment or certification.

Plans and product boundary

Student, Professional, and Team plans bill monthly in USD at 9, 29, and 89 as on the pricing page. HENSYNTH is live for the geometry–requirements–run–compliance–synthesis–report path described here. Wind-tunnel validation and type certification remain outside that path by design.

In simple words: what this page is for

End-to-end HENSYNTH help path: dashboard project, Aircraft geometry, Requirements, Run screening, compliance, Synthesize, candidate apply, zip report, HEN-AI.

This lesson exists because aircraft teams often jump to heavy CFD before the mission is even closed. HENSYNTH workflow: dashboard to technical report 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 workflow: dashboard to technical report 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 workflow: dashboard to technical report 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