Make OpenMLTraceIteration a dataclass #1201
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR changes OpenMLTraceIteration into a dataclass, which makes the code neater and comes with a nice default repr.
Someone recently remarked that the OpenMLTrace iteration representation was cryptic and hard to miss.
One example (produced by MWE below, shortened for convenience):
In a large dump, it's easy to miss at first take that the "[(0,9,4): 0.798329 (True)]" parts represent custom OpenML objects.
Even when you spot that, it's not immediately obvious what the provided information is and it misses some of the information for the trace (e.g., parameter values).
This PR will change the corresponding output to:
new:
Both outputs were generated by following script: