The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
Implements multitaper spectral analysis using discrete prolate spheroidal sequences (Slepians) and sine tapers. It includes an adaptive weighted multitaper spectral estimate, a coherence estimate, Thomson's Harmonic F-test, and complex demodulation. The Slepians sequences are generated efficiently using a tridiagonal matrix solution, and jackknifed confidence intervals are available for most estimates. This package is an implementation of the method described in D.J. Thomson (1982) "Spectrum estimation and harmonic analysis" <doi:10.1109/PROC.1982.12433>.
Version: | 1.0-17 |
Depends: | R (≥ 3.0), methods |
Suggests: | psd, fftwtools, slp |
Published: | 2023-07-20 |
DOI: | 10.32614/CRAN.package.multitaper |
Author: | Karim Rahim, Wesley S. Burr |
Maintainer: | Karim Rahim <karim.rahim at queensu.ca> |
License: | GPL-2 | GPL-3 [expanded from: GPL (≥ 2)] |
URL: | https://github.com/krahim/multitaper/ |
NeedsCompilation: | yes |
Citation: | multitaper citation info |
In views: | TimeSeries |
CRAN checks: | multitaper results |
Reference manual: | multitaper.pdf |
Package source: | multitaper_1.0-17.tar.gz |
Windows binaries: | r-devel: multitaper_1.0-17.zip, r-release: multitaper_1.0-17.zip, r-oldrel: multitaper_1.0-17.zip |
macOS binaries: | r-release (arm64): multitaper_1.0-17.tgz, r-oldrel (arm64): multitaper_1.0-17.tgz, r-release (x86_64): multitaper_1.0-17.tgz, r-oldrel (x86_64): multitaper_1.0-17.tgz |
Old sources: | multitaper archive |
Reverse depends: | waveslim |
Reverse imports: | astrochron, pdSpecEst |
Reverse suggests: | psd |
Please use the canonical form https://CRAN.R-project.org/package=multitaper to link to this page.
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.