From: "Kevin H. Hobbs" <hobbsk@ohiou.edu>
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: Wed, 02 Jan 2008 13:40:00 -0000 [thread overview]
Message-ID: <1199280754.30472.14.camel@gargon.hooperlab> (raw)
In-Reply-To: <4772D239.9070206@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
On Wed, 2007-12-26 at 23:14 +0100, Frank Reininghaus wrote:
> Hi,
>
> I've found some problems with adaptive step size control which can
> lead to an infinite loop under special circumstances.
<snip>
> In testcase1.c, the function rhs (t) yields 1 for t>=1.0 and 0
> otherwise.
I may have encountered this when using step functions for current
injection into neuron models. I'd like to be included in the replies.
My workaround was to adjust the step size so that the step ends at the
time of the current injection change. I had to tell the model to change
the current through the comm pointer so that the end point of the step
before the change and the start point of the step after the change have
the same current level as the rest of the step. This workaround is
probably too complex for beginners.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-01-02 13:40 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 [this message]
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
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=1199280754.30472.14.camel@gargon.hooperlab \
--to=hobbsk@ohiou.edu \
--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).