BMS 0.3.0 to 0.3.5
CRANRecord of 0.3.0Record of 0.3.5Both records side by side
- 0.3.0 and 0.3.5
- between them
- other releases
- daily mean, in 30-day steps
- before the CRAN mirror’s logs begin
- after this copy’s series ends on 26 Oct 2026
- Time between
- 4,114 days3 releases 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
- 24 addednone removed
- Dependencies
- 3 changes2 added, 1 bound
- Licence
- Changednow BSD_3_clause + file LICENSE
- Maintainer
- SameStefan Zeugner
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
- – before the CRAN mirror’s logs begin on 1 Oct 2012
| Release | Days newest | Days counted | CRAN downloads | Daily mean |
|---|---|---|---|---|
| 0.3.5 9 Aug 2022 to 28 Oct 2026, still the newest | 1,542 | 1,540 | 45,638 | 30 |
| 0.3.0 5 May 2011 to 4 Sep 2012 | 489 | – | – |
Counted on the CRAN mirror from each release's day to the day before the next release. This copy's daily series ends on 26 Oct 2026, so a span that runs past it is counted to that day and its daily mean covers the days counted. 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
- bound or field changed
| Package | Field | 0.3.0 | 0.3.5 | |
|---|---|---|---|---|
| changed | R | Depends | >= 2.5 | >= 2.10 |
| added | graphics | Depends | – | any version |
| added | stats | Depends | – | any version |
Side by side
| Measure | 0.3.0 | 0.3.5 | Change |
|---|---|---|---|
| R | >= 2.5 | >= 2.10 | changed |
| Depends | 1 package | 3 packages | +2 |
Exports
added Added (24)
as.zlmbeta.draws.bmabin2hexbmsestimates.bmaf21hyperfullmodel.ssqgdensityhex2bininfo.bmais.bmais.topmodlps.bmaplotCompplotConvplotModelsizepmp.bmapmpmodelpost.pr2post.varpred.densitytopmodtopmodels.bmazlm
Licence and people
Method, licences 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.
| Part | 0.3.0 | 0.3.5 | |
|---|---|---|---|
| changed | Licence | Artistic-2.0 | BSD_3_clause + file LICENSE |
| added | Person named | – | Paul Hofmarcher |
Side by side
| Measure | 0.3.0 | 0.3.5 | Change |
|---|---|---|---|
| Licence | Artistic-2.0 | BSD_3_clause + file LICENSE | changed |
| Maintainer | Stefan Zeugner | Stefan Zeugner | |
| People named | Martin Feldkircher, Stefan Zeugner | Martin Feldkircher, Stefan Zeugner, Paul Hofmarcher | changed |
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.3.0 | 0.3.5 | Change |
|---|---|---|---|
| Lines of R code | 4,220 | 6,845 | +2,625 up |
| Files | 105 | 59 | −46 down |
| Public exports | Not measured | 24 | |
| Internal functions | 0 | 63 | +63 up |
| Mean complexity | 7.3 | 7.5 | +0.2 up |
| Highest complexity | 57 | 60 | +3 up |
| Download size | 455 KB | 3.6 MB | +3.2 MB up |
| Source, unpacked | 732 KB | 4.1 MB | +3.3 MB up |
1 other figure of the code is the same in both.
Side by side
| Measure | 0.3.0 | 0.3.5 | Change |
|---|---|---|---|
| Lines of R code | 4,220 | 6,845 | +2,625 |
| Lines of compiled code | 0 | 0 | |
| Files | 105 | 59 | −46 |
| Public exports | Not measured | 24 | |
| Internal functions | 0 | 63 | +63 |
| Mean complexity | 7.3 | 7.5 | +0.2 |
| Highest complexity | 57 | 60 | +3 |
| Download size | 455 KB | 3.6 MB | +3.2 MB |
| Source, unpacked | 732 KB | 4.1 MB | +3.3 MB |
| 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.3.0 | 0.3.5 |
|---|---|---|
| Exports named in tests | Not measured | 0.0% |
3 other figures of the tests are the same in both.
Side by side
| Measure | 0.3.0 | 0.3.5 | Change |
|---|---|---|---|
| Lines run by tests | Not measured | No tests to run | |
| Test cases | 0 | 0 | |
| Lines of tests | 0 | 0 | |
| Test lines per line of code | 0.00 | 0.00 | |
| Exports named in tests | Not measured | 0.0% |
Documentation
| Measure | 0.3.0 | 0.3.5 | Change |
|---|---|---|---|
| Exports documented | Not measured | 100.0% | |
| Arguments documented | Not measured | 99.3% | |
| Return value documented | Not measured | 85.7% | |
| Lines of documentation | 2,590 | 2,986 | +396 up |
| Lines of guides | 0 | 678 | +678 up |
Side by side
| Measure | 0.3.0 | 0.3.5 | Change |
|---|---|---|---|
| Exports documented | Not measured | 100.0% | |
| Arguments documented | Not measured | 99.3% | |
| Return value documented | Not measured | 85.7% | |
| Lines of documentation | 2,590 | 2,986 | +396 |
| Lines of guides | 0 | 678 | +678 |
Files changed
- Files changed
- 123over 4 releases
- Lines added
- 15,216
- Lines deleted
- 11,186
Most changed files (12 of 123)
| File | Lines added | Lines deleted |
|---|---|---|
R/BMS-internal.R | 1,657 | 3,278 |
R/aux_outer.R | 4,687 | 0 |
R/pred.density.R | 399 | 797 |
R/bms.R | 393 | 698 |
R/aux_inner.R | 1,043 | 0 |
R/bma.R | 843 | 0 |
R/density.bma.R | 266 | 532 |
vignettes/bms.Rnw | 530 | 1 |
R/combine_chains.R | 166 | 332 |
man/bms.Rd | 308 | 160 |
R/gdensity.R | 141 | 282 |
MD5 | 174 | 220 |
Each release is counted against the release before it, so a line changed twice counts twice.
Release notes
From the NEWS file of 0.3.5. Only the section for the newest release on record is kept.
- Last build 2022-08-05. Rebuilding package with modern means in order to prepare expansion of package.
- Coding started in Jan 2022, fixing small issues...
- License changed from artistic to BSD3
- Co-author added: Paul Hofmarcher, maintainer email changed.
- Source coude released at github: github.com/zeugner/BMS, no with roxygen documentation
- For issues, check bms.zeugner.eu
- *
bms(): Fixed numerical tolerance bugs relating to enumeration over datasets with 1000+ observations- Fixed coercion to logical(1) issue
- Reduced file size of bma objects somewhat
Unchanged and not compared
Maintainer is the same in both releases. No advisory is known for either release. Neither release has tests.
Checks, the install tree, dependents and the repository describe the package as it is now, so they are on the package page.