-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
metrics: Use "metrics.json" as DEFAULT_METRICS_FILE. #8484
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.
I was thinking about how DEFAULT_PARAMS_FILE
affects the dvc.yaml
definition but I don't think it makes much sense to change metrics
to also support a "granular" definition.
Feels overkill to implement:
metrics:
- metrics.json:
foo
And use the default file to make it equivalent to:
metrics:
- foo
890fb65
to
ef94e63
Compare
I know we just use |
Agreed that metrics don't need granular support.
There's some related discussion in iterative/dvclive#292. I'd vote to keep as is since we already have it implemented that way in dvclive. @daavoo Is this still desirable given the coming changes in #8371 and iterative/dvclive#311? My concern would be that we are adding defaults that do not match the dvclive outputs. |
I was checking how hard was to do this and then combine it with #7939 in comparison to #8371 |
It's more limited (for example, you can't have mutliple dvclive dirs), but I'm open to it as a first step if it's quicker. cc @skshetry |
Closing in favor of top-level metrics |
Closes #6168