Paweł Redzyński

I see that I answered some of the questions under #150 Let's keep the discussion here? I think this issue heavily relies on iterative/dvc#5980 - and we might need to...

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 each...

Agree, we could possibly extend logging arrays to `tsv` too, but it would make them a bit unreadable. I have something like this in mind: ``` step a 0 {val1}...

I like that idea! @dberenbaum what do you think?

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

@dberenbaum I would leave visible the most important parameters (eg init path) and put rest into kwargs and provide more info in docs/doscstrings for the method.

I am all for that, not sure what users might prefer.

Yes, we could add option for turning off automatic checkpoint creation and add manual method for `MetricLogger` class.

Related to #91

related to https://github.com/iterative/dvc/discussions/5980