-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Enabling custom groupId column in the Ranking AutoML experiment #5246
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
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -57,9 +57,9 @@ public bool IsModelPerfect(double score) | |
| } | ||
| } | ||
|
|
||
| public RankingMetrics EvaluateMetrics(IDataView data, string labelColumn) | ||
| public RankingMetrics EvaluateMetrics(IDataView data, string labelColumn, string groupIdColumn) | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can we just put groupId column as an option when creating RankingMetricsAgent? So that we don't have to add an extra groupIdColumn to IAgent.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, we can do that. I think a possible concern is that GroupId is required by RankingTrainers, and passing it in as an option gives me the impression that it's optional. I think that if we make the default value of |
||
| { | ||
| return _mlContext.Ranking.Evaluate(data, labelColumn); | ||
| return _mlContext.Ranking.Evaluate(data, labelColumn, groupIdColumn); | ||
| } | ||
| } | ||
| } | ||
Uh oh!
There was an error while loading. Please reload this page.