Optimize fields: objective, algorithm, constraints and operating points

What Optimize is for

Optimize proposes a better section inside a stated design space under stated objectives and constraints. It does not replace judgement, geometry gates or certification analysis. Baseline: pick an airfoil first. After Optimize: re-run Geometry Doctor and VIC polars on the candidate.

Jobs can leave the page once queued — watch Dashboard → Jobs.

---

Objective

Purpose. The scalar the search maximises or minimises (for example max L/D at the operating points). Why it must match the mission. Maximising L/D at climb CL is a different foil than maximising L/D at cruise CL. Result. objectiveValue, improvement % vs baseline, and a candidate shape tagged with that objective id.

Pick the objective in the Objective & search panel before choosing an algorithm.

---

Algorithm

Why algorithm choice matters. Grid is honest and limited; Bayesian explores; gradient assumes a smooth CST parameterization. Wrong algorithm wastes monthly optimize quota.

---

Iterations

Purpose. Search budget (UI typically caps, e.g. 1–20). Why not always max. Each iteration burns viscous evaluations at every operating point. Result. More iterations → more chance to improve, more quota use. Stop when improvement flattens or budget ends.

---

Constraints

Result. Candidates that violate constraints are rejected or penalised — you should not get a “winner” that breaks the spar depth you typed.

---

Operating points (multi-point design)

Each row is a design condition:

Why multi-point. A foil great only at one CL often fails climb or reserve. Weights encode “cruise matters twice as much as climb.” Cost. Each point costs several viscous solves per candidate — keep the table honest and short (UI allows a small number of points). Result. Objective averaged across weighted points; improvement reported vs baseline under the same points.

Use + Add point for cruise + climb (or similar). Remove points you do not mean.

---

What results you get

Expect:

• Candidate coordinates / parameters
• Objective value and improvement % vs baseline
• Notes when the search did not beat baseline (already optimal for this objective/constraints, or needs another algorithm)
• Ability to save the optimized airfoil into your library
• Progress via the analysis job UI / Dashboard

What you must do next

1. Geometry Doctor on the new shape
2. Fresh VIC polars (do not trust optimize-internal numbers alone for review)
3. Optional: robustness / sensitivity (Re, transition, manufacturing)
4. Selection compare if multiple candidates exist
5. Export datasheet / package when the trail is worth archiving

---

Field checklist

1. Baseline foil selected and gated
2. Objective matches the review question
3. Algorithm matches the parameterization (NACA vs CST)
4. Min/max t/c and Cm from real constraints
5. Operating points from real mission Re / Mach / CL with thoughtful weights
6. Iterations sized to monthly optimize budget

Honesty reminder

Optimize proposes. You still own the decision. Method IDs and gates stay on every follow-up polar. Robustness after the peak matters more than the peak.

In simple words: what this page is for

What every Optimization control means — max L/D objectives, NACA/CST/Bayesian search, t/c and Cm limits, multi-point Re/Mach/CL weights — and what results to trust.

This lesson exists because section decisions fail when geometry, method labels and selection reasons are scattered. Optimize fields: objective, algorithm, constraints and operating points 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 Optimize fields: objective, algorithm, constraints and operating points 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 Optimize fields: objective, algorithm, constraints and operating points 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