-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aggregate component #26
aggregate component #26
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Hakimovich99,
This will only aggregate a single metric, right?
I would prefer to hardcode the metrics that we're using instead of making it dynamic and limited to a single metric.
No, it aggregates every metric. Here it's the context_relevancy and context_precision. It takes all metrics columns output from the previous component and gives the agg metric for each. |
Actually not interesting to have this argument. The user will already choose the metrics to compute in the "retriever_eval" component, no need to choose again which metrics to agg, we can just agg them all.
Ah yes, I see. Since you add the metrics as rows. Nice solution 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Dask transform component to aggregate the evaluation results. Might have to be adapted to new dataset format.