-
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: show names for the queued experiments #6050
Comments
If the user is specifying a name with When it comes to the current autogenerated names we cannot generate them for queued experiments, as they are derived from the resulting pipeline after reproduction. So displaying autogenerated names for queued experiments will require changing how we autogenerate names. Regarding removing queue experiments, that will happen eventually along with proper queue management in general (#5615) Regarding priority, I don't think it's worth it to put much time into how |
👍 |
@aguschin This part got lost in the discussion, but see #6157. @pmrowla I think it would be helpful to add this to the loose ends to clean up for experiments. It's not clear if or when we will have a separate |
@dberenbaum this is pretty much just a one liner UI change. We already have names for queued experiments internally, we just don't show them in the UI right now. |
It would be great to see the name of a queued experiment. Right now if we run, for example
the table below won't show it's name right away:
only after we run it with
dvc exp run --run-all
:We could live fine without names, but if for example we want to review multiple queued experiments with
dvc exp show
and look for what we forgot to add to the queue, it would be helpful to see them.Another use case which is not supported now, AFAK, is to remove queued experiments. If I added few experiments, I may want to remove one of them before running them all. Right now I need to reset all queued experiments with
dvc exp remove --queue
and add required ones again. This removal would be convenient to do if we could reference the queued experiments by their names. If it seems like a valid use case and dvc has no such feature, I can create a feature request.The text was updated successfully, but these errors were encountered: