dvclive
dvclive copied to clipboard
iterative
📈 Log and track ML metrics, parameters, models with Git and/or DVC
I think we should keep the path in envvar in an absolute form in `DVCLIVE_PATH`. Otherwise, the user's script could change the working directory similar to following: ```suggestion (tmp_dir /...
After https://github.com/iterative/dvc.org/pull/3411, the easiest way to track plots in `dvc.yaml` is: ``` plots: - dvclive ``` However, this will track `dvclive/report.html`, which is generally not desired. Some options to handle...
Now that dvclive is decoupled from dvc, it should be pretty trivial to log data in formats expected by other ML tracking tools like mlflow. It would be great to...
```python import dvclive live = dvclive.Live(resume=True) while (epoch := live.get_step()) < 10: print(epoch) live.log("epoch", epoch) # need to log at least one thing for `next_step` to work live.next_step() ``` -...
Values from previous steps are kept in the following steps. Take the following example: ``` import dvclive live = dvclive.Live() while (epoch := live.get_step()) < 10: live.log("epoch", epoch) if not...
Similar to how Ray provides integration for other loggers within [Ray Tune](https://docs.ray.io/en/latest/tune/index.html) it would be good if DVC Live could have its own integration. Concretely, in its documentation for integration...
Seems odd to do this. If there are multiple things to log per iteration, you dump multiple times? - Seems better to dump only on `next_step()` - Could also make...
> It seems odd to pass Live(report="html") in no-step scenarios and have that kwarg do nothing. Not sure if it should be part of this PR, but currently, I can...
Currently scalar values have timestamps associated with each step that is written to the csv file. It would be nice to be able to disable this for cases where the...
Currently, dvclive without dvc produces just a tsv output tracking metrics progress. This doesn't seem like enough to make it worthwhile for users. There are at least a few drawbacks...