Marcus Märtens
**Is your feature request related to a problem? Please describe.** Currently, archipelago evolution has a bottleneck since selection and migration policies are executed in the main thread. This is barely...
The current (default) implementation of PSO in pagmo is from 2007 and is no longer up to date. The PSO community has a reference implementation for benchmarking purposes (SPSO2011) which...
Add a new metaproblem "noise" which allows to turn a UDP into a stochastic version by adding different flavors of noise to the objective function.
There is currently a switch statement in the DTLZL-problem that triggers certain objective functions to be executed on the decision vector. A potential performance improvement would be to substitute this...
Getting list of islands would already be helpful, because as it stands now, one has to index each island directly or loop over the whole archipelago if one is interested...
Currently, an archipelago object allows to access its islands by indexing: > `archi[1]` > Island name: Multiprocessing island > Status: idle > ... Looping like `for isl in archi` is...
Currently, all functionality related to the low discrepancy sequences is only available in [C++](https://esa.github.io/pagmo2/docs/cpp/utils/discrepancy.html). It would be nice to access those sequences from Python as well.
`set_output_f` exists only for dcgpann-types at the moment, which is a pity. It makes it difficult to simply switch the type of dcgp-expression with something else (like expression_double). Having better...
The docs say that the `dcgpy.expression_ann` can take ephemeral constants, however the python constructor does not allow it. https://darioizzo.github.io/dcgp/docs/python/expression_ann.html Some of the example code does not work, for example ```...
If symbolic expressions become too convoluted/long during evolution, the log-file grows extremely in size until it fills up the memory, leading to poor performance and freezes. The following code can...