Improve Error Message: catch invalid initializers earlier? #1290
Replies: 1 comment 1 reply
-
The benevolent dictator orders his subjects to rely on deep stack traces and spurious type assertions rather than readable type errors. If you want good error messages go to the Rust community instead! ;) On a more serious note: |
Beta Was this translation helpful? Give feedback.
-
Consider the following snippet, adapted from the flax examples, which has a minor bug ( can you spot it? )
If we look at the stack trace, it is pretty long and ends at:
Reading the stack trace, it sound as if the problem is related to the lax dot product, but the actual problem is that
kernel_init
should have been set tonn.initializers.lecun_normal()
with()
at the end ( in contrast with the zeros initializer ??).Maybe such a problem could be caught earlier in the
self.param(...)
call, which would help the user pinpoint the problem?Beta Was this translation helpful? Give feedback.
All reactions