RTCA
‹Bioconductor 3.23
- Bioconductor 3.2329 Apr 2026, current
- Bioconductor 3.2230 Oct 2025
- Bioconductor 3.2116 Apr 2025
- Bioconductor 3.2030 Oct 2024
- Bioconductor 3.191 May 2024
- Bioconductor 3.1825 Oct 2023
- Bioconductor 3.1726 Apr 2023
- Bioconductor 3.162 Nov 2022
- Bioconductor 3.1527 Apr 2022
- Bioconductor 3.1427 Oct 2021
- Bioconductor 3.1320 May 2021
- Bioconductor 3.1228 Oct 2020
- Bioconductor 3.1128 Apr 2020
- Bioconductor 3.1030 Oct 2019
- Bioconductor 3.93 May 2019
- Bioconductor 3.831 Oct 2018
- Bioconductor 3.71 May 2018
- Bioconductor 3.631 Oct 2017
- Bioconductor 3.525 Apr 2017
- Bioconductor 3.418 Oct 2016
- Bioconductor 3.34 May 2016
- Bioconductor 3.214 Oct 2015
- Bioconductor 3.117 Apr 2015
- Bioconductor 3.014 Oct 2014
- Bioconductor 2.1414 Apr 2014
- Bioconductor 2.1315 Oct 2013
- Bioconductor 2.124 Apr 2013
- Bioconductor 2.113 Oct 2012
- Bioconductor 2.102 Apr 2012
- Bioconductor 2.91 Nov 2011
- Bioconductor 2.814 Apr 2011
- Bioconductor 2.718 Oct 2010
- Bioconductor 2.623 Apr 2010
- Bioconductor 2.528 Oct 2009
Open-source toolkit to analyse data from xCELLigence System (RTCA)
- Released
- 29 Apr 2026with R 4.6
- 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 publishedfor Bioconductor
- Test coverage, method
Method
Test coverage
Test coverage is measured by downloading each CRAN package's current source file, installing its dependencies, building it and running its tests under covr.
- Almost half of CRAN has no tests to run
- Only CRAN packages are measured. Many have no percentage, most often because the package has no tests, and that blank is a recorded outcome, not missing data.
- NOT_CRAN
- Tests run with NOT_CRAN=true, so tests that skip themselves on CRAN run here, and the figure can differ from what CRAN's own checks see.
- Current version only
- Only the current version is measured, and a new version on CRAN is measured again. Older rows are kept but never filled in later. This is one package's run.
- Never 0%
- On a package page three states stay apart: measured, no tests, and not measured. Neither of the last two is ever shown as 0%.
- –not measured for Bioconductor
- Public exports, method
Method
Code metrics
Code metrics come from reading the released source of each package version. The package is never installed, loaded or run.
- One row a version
- Each analysed version gives one row of figures. The Code, Tests and Documentation sections, the pages of older releases and Release changes all read from those rows.
- CRAN
- CRAN versions are read from the github.com/cran mirror, which holds one commit for each released source file, and every version tag is analysed. Nothing is built, installed or run.
- Release, not repository
- Documentation describes what the analysed release holds: a
README, vignettes, aNEWSfile 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. - Zero
- Zero means the analysis looked and found none.
- 19none added or removed
Record made 3 Nov 2026, 03:29 UTC from data release v2026-11-01, merged 22:46 UTC. Project DOI 10.5281/zenodo.21843040.
https:/
This page reports what R Observatory measured for this release. It is not a validation, and it does not say whether the package is fit for your intended use.
Compare
Compared with Bioconductor 3.22, released 30 Oct 2025.
- Time between
- 181 daysno release in between
- Advisories
- None publishedfor Bioconductor
- Exports
- No changebetween the two
- Files changed
- 1+1 −1 lines
Values that differ (2)
| Measure | Section | Bioconductor 3.22 | Bioconductor 3.23 |
|---|---|---|---|
| Package version | Release | 1.62.0 | 1.64.0 |
| R version | Release | 4.5 | 4.6 |
Most changed files (1 of 1)
| File | Lines added | Lines deleted |
|---|---|---|
DESCRIPTION | 1 | 1 |
Release
- Package version
- 1.64.0
- Bioconductor release
- 29 Apr 2026
- R version
- 4.6
- Status
- Current release
- Previous
- 3.22, 30 Oct 2025
- First Bioconductor release
- 2.5, 28 Oct 2009
- Last Bioconductor release
- 3.23, 29 Apr 2026
- License
- LGPL-3, OSI approved
- Maintainer
- Jitao David Zhang
- Authors
- Jitao David Zhang
Advisories
- This release
- None published for Bioconductor
Checks
Method, Checks Method CRAN runs every current package through Checks and health
R CMD check on a set of machines and publishes a result for each one. The health shown on a package page comes from these results alone.
- Results
- Not collected for Bioconductor
Code
- Lines of R code
- 1,231
- Public exports
- 19
- Internal functions
- 12
- Mean complexity
- 5.9the most is 100
Lines by kind (2,649)
| Kind | Lines | Share |
|---|---|---|
| R code | 1,231 | 46% |
| Tests | 44 | 2% |
| Documentation | 994 | 38% |
| Guides | 380 | 14% |
Tests
- Test cases
- 0
- Lines of tests
- 44
- Exports named in tests
- 47.4%
- Tests
- Yes, R scripts, 1 script file
- Test lines per line of code
- 0.04
- Coverage
- Not measured for Bioconductor packages
- Help pages with running examples
- 17 of 17
Documentation
- Exports documented
- 100%
- Arguments documented
- 99.5%
- Return value documented
- 100%
- Vignettes
- 2
- Help pages
- 17
- Exports with examples
- 100%
- NEWS
- No
- Citation file
- No
- Website
- Yes
Dependencies
Method, Dependencies Method Dependent packages are other packages that list this one under Reverse dependencies
Depends, Imports or LinkingTo in their DESCRIPTION file. Those fields list the packages a package needs to install, so dependents break if this one is archived or broken.Suggests install 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.
- Direct dependencies
- 6
- Install tree
- Not collected for Bioconductor
Today
- Bioconductor downloads, last 12 months
- 16,091, rank #1,337 among software packages
- Bioconductor downloads, last month
- 3,316
- Reverse dependencies
- 0 direct, 0 Bioconductor, 0 CRAN
- Suggested by
- 0
Sources
| Part | From | As of |
|---|---|---|
| Release dates | Bioconductor release dates | 1 Nov 2026 |
| Advisories | osv-advisories 1.0.0, R version 4.6.2 (2026-10-29) | 1 Nov 2026 |
| Checks | Not collected for Bioconductor | |
| Tests, documentation, code | Bioconductor metrics, rpkg-analyzer 0.5.0 | 29 Sep 2026 |
| Coverage | Not measured for Bioconductor packages | |
| Downloads | Bioconductor download statistics | 1 Oct 2026 |
| Reverse dependencies | CRAN and Bioconductor package metadata | 1 Nov 2026 |
Daily data releases are kept on GitHub, so the data behind this record can be fetched again from v2026-11-01 (merged 22:46 UTC). Values not kept for a release say so and are never filled in from another release.