Automating the Creation of Stan Code for TDCMs
- 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.
- All OK13 platforms
- CRAN 30-day downloads, method
- 217−15.2% down on the 30 days before, the worse direction
- 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 29 Oct 2026, 19,585 of the 25,593 current CRAN packages had no dependent package.
- 0none suggest it
- 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%.
- 52%of lines run by tests
- 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.
A collection of functions for automatically creating 'Stan' code for transition diagnostic classification models (TDCMs) as they are defined by Madison and Bradshaw (2018) <DOI:10.1007/s11336-018-9638-5>.
Full description
A collection of functions for automatically creating 'Stan' code for transition diagnostic classification models (TDCMs) as they are defined by Madison and Bradshaw (2018) <DOI:10.1007/s11336-018-9638-5>. This package supports automating the creation of 'Stan' code for TDCMs, fungible TDCMs (i.e., TDCMs with item parameters constrained to be equal across all items), and multi-threaded TDCMs.
- Maintainer
- Jeffrey Hoover
- Licence
- GPL (>= 2)
- Latest release
- 28 Mar 2024
- First release
- 9 May 2022
More details
- Releases
- 3
- Needs compilation
- No
- Needs R
- >= 3.5.0
- RoxygenNote
- 7.2.3
Subjects (1) Method, SubjectsMethod
Subjects and collections
Subjects are the site's own grouping of CRAN packages, found by clustering. Collections are sets of packages that communities declare, such as the tidyverse.
- Subjects
- Subjects are found by clustering the words of current CRAN packages and the packages they use. No one edits them by hand.
- Collections
- Collections are sets that communities declare, through a package that installs the set or an organization on GitHub. The site finds them by rules.
- Who made each
- Subjects are marked Site and collections Community. Subjects, collections and task views are never mixed in one list.
- The day of the data
- Subjects and collections were last worked out on 22 Oct 2026.
Cite
Package
Run in R for the authors' preferred citation:
citation("tdcmStan")Hoover, J., & Thompson, W. J. (2024). tdcmStan: Automating the Creation of Stan Code for TDCMs (Version 3.0.0) [Computer software]. https://doi.org/10.32614/CRAN.package.tdcmStan
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 tdcmStan version 3.0.0 [Data set]. HJJB, LLC. Data release v2026-10-29. https://doi.org/10.5281/zenodo.21843040
About
From data release v2026-10-29, which the citation names so these numbers can be found later.
Health
All 13 check platforms pass.
r-devel-linux-x86_64-debian-clangThe unreleased R on Linux, x86_64, debian-clang
OK
- Version checked
- 3.0.0
- Time taken
- 41 s
r-devel-linux-x86_64-debian-gccThe unreleased R on Linux, x86_64, debian-gcc
OK
- Version checked
- 3.0.0
- Time taken
- 33 s
r-devel-linux-x86_64-fedora-clangThe unreleased R on Linux, x86_64, fedora-clang
OK
- Version checked
- 3.0.0
- Time taken
- 26 s
r-devel-linux-x86_64-fedora-gccThe unreleased R on Linux, x86_64, fedora-gcc
OK
- Version checked
- 3.0.0
- Time taken
- 25 s
r-devel-windows-x86_64The unreleased R on Windows, x86_64
OK
- Version checked
- 3.0.0
- Time taken
- 71 s
r-oldrel-macos-arm64The previous release of R on macOS, arm64
OK
- Version checked
- 3.0.0
r-oldrel-macos-x86_64The previous release of R on macOS, x86_64
OK
- Version checked
- 3.0.0
- Time taken
- 37 s
r-oldrel-windows-x86_64The previous release of R on Windows, x86_64
OK
- Version checked
- 3.0.0
- Time taken
- 65 s
r-patched-linux-x86_64The patched release of R on Linux, x86_64
OK
- Version checked
- 3.0.0
- Time taken
- 36 s
r-release-linux-x86_64The current release of R on Linux, x86_64
OK
- Version checked
- 3.0.0
- Time taken
- 37 s
r-release-macos-arm64The current release of R on macOS, arm64
OK
- Version checked
- 3.0.0
- Time taken
- 13 s
r-release-macos-x86_64The current release of R on macOS, x86_64
OK
- Version checked
- 3.0.0
- Time taken
- 40 s
r-release-windows-x86_64The current release of R on Windows, x86_64
OK
- Version checked
- 3.0.0
- Time taken
- 59 s
- 13 OK
Over time
No change since 4 Aug 2026
As a list (5)
| Changed | Worst status | OK | Notes | Warnings | Errors |
|---|---|---|---|---|---|
| 4 Aug 2026 | OK | 13 | 0 | 0 | 0 |
| 1 Aug 2026 | Note | 12 | 1 | 0 | 0 |
| 9 May 2026 | OK | 13 | 0 | 0 | 0 |
| 8 May 2026 | Warning | 12 | 0 | 1 | 0 |
| 10 Mar 2026 | OK | 14 | 0 | 0 | 0 |
Since March 2026
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
- Total downloads in the last 30 days
- 220−17.9% down on the 30 days before, the worse directionIt is the sum of 3 channels: CRAN, r2u and autoCRAN.
CRAN rank
21,502 of 26,553
CRAN
217 downloads in the last 30 days
- Rank
- 21,502 of 26,553
- Change
- −15.2% down on the 30 days before, the worse direction
It is in the total. Take it out
r2u
1 downloads in the last 30 days
- Rank
- 19,986 of 30,526
- Change
- −80% down on the 30 days before, the worse direction
It is in the total. Take it out
autoCRAN
2 downloads in the last 30 days
- Rank
- 23,041 of 29,233
- Change
- −71.4% down on the 30 days before, the worse direction
It is in the total. Take it out
The total is 220 downloads in the last 30 days. It is the sum of 3 channels: CRAN, r2u and autoCRAN.
Over time
Dependencies
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
- 6
- Public exports
- 6
- Lines of R code
- 1,809
- Median complexity
- 5
Functions (6)
Size and composition
Lines by kind (4,327)
| Kind | Lines | Share |
|---|---|---|
| R code | 1,809 | 42% |
| Tests | 2,386 | 55% |
| Documentation | 132 | 3% |
Lines by language
| Language | Lines | Share |
|---|---|---|
| Stan | 2,340 | 54% |
| R | 1,855 | 43% |
| Rd | 132 | 3% |
Languages are counted from file extensions.
- Files
- 30
- R functions
- 6
Complexity
- Median
- 5
- Mean
- 4.5
- Highest
- 6
- Median lines per function
- 344.5
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
- 6
- Calls
- 4
- Unconnected
- 1
- Groups
- 1
Growth (3 releases)
Release changes
Tests
The tests ran and coverage was measured.
- Lines run by tests
- 52.1%
- Expressions run by tests
- 53.9%
- Test cases
- 3
Coverage by file (5)
Coverage run
- Lines counted
- 1,606
- Lines the tests ran
- 836
- Tests passed
- Yes
- Measured with
- covr 3.6.5 on R 4.6.1
Test suite
- Has tests
- Yes
- Test frameworks
- testthat
- Test cases
- 3
- Lines of tests
- 2,386
- Test lines per line of code
- 1.32
Documentation
- Help pages with examples
- 100%
- Examples run in checks
- 100%
Other documentation
- README
- Yes, 46 words
- Release notes file
- No
- Help pages
- 6
- Lines of documentation
- 132
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.
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.
atlas-aai / tdcmstan on github.com
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Last commit
- 30 Apr 2024
Activity
- Commits
- 129
- Open pull requests
- 0
- Tagged releases
- 1
- Latest tagged release
- v3.0.0, 28 Mar 2024
- In development
- Default branch at 3.0.0.9000, ahead of CRAN 3.0.0 (checked 2026-10-25)
- Issues closed in
- 35 days (median)
- Pull requests closed in
- 0 days (median)
- Pull requests merged
- 100%
- Created
- 5 May 2022
- Licence file reads as
- –
Development practices (13)
| Kind | Found |
|---|---|
| Continuous integration | GitHub Actions, R CMD check workflow The R CMD check workflow runs on Linux, macOS and Windows, and on R-devel |
| Governance and community | Code of conduct, Contributing guide |
| Docs source | README.Rmd, pkgdown |
| Coverage | Coverage reporting (Codecov) |
| Reproducibility and dev environment | data-raw/ |
| CRAN release process | cran-comments.md, revdep/ |
| Lint, format, editor | lintr, Lint workflow, RStudio project |
Method, repository practices Method Beta Each week a scan of the public source repository a package links to looks for the tools a maintainer has set up, and the Repository section lists the findings. Repositories on GitHub and GitLab are scanned.Repository practices
R CMD build reads .Rbuildignore and leaves out files used only in development, such as .github/, .lintr, renv/, a Dockerfile and cran-comments.md, so the released source file holds almost none of them. The repository is the one place these files stay visible.
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 29 Oct 2026, the day the data was read.Packages leaving