From: Steven Tweed <orthochronous@gmail.com>
To: Ealdwulf Wuffinga <ealdwulf@googlemail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
John Tapsell <johnflux@gmail.com>,
Christian Couder <chriscool@tuxfamily.org>,
Git List <git@vger.kernel.org>
Subject: Re: Generalised bisection
Date: Fri, 13 Mar 2009 15:19:38 +0000 [thread overview]
Message-ID: <d9c1caea0903130819u770686b1w867f074ffef8fabf@mail.gmail.com> (raw)
In-Reply-To: <efe2b6d70903130549m63ae9bdeg1cd3f24a43b3e66f@mail.gmail.com>
On Fri, Mar 13, 2009 at 12:49 PM, Ealdwulf Wuffinga
<ealdwulf@googlemail.com> wrote:
> On Thu, Mar 12, 2009 at 6:02 PM, Steven Tweed <orthochronous@gmail.com> wrote:
>> 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.)
>
> Are you sure you aren't thinking of when you are using fixed point? I
> was under the impression
> that Bayesian algorithms usually worked okay in floating point.
Underflow when using probabilities and lack of precision (rather than
overflow) when using negated logarithms are well known problems in the
kind of probabilistic object tracking, inference in graphical networks
and object identification processes I work with (in computer vision).
I there may well be other areas of Bayesian decision theory where this
doesn't happen, and indeed a _very_ quick scan through your document
suggests that you're adding to tallying information on each timestep
and recalcuating the entire model from those tallys, which is one of
the few cases where you can't really do rescaling. I'll try and have a
more detailled read over the weekend.
> One issue in BBChop which should be easy to fix, is that I use a dumb
> way of calculating Beta functions. These
> are ratios of factorials, so the subexpressions get stupidly big very
> quickly. But I don't think that is the only problem.
Yes, "Numerical Recipes" seems to suggest that computing with
log-factorials and exponentiating works reasonably, although I've
never tried it and NR does occasionally get things completely wrong...
next prev parent reply other threads:[~2009-03-13 15:26 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
2009-03-13 10:00 ` Ealdwulf Wuffinga
2009-03-13 12:49 ` Ealdwulf Wuffinga
2009-03-13 15:19 ` Steven Tweed [this message]
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=d9c1caea0903130819u770686b1w867f074ffef8fabf@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 \
/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).