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

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

• Explain the code structure and reasoning behind *inp and *out pointers
• Host a Github page for the documentation
• Clarify the LICENSE
• Separate the original code documentation from the refactored version

It doesn't seem to make much sense at the moment to have two separate documentations, especially since much of the DESDEO documentation refers to desdeo-vis stuff. A short term solution is just to make desdeo's docs script clone desdeo-vis (use submodules?) and symlink all the docs into desdeo's docs.

• Write Vignette explaining how to define a MOEADr-compliant problem
• Write vignette explaining the variation stack
• Finish documentation of function moead()
• Thorough review of documentation
• Update vignette "Writing functions for MOEADr" to reflect recent changes (local search, constraint handling, changes in variable passing etc.)