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
Allowing MetricCollection to contain other MetricCollections for even less boilerplate and coding effort.
Motivation
When using both micro and macro metrics I either need to call two different collections or provide the collection with a dictionary of names, which could easily be created by appending a post-/prefix to the metric name.
But I think accepting nested collections would make for a more convenient interface.
(It would probably be the easiest solution to just generate this version if presented with nested collections.)
The text was updated successfully, but these errors were encountered:
🚀 Feature
Allowing MetricCollection to contain other MetricCollections for even less boilerplate and coding effort.
Motivation
When using both micro and macro metrics I either need to call two different collections or provide the collection with a dictionary of names, which could easily be created by appending a post-/prefix to the metric name.
Pitch
I envision something like:
I want a nested collection to be treated like any other metric. Ideally nested collections would also make use of
compute_groups
.Alternatives
The same functionality can already be achieved by:
But I think accepting nested collections would make for a more convenient interface.
(It would probably be the easiest solution to just generate this version if presented with nested collections.)
The text was updated successfully, but these errors were encountered: