From: Gerard Jungman <jungman@lanl.gov>
To: gsl-discuss@sourceware.org
Subject: Re: error estimates
Date: Fri, 25 Mar 2016 21:37:00 -0000 [thread overview]
Message-ID: <56F5AF8A.5010204@lanl.gov> (raw)
In-Reply-To: <56F5AC89.6050708@lanl.gov>
Sorry, I accidentally hit the send button and
the message was cut off. Oi.
Anyway, that's basically all I had to say,
at least for now. There are obviously some
very difficult questions about how to
organize the code, factor things properly,
and create directed and useful tests.
In my dreams, I would like to see a code base
that not only burps out function values on
request but also makes itself useful in
other ways. Often clients want arrays of values,
for sequences of parameters, such as 'ell' for
Legendre functions or 'nu' for Bessel functions
Such arrays are always computed using some
iterative procedure, which is essentially
the same procedure as used to compute
single values. The library already has
some "_array" functions that do some of these.
But the best possible thing is to expose the
actual recursion to the client, so that they
can manipulate it and get what they want.
This would also simplify the design of the
underlying library code, which could reuse
the same facilities.
There are similar design questions about computing
zeros of functions. Almost always needed in sets
of many, and also closely related to other problems
of interest to the client.
Maybe one day, all this stuff could be made better.
--
G. Jungman
prev parent reply other threads:[~2016-03-25 21:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56F42FED.8060500@colorado.edu>
2016-03-24 18:22 ` GSL K0/K1 Patrick Alken
2016-03-25 20:03 ` Gerard Jungman
2016-03-25 21:18 ` Patrick Alken
2016-03-26 5:43 ` Pavel Holoborodko
2016-03-25 22:20 ` Brian Gladman
2016-03-25 21:24 ` error estimates (was: GSL K0/K1) Gerard Jungman
2016-03-25 21:37 ` Gerard Jungman [this message]
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=56F5AF8A.5010204@lanl.gov \
--to=jungman@lanl.gov \
--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).