Re:Inventor Claims to Have Solved Floating Point Error Problem
by kbenson on Thursday January 18, 2018 @12:47PM
(#16179339)
It depends on how you interpret "floating point error". If by that you mean the error the error inherent in the representation, it actually increases that through loss of precision, as you note. If you interpret it as "problems caused by lack of precision in floating point" (i.e. the patriot missile problem references in the article is a "floating point error"), then the tracking of precision will allow you to easily know when you've hit an error threshold that is unacceptable, allowing you to avoid those problems.
Re:Inventor Claims to Have Solved Floating Point Error Problem
by enervate on Thursday January 18, 2018 @12:46PM
(#16179323)
how is this better than checking if its within some value by some epsilon manually?
Re:Inventor Claims to Have Solved Floating Point Error Problem
by jovial_cavalier on Thursday January 18, 2018 @01:05PM
(#16179584)
> If an operation exceeds this limit, an insufficient significant bits signal "sNaN(isb)" would be raised.
What about for binary repeating decimals like 0.3? Wouldn't it always raise that signal?
Re:Inventor Claims to Have Solved Floating Point Error Problem
by oh_sigh on Thursday January 18, 2018 @01:41PM
(#16179973)
Presumably if you specify that you want more units of precision than are available, then yes. But if you say you only want 1 significant digit, then it can store it.
Re:Inventor Claims to Have Solved Floating Point Error Problem
by _bxg1 on Thursday January 18, 2018 @12:13PM
(#16178838)
Yeah. It seems like just a clever mitigation technique, which could prove useful in the fields he mentioned (military, industrial, etc.), but it's far from the wholesale solution he claims.
Not only does this method not reduce floating point error, it reduces the precision that you have for any given number of bits.
Unfortunately I can't find any of the figures referenced in the patent to help me understand the novelty of this patent.