-
Couldn't load subscription status.
- Fork 1.3k
Closed
Labels
feature requestRequesting a new featureRequesting a new featurep3-nice-to-haveIt should be done this or next sprintIt should be done this or next sprint
Description
I think being able to define a list of metric type + xpath for a single output file will come in VERY handy. An additional "metric name" property would also help a lot when you are actually looking back at your metrics and trying to decide what to do about them.
As an example of why this should come in handy, check out the following repo:
https://dagshub.com/Guy/uri_nlp_ner_workshop/src/175bbd99d7dcc833049429d04334e7afe5763340
The training stage has a bunch of metric outputs, and I'm left with one of two choices:
- Dump them all in one big json (or other) file, and treat it as one big raw metric. That means no good visualization.
- Dump each one in its own json file, as I did in the linked repo. This allows visualization but is very cumbersome, not to mention it makes the DAG blow up and requires the
dvc runcommand to be very long and tightly coupled to the training code.
efiop, PavelKovalets, dmpetrov and achary
Metadata
Metadata
Assignees
Labels
feature requestRequesting a new featureRequesting a new featurep3-nice-to-haveIt should be done this or next sprintIt should be done this or next sprint