Re:High Performance Computing: Are We Just Getting Wrong Ans...
by triska on Sunday September 23, 2018 @08:07PM
(#18054099)
This is indeed a key point in John Gustafson's arguments: With floats, even though there are specialized flags and values that let you detect certain problematic situations, these flags are often not readily accessible in programming languages, and hence these issues tend to go unnoticed.
Re:High Performance Computing: Are We Just Getting Wrong Ans...
by jcranmer on Sunday September 23, 2018 @09:30PM
(#18054402)
> these flags are often not readily accessible in programming languages
Unless you use C, C++, or Fortran. Which accounts for most numerical algorithms code. Yes, most people aren't aware of them, but not being aware of all the functions in the standard library isn't the same as them not being present there.
Re:High Performance Computing: Are We Just Getting Wrong Ans...
by jcranmer on Sunday September 23, 2018 @09:24PM
(#18054383)
Just because the error interval is [-inf, +inf] doesn't mean the actual error is [-inf, +inf]. There are other techniques (such as Monte Carlo simulation) that can give much narrower error bounds for the actual computation.
Re:High Performance Computing: Are We Just Getting Wrong Ans...
by Something1234 on Sunday September 23, 2018 @11:28PM
(#18054821)
How do I calculate measurement and error bounds for my plots when I'm using floating point? I honestly have on idea what to google.
With ordinary floating point, all too often people don't realize their results are nonsense. Adding measurement and computation error bounds to their graphs is illuminating.