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
We are now fixing the torch.load() by specifying the device. However, running dvc repro on a CPU vs. GPU system would produce different artifacts. Should we also modify the code of morphoclass training to make sure that it's consistently written as CPU?
Basically I am talking about this:
But I guess it's not trivial (maybe we need to iterate through each element of the dict and convert it?) because there's no equivalent of torch.load's map_location=device for torch.save.
We are now fixing the
torch.load()
by specifying thedevice
. However, runningdvc repro
on a CPU vs. GPU system would produce different artifacts. Should we also modify the code ofmorphoclass training
to make sure that it's consistently written as CPU?Basically I am talking about this:
morphoclass/src/morphoclass/training/training_log.py
Lines 177 to 179 in 8fca841
But I guess it's not trivial (maybe we need to iterate through each element of the
dict
and convert it?) because there's no equivalent oftorch.load
'smap_location=device
fortorch.save
.Originally posted by @FrancescoCasalegno in #15 (comment)
The text was updated successfully, but these errors were encountered: