You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the RunHistory class, when loading data from a file, quite some data on an entry level is being extracted by using hard coded indices of a list. This is very error prone and can lead to older runhistories no longer to work with a new release.
Possible Solution
Store the information as a dictionary instead so we can do key/value matching for each stored attribute.
Versions
2.2.0
The text was updated successfully, but these errors were encountered:
Hey Thijs,
First, thank you for raising the issue, and I will immediately start to get on it. However, an adapted runhistory might not be included in the next release because of chain dependencies.
Talking about the issue: Are you referring to the list of previously evaluated configurations reporting the different performances?
I believe its within the reader part of the runhistory, where it on some lower level of the .json determines which value represents what using hardcoded indexes
Description
In the RunHistory class, when loading data from a file, quite some data on an entry level is being extracted by using hard coded indices of a list. This is very error prone and can lead to older runhistories no longer to work with a new release.
Possible Solution
Store the information as a dictionary instead so we can do key/value matching for each stored attribute.
Versions
2.2.0
The text was updated successfully, but these errors were encountered: