You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's merging metrics (e.g. train.loss across commits from the new monorepo layout, and the old one). Relative paths for those metrics are the same indeed, but they belong to different projects.
Not sure how critical it is. E.g. if it's possible to create a situation when it clearly reads and merges file from to co-evolving projects.
In 3ebca, the metrics are only found in the subdirectory, and not in the root results dir, correct?
If that's the case, I think it's expected, and it should be the same in plots after #9898. If each commit has only one metric/plot with that name, they will be merged.
It makes sense in some cases, in some cases it might be creating some weird behavior. I don't know what the right solution is. It was a bit unexpected to see, but I also see that it's a non-trivial task to come with one-fits-all semantics here.
In case of monorepo and subdir, but introducing a subdir we are effectively changing names of the metrics, plots, etc, w/o even moving them. E.g. let's say subdir existed before, but was part of the main repo, and now we want to isolate it - we don't move any files at all, just do extra dvc init --subdir; git commit. So if before metrics were being merged in one way, now because of their name change they will start being merged with some metrics in root directory.
A more practical example. Let's say we have an ensemble of models and all of them have acc + the final acc at the root. If we introduce subdir then acc in it will start getting merged with acc in the root, at least in the previous commits.
Probably the same applies to plots- need to check.
In a monorepo scenario.
We moved everything from the
example-get-started-experiments
repo into asubdir
, and created a new commit in a new branch:Here is the new layout:
If we now run
dvc exp show -A
(insidesubdir
), it outputs:It's merging metrics (e.g.
train.loss
across commits from the new monorepo layout, and the old one). Relative paths for those metrics are the same indeed, but they belong to different projects.Not sure how critical it is. E.g. if it's possible to create a situation when it clearly reads and merges file from to co-evolving projects.
DVC Version
The text was updated successfully, but these errors were encountered: