Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

exp: Standalone experiment running in `--temp` folder should be included in `dvc exp show` table

See original GitHub issue

When executing an experiment using dvc exp run --temp, the running experiment is not included in the output of dvc exp list nor dvc exp show. Using --queue, on the other hand, shows the experiment as running. It would be great if also in case of dvc exp run --temp the experiment would be included in the output of dvc exp show. Similarly, it should be possible to follow metrics and other plots produced by DVCLive (e.g., using VS Code extension).

Issue Analytics

State:
Created 10 months ago
Comments:13 (2 by maintainers)

Top GitHub Comments

3reactions

aschuh-hfcommented, Nov 24, 2022

With the latest DVC version and VS Code Extension, I can now see the experiment executed with dvc exp run --temp in both the dvc exp show output and the VS Code Experiments tab. It took a few minutes after starting the experiment and a first checkpoint was made before it showed up. The VS Code Experiments table shows an entry for the checkpoints, but not a row with spinning wheel to indicate the running experiment (past the last checkpoint). Live plots of the running experiment are not showing.

The VS Code Experiments table seems to take quite some time to update (my Git repo is a larger mono-repo), but once I see it was executing dvc exp show -n 3 --json in the DVC Output window, the new checkpoints of the standalone experiment running in the --temp folder appear in the list / table.

I’m closing this issue and may open a new one for the DVC Live plots if I continue to observe these not showing.

UPDATE: The plots are also updating. It’s just a bit slow for my repo, that’s all.

1reaction

aschuh-hfcommented, Nov 24, 2022

$ time dvc exp show -n 3 --json --hide-failed > /dev/null

real    0m6.875s
user    0m4.751s
sys     0m2.081s

$ time dvc exp show -n 3 --json > /dev/null

real    0m47.790s
user    0m31.023s
sys     0m16.655s

Seems related to

It would be great if one could check / uncheck these options through the VS Code Settings. A workaround for me here would indeed be to be able to ignore failed experiments.

Top Results From Across the Web

exp run | Data Version Control - DVC

Provides a way to execute and track experimentsexperiments in your projectproject without polluting it with unnecessary commits, branches, directories, etc.

Intel® VTune™ Profiler User Guide

On a macOS system, you can install VTune Profiler and run a remote analysis and view collected data on the macOS host. You...

guA - River Thames Conditions - Environment Agency - GOV.UK

Credomatic american express telefono, Beauty4u huddersfield, ... Bonel yay kayseri, Forever bridal show 2016, Helen ngalaba, Mip charges in nebraska, ...

Debugging with GDB - sourceware.org

Only a restricted set of commands can be placed into an early initialization file, see Initialization Files, for details. Executes commands and command...

Daslight 4 | SIRS-E

Daslight 4 - the main lighting controller software. Easy View 2 - a real-time 3D visualizer allowing you to see your lights and...