From: Brian Gough <bjg@network-theory.co.uk>
To: Carlo Ferrigno <ferrigno@pa.iasf.cnr.it>
Cc: gsl-discuss@sources.redhat.com
Subject: Re: convolution
Date: Thu, 16 Oct 2003 09:06:00 -0000 [thread overview]
Message-ID: <16270.24436.696457.173956@debian.local> (raw)
In-Reply-To: <200310151601.11889.ferrigno@pa.iasf.cnr.it>
Carlo Ferrigno writes:
> Hello,
>
> is there any, already made, way to perform the convolution between two
> gsl_vectors in GSL ?
There is no ready made routine, because the best choice of algorithm
is problem-dependent. (e.g. which type of fft to use)
regards
--
Brian Gough
next prev parent reply other threads:[~2003-10-16 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 13:59 convolution Carlo Ferrigno
2003-10-16 9:06 ` Brian Gough [this message]
2003-10-16 9:37 ` convolution Axel Hutt
-- strict thread matches above, loose matches on Subject: below --
2006-06-11 10:05 convolution Jochen Küpper
2006-06-12 17:08 ` convolution Brian Gough
2001-12-19 13:20 Convolution marc chenu
2001-12-19 13:20 ` Convolution 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=16270.24436.696457.173956@debian.local \
--to=bjg@network-theory.co.uk \
--cc=ferrigno@pa.iasf.cnr.it \
--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).