Skip to content
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

Expose negate_key_metric argument in Job API. #2585

Open
holgerroth opened this issue May 17, 2024 · 0 comments
Open

Expose negate_key_metric argument in Job API. #2585

holgerroth opened this issue May 17, 2024 · 0 comments
Assignees

Comments

@holgerroth
Copy link
Collaborator

          This is different, what metrics you pass in vs. how best model selector behaviors

for example if the metrics is "accuracy", or "auc"

 the best model selection criteria will be   metrics_new > metrics_old

if the metrics is "loss"
the best model selection criteria will be metrics_new < metrics_old

Does best model selection handle these ? how does the model know metrics criteria to use (> or <) for given metrics name ?

Originally posted by @chesterxgchen in #2563 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant