public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Rhys Ulerich <rhys.ulerich@gmail.com>
To: Patrick Alken <patrick.alken@colorado.edu>
Cc: gsl-discuss@sourceware.org
Subject: Re: [PATCH] Add Greville abscissae functionality to B-splines
Date: Wed, 17 Jun 2009 22:52:00 -0000	[thread overview]
Message-ID: <4a00655d0906171551j3557799g75fe5bc8e59b0986@mail.gmail.com> (raw)
In-Reply-To: <20090617221222.GA31761@hippogriff.homeunix.org>

Hi Patrick,

I'm fine if you'd like to back out the previous patch until you can
review the two applied together.

The trap I fell into is that, confusingly, the indexing of the
abscissa as it usually appears excludes the very first and very last
knots in GSL's w->knots vector.  Apparently this is a common
convention I didn't know about until I ran into a friend in the hall
today.  Also, the abscissa location should be averaged over degree
(w->km1) knots and not order (w->k) knots.

> I also found a matlab code on it which I used to verify some of your
> test cases, which did look correct.

Odds are good that you can get the new unit tests will also look okay
against that same Matlab code if you (a) throw out the first and last
knot, and (b) use the degree and not the order.

The new patch's documentation includes a reference to a 2005 paper by
Johnson that gives both a definition and an example set of
knots/abscissae for a C3 quartic (Figure 2) if you'd like another
comparison point.

Have a good trip,
Rhys

  reply	other threads:[~2009-06-17 22:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14 17:02 Rhys Ulerich
2009-06-15 10:30 ` Brian Gough
2009-06-15 14:44   ` Rhys Ulerich
2009-06-15 17:38     ` Patrick Alken
2009-06-15 18:14       ` Rhys Ulerich
2009-06-15 18:31         ` Patrick Alken
2009-06-17 21:54           ` Rhys Ulerich
2009-06-17 22:11             ` Patrick Alken
2009-06-17 22:52               ` Rhys Ulerich [this message]
2009-07-05  1:10             ` Patrick Alken

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=4a00655d0906171551j3557799g75fe5bc8e59b0986@mail.gmail.com \
    --to=rhys.ulerich@gmail.com \
    --cc=gsl-discuss@sourceware.org \
    --cc=patrick.alken@colorado.edu \
    /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).