From: Rhys Ulerich <rhys.ulerich@gmail.com>
To: Brian Gough <bjg@gnu.org>
Cc: gsl-discuss@sourceware.org
Subject: Re: Where a generalized Richardson extrapolation routine would fit in GSL?
Date: Tue, 15 Dec 2009 17:31:00 -0000 [thread overview]
Message-ID: <4a00655d0912150931q4b34fd24p94594ed08857254f@mail.gmail.com> (raw)
In-Reply-To: <87d42ggnsv.wl%bjg@network-theory.co.uk>
Thanks for looking through the patch Brian.
> One question: it looks like this
> extrapolates a vector quantity. For simplicity, would it make sense
> to work with scalars as in the gsl_sum routines -- since presumably
> that is the common case -- or is there some application where vector
> extrapolation is unavoidable? (could each component can be
> extrapolated independently?)
You're right that each component could be extrapolated independently.
I wrote it using vectors because doing so allows using BLAS calls for
the linear algebra and speeds up many component use cases. I'd prefer
to keep the code vector-capable under the covers under the theory that
people extrapolating only a scalar at a time aren't all that worried
about speed.
My vector use case arose from testing convergence orders for
timesteppers (non-GSL, but similar in interface) that manipulate
vectors of state variables.
If you'd like, I can submit an additional patch that 1) Renames
gsl_extrap_richardson to something like gsl_extrap_richardson_vector,
2) Provides a scalar-only gsl_extrap_richardson that wraps up scalars
and calls the gsl_extrap_richardson_vector routines under the covers,
and 3) Exercises the scalar-only wrappers fully in the test suite.
That way if someone later does need a faster scalar-only version, he
or she can change over the underlying implementation without fear of
regression.
- Rhys
next prev parent reply other threads:[~2009-12-15 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4a00655d0908201247g7d7bd9a1t466f4a66f08df4@mail.gmail.com>
[not found] ` <4a00655d0911291536t5a11752fp27ab9c274148f822@mail.gmail.com>
2009-11-29 23:39 ` Rhys Ulerich
2009-12-01 14:08 ` Brian Gough
2009-12-13 23:49 ` Rhys Ulerich
2009-12-15 17:17 ` Brian Gough
2009-12-15 17:31 ` Rhys Ulerich [this message]
2009-12-16 4:25 ` Rhys Ulerich
2009-12-16 17:21 ` Brian Gough
2009-12-17 0:44 ` Rhys Ulerich
2009-12-17 22:50 ` Brian Gough
2009-12-18 17:21 ` Brian Gough
2010-02-06 15:26 ` Rhys Ulerich
2010-02-09 8:47 ` 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=4a00655d0912150931q4b34fd24p94594ed08857254f@mail.gmail.com \
--to=rhys.ulerich@gmail.com \
--cc=bjg@gnu.org \
--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).