Sander van Rijn
Sander van Rijn
Current documentation needs an update about the `AdjustableMultiFidelityFunction` class and any old references to numbered adjustable parameters such as `a2` for paciorek
https://github.com/nschloe/perfplot
See: https://asv.readthedocs.io/en/stable/ Given how often these functions may be called, being aware of possible performance regressions would be very nice. On the other hand, I don't expect that many changes...
There is currently no recorded distinction, relying on user knowledge to e.g. invert `currin` when minimizing
**In which paper is this function introduced?** "Efficient Use of Partially Converged Simulations in Evolutionary Optimization", J. Branke, M. Asafuddoula, K. S. Bhattacharjee and T. Ray, doi: 10.1109/TEVC.2016.2569018. **What function(s)...
**In which paper is this function introduced?** "A Generic Test Suite for Evolutionary Multi-Fidelity Optimization", H. Wang, Y. Jin and J. Doherty, DOI: [10.1109/TEVC.2017.2758360](https://doi.org/10.1109/TEVC.2017.2758360). **Additional information** PDF also available on...
The documentation per function is currently rather bare. By including 2d heatmap plots and/or 3d landscape plots of the functions, it will be easier for users to inspect the functions...
The code blocks in the [solution](https://carpentries-incubator.github.io/python-intermediate-development/24-diagnosing-issues-improving-robustness/index.html#solution) to the optional exercise "Add a Precondition to ..." are not syntax highlighted, as opposed to e.g. [this one in episode 2.2](https://carpentries-incubator.github.io/python-intermediate-development/22-scaling-up-unit-testing/index.html#solution)
Fixes #327 Does this warrant a new test, or is an additional check to an existing one enough?