waveclock
1.0-4CRANTime-frequency analysis of cycling cell luminescence data
Archived on 20 Nov 2009
- CRAN's reason
- No reason on record
- Last release
- 1.0-4, 20 Nov 2009
# Needs the pak package.
# install.packages("pak")
pak::pak("cran::waveclock@1.0-4") - CRAN checks, method
Method
Checks and health
CRAN runs every current package through
R CMD checkon a set of machines and publishes a result for each one. The health shown on a package page comes from these results alone.- Problems
- Notes alone never count against a package, but a warning, an error or a failure on any platform is a problem. Open CRAN deadlines are a fact of their own, shown as a clock after the mark, so the mark always says what the checks found.
- Checks only
- Health reflects CRAN's check results and nothing else. Even a package with no tests, no coverage or no recent release can have every platform OK.
- Once a day
- Results are collected once a day from files CRAN publishes. Each platform is one machine set-up, named by its R version, operating system, architecture and compiler, such as r-devel-linux-x86_64-fedora-clang.
- Platforms counted
- The 13 in 3 of 13 is the number of platform rows CRAN published for that package on the day of collection. The set of machines changes over time, so the number is not fixed, and a package missing from a platform counts as neither passing nor failing there.
- Not checkedarchived 20 Nov 2009
- Dependent packages, method
Method
Reverse dependencies
Dependent packages are other packages that list this one under
Depends,ImportsorLinkingToin theirDESCRIPTIONfile. Those fields list the packages a package needs to install, so dependents break if this one is archived or broken.- As declared
- The counts follow the declarations as written, not whether a package uses the other one when it runs.
- Suggests apart
- Packages that list this one only under
Suggestsinstall and run without it, and use it for tests, examples or an optional feature. They are counted as Suggested by, never among the dependents, and a package that also lists it under one of the three fields is a dependent and is not counted again. - Zero
- Zero dependents means no current CRAN package declares a need for this one, though some may suggest it. On 28 Oct 2026, 19,572 of the 25,583 current CRAN packages had no dependent package.
- 0none suggest it
- Advisories, method
Method
Security advisories
Advisories come from the R Consortium advisory database, a community record of security problems in R packages, as OSV publishes it.
- The copy
- The record is read once a day. The data is published under the Apache License 2.0 and is credited on the advisories list.
- Box under the name
- Under the package's name, a box names any advisory that affects the current release, with its fix or that there is none.
- Ranges
- Advisories state ranges, such as from 0.9.12 up to but not including 1.8.8. Each range is checked against every version CRAN has published, using the version rules R itself uses, so a release that came out after the advisory was written is still caught by its range.
- Not the package
- The rating is for the library flaw itself, not for how exposed the R package is, and it is never added up into a figure for the package.
- None known
About
Method, About Method Licence figures come from the Licences
License field of each package's DESCRIPTION file, read the way R itself reads it. No licence file is opened.tools::analyze_license() and R's own licence database, as CRAN's checks read it.| is read, so one string can offer two families.
waveclock is an R function designed to assess the period and amplitude of cycling cell luminescence data. The function reconstructs the modal frequencies from a continuous wavelet decomposition of the luminescence data using the 'crazy climbers' algorithm described in "Practical Time-Frequency ...
Full description
waveclock is an R function designed to assess the period and amplitude of cycling cell luminescence data. The function reconstructs the modal frequencies from a continuous wavelet decomposition of the luminescence data using the 'crazy climbers' algorithm described in "Practical Time-Frequency Analysis: Gabor and Wavelet Transforms with an Implementation in S", by Rene Carmona, Wen L. Hwang and Bruno Torresani, Academic Press, 1998.
- Maintainer
- Tom Price
- Licence
- GPL (>= 2)
- Latest release
- 20 Nov 2009
- First release
- 16 Jun 2008
More details
- Releases
- 6
- Needs R
- >= 2.7.0
- Date
- 2009-11-20
Cite
Package
Run in R for the authors' preferred citation:
citation("waveclock")Price, T. (n.d.). waveclock: Time-frequency analysis of cycling cell luminescence data (Version 1.0-4) [Computer software]. Retrieved October 29, 2026, from https://CRAN.R-project.org/package=waveclock
About
This package has no citation file, so citation() returns this entry built from DESCRIPTION.
R Observatory
For a number measured here: a download total, a coverage figure, an archival date.
Balamuta, J. J. (2026). R Observatory: Metrics for waveclock version 1.0-4 [Data set]. HJJB, LLC. Data release v2026-10-28. https://doi.org/10.5281/zenodo.21843040
About
From data release v2026-10-28, which the citation names so these numbers can be found later.
Health
CRAN checks only the packages on CRAN, and it archived this one on 20 Nov 2009.
Downloads
Method, Downloads Method Download figures count requests logged by each distribution channel. They are not counts of installs or of users, because each channel publishes its own totals and this site reads them.Downloads
All time
- Total downloads over all time
- 4,188It comes from CRAN alone.
The total is 4,188 downloads over all time. It comes from CRAN alone.
Over time
Dependencies
- Needs
- 1
- Dependent packages
- 0
- Suggested by
- 0
Needs (1)
Code
Method, Code Method Code metrics come from reading the released source of each package version. The package is never installed, loaded or run.Code metrics
README, vignettes, a NEWS file and the shares read from its help pages. Files kept only in the repository, such as a pkgdown configuration or CI files, are read by the repository scan instead.
- Functions
- 4
- Public exports
- 2
- Lines of R code
- 621
- Median complexity
- 5
Functions (4)
Size and composition
Lines by kind (868)
| Kind | Lines | Share |
|---|---|---|
| R code | 621 | 72% |
| Documentation | 247 | 28% |
Lines by language
| Language | Lines | Share |
|---|---|---|
| R | 621 | 72% |
| Rd | 247 | 29% |
Languages are counted from file extensions.
- Files
- 11
- R functions
- 4
Complexity
- Median
- 5
- Mean
- 14.75
- Highest
- 48
- Median lines per function
- 74
About complexity
Cyclomatic complexity counts the independent paths through a function: 1 is a straight line, higher is harder to test. R functions only.
Call graph figures
- R functions
- 4
- Calls
- 0
- Unconnected
- 4
- Groups
- 0
Growth (6 releases)
Release changes
Tests
Method, Tests Method Test coverage is measured by downloading each CRAN package's current source file, installing its dependencies, building it and running its tests under covr.Test coverage
No coverage run is on record for this package.
- Lines of tests
- 0
- Exports named in tests
- 0%
- Has tests
- No
- Test frameworks
- No tests in this release
- Test lines per line of code
- 0
Documentation
- Exports documented
- 100%
- Arguments documented
- 63%
- Return value documented
- 0%
- Help pages with examples
- 33.3%
- Examples run in checks
- 100%
Other documentation
- README
- No
- Release notes file
- No
- Help pages
- 3
- Lines of documentation
- 247
Datasets
Method, Datasets Method The datasets inside packages are read from their R objects in datasets
data/ folders when the code is analysed. Each object is described by its class, its shape and its columns, and fingerprinted so the same data can be found in other packages.data() are listed, 76,180 on CRAN and 8,045 on Bioconductor, so the list is not every file in data/.
| Dataset | Size |
|---|---|
| U2OSLuminescence measurements from U2-OS osteosarcoma cells | length 13 |
People
Method, People Method People on the site are the names packages give them in their Author and maintainer identity
DESCRIPTION files: authors from the author list, and the maintainer from the Maintainer field. Spellings of one name become one person only where the rules below allow it, and when in doubt the rules keep people apart.
Maintainer since 1.0-0 (2008)
Repository
Method, figures by host Method Repository signals are the figures read from the source repository a package links to: stars, forks, issues, commits, releases and the time issues take to close. They are read from GitHub, GitLab, Codeberg and Bitbucket.Repository signals
URL and BugReports fields of its DESCRIPTION file. Read-only mirrors, the cran and bioc accounts on GitHub and git.bioconductor.org, are left out.
No repository on record
History
Method, History Method Archived is built from CRAN's archive records, its list of check deadlines and Bioconductor's package records. Every figure is counted to 28 Oct 2026, the day the data was read.Packages leaving
- On CRAN
- Archived
- Release
Archived
| Archived | Back | CRAN's reason | Kind |
|---|---|---|---|
| 20 Nov 2009 | not back | No reason on record | No reason given |