`dvc queue run <hash>` to run a specific experiment

[PythonFZ]

I'm using the dvc experiment feature together with the queue to plan multiple experiments I want to run.
I wanted to run an already queued experiment to check its outputs without submitting all jobs.

My Idea would be something like
dvc queue run <hash> which will run the given experiment in .dvc/tmp/ and upon success remove it from the queue.

[dberenbaum]

Keeping this feature request open, but in case you want a workaround for this in the meantime, you can do:

$ dvc exp apply <queue_id>
$ dvc exp run --temp

[PythonFZ]

Thanks, I had to add dvc queue remove to clean the queue from the old experiment which would just be a copy. But this was more or less exactly what I was looking for.

dvc exp apply $queue_id
dvc exp run --temp
dvc queue remove $queue_id

[dberenbaum]

Maybe dvc queue pop <hash> would make sense as an alias for that?

[PythonFZ]

It probably can't be dvc queue run <hash> because the id changes so I like the dvc queue pop <hash> idea.
How would this affect the workspace? If you use apply + run --temp it will change the workspace, so maybe use stash the workflow before the apply and then apply the stash afterwards?

[PythonFZ]

In addition to dvc queue pop <id> one could also have just dvc queue pop to start the next experiment in line. In this way one can run multiple experiments in temporary directories from the same repository. This could be especially useful on shared file systems to run experiment from different machines.

[PythonFZ]

I found a solution for myself by writing https://github.com/zincware/dask4dvc and adding this feature via dask4dvc run <id> which will reproduce the specific experiment.

[dberenbaum]

Nice @PythonFZ! Any interest in submitting a PR to do it in DVC?

[gregstarr]

Thanks, I had to add dvc queue remove to clean the queue from the old experiment which would just be a copy. But this was more or less exactly what I was looking for.

dvc exp apply $queue_id
dvc exp run --temp
dvc queue remove $queue_id

does this work in the case of multiple workers assuming the workers aren't trying to do dvc exp apply at the same time? once the call to dvc exp run --temp is called, can the workspace be safely changed by another worker with dvc exp apply?