Dave Berenbaum
Dave Berenbaum
Makes sense. The reason I raised the question is because `dvclive.init()` already has several arguments, and it's easy to keep adding more. How can dvclive functionality continue to be extended...
Sounds good. I don't have any objection to this idea, just something to keep in mind.
Could support both, but maybe that goes against the "canonical workflow."
Looking at the docs, this would do a lot to simplify the API.
> Could support both, but maybe that goes against the "canonical workflow." Also could deprecate by keeping but not documenting the step methods.
@casperdcl Why do you want to use `next_step()` without `log()`? I don't see a problem doing so, but I'm confused how it's useful. Edit: To clarify, I meant that your...
We probably need to decouple `log()` from setting the step to resolve this issue. @casperdcl I moved the optimization to #238. Both are good points that are largely due to...
Actually, I think we just need to call `make_summary()` always during `set_step()` (ignoring #238).
Related to https://github.com/iterative/dvclive/issues/91#issuecomment-1035015144, I think the most useful integration here would be making it dead simple to send full reports (similar to the html today) through supported channels. For example,...
> For metrics is very feasible. However, the images / rendered plots would be kind of tricky because most channels don't have support to directly send images. We could rely...