A methodology to develop Service Oriented Evolutionary Algorithms

García-Sánchez, Mora, Castillo, González and Merelo

GeNeura + CITIC for IDC14. Watch this at goo.gl/KRhMi9

Evolutionary algorithms? What's that?

Sheep from US national archives

Population-based algorithms

From Flocks in Owens Valley, Ansel Adams

Evolving solutions through natural selection

Wing from the origin of Species

Select the best, combine and change them, repeat until solution found

From The descent of man by Darwin

Do current EA models have a problem?

They have 3

3 problems

Flickr image by Mutiara Karina https://flic.kr/p/a9SSm3.

Not integrated

Not standardized

By EDans

Flickr image by Edans https://flic.kr/p/opfTn.

Not dynamic

By Street Railway Journal

Flickr image by Book Archive https://flic.kr/p/ouqPNZh.

Service oriented architectures offer

Language-independence

And distribution transparency

Standard service interfaces

Distributed control of nodes

SOMA methodology for service design

Identification

Problem, algorithm and infrastructure domains

Specification

Fitness, population, parameters, operators as services

Implementation and deployment

Choose technology for publication, discovery and distribution: OSGi/WSDL/other

This buys me what?

tea and scones by Ian

A cup of tea. And scones, too.

Image by Ian at https://flic.kr/p/murCeu

Dynamic binding of services

Operators changed or added during runtime

EAs might fall in local minimum

Local minimum: valley

Some selection operators have higher selection pressure

Image from Library of congress

Binary tournament: greedy

Roulette selection: relaxed

Enabling new operators

Identification and specification

Results with dynamic binding

Dynamic binding rules!

Services afford new ways of assembling evolutionary algorithms

Dynamic monitoring and binding of operators/services rock!

Open Science!

Download/comment/copy at http://osgiliath.org

Any question?

Download/fork this presentation from http://git.io/idc14soea

Use arrow keys to navigate