1085 runhistory documentation #1175
Conversation
docs/advanced_usage/8_logging.md
Outdated
| }, | ||
| ``` | ||
|
|
||
| Lastly, `config_origins` contains the origin of a configuration. |
There was a problem hiding this comment.
add, that origins can be the from the initial design or from different acquisition function maximization techniques
docs/advanced_usage/8_logging.md
Outdated
| ] | ||
| ``` | ||
|
|
||
| `configs` contains a human readable dictionary of configurations. Note that this list starts by one, therefore the 0 entry from above is mapped to 1. |
There was a problem hiding this comment.
rephrase: The config ids are 1-based. (just leave out the last half-sentence, it confused me a bit)
There was a problem hiding this comment.
The problem is that in the data part, the values are actually not starting at config_index 1, but at config_index 0. This has previously caused issues in multiple implementations :)
I will find a better way to put this :)
There was a problem hiding this comment.
weird that it is logged like this 😅
There was a problem hiding this comment.
Yes. It is one of the reasons why I want to revamp it. I am also confused by even separating the two different dictionaries. Would it not be nicer as a normal json?
|
LGTM |
Output of runhistory not well documented, related: #1174
(First step to update docs, then code bc changing code has downstream consequences of libs like DeepCAVE)
Closes #1085