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

guide: top-level dvc.yaml sections #4251

Closed
dberenbaum opened this issue Jan 19, 2023 · 7 comments
Closed

guide: top-level dvc.yaml sections #4251

dberenbaum opened this issue Jan 19, 2023 · 7 comments
Labels
C: guide Content of /doc/user-guide

Comments

@dberenbaum
Copy link
Collaborator

Report

Update docs to better reflect that params, metrics, and plots may be either parts of stages or independent entries in dvc.yaml.

@dberenbaum dberenbaum added the C: guide Content of /doc/user-guide label Jan 19, 2023
@dberenbaum dberenbaum changed the title Top-level dvc.yaml sections guide: top-level dvc.yaml sections Jan 19, 2023
@jorgeorpinel
Copy link
Contributor

jorgeorpinel commented Jan 26, 2023

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?

@dberenbaum
Copy link
Collaborator Author

Closing in favor of #2572

@skshetry
Copy link
Member

I wish we had a good name for this. Top-level plots/params/metrics is an odd naming,
even more so in the internals. :)

@jorgeorpinel
Copy link
Contributor

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.

@skshetry
Copy link
Member

skshetry commented Jan 28, 2023

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.

@skshetry
Copy link
Member

Or maybe call top-level ones simply plots/metrics/params and stage-level ones to be Pipeline artifacts/plots/metrics/params?

@dberenbaum
Copy link
Collaborator Author

@skshetry Maybe better to discuss in #3763?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: guide Content of /doc/user-guide
Projects
None yet
Development

No branches or pull requests

3 participants