lodi 0.9.1 to 0.9.2
CRANRecord of 0.9.1Record of 0.9.2Both records side by side
- 0.9.1 and 0.9.2
- other releases
- daily mean, week by week
No release lies between 0.9.1 and 0.9.2.
- Time between
- 163 daysno release between
- 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 knownfor either release
- Exports, method
- No changebetween the two
- Dependencies
- 1 change1 added
- Licence
- SameGPL-3
- Maintainer
- SameAlexander Rix
Downloads while newest
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
| Release | Days newest | CRAN downloads | Daily mean |
|---|---|---|---|
| 0.9.2 7 Feb 2020 to 7 May 2026, then archived | 2,282 | 13,015 | 6 |
| 0.9.1 28 Aug 2019 to 6 Feb 2020 | 163 | 1,680 | 10 |
Daily mean while newest, 0.9.2 −44.7% down since 0.9.1
Counted on the CRAN mirror from each release's day to the day before the next release. Other channels repackage on their own schedules, so they are not split by release.
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.
- added
| Package | Field | 0.9.1 | 0.9.2 | |
|---|---|---|---|---|
| added | testthat | Suggests | – | any version |
Side by side
| Measure | 0.9.1 | 0.9.2 | Change |
|---|---|---|---|
| Imports | 2 packages | 2 packages | |
| Suggests | 2 packages | 3 packages | +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.
| Measure | 0.9.1 | 0.9.2 | Change |
|---|---|---|---|
| Lines of R code | 460 | 489 | +29 up |
| Files | 19 | 21 | +2 up |
| Mean complexity | 8.5 | 9.5 | +1.0 up |
| Highest complexity | 17 | 21 | +4 up |
| Download size | 18 KB | 19 KB | +1 KB up |
| Source, unpacked | 56 KB | 60 KB | +4 KB up |
3 other figures of the code are the same in both.
Side by side
| Measure | 0.9.1 | 0.9.2 | Change |
|---|---|---|---|
| Lines of R code | 460 | 489 | +29 |
| Lines of compiled code | 0 | 0 | |
| Files | 19 | 21 | +2 |
| Public exports | 4 | 4 | |
| Internal functions | 0 | 0 | |
| Mean complexity | 8.5 | 9.5 | +1.0 |
| Highest complexity | 17 | 21 | +4 |
| Download size | 18 KB | 19 KB | +1 KB |
| Source, unpacked | 56 KB | 60 KB | +4 KB |
| Analysed with | rpkg-analyzer 0.5.2 | rpkg-analyzer 0.5.2 |
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
| Measure | 0.9.1 | 0.9.2 | Change |
|---|---|---|---|
| Test cases | 0 | 1 | +1 up |
| Lines of tests | 0 | 46 | +46 up |
| Test lines per line of code | 0.00 | 0.09 | +0.09 up |
| Exports named in tests | 0.0% | 25.0% | +25.0 points up |
Side by side
| Measure | 0.9.1 | 0.9.2 | Change |
|---|---|---|---|
| Lines run by tests | Not measured | Not measured | |
| Test cases | 0 | 1 | +1 |
| Lines of tests | 0 | 46 | +46 |
| Test lines per line of code | 0.00 | 0.09 | +0.09 |
| Exports named in tests | 0.0% | 25.0% | +25.0 points |
Files changed
- Files changed
- 12in 0.9.2
- Lines added
- 477
- Lines deleted
- 372
Most changed files (12 of 12)
| File | Lines added | Lines deleted |
|---|---|---|
R/clmi.R | 256 | 240 |
R/cca-r2.R | 61 | 48 |
README.md | 54 | 31 |
tests/testthat/test_clmi.R | 42 | 0 |
inst/doc/lodi.html | 14 | 20 |
MD5 | 11 | 9 |
inst/doc/lodi.R | 7 | 7 |
NEWS.md | 12 | 1 |
DESCRIPTION | 6 | 6 |
man/lod_root2.Rd | 6 | 6 |
man/clmi.Rd | 4 | 4 |
tests/testthat.R | 4 | 0 |
Each release is counted against the release before it, so a line changed twice counts twice.
Release notes
From the NEWS file of 0.9.2. Only the section for the newest release on record is kept.
- Added badges to README.Rmd / README.md to show the CRAN version of lodi, Github version of lodi, and a Travis-CI badge showing whether or not lodi tests are passing. If the Github version and CRAN versions differ, the badges appear as different colors.
- Added some unit tests to be run when updating the package / before CRAN submission.
- Added check to ensure exposure data that is below the
lodis coded asNA. Users might input an already log transformed exposure in clmi, while not transforming thelodvariable. If the transformation is logarithmic, this will catch it - Changed the optimization algorithm uses in the MLE procedure from
L-BFGS-BtoBFGSwith reparameterized variance (ieexp(var)) to ensure non-negativity instead of box constraints. UsingL-BFGS-Bcould cause non-finite values of the objective function due to large gradients when evaluating the initial value of the function. - Fixed a subtle bug when calling lodi inside of a function when using a custom exposure function. lodi was internally using the parent frame to enclose the transformation, which is the lodi package namespace, instead of the caller's frame.
Unchanged and not compared
Exports, licence, maintainer, the people named and the documentation figures are the same in both releases. No advisory is known for either release.
CRAN archived lodi on 8 May 2026, so 0.9.2 was its last release and the newest until the day before.
Checks, the install tree, dependents and the repository describe the package as it is now, so they are on the package page.
Documentation side by side
| Measure | 0.9.1 | 0.9.2 | Change |
|---|---|---|---|
| Exports documented | 100.0% | 100.0% | |
| Arguments documented | 100.0% | 100.0% | |
| Return value documented | 0.0% | 0.0% | |
| Lines of documentation | 216 | 216 | |
| Lines of guides | 108 | 108 |