All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Tweed <orthochronous@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: John Tapsell <johnflux@gmail.com>,
	Ealdwulf Wuffinga <ealdwulf@googlemail.com>,
	Christian Couder <chriscool@tuxfamily.org>,
	Git List <git@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: Generalised bisection
Date: Thu, 12 Mar 2009 18:02:37 +0000	[thread overview]
Message-ID: <d9c1caea0903121102y5452603fua0e7a1b82e121b01@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0903121154560.10279@pacific.mpi-cbg.de>

On Thu, Mar 12, 2009 at 10:55 AM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> On Thu, 12 Mar 2009, John Tapsell wrote:
> > 2009/3/11 Ealdwulf Wuffinga <ealdwulf@googlemail.com>:
> > > What I use is the multiprecision floating point number class. doubles
> > > don't seem to be long enough.
> >
> > Hmm, really really?  Sometimes this sort of thing can be fixed by just
> > readjusting the formulas.  What formulas are you using that require more
> > precision than doubles?
>
> Maybe you could post the formulae instead of forcing people to deduct them
> from the source code?

I haven't even looked at the source code so a description of the
mathematical algorithm would help, but I'll just point out that
underflow (in the case of working with probabilities) and overflow
(when working with their negated logarithms) is inherent in most
multi-step Bayesian algorithms. The only solution is to rescale things
as you go so that things stay in a "computable" range. (You're almost
never interested in absolute probabilities anyway but rather relative
probabilities or, in extreme cases, just the biggest probability, so
rescaling isn't losing any useful information.)

cheers,
dave tweed

  reply	other threads:[~2009-03-12 18:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-09  1:40 Generalised bisection Ealdwulf Wuffinga
2009-03-10  7:08 ` Christian Couder
2009-03-11  8:59   ` Ealdwulf Wuffinga
2009-03-11  9:35     ` John Tapsell
2009-03-11 12:05       ` Johannes Schindelin
2009-03-11 12:08         ` John Tapsell
2009-03-11 13:04           ` Johannes Schindelin
2009-03-11 13:24             ` John Tapsell
2009-03-11 22:14               ` Ealdwulf Wuffinga
2009-03-11 22:15       ` Ealdwulf Wuffinga
2009-03-12  6:45         ` John Tapsell
2009-03-12 10:55           ` Johannes Schindelin
2009-03-12 18:02             ` Steven Tweed [this message]
2009-03-13 10:00               ` Ealdwulf Wuffinga
2009-03-13 12:49               ` Ealdwulf Wuffinga
2009-03-13 15:19                 ` Steven Tweed
2009-03-15 19:16                   ` Ealdwulf Wuffinga
2009-03-16 10:29                     ` Steven Tweed
2009-03-16 10:37                       ` John Tapsell
2009-03-16 22:47                         ` Ealdwulf Wuffinga
2009-03-16 22:08                       ` Ealdwulf Wuffinga
2009-03-13  9:58           ` Ealdwulf Wuffinga
2009-03-13 10:55             ` Johannes Schindelin
2009-03-13 12:42               ` John Tapsell
2009-03-13 13:56                 ` Johannes Schindelin

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=d9c1caea0903121102y5452603fua0e7a1b82e121b01@mail.gmail.com \
    --to=orthochronous@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=chriscool@tuxfamily.org \
    --cc=ealdwulf@googlemail.com \
    --cc=git@vger.kernel.org \
    --cc=johnflux@gmail.com \
    --cc=mingo@elte.hu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.