From: Brian Gough <bjg@network-theory.co.uk>
To: Jose Miguel Buenaposada Biencinto <jmbuena@dia.fi.upm.es>
Cc: "gsl-discuss@sources.redhat.com" <gsl-discuss@sources.redhat.com>
Subject: Re: Discrete cosine transform ...
Date: Wed, 19 Dec 2001 13:20:00 -0000 [thread overview]
Message-ID: <15338.41209.650181.755446@debian> (raw)
In-Reply-To: <3BEA5B3B.DA4DE753@dia.fi.upm.es>
Jose Miguel Buenaposada Biencinto writes:
> I don't know yet if I'm going to need it but anyway, Is there an
> implementation of the discrete cosine transform in gsl?
There are no cosine transforms, if anyone wants to volunteer to add
them that would be useful.
It's possible to do cosine transforms with the existing real fft
routines of course, using the trick of extending the dataset by 2x or
4x with the appropriate periodicity.
> Any other free library with discrete cosine transformation
> implementation?
FFTPACK for general-N, if you use f2c. For radix-2 there are several
routines on netlib I think.
Brian
prev parent reply other threads:[~2001-12-19 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 13:20 Jose Miguel Buenaposada Biencinto
2001-12-19 13:20 ` Brian Gough [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=15338.41209.650181.755446@debian \
--to=bjg@network-theory.co.uk \
--cc=gsl-discuss@sources.redhat.com \
--cc=jmbuena@dia.fi.upm.es \
/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).