The generation of the diagrams for the user manual requires a lot of manual work: trigger the generation and copying the graphs into the right directory. This generation process needs to be unified and automated. Ideally one script call, e.g. generate_graphs.sh, should trigger the generation process and copy the results into the correct directory.

The place where the diagram generation code i

I am entering the subject as a non mathematician and non data scientist. I'm a potential user of your code who is looking to solve actual down to earth practical problems. While your code apparently beautifully includes a multitude of problems and algorithms, they are really wasted on me as I simply don't get the math, the lingo or the examples.

I therefore suggest you provide a few practical e

Can you give an example about how to use parameter 'outputFcn' in main function without GUI.
The format is like below:

1. for r = 1 : 10
2. main('-algorithm',@ARMOEA,'-problem',@DTLZ5,'-save',1,'-run',r);
3. end

One of the strengths of evolution strategy algorithm is its linear scalability.
Thus it would be great to have this implemented in Evostra.

Needs to allow for:

• hoc code should be read from string (See #143). hoc_path is not necessary anymore. Should be first argument after name.
• we need a morph_dir argument to specify morphology directory. when this is specified morph filename in hoc can be used.
• morph_filename, overwrite morph_filename specified in hoc
• hoc code should not have full path to morpho anymore (only morph_filename

The attr ranges could accept a set of chars. The attr ranges are mainly used by the plugins to define their attributes, e.g., see the attributes of this plugin.

The examples below could be supported:
`"char{a,y,c,p

Is your feature request related to a problem? Please describe.
When using the built in agents, users cannot override the strategies.

Describe the solution you'd like
The constructors for the built in agents should take strategy as an optional argument that defaults to the parent's default strategy.

The Optimizers must all be present in buildOptions for a successful build.
Should be documented (and more clearly named) if this is the correct behavior.

Some problems/algorithms seem to have an inconsistent python exposition in terms of types.

For instance, in ../src/problems/dtlz.cpp we have:

dtlz::dtlz(unsigned prob_id, vector_double::size_type dim, vector_double::size_type fdim, unsigned alpha)

But in the ../pygmo/expose_problems_0.cpp it is exposed as:

dtlz_p.def(bp::init<unsigned, unsigned, unsigned, unsigned>

I