home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!wupost!gumby!destroyer!news.iastate.edu!iscsvax.uni.edu!kraai4712
- From: kraai4712@iscsvax.uni.edu
- Newsgroups: sci.math
- Subject: Re: Rounding Rules
- Message-ID: <1993Jan4.142226.9639@iscsvax.uni.edu>
- Date: 4 Jan 93 14:22:26 -0600
- References: <1992Dec20.003018.14325@sol.ctr.columbia.edu> <1992Dec23.140148.21009@hubcap.clemson.edu>
- Organization: University of Northern Iowa
- Lines: 34
-
- In article <1992Dec23.140148.21009@hubcap.clemson.edu>, steve@hubcap.clemson.edu ("Steve" Stevenson) writes:
- > In article <1992Dec20.003018.14325@sol.ctr.columbia.edu> shaw@toadflax.UCDavis.EDU (Rob Shaw) writes:
- >>What is the rationale behind the following rounding rule?
- >>
- >>when dealing with 5's followed by all zero's, check the
- >>next digit to the left. If it's even, round down; odd,
- >>round up.
- >>
- >>For example both 1.13500 and 1.14500 are 1.14 to 3 places.
- >>What is the advantage of having the interval closed at both
- >>ends around even digits, and open at both ends around odds?
- >>
- >
- > The problem with many of the "rounding rules" is that they are biased.
- > In the IEEE round of rules, an attempt is made to make rounding as unbiased
- > as possible. Round to even is specified as the rule of choice, since it
- > avoids many of the problems of "round to infinity" or "round towards zero".
-
- My personal favorite rounding rule is to round anything that has {0,1,2,3,4} in
- the "rounding place" "down" and anything that has {5,6,7,8,9} "up". So as in
- the previous example, 1.13500 would be rounded to 1.14 and 1.14500 would be
- rounded to 1.15.
-
- To this my teachers always gasped that this method was biased, and no amount of
- pursuasion using the above-mentioned sets could pursuade them.
-
- I have come to believe that the people who thought this was biased believed
- that anything that had a zero digit in the place to be rounded couldn't be
- rounded or didn't need to be rounded or some other mental block.
-
- Isn't it be less computationally intensive to round this way instead of looking
- at the _previous_ digit?
-
- --jim
-