-
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
exp show csv/tsv option #5446
Comments
The checkpoint tip column is redundant here, the json field is pretty specific to how we are rendering the table in the CLI & vscode extensions. (You can figure out the tip of a checkpoint branch by tracing the checkpoint parents field in reverse). I'm also not sure if |
We could have a "Branches" or "Refs" (to include tags) column like this:
Or maybe it makes more sense to drop this column completely? |
Following up on this since it's related to #5980 (reply in thread) and other discussions around plotting metrics from multiple experiments. This issue is not specifically about csv/tsv format, but instead about ease of parsing data from |
I think it'd be really useful to include a to_csv option. Personally I just find the In addition I plan on running my pipeline lots of times, and the table this command shows is perfect, it would just be nice to store a lot of iterations of the pipeline in a csv file. This would enable the data to be easily viewed in excel, and manipulated in that environment which would be a really helpful functionality! Thanks! |
This should be easy to do if it's simply taking the existing table that shows in the terminal and putting it into csv format (instead of designing a specific csv format like the comments above). |
* Show csv format of experiments fix #5989 and #5446 1. add --show-csv to dvc exp show 2. add a new functional test for csv format 3. add a new unit test for show_experiements 4. solve name duplication in table common headers (Created,Parent, etc... ), metrics files and param files. Co-authored-by: Peter Rowlands (변기호) <peter@pmrowla.com>
See #5381 (comment) for context.
This is NOT a requirement for 2.0 release, but a nice-to-have that could be added after release.
Proposed format:
Questions:
@pmrowla @dmpetrov
The text was updated successfully, but these errors were encountered: