4 ms·
Another trick is to use 32 bit float and just test every single number. 4 billion is something computers can handle, and it will give you pretty much all the e
by RcouF1uZ4gsC 2y ago
Another trick is to use 32 bit float and just test every single number.
4 billion is something computers can handle, and it will give you pretty much all the edge cases of floating point representation.
- owlbite 2y agoThat quickly becomes unfeasible for things that are not single input (and still requires being able to identify a correct result).
- eesmith 2y agoecef_to_lla requires two values, so even if one is willing to take the reduced geospatial resolution of float32, that's still 64-bits of parameter space. if you do need 1 mm accuracy, including in the Pacific Ocean around 180 E/W then neither float32 nor scaled 32-bit ints are enough.
- boscillator 2y agoBut test against what? This only makes sense for the property based testing, but then random sampling should give the same result up to a statistical margin of error (unless there's some specific pathological case). I suppose this is good for extremely critical routines, kind of like the modified condition/decision coverage safe critical flight software has to undergo.
- spenczar5 2y agoIf you have an inverse function, use that to test all round tripa?