HENSYNTH candidate cards, Use this aircraft, and CAD

What each candidate card carries

After Synthesize candidates completes, HENSYNTH renders one card per returned style. The title line is Candidate {id} — {name} with optional architecture label. Body text includes why the style exists, plus and minus trade bullets, and risk strings when the engine stored them. A monospace line summarizes wing loading W/S, aspect ratio AR, battery fraction bat, and compliance pass count passes.

When predictions exist, a second line shows MTOW, range in kilometres, and endurance in hours derived from stored screening values — read them from your run, do not treat this blog as a sample data sheet.

Download and mail on the card

Icons in the card corner mirror the requirements run panel: download builds the candidate zip with PDF, metrics PNG, planform PNG, compliance PNG, and text sections documenting sizing choices and method note. Mail opens share with CC/BCC cap and attaches the same archive. Use these when the audience needs a frozen snapshot of that style search.

Use this aircraft

Use this aircraft calls the project update API with the candidate's aircraft object when the card includes one. Success message confirms the candidate id applied as current aircraft. The button stays disabled when no aircraft payload was stored — not every partial result carries geometry.

Applying a candidate replaces the saved configuration your next Run screening will read. It does not automatically re-run analysis; open the project workspace and Run screening after apply to refresh compliance on Requirements.

Link to Aircraft and CAD continuity

Cards link to the Aircraft route for the same project so you can inspect wing, fuselage, tails, and 3D view after apply. The Aircraft page includes CAD continuity tooling: query downstream impact, revision deltas, and recompute notes when planform parameters change. That panel reminds you geometry edits invalidate stale analysis until you run again.

Sidebar CAD routes exist for deeper export workflows when your plan unlocks them. Conceptual screening on Requirements remains the quick PASS/FAIL gate; CAD is the path toward external solid models, still not certification by itself.

From card back to requirements

If compliance pass count is lower than you need, adjust requirements or try another style before apply. If apply fixes range but fails landing, edit tails or weight drivers on Aircraft, save, re-run. Candidate cards are starting points in the style search space — the authoritative compliance table is always the latest requirements run on the aircraft you saved.

In simple words: what this page is for

Read synthesis candidate cards, apply geometry with Use this aircraft, open the Aircraft page and CAD continuity after a style search — screening handoff, not auto-certification.

This lesson exists because aircraft teams often jump to heavy CFD before the mission is even closed. HENSYNTH candidate cards, Use this aircraft, and CAD 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 candidate cards, Use this aircraft, and CAD 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 candidate cards, Use this aircraft, and CAD 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 compliance matrix: PASS, FAIL, and margin
• HENSYNTH download and share technical reports
• HENSYNTH Geometry page: wing, fuselage, and tails
• HENSYNTH workflow: dashboard to technical report
• All HENDOI blog articles
• HENSYNTH product page
• HENFOIL product page
• Pricing — Student, Professional & Team
• FAQ
• Login · Register now