When I compare two experiments in DVC studio the val.loss in the Changes tab is clipped to one decimal, see the first image. The other metrics and the training loss is fine and even the plot of the val.loss shows that the values are there with more precision, see the second image.
second image, because I could not put in the original post
This is an edge case that happens if there are large numbers for that metric (in order to limit the number of digits shown in the column). Can you check if the loss metric somehow includes a commit or experiment that contains an unusually large value? I believe Studio will try to show up to 6 digits, so this means there is likely a value >= 100000 for the loss metric somewhere.
hey,
thanks for the fast response. I have one commit with a loss value of around 19000. But because its a commit and not an experiment I am not sure how to delete/remove it from dvc…
in general is it intended that every commit shows up in dvc exp show even if no experiment was run with this commit? is there a way to filter these commits?
You can hide commits in Studio, but it won’t currently help with the clipping issue unfortunately. The cleanest option is probably to use git rebase to remove that value from that commit.
hey,
thanks for the tip, sadly I have never used git rebase before…
From my understanding I would need to apply the changes of the commit bd581eb to commit ee60fbb correct?
would this then be the correct command git rebase --onto bd581eb ee60fbb ?
thanks in advance
Fabian
Usually, I use git rebase -i to make changes interactively. It may be less scary that way. Take a look at git - How do I modify a specific commit? - Stack Overflow for how it works.
thx that fixed it 
