atlas

Research map / Learning theory and algorithms / Combinatorial and search optimization

How to Use the Metropolis Algorithm for Multi-Objective Optimization?

AAAI 2024 · Learning theory and algorithms › Combinatorial and search optimization · approach: Multi-objective optimization · 9 citations (OpenAlex)

Read the paperCheck your idea against 108,967 papers

AI-extracted summary. Written by AI from the paper's full text. Numbers and claims can be wrong or missing context, so check the paper before you cite or build on it.

Runtime analysis of multi-objective Metropolis algorithms on a new bi-objective multimodal benchmark DLTB, showing parent-replacement variants are inefficient while a keep-parent variant solves it efficiently.

Problem

Whether the advantages of the Metropolis algorithm (accepting inferior solutions to escape local optima), proven for single-objective optimization, carry over to multi-objective optimization.

Approach

Introduces DLTB, a bi-objective multimodal benchmark built from the single-objective DLB problem, where not all local optima are Pareto optimal; shows that replacing the parent with an accepted inferior offspring fails, while keeping the parent (removing only weakly dominated solutions) yields efficient runtimes.

Key results

Measured effects reported in the paper

What was changedWhereMeasuredEffect
Replace the parent with an accepted inferior offspringMulti-objective Metropolis with one-bit mutation · DLTBcoverage of the full Pareto frontHurt
Replace the parent with an accepted inferior offspringMulti-objective Metropolis with standard bit-wise mutation · DLTBexpected runtime to cover the full Pareto frontHurt
Use one-bit mutation instead of standard bit-wise mutation (ablation)Multi-objective Metropolis with parent replacement · DLTBcoverage of the full Pareto frontHurt
Keep the parent when an inferior offspring is accepted (ablation)Multi-objective Metropolis · DLTBexpected runtime to cover the full Pareto front: cannot cover the full Pareto front -> O(n5)Helped
Use standard bit-wise mutation instead of one-bit mutation (ablation)Multi-objective Metropolis with parent kept · DLTBruntimeHurt
Use GSEMO instead of parent-replacement multi-objective MetropolisDLTB optimizers · DLTBexpected runtime to cover the full Pareto front: Ω(n5) -> 3en3(n−1)/2Helped
Use NSGA-II instead of parent-replacement multi-objective MetropolisDLTB optimizers · DLTBexpected iterations to cover the full Pareto front: Ω(n5) -> O(n3)Helped
Use SMS-EMOA instead of parent-replacement multi-objective MetropolisDLTB optimizers · DLTBexpected runtime to cover the full Pareto front: Ω(n5) -> 3eµn3/2Helped
Use parent-kept Metropolis with one-bit mutation instead of GSEMODLTB optimizers · DLTBruntimeHelped
Use parent-kept Metropolis with standard bit-wise mutation instead of GSEMODLTB optimizers · DLTBruntimeNo clear effect

Surprising findings

Limitations

Experimental setup

Benchmarks: DLTB

Metrics: expected number of fitness evaluations to cover the Pareto f

Baselines: GSEMO NSGA-II SMS-EMOA SEMO RLS

Builds on: Metropolis algorithm SEMO GSEMO NSGA-II SMS-EMOA

Closest papers by meaning

Writing a paper in this area? scime draft is a free LaTeX editor with AI included, real-time co-authors and a check of your references and venue rules before you submit. It also imports OpenAI Prism projects.

Open scime draft

Get the next scime Dispatch and a monthly field update

Free. We send a confirmation link first; every email has a one-click unsubscribe. Privacy