Papers › Finding Efficient Trade-offs in Multi-Fidelity Response Surface Modeling
Finding Efficient Trade-offs in Multi-Fidelity Response Surface Modeling
Sander van Rijn, Sebastian Schmitt, Matthijs van Leeuwen, Thomas Bäck
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
In the context of optimization approaches to engineering applications, time-consuming simulations are often utilized which can be configured to deliver solutions for various levels of accuracy, commonly referred to as different fidelity levels. It is common practice to train hierarchical surrogate models on the objective functions in order to speed-up the optimization process. These operate under the assumption that there is a correlation between the high- and low-fidelity versions of the problem that can be exploited to cheaply gain information. In the practical scenario where the computational budget has to be allocated between multiple fidelities, limited guidelines are available to help make that division. In this paper we evaluate a range of different choices for a two-fidelity setup that provide helpful intuitions about the trade-off between evaluating in high- or low-fidelity. We present a heuristic method based on subsampling from an initial Design of Experiments (DoE) to find a suitable division of the computational budget between the fidelity levels. This enables the setup of multi-fidelity optimizations which utilize the available computational budget efficiently, independent of the multi-fidelity model used.
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Datasets
Introduced by this paper, per the archive.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections