Skip to content

Commit b59fca5

Browse files
author
Sarah Krebs
committed
Add documentation on incumbent calculation for non-deterministic runs
1 parent 4af082e commit b59fca5

File tree

2 files changed

+8
-1
lines changed

2 files changed

+8
-1
lines changed

docs/plugins/configuration_footprint.rst

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,9 @@ Performance plot
4141
----------------
4242
Perhaps the most useful plot of the two is to see how much we know about which configuration will
4343
achieve which **objective** score. To view this, mousing over the **Incumbent** will tell you the
44-
best configuration found for the given *objective* and *budget*. The **Evaluated Configuration**
44+
best configuration found for the given *objective* and *budget*. For non-deterministic runs (i.e.
45+
multiple seeds evaluated per configuration), only configurations evaluated on the maximum number of
46+
seeds are considered to choose the best configuration from. The **Evaluated Configuration**
4547
points will have a true objective score, all be it possibly noisy if the objective is noisy.
4648
Using these two kind of points, we can try to infer what the performance for the rest of the
4749
configuration space will be.

docs/plugins/cost_over_time.rst

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,11 @@ deviation too.
1313
The configuration spaces of the selected runs should be equal. Otherwise, a good comparison
1414
is not possible. They can, however, still be displayed in the same graph.
1515

16+
.. note::
17+
For non-deterministic runs (i.e. multiple seeds evaluated per configuration), only
18+
configurations evaluated on the maximum number of seeds are considered to choose the best
19+
configuration at a given time from.
20+
1621
This plugin is capable of answering following questions:
1722

1823
* Does the optimizer converge?

0 commit comments

Comments
 (0)