721
Floating-point arithmetic
(lemmy.ml)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 08 Feb 2024
721 points (99.3% liked)
Programmer Humor
32124 readers
1299 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
Took me 2 hours to find out why the final output of a neural network was a bunch of NaN. This is always very annoying but I can't really complain, it make sense. Just sucks.
I guess you can always just add an
assert not data.isna().any()in strategic locationsThat could be a nice way. Sadly it was in a C++ code base (using tensorflow). Therefore no such nice things (would be slow too). I skill-issued myself thinking a struct would be 0 -initialized but
MyStruct input;would not whileMyStruct input {};will (that was the fix). Long story.I too have forgotten to memset my structs in c++ tensorflow after prototyping in python.
If you use the GNU libc the
feenableexceptfunction, which you can use to enable certain floating point exceptions, could be useful to catch unexpected/unwanted NaNsOof. C++ really is a harsh mistress.
Oof. This makes me appreciate the abstractions in Go. It's a small thing but initializing structs with zero values by default is nice.