Geometry Doctor results: metrics, scores and PASS / WARNING / FAIL

Why geometry comes first

A spiked LE, crossed TE, undersampled camber or noisy digitize invents lift and drag long before VIC deserves the blame. Geometry Doctor (the quality gate) decides whether analysis may proceed honestly.

After Create, Import or Digitize: inspect → repair → repanel → normalize as needed, then read the gate.

---

Core section metrics (what they mean)

Result. Numbers on the section card and in digitize quality panels after Reconstruct. If they disagree with the drawing you thought you traced, fix the source — do not “hope the polar averages it out.”

---

Gate statuses

FAIL blocks the polar path until you fix the section. WARNING keeps the warning visible — it does not erase it.

---

Quality / readiness scores (digitize & geometry)

After digitize Reconstruct (and similar geometry packs) you may see scores such as:

How to use them. Treat suggestions as a starting polar recipe, not as certification limits. A high DAT score does not mean the foil is “good” aerodynamically — only that export geometry is orderly.

---

What the gate checks (checklist)

• Thickness ratio and camber distribution sanity
• Leading-edge radius and nose resolution
• Trailing-edge state (open, crossed, collapsed)
• Curvature smoothness and local spikes
• CST / PARSEC fit residual when those parameterizations apply

Results land with a reason you can act on — not a silent boolean.

---

Import path extras

Selig / Lednicer DAT: inspect → repair → repanel. Import is not “load and hope.” Conditioning decides whether analysis may proceed. The same PASS / WARNING / FAIL language applies.

---

Expected workflow result

1. Metrics you can quote in a datasheet
2. A gate decision with reasons
3. Optional repairs that change the ordinate trail (documented)
4. Permission — engineering, not legal — to climb thin-airfoil → panel → VIC

Honesty reminder

Skipping conditioning does not save time. It exports noise into compare, optimize and review. The quality gate exists so selection starts from geometry you can defend.

In simple words: what this page is for

What t/c, camber, LE radius, TE state, CST residual, polar readiness scores mean — and why you should fix FAIL before climbing the analysis ladder.

This lesson exists because section decisions fail when geometry, method labels and selection reasons are scattered. Geometry Doctor results: metrics, scores and PASS / WARNING / FAIL helps you keep a clean trail from shape to polar to choice.

Why the topic matters

Engineers lose time when a title sounds clear but the page only sketches the idea. This article expands Geometry Doctor results: metrics, scores and PASS / WARNING / FAIL 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: create a HENDOI account or log in, open HENFOIL, bring a section in (create, import DAT, or digitize), pass the geometry gate, climb the analysis ladder only as far as the decision needs, then compare and archive. Every calculated number should keep its method label.

When the section choice is ready for the aircraft, continue in HENSYNTH for mission, compliance and trades. Same account. Same plans.

What this page will not claim: a teaching polar or geometry note is not a flight-Re certificate. HENFOIL labels methods so you know what you bought. Tunnel data and professional judgement still sit outside any single software run.

Checklist before you leave this page

• Can you state the idea of Geometry Doctor results: metrics, scores and PASS / WARNING / FAIL in one sentence?
• Do you know which product owns the next action — HENFOIL or HENSYNTH?
• 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

• Airfoil selection with a documented why-#1
• The HENFOIL analysis ladder: when to escalate
• Create airfoil fields: NACA, analytic and CST — what each digit means
• Digitize field-by-field: every control, why fill it, what you get
• All HENDOI blog articles
• HENFOIL product page
• HENSYNTH product page
• Pricing — Student, Professional & Team
• FAQ
• Login · Register now