Blog / Design and modification

Design and modification

Gradient-Based vs Genetic Algorithm Airfoil Optimization: Which Method Should You Use?

HENDOI · 27 October 2026

A gradient method follows the local slope and finishes quickly near a good start. A genetic algorithm searches more widely and spends many more evaluations. The airfoil problem decides, not a fashion.

The same problem, two ways of walking

Both methods need the same ingredients: design variables, bounds, an objective such as CD at a fixed CL, and constraints such as thickness and moment. The difference is how they choose the next shape. A gradient method estimates the slope of the objective with respect to each variable, by finite differences or by an adjoint, and steps downhill. A genetic algorithm keeps a population, combines parents, mutates children and prefers the fitter ones. It does not need a slope.

A fair comparison

Gradient-basedGenetic algorithm
EvaluationsFew, if the start is decent and the gradient is real. Finite differences cost one extra polar per variable per step.Many. A population of dozens, for dozens of generations, is ordinary. Each member is a polar, or several polars if you include a trip.
Where it endsA local minimum: the best shape in the basin where you started.A better chance of leaving a bad basin. Not a proof that the result is the global minimum.
Noise and failed pointsA single unconverged polar tilts the slope and can send the step the wrong way.More tolerant of a failed individual, because one bad member is not the only direction information you have. Still capable of breeding toward a numerical cheat.
ConstraintsNatural, if you have a real constraint formulation.Usually penalties or a feasibility rule. A soft penalty will be exploited.
Best use on airfoilsPolishing a section that is already close, in a smooth attached-flow objective, with few variables.A wide CST search, a noisy low-Re objective, or a mix of discrete choices, when you can afford the runs.

Which one you should use

  • Use a gradient method when you can start from a known section, the objective is CD in attached flow at one CL, and a finite-difference step does not fall into unconverged points. Check the result by restarting from a neighbour. If you land in the same place, the basin is real. If you do not, you have found the method’s locality, which is not a scandal. It is the method.
  • Use a genetic algorithm when the space has many CST modes, the low-Re landscape is bumpy because of bubbles, or you do not have a trustworthy baseline. Budget the evaluations first. An under-run GA is a random sample with extra confidence.
  • A practical combination is a modest global sample, or a short GA, to pick a basin, then a gradient polish. The polish is not allowed to violate the geometric constraints the GA was already enforcing.

Neither result is validated because the optimizer stopped. Re-run the winner at a second Reynolds number and with a trip, and look at the Cp plot for wrinkles. The optimization lesson and the multi-objective lesson cover objectives and Pareto fronts. This page only chooses the walker.


Where this sits in the series

In simple words: what this page is for

A gradient method follows the local slope and finishes quickly near a good start. A genetic algorithm searches more widely and spends many more evaluations. The airfoil problem decides, not a fashion.

This lesson exists because section decisions fail when geometry, method labels and selection reasons are scattered. Gradient-Based vs Genetic Algorithm Airfoil Optimization: Which Method Should You Use? 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 Gradient-Based vs Genetic Algorithm Airfoil Optimization: Which Method Should You Use? 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 Gradient-Based vs Genetic Algorithm Airfoil Optimization: Which Method Should You Use? 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?

These pages teach the ideas. They are not wind-tunnel data and not a certification analysis. When a number matters, compute it at a stated Reynolds number, Mach number and transition setting, and keep the method label on the result. In HENFOIL that production polar is a VIC polar — see the analysis ladder and the polar field guide.

Both products live

Use this lesson in the HENDOI workspace

This page sits in Design and modification. HENFOIL and HENSYNTH are both live on one account. These articles are screening lessons — not certification reports.

Live · section

HENFOIL

Turn this lesson into a section you can draw, check, analyse and compare. Run the polar at the Reynolds number of the vehicle. The method name stays on the result.

To Know More

Live · aircraft

HENSYNTH

After the section is chosen, set geometry and mission requirements, run screening, read compliance, synthesize candidates and download or mail the report.

To Know More

Aerospace industry collaboration

Share thoughts and ideas — help us build better solutions

We are looking for aerospace industry collaboration. Share your thoughts, ideas and real workflow challenges so we can improve our products and deliver the best solutions for OEMs, UAV / eVTOL teams, labs and aeronautical engineering companies.

Written by

Sundarapandi Muthupandi, Founder and CEO of HENDOI

This post by

Sundarapandi Muthupandi

Founder & CEO · HENDOI

Click to visit my profile

Related articles

Call usChat with us