ref: document `dvc queue` and `dvc exp` task-queuing changes
See original GitHub issueDocs meta-issue for https://github.com/iterative/dvc/issues/7592
- Initial documentation (command refs) will be driven by the core team.
- Update existing
exp
commands/flags that get aliased/deprecated or otherwise chaged. - User guides/ other docs should be updated, but existing functionality is being preserved (so there is no special rush on this rn).
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:12 (12 by maintainers)
Top Results From Across the Web
queue | Data Version Control - DVC
A set of commands to manage the DVC experiments task queue: start, stop, status, ... You can use dvc exp run --queue to...
Read more >Issues · iterative/dvc.org · GitHub
... with Code review Manage code changes Issues Plan and track work Discussions ... ref: document dvc queue and dvc exp task-queuing changes...
Read more >conda-forge - :: Anaconda.org
7za, 9.20, LGPL, X, A file archiver with a high compression ratio ... SSH plugin for DVC. dvc-task, 0.1.8, Apache-2.0, X, Extensible task...
Read more >DVC Experiment management workflow - git - Stack Overflow
You did everything alright. In the end, after pulling, you can see that when using dvc exp show your experiments will be there....
Read more >US8724436B2 - Audiovisual distribution system for playing an ...
The entire contents of which are hereby incorporated by reference in this application. ... 7 is a flowchart which describes task queuing.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
queue logs -f/--follow
without a task should automatically follow the currently running experiment in the future.When developing the
queue
related feature. What I realized is that queuetasks
andexperiment
are different aspects. Although they are strongly related but are still different.tasks
are more focused on execution whileexperiments
are more focused on the result. One checkpoint task can generate dozens ofexperiments
, and experiments can be run without using a queue worker. The difference also comes into thestatus/show
table, we can delete a succeeded task msg and leave the experiment result (revision) untouched.I think we can at least start with the current help output to give an overview: