From: Kenneth Geisshirt <kenneth@geisshirt.dk>
To: "gsl-discuss@sources.redhat.com" <gsl-discuss@sources.redhat.com>
Subject: Re: gsl_cspline_init bug?
Date: Wed, 06 Nov 2002 07:36:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0211061052560.688-100000@lithium> (raw)
In-Reply-To: <20021105204213.H10500-200000@exigence.rootnode.com>
On Tue, 5 Nov 2002, R. Sean Bowman wrote:
> gsl: view_source.c:28: ERROR: vector length n must be positive integer
> Default GSL error handler invoked.
> Aborted
I can reproduce the error message. But if I set PTS to 10 (as the example
in the manual), the problem disappears.
> Isn't this a problem? Shouldn't csplines need more than two points to do
> interpolation?
Yes, and maybe we should validate the input parameters :-).
Kneth
--
Kenneth Geisshirt, M.Sc., Ph.D. http://kenneth.geisshirt.dk
Grøndals Parkvej 2A, 3. sal kenneth@geisshirt.dk
DK-2720 Vanløse +45 38 87 78 38
next prev parent reply other threads:[~2002-11-06 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 23:11 R. Sean Bowman
2002-11-06 7:36 ` Kenneth Geisshirt [this message]
2002-11-06 16:05 ` Gerard Jungman
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=Pine.LNX.4.44.0211061052560.688-100000@lithium \
--to=kenneth@geisshirt.dk \
--cc=gsl-discuss@sources.redhat.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).