-
Notifications
You must be signed in to change notification settings - Fork 386
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
guide: top-level dvc.yaml sections #4251
Comments
Related to #2572? (Maybe dupe) We have also discussed moving some or all of https://dvc.org/doc/user-guide/project-structure into a new "File Format Reference" section. Thoughts? |
Closing in favor of #2572 |
I wish we had a good name for this. Top-level plots/params/metrics is an odd naming, |
Agreed. Has been discussed too but probably merged in that way to docs as a temporary measure. In general I think we can avoid using special names that emphasize technical details like where the plots/params/metrics are defined in a YAML file. They're all still just regular plots/params/metrics. |
But I think the problem goes beyond just the naming, we have two places to write a metadata for plots/params/metrics. Maybe we should just document the top-level ones, and slowly deprecate the pipeline-level from DVC. |
Or maybe call top-level ones simply plots/metrics/params and stage-level ones to be Pipeline artifacts/plots/metrics/params? |
Report
Update docs to better reflect that params, metrics, and plots may be either parts of stages or independent entries in dvc.yaml.
The text was updated successfully, but these errors were encountered: