public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Brian Gough <bjg@network-theory.co.uk>
To: Frank Reininghaus <frank78ac@googlemail.com>
Cc: gsl-discuss@sourceware.org
Subject: Re: Bug report and fix for adaptive step size control in ODE solving
Date: Thu, 03 Jan 2008 15:54:00 -0000	[thread overview]
Message-ID: <87ejcync3o.wl%bjg@network-theory.co.uk> (raw)
In-Reply-To: <4772D239.9070206@googlemail.com>

At Wed, 26 Dec 2007 23:14:17 +0100,
Frank Reininghaus wrote:
> I've found some problems with adaptive step size control which can
> lead to an infinite loop under special circumstances. I've attached
> three test case programs where the rhs of the ODE to be solved is a
> step function. All programs lead to infinite loops either in the the
> loop in my code (which should be equivalent to the loop in the example 
> program
> in the documentation) or in gsl_odeiv_evolve_apply () (in the file
> ode-initval/evolve.c) for different reasons.

Thanks for the bug report. This is really useful.
I am adding the examples to the test suite right now.
Then I'll see what the best solution is.

-- 
Brian Gough

  parent reply	other threads:[~2008-01-03 15:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-26 22:14 Frank Reininghaus
2008-01-02 13:40 ` Kevin H. Hobbs
2008-01-02 14:18 ` Jochen Küpper
2008-01-02 18:51   ` Frank Reininghaus
2008-01-03  9:01     ` Unwanted compiler optimization (was: Bug report and fix for adaptive step size control in ODE solving) Jochen Küpper
2008-01-04 10:44       ` Brian Gough
2008-01-03  5:15 ` Bug report and fix for adaptive step size control in ODE solving Michael Stauffer
2008-01-03 15:54 ` Brian Gough [this message]
2008-01-04  9:46 ` Brian Gough

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=87ejcync3o.wl%bjg@network-theory.co.uk \
    --to=bjg@network-theory.co.uk \
    --cc=frank78ac@googlemail.com \
    --cc=gsl-discuss@sourceware.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).