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
Right now if I modify a module like nn.Normalize, and want to reload this in iTorch, I get an error saying it's already defined (if I have required 'nn' already).
My current workaround is something like this at the beginning of the file.
local Normalize, parent
if nn.Normalize == nil then
Normalize, parent = torch.class('nn.Normalize', 'nn.Module')
else
Normalize = nn.Normalize
parent = nn.Module
end
This is fine, except that every time I want to push to nn I'd have to revert this back to the original code. So is there any safety issues with not defaulting torch.class to return the already defined class?
The text was updated successfully, but these errors were encountered:
Right now if I modify a module like nn.Normalize, and want to reload this in iTorch, I get an error saying it's already defined (if I have required 'nn' already).
My current workaround is something like this at the beginning of the file.
This is fine, except that every time I want to push to nn I'd have to revert this back to the original code. So is there any safety issues with not defaulting
torch.class
to return the already defined class?The text was updated successfully, but these errors were encountered: