[KongchangAI]
ConceptHEMO 框架

HEMO

A framework that treats the harness in automatic operator design as the object of self-evolution, achieving self-modification of the search process for multi-objective combinatorial optimization through single-module updates, discounted UCB scheduling, and persistent memory.

Timeline (last 90 days)

Oct 30

HEMO proposes making the harness of automatic operator design itself the optimization target, and maintaining a persistent harness state that is updated module by module.

Unverified50%
Oct 30

HEMO's harness revision logic covers four levels: which piece of experience to retrieve, which operator to improve, which parents to select, and how to orchestrate the search steps.

Unverified50%
Oct 30

HEMO adopts a single-module update design to reduce the coupling of the search space, making the effect of each change easier to attribute.

Unverified50%
Oct 30

HEMO uses a discounted UCB scheduler to direct adaptation resources toward more promising modules based on changes in each module's utility.

Unverified50%
Oct 30

HEMO uses a persistent memory file system that preserves candidate results and diagnostic feedback across harness states, enabling subsequent states to build on previously accumulated optimization experience.

Unverified50%
Oct 30

HEMO was validated on eight MOCO tasks and two structurally different evolutionary backbones.

Unverified50%
Oct 30

Experimental results show that HEMO performs strongly compared with traditional evolutionary methods, neural network methods and LLM-based AOD baselines, and can effectively transfer to related tasks.

Unverified50%
Oct 30

The cost of HEMO is increased system complexity, and how the additional overhead brought by module updates and scheduling varies with task scale still requires follow-up work to answer.

Unverified50%

All Facts (8)

Source Articles