HENSYNTH Synthesize page and four candidate styles

Requirements → aircraft

The Synthesize page title in HENSYNTH is Requirements → aircraft. It assumes you already saved mission caps on the Requirements page. Feasibility is answered first — either on Requirements with the plausibility button or again when synthesis returns. If the feasible region exists, the UI says candidates below are style searches, not a certified set.

Run Synthesize candidates

The header action Synthesize candidates calls the synthesis API on the current project. While the search runs, the button reads Searching…. Results land as up to four candidate cards plus a feasibility summary when the engine provides one.

Handoff from Requirements: the link Then auto-size aircraft candidates → saves requirements, stores a session handoff key, navigates here, and can trigger synthesis when the handoff matches the project id.

The four styles

Intro copy on the page names the starting points:

• Minimum MTOW — pushes wing loading and sizing toward the lightest takeoff mass that still closes the requirement loop in screening.
• Maximum endurance — biases battery fraction and aerodynamic choices toward loiter time on the stored energy model.
• Minimum energy — favors the style that minimizes energy use for the stated cruise point within the search grid.
• Balanced design — a compromise point across the same wing-loading, aspect-ratio, and battery-fraction styles the engine documents in candidate packages.

Each card shows architecture label, why/plus/minus narrative, risks, wing loading W/S, aspect ratio AR, battery fraction, compliance pass count, and headline predictions (MTOW, range, endurance) when the slim analysis stored them.

What synthesis is not

Synthesis sweeps class-level sizing knobs — wing loading, aspect ratio, battery fraction — then runs the same slim multidisciplinary analysis used for screening. It does not run wind-tunnel corrections, does not optimize every geometric degree of freedom, and does not output a type-approved aircraft. Pick a card when it explains a trade you want to explore, then Use this aircraft to copy its geometry into the project for a full Run screening on the Aircraft workflow.

Reports on each card

Every candidate card carries download and mail icons like the requirements run panel. The zip documents sizing choices, compliance image, planform figure, and method note: class wing-loading, aspect-ratio and battery-fraction styles, then slim analysis. Share by email with the same two-address limit and optional note.

In simple words: what this page is for

Run Synthesize candidates after feasibility: minimum MTOW, maximum endurance, minimum energy, and balanced design — style searches with wing loading, AR, and battery fraction.

This lesson exists because aircraft teams often jump to heavy CFD before the mission is even closed. HENSYNTH Synthesize page and four candidate styles 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 Synthesize page and four candidate styles 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 Synthesize page and four candidate styles 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