From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 109d8a,c7637cfdf68e766 X-Google-Attributes: gid109d8a,public X-Google-Thread: 103376,c7637cfdf68e766 X-Google-Attributes: gid103376,public X-Google-Thread: f43e6,c7637cfdf68e766 X-Google-Attributes: gidf43e6,public X-Google-Thread: 107079,c7637cfdf68e766 X-Google-Attributes: gid107079,public X-Google-Thread: f8362,c7637cfdf68e766 X-Google-Attributes: gidf8362,public From: Email_To...Hans.Olsson@dna.lth.se (Hans Olsson) Subject: Re: floating point comparison Date: 1997/08/19 Message-ID: <5tc2q1$a78$1@news.lth.se>#1/1 X-Deja-AN: 265235935 Distribution: inet References: <33E61497.33E2@pseserv3.fw.hac.com> <5t5976$rle$1@ccioffe.ioffe.rssi.ru> Organization: Lund Institute of Technology, Sweden Newsgroups: comp.lang.ada,sci.math.num-analysis,comp.software-eng,comp.theory,sci.math Date: 1997-08-19T00:00:00+00:00 List-Id: In article , Robert Dewar wrote: >Andrew says > ><< Strongly disagree. There ARE roundoff errors even in the IEEE 754 >arithemtic model. Moreover, the standard clearly specifies rounding models.>> > >You completely miss the point I am making. > >There are no *errors*, the discrepancies between IEEE arithmetic and >real arithmetic are not errors, they are simply differences that come from >two different arithmetic models. > >When we have integer arithmetic and we divide 10 by 3 to get 3, we do >not say this is an error. The result is different from the mathematical >value of 10.0/3.0, but there is no error here, just a different arithmetic >model. > >I know perfectly well that the phrase "rounding error" is well established, >but my point is that calling it an error leads people into the niave trap >of thinking of floating-point arithmetic as being real arithmetic. > >In fact I received quite a few email messages, from some quite interesting >people :-) saying that they agreed that it was a pity that the term >rounding error had ever got into the literature, but of course >it is much too entrnched to get rid of. > >But your repsonse tends to make me think that you are indeed fallling >into the trap of thinking of these xdiscepancies as errors. It's a mistake! No, it's a way of seeing things. By seeing computer arithmetic as real arithmetic combined with rounding errors obeying some simple rules, some algorithms can easily be analyzed. That model of arithmetic is not appropiate for all purposes, but it's in general appropiate for the numerical analysis I'm interested in. IEEE makes the rounding predictable, which can help in some cases, and in _those_cases_ the term rounding error can be misleading. Note that calling a well-defined and predictable discrepancy for error instead of the result of different arithmetic/formula/model is very common in numerical analysis, because it often gives a simple insight. In some cases the errors are further analyzed, but are still called errors. Consider discretizations of ODE/DAE/PDE. One could make an equally good case that the error of a Runge-Kutta method is not an error, but the time-discretization is a completely different problem and should be analyzed as such. Seeing the Runge-Kutta discretization as a new problem is appropiate in some cases, but I'm still happy with the term "global error". BTW: Does there even exist error at all in your view of numerical analysis? (Excluding programming errors). If so, can you give any examples? -- // Homepage http://www.dna.lth.se/home/Hans_Olsson/ // Email To..Hans.Olsson@dna.lth.se [Please no junk e-mail]