A Simple Way to Specify Symmetric, Block Diagonal Matrices
- 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
- 2,560+0.99% up on the 30 days before, the better 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 26 Oct 2026, 19,530 of the 25,531 current CRAN packages had no dependent package.
- 82 more 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%.
- Not measuredthe run failed
- 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.
Provides a simple mechanism to specify a symmetric block diagonal matrices (often used for covariance matrices). This is based on the domain specific language implemented in 'nlmixr2' but expanded to create matrices in R generally instead of specifying parts of matrices to estimate.
Full description
Provides a simple mechanism to specify a symmetric block diagonal matrices (often used for covariance matrices). This is based on the domain specific language implemented in 'nlmixr2' but expanded to create matrices in R generally instead of specifying parts of matrices to estimate. It has expanded to include some matrix manipulation functions that are generally useful for 'rxode2' and 'nlmixr2'.
- Maintainer
- Matthew L. Fidler
- Licence
- GPL (>= 2)
- Latest release
- 11 Sep 2026
- First release
- 14 May 2019
More details
- Releases
- 14
- Needs compilation
- Yes
- Needs R
- >= 3.4.0
- Config/roxygen2/version
- 8.1.0
- Config/testthat/edition
- 3
- Language
- en-US
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("lotri")Fidler, M. L., Denney, B., & Vargas Sepulveda, M. (2026). lotri: A Simple Way to Specify Symmetric, Block Diagonal Matrices (Version 1.0.5) [Computer software]. https://doi.org/10.32614/CRAN.package.lotri
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 lotri version 1.0.5 [Data set]. HJJB, LLC. Data release v2026-10-26. https://doi.org/10.5281/zenodo.21843040
About
From data release v2026-10-26, 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
- 1.0.5
- Time taken
- 121 s
r-devel-linux-x86_64-debian-gccThe unreleased R on Linux, x86_64, debian-gcc
OK
- Version checked
- 1.0.5
- Time taken
- 88 s
r-devel-linux-x86_64-fedora-clangThe unreleased R on Linux, x86_64, fedora-clang
OK
- Version checked
- 1.0.5
- Time taken
- 80 s
r-devel-linux-x86_64-fedora-gccThe unreleased R on Linux, x86_64, fedora-gcc
OK
- Version checked
- 1.0.5
- Time taken
- 87 s
r-devel-windows-x86_64The unreleased R on Windows, x86_64
OK
- Version checked
- 1.0.5
- Time taken
- 273 s
r-oldrel-macos-arm64The previous release of R on macOS, arm64
OK
- Version checked
- 1.0.5
- Time taken
- 33 s
r-oldrel-macos-x86_64The previous release of R on macOS, x86_64
OK
- Version checked
- 1.0.5
- Time taken
- 130 s
r-oldrel-windows-x86_64The previous release of R on Windows, x86_64
OK
- Version checked
- 1.0.5
- Time taken
- 184 s
r-patched-linux-x86_64The patched release of R on Linux, x86_64
OK
- Version checked
- 1.0.5
- Time taken
- 108 s
r-release-linux-x86_64The current release of R on Linux, x86_64
OK
- Version checked
- 1.0.5
- Time taken
- 106 s
r-release-macos-arm64The current release of R on macOS, arm64
OK
- Version checked
- 1.0.5
- Time taken
- 39 s
r-release-macos-x86_64The current release of R on macOS, x86_64
OK
- Version checked
- 1.0.5
- Time taken
- 131 s
r-release-windows-x86_64The current release of R on Windows, x86_64
OK
- Version checked
- 1.0.5
- Time taken
- 155 s
- 13 OK
Over time
No change since 17 Sep 2026
As a list (3)
| Changed | Worst status | OK | Notes | Warnings | Errors |
|---|---|---|---|---|---|
| 17 Sep 2026 | OK | 13 | 0 | 0 | 0 |
| 16 Jul 2026 | Note | 11 | 2 | 0 | 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
- 5,166+21.9% up on the 30 days before, the better directionIt is the sum of 5 channels: CRAN, r2u, autoCRAN, conda-forge and c2d4u.
CRAN rank
2,261 of 26,529
CRAN
2,560 downloads in the last 30 days
- Rank
- 2,261 of 26,529
- Change
- +0.99% up on the 30 days before, the better direction
It is in the total. Take it out
r2u
226 downloads in the last 30 days
- Rank
- 1,617 of 30,526
- Change
- +96.5% up on the 30 days before, the better direction
It is in the total. Take it out
autoCRAN
6 downloads in the last 30 days
- Rank
- 7,678 of 29,130
- Change
- −66.7% down on the 30 days before, the worse direction
It is in the total. Take it out
conda-forge
2,369 downloads in the last 30 days
- Rank
- 642 of 3,828
- Change
- +51.8% up on the 30 days before, the better direction
It is in the total. Take it out
c2d4u, no longer updated
5 downloads in the last 30 days
- Rank
- 3,123 of 7,575
- Change
- −50% down on the 30 days before, the worse direction
It is in the total. Take it out
The total is 5,166 downloads in the last 30 days. It is the sum of 5 channels: CRAN, r2u, autoCRAN, conda-forge and c2d4u.
Over time
Dependencies
- Needs
- 7
- Dependent packages
- 8
- Suggested by
- 2
Needs (7)
- armadillo4r
- checkmate
- cpp4r
- crayon
- methods
- stats
- utils
- Installing it adds
- 5 packages, 1.5 MB of source
- Of those, need compilation
- 2
Dependent packages (8)
| Package | Title | Downloads in 30 days |
|---|---|---|
| rxode2 | Facilities for Simulating from ODE-Based Models | 3,706 |
| nlmixr2est | Nonlinear Mixed Effects Models in Population PK/PD, Estimation Routines | 2,351 |
| nlmixr2extra | Nonlinear Mixed Effects Models in Population PK/PD, Extra Support Functions | 1,750 |
| nlmixr2 | Nonlinear Mixed Effects Models in Population PK/PD | 1,602 |
| nonmem2rx | Converts 'NONMEM' Models to 'rxode2' | 1,030 |
| babelmixr2 | Use 'nlmixr2' to Interact with Open Source and Commercial Software | 815 |
| monolix2rx | Converts 'Monolix' Models to 'rxode2' | 461 |
| nlmixr2scm | Stepwise Covariate Modeling for 'nlmixr2' Models | 413 |
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
- 187
- Public exports
- 17
- Lines of R code
- 6,310
- Median complexity
- 4
Functions (187)
Size and composition
Lines by kind (18,543)
| Kind | Lines | Share |
|---|---|---|
| R code | 6,310 | 34% |
| Tests | 8,388 | 45% |
| Documentation | 923 | 5% |
| Guides | 1,059 | 6% |
| Compiled code | 1,863 | 10% |
Lines by language
| Language | Lines | Share |
|---|---|---|
| R | 14,564 | 79% |
| C | 1,510 | 8% |
| Vignettes | 1,059 | 6% |
| Rd | 923 | 5% |
| C++ | 353 | 2% |
| Markdown | 134 | 0.7% |
Languages are counted from file extensions.
- Files
- 107
- R functions
- 137
- Compiled functions
- 50
- Object systems
- S3: 11 methods
Complexity
- Median
- 4
- Mean
- 7.54
- Highest
- 66
- Median lines per function
- 14
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
- 137
- Calls
- 208
- Unconnected
- 13
- Groups
- 2
Growth (14 releases)
Release changes
Tests
The package could not be built for the coverage run.
- Test cases
- 293
- Lines of tests
- 8,388
- Exports named in tests
- 94.1%
Test suite
- Has tests
- Yes
- Test frameworks
- testthat
- Test cases
- 293
- Snapshot tests
- 4
- Test lines per line of code
- 1.33
Documentation
- Exports documented
- 100%
- Arguments documented
- 98.3%
- Return value documented
- 92.9%
- Help pages with examples
- 85.7%
- Examples run in checks
- 100%
Other documentation
- README
- Yes, 1,342 words
- Release notes file
- Yes
- Help pages
- 14
- Lines of documentation
- 923
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 and Codeberg.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.
- Stars
- 7
- Forks
- 3
- Open issues
- 5
- Last commit
- 11 Sep 2026
Activity
- Commits
- 490
- Open pull requests
- 4
- Tagged releases
- 9
- Latest tagged release
- v1.0.5, 11 Sep 2026
- Issues closed in
- 2 days (median)
- Pull requests closed in
- 0 days (median)
- Pull requests merged
- 92%
- Created
- 1 Dec 2021
- Licence file reads as
- –
Development practices (10)
| 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 |
| Docs source | README.Rmd, pkgdown GitHub Pages site last deployed 2026-09-11 The repository has a site deploy workflow pkgdown site last built 2026-09-11 |
| Coverage | Coverage reporting (Codecov) |
| CRAN release process | cran-comments.md, CRAN-SUBMISSION |
| Lint, format, editor | lintr |
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.
AI tools
Method, AI tools Method Beta What is found in a repository is not a measure of the code.AI tool findings
Tools
| Tool | First seen | Found | Commits by it | Commits crediting it |
|---|---|---|---|---|
| Claude Code | 2 Apr 2026 | Seen in the repositoryCLAUDE.mdNamed in .Rbuildignore.claudeCLAUDE.mdPull request it wrote: opened by a project member | 5 at least | |
| GitHub Copilot | 3 Apr 2026 | 1 | ||
| Antigravity | 13 May 2026 | Named in .Rbuildignore.antigravity |
- Seen in the repository
- Named in .Rbuildignore
- Pull request
Models
| Model | Commits | First commit | Last commit | Credit lines of |
|---|---|---|---|---|
| Claude Opus 4.8 | 2 | 15 Jun 2026 | 15 Jun 2026 | Claude Code |
| Claude Sonnet 4.6 | 3 | 2 Apr 2026 | 2 Apr 2026 | Claude Code |
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 26 Oct 2026, the day the data was read.Packages leaving
| Version | Released | R | Events |
|---|---|---|---|
| 1.0.5 current | 11 Sep 2026 | 4.6.1 | Fix due 11 Sep 2026 The checks were fixed and the deadline was lifted. |
| 1.0.4 | 14 May 2026 | 4.6.0 | |
| 1.0.3 | 11 Mar 2026 | 4.5.3 | |
| 1.0.2 | 29 Aug 2025 | 4.5.1 | |
| 1.0.1 | 18 Jul 2025 | 4.5.1 | |
| 1.0.0 | 18 Sep 2024 | 4.4.1 | |
| 0.4.3 | 20 Mar 2023 | 4.2.3 | |
| 0.4.2 | 18 Jun 2022 | 4.2.0 |
Earlier versions (6)
Release notes (1.0.5)
New features
- A block can now be repeated with
same(), which is NONMEM's$OMEGA BLOCK(n) SAME:
```r
lotri({
iov.cl1 + iov.v1 ~ c(0.1,
0.01, 0.2)
iov.cl2 + iov.v2 ~ same()
iov.cl3 + iov.v3 ~ same()
})
```
This is one estimated 2x2 covariance shared by three blocks, which is
how inter-occasion variability is parameterized when every occasion
draws its own random effects from one shared covariance -- and it is
what lets those random effects be *correlated*.
same() repeats the immediately preceding block under new names and
takes no arguments. A further same() repeats that same original
block rather than the copy, the way NONMEM chains SAME. It works
with a condition (iov.cl2 + iov.v2 ~ same() | occ), it inherits the
fixed flags of the block it repeats, and it composes with the
cnd(same = n) nesting property that lotriSep() uses.
- The `condition` column can now carry a `:same:` suffix. Rather than adding a column to the data frame from
as.data.frame(), a repeated block records the element it mirrors in the existingconditioncolumn, naming it: ``<baseCondition>:same:<masterEta> # diagonal row <baseCondition>:same:<masterEta1>:<masterEta2> # covariance row`The master is named rather than indexed becauseneta1/neta2are renumbered whenever parameters are added, dropped or reordered. A copy keeps its master'sestandfix, so a consumer that does not understand the suffix still sees a numerically correct matrix -- just with more free parameters than the model really has. Four helpers are exported for reading that column, and code that comparesconditiondirectly (condition == "id"`) should move to them, since such a test misclassifies a repeated block: lotriBaseCondition()strips the suffix,lotriIsSame()says whether a row mirrors another,lotriSameMap()maps each eta to the eta it mirrors,lotriSameBreak()drops the linkage for a block that has been structurally changed.
same() round trips through as.data.frame(), as.lotri() and
as.expression(), and the linkage is carried across lotriMat().
A repetition that no longer describes a real mirror -- because the
blocks it was built from were reordered or dropped, or because it
carries something same() cannot express -- is written out with its
explicit values instead. That loses the annotation, never the
numbers.
A prior cannot be put on a repeated block -- it is not a parameter of
its own, so the prior belongs on the block it mirrors. Without this
a model could carry two different priors on what is one estimated
parameter.
same() cannot be combined with a cov function, nor with
rcm=TRUE on a matrix the permutation would actually reorder; both
would move a repeated block away from the block it repeats, and are
refused rather than silently producing a matrix whose repetition is
no longer true. A same() matrix that is already block diagonal is
left alone, since there rcm is a no-op, which keeps rxode2's
ini({}) -- which always passes rcm=TRUE -- working.
- Prior distributions can now be specified in a
lotri({})(and thereforeini({})) block withprior(name) ~ dist(...), ie:
```r
lotri({
tka <- 0.45
tcl <- c(0, 1, 10)
eta.cl + eta.v ~ c(0.1,
0.01, 0.2)
prior(tka) ~ dnorm(0, 10)
prior(tcl) ~ dlnorm(1, 0.5)
prior(eta.cl, eta.v) ~ lkjCorr(2)
})
```
Because the statement names its target, prior lines may be given
anywhere in the block. Priors may be put on population estimates,
on individual etas, and on whole covariance blocks (with the
matrix-valued distributions like lkjCorr() and invWishart()).
Every distribution has three accepted spellings: the R name where R