[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Help-gsl] GSL1.15: interp.c: 150: ERROR: interpolation error

From: David Zaslavsky
Subject: Re: [Help-gsl] GSL1.15: interp.c: 150: ERROR: interpolation error
Date: Sun, 05 May 2013 00:42:55 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130410 Thunderbird/17.0.5

I have a library that performs 2D interpolation on Github:
It's not ready to be fully released, primarily because there is little
to no documentation or test cases, but I have used the bilinear and
bicubic interpolation routines in a real-world application or two and
they seem to give accurate results. So if you need 2D interpolation, you
could clone the repository and take your chances with it.

:) David

On 05/03/2013 08:40 AM, jeremy theler wrote:
> I like it, but the function name should not say only "extrap", but should 
> reflect the fact that it performs both interpolation and extrapolation.
> Also, a flag can be set indicating if the operation was interpolation or 
> extrapolation.
> BTW, as we are on the subject: any plans for multidimensional interpolation?
> --
> jeremy
> On Thursday 02 May 2013 23:54:08 Rhys Ulerich wrote:
>>> I also miss the good old days when extrapolation was automatically
>>> computed using the chosen interpolation scheme. Can this behavior be
>>> added as a flag or as a new function?
>> I could see a gsl_extrap_eval() and friends that were identical in
>> functionality but that did not perform this x < xmin || x > xmax
>> check.  gsl_interp_eval() could then be implemented as this check
>> followed by calling gsl_extrap_eval().  People wanting the old
>> behavior could call the new function which would then self-document
>> that extrapolation is a possibility.
>> Thoughts?
>> - Rhys

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]