public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Brian Gough <bjg@gnu.org>
To: Rhys Ulerich <rhys.ulerich@gmail.com>
Cc: gsl-discuss@sourceware.org
Subject: Re: Where a generalized Richardson extrapolation routine would fit in 	GSL?
Date: Fri, 18 Dec 2009 17:21:00 -0000	[thread overview]
Message-ID: <87ljh0nqp4.wl%bjg@network-theory.co.uk> (raw)
In-Reply-To: <87zl5hnrkh.wl%bjg@network-theory.co.uk>

At Thu, 17 Dec 2009 22:50:22 +0000,
Brian Gough wrote:
> > There's just enough to the argument processing and general normtable
> > handling that it's easier to get good test coverage if there's one
> > implementation that does the whole enchilada and then everything else
> > sits as convenience wrappers.  That prevents changes to one
> > convenience function from accidentally changing the interface's
> > semantics (especially for the 'k' handling).
> > 
> > All that said, I'm happy to make the interface conform.  Would you be
> > willing to take draft public API in gsl_extrap.h (inline below) and
> > change the functions and their signatures to resemble what you'd like?
> 
> I will send that once I've looked at it a bit more.

I think the best interface would be the analog of the existing levin
sum routines:

int gsl_sum_levin_u_accel (const double *array,
                           const size_t n,
                           gsl_sum_levin_u_workspace * w,
                           double *sum_accel, double *abserr);

e.g.

int gsl_extrap_richardson (const double *array,
                           const size_t n,
                           const double t,
                           const size_t k
                           gsl_extrap_richardson_workspace * w,
                           double *result, double *abserr);

It would be useful to have both a result and abserr, to take into
account cancellation error.

  reply	other threads:[~2009-12-18 17:21 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
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 [this message]
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=87ljh0nqp4.wl%bjg@network-theory.co.uk \
    --to=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).