Martin van der Schelling

## Problem By tackling #259 , there exists a use-case where the user wants to only store selected information (e.g. the loss) instead of the entire history of evaluations. A...

## Problem The computational burden of optimization and memory issues of optimization for large dimensions merely comes from storing the history of the input vector and losses. At the moment...

## Problem When sampling from a Domain with a constant variable with a float, the following error is raised: ``` Traceback (most recent call last): File "/home/martin/Documents/scratchbook/try_hydra/main.py", line 10, in...

## Problem In the documentation, it is not clear how you can create an `ExperimentData` object from a previously created `f3dasm` project directory (the .from_file method) when using `hydra` ##...

## Problem Docs are accessible from both [](https://bessagroup.github.io/f3dasm/) and [](https://f3dasm.readthedocs.io/en/latest/). That might be confusing from a new user. ## Possible Solution - remove workflow from github actions to publish documentation...

## Problem Constructing a `DataGenerator` can be quite complex, so in order to improve the usability, it would be great if there was a way to convert the simplest of...

## Problem Currently there is no easy way to remove 'error' jobs in your experiment_data. ## Possible solution add a `.select_all_finished` method to `ExperimentData` to only display experiments that are...

Implement a new `x0_selection` strategy that samples new samples for the initial populatioin

In the benchmarkfunction section, there should be more information or a link to more information about the benchmark functions. For example, pictures of the 2D loss landscapes are now missing

undefined