public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Brian Gough <bjg@network-theory.co.uk>
To: "Kostrun, Marijan" <Marijan.Kostrun@sylvania.com>
Cc: gsl-discuss@sources.redhat.com
Subject: Re: [Bug-gsl] Feature request for ODE integrators
Date: Mon, 31 Jul 2006 07:25:00 -0000	[thread overview]
Message-ID: <877j1we7rc.wl%bjg@network-theory.co.uk> (raw)
In-Reply-To: <1153488406.8749.40.camel@rdfa0117578.sylvania.com>

At Fri, 21 Jul 2006 09:26:46 -0400,
Kostrun, Marijan wrote:
> I inspected the codes and have implemented them for my project rlabplus
> at http://rlabplus.sourceforge.net, however, the solution is not quite
> satisfactory. 
> Let me explain why. Imagine you have ask for integration on the interval
> [t1,t2] but the NaN appears somewhere inside the interval. When gsl
> integrator hits NaN it does not integrate any further, an error flag is
> rised (from 0 to 2) and t1 is reset to its original value. I would like
> t1 to contain the last successful time and the array pointer the
> solution to the ODE at that time. This feature is implemented in other
> integrators, e.g., code ODE.F by Shampine and Gordon from netlib.
> If this is too complicated to implement, I will have to write the code
> to use some sort of bisection on the interval [t1,t2] to find the time
> up to which the integration can be performed.

Hello, 

I think the only information that gsl_odeiv_evolve_apply can return
that it currently doesn't is the step size h that triggered the NaN. I
will modify it to do that.  All the other information should be
available as it returns to the user after any successful single step.

-- 
best regards,

Brian Gough

           reply	other threads:[~2006-07-31  7:25 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1153488406.8749.40.camel@rdfa0117578.sylvania.com>]

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=877j1we7rc.wl%bjg@network-theory.co.uk \
    --to=bjg@network-theory.co.uk \
    --cc=Marijan.Kostrun@sylvania.com \
    --cc=gsl-discuss@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).