David de la Iglesia Castro

> Essentially, user may want to store any kind of artefact over epochs to compare them between each other (few more examples - images with bounding boxes produced by NN,...

Created a separate issue for images: https://github.com/iterative/dvclive/issues/150

> The initial example of logging arrays is pretty much already supported in dvc though as plots if I'm understanding correctly, so that is one type for which support could...

> Personally, out of the options above, I see #2 as the most useful. I think that using a JSON format would be better than TSV (could be probably used...

Apart from the above discussion, we are currently assuming that logging a 1D array means that the user wants multi-step `linear` plots. However, another common use case would be to...

> Not sure I understand what the data is in your example or how it's different from the scalar logging already being done. Is it about logging multiple epochs in...

> JSON or YAML are definitely more versatile than `*sv` types. If we want to support logging whole arrays (which makes sense to me if we, for example, generate ROC...

> Does all of this get saved under {dvclive_dir}/{step}? We may want some additional subdir for both this and images, like {dvclive_dir}/artifacts/{step} or something to separate it better from the...

> To me, this is a generalization of #189, where json outputs are saved at each step for plots. One difference is that, so far in this issue, we have...

> @dberenbaum I guess this is more for the integrations, where sometimes you have predefined names (like keras). Or am I wrong here @daavoo? The use case would be definitely...