public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Tuomo Keskitalo <Tuomo.Keskitalo@iki.fi>
To: Rhys Ulerich <rhys.ulerich@gmail.com>
Cc: Brian Gough <bjg@gnu.org>, gsl-discuss@sourceware.org
Subject: Re: Implementing hybrid explicit/implicit ODE stepper
Date: Thu, 04 Jun 2009 18:52:00 -0000	[thread overview]
Message-ID: <4A28180A.2030103@iki.fi> (raw)
In-Reply-To: <4a00655d0906041040y135755cdlc877ba570c4308da@mail.gmail.com>

On 06/04/2009 08:40 PM, Rhys Ulerich wrote:

> This integrator tends to get used in DNS of Navier-Stokes since the
> memory savings become significant for very large fields.

Ok, now I understand a bit more. I don't think the current GSL 
ode-initval is directly suitable for that kind of specialized problem. 
The framework does not support separation of f(u) into two components. 
You would first have to make changes to gsl_odeiv_system to provide 
that, and then modify all the rest accordingly. Might be doable, I don't 
know.

Would your application benefit from step size control, or evolution 
functionality similar to those in ode-initval? If yes, then you might 
try to start from ode-initval and modify it. Otherwise I suggest you 
look for how others have designed these kinds of solvers and then create 
a new framework suitable for this kind of a problem.

Of course, if you end up implementing only that one stepper, you can use 
code snippets from ode-initval for it.

Regards,
Tuomo

-- 
Tuomo.Keskitalo@iki.fi
http://iki.fi/tuomo.keskitalo

      reply	other threads:[~2009-06-04 18:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-03 14:32 Rhys Ulerich
2009-06-04 13:38 ` Brian Gough
2009-06-04 17:20   ` Tuomo Keskitalo
2009-06-04 17:40     ` Rhys Ulerich
2009-06-04 18:52       ` Tuomo Keskitalo [this message]

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=4A28180A.2030103@iki.fi \
    --to=tuomo.keskitalo@iki.fi \
    --cc=bjg@gnu.org \
    --cc=gsl-discuss@sourceware.org \
    --cc=rhys.ulerich@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 read-only IMAP folder(s) and NNTP newsgroup(s).