-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logging non-tensor scalar with result breaks subsequent epoch aggregation #3276
Comments
@williamFalcon is it still there? @s-rog mind check if it is still on master? or better add test for such case... |
I'll take a look again when I get a chance, haven't probed much due to the refactors... Are they mostly done? |
@Borda the bug is still here, the following template tests for this issue as well as #3278 For this problem the easiest fix would be to force type to tensors. Though that's probably just a bandaid solution, thoughts? Test template for reference
|
I looked into it a bit and This is probably not intended behavior? |
@edenlightning this is not related to metrics. @s-rog I guess a simple type check that converts scalars to scalars tensor should do the trick? If so, could you open a PR with this fix? |
fixed by #3855 |
@Borda I don't think the issue was fixed completely, this is on rc5 (using self.log) |
@s-rog mind add a test for this case? |
william beat me to it :] |
🐛 Bug
Logging non-tensor scalar with result breaks subsequent epoch/tbptt aggregation
(on both 0.9 and master)
To Reproduce
To Fix
Expected behavior
In
log()
of result objects, value should accept non tensor values asvalue: Any
and not cause issues with other metrics to be loggedAdditional context
log()
can be changed to only accept tensors, or have a built-in conversion, will update as I investigate furtherThe text was updated successfully, but these errors were encountered: