9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] circular fonctions: precision?
Date: Sun,  2 Oct 2011 20:28:46 +0200	[thread overview]
Message-ID: <20111002182846.GA20646@polynum.com> (raw)
In-Reply-To: <20111002175227.2D7F1B856@mail.bitblocks.com>

On Sun, Oct 02, 2011 at 10:52:27AM -0700, Bakul Shah wrote:
> On Sun, 02 Oct 2011 18:38:00 +0200 tlaronde@polynum.com  wrote:
> > Hello,
> > 
> > Is there some documentation about the precision of the circular (i.e
> > trigonometric) fonctions, depending on the (plan9) implementation and
> > the hardware?
> 
> Do you mean precision (number of significant bits) or accuracy
> (closeness to true value)? For a double the precision is 52
> bits, for a float 23.

Sorry, I meant accuracy.

> 
> > To my limited knowledge, an OS is integer based, so the floating
> > point support is mainly "user space" and is, despite IEEE754 and due to
> > the interaction between hardware, software, and programmer, really
> > floating, but is there a range given for the association of OS/hardware
> > telling that say sin(r) or asin(s) is accurate, at worst, at some 
> > epsilon near?
> 
> It depends on the algorithm used, not on the OS. The C
> standard leaves accuracy upto the implementation. If you care,
> you can compare the result of a C function with what bc(1)
> computes for the same function (by using a suitably large
> scale).

Here, I mean by "OS" not the kernel, but the whole soft-system, i.e.
here the implementation of libc and the direct use of sin(3) etc.

It seems you've answered my badly formulated question: if I want
to know exactly what I use, I must rely on some defined library
linked against my software that implements directly the fonctions.
(Testing against bc(1) is probably worth for having an idea; but
the problem is that 1) the results depend on the system/implementation;
2) there may be singularities and testing the whole range with a
small granularity is probably not an option.)

I sometimes wonder if the more common 64bits will not someday see
CAD or related software go back to scaled integer arithmetic à la
Intergraph dgn, where 64bits is enough for the range of coordinates
and precision used...

Thanks for the answer.
-- 
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                      http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C



  parent reply	other threads:[~2011-10-02 18:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-02 16:38 tlaronde
2011-10-02 17:52 ` Bakul Shah
2011-10-02 18:06   ` erik quanstrom
2011-10-02 18:40     ` Bakul Shah
2011-10-02 18:44       ` erik quanstrom
2011-10-02 18:59         ` andrew zerger
2011-10-02 19:04         ` tlaronde
2011-10-02 19:14         ` Bakul Shah
2011-10-02 19:18           ` erik quanstrom
2011-10-02 18:44     ` tlaronde
2011-10-02 18:48       ` tlaronde
2011-10-02 18:28   ` tlaronde [this message]
2011-10-02 19:06     ` Bakul Shah
2011-10-03 11:41       ` tlaronde
2011-10-03 14:39         ` Bakul Shah
2011-10-03 14:46           ` erik quanstrom
2011-10-03 15:29             ` Bakul Shah
2011-10-03 15:58               ` Bakul Shah
2011-10-03 16:49           ` tlaronde
2011-10-03 13:03 ` Russ Cox
2011-10-03 14:44   ` Bakul Shah
2011-10-03 14:57     ` Russ Cox
2011-10-03 15:34       ` Bakul Shah
2011-10-03 15:47         ` Russ Cox
2011-10-03 16:53   ` tlaronde

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111002182846.GA20646@polynum.com \
    --to=tlaronde@polynum.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).