← Back to all sparks
T

tern.rbmi

ANALYTICS
Velocity0.0

Create TLGs using rbmi and tern

Reference-based multiple imputation tables, shipping only what CRAN checks demand.

pharmaversemultiple-imputationcran-maintenancetabulationdormant
Current state
tern.rbmi renders the output of {rbmi} reference-based multiple imputation analyses into tern tables for clinical reporting. Its three most recent releases exist to satisfy CRAN: restricting vignette builds to gcc, adding V8 to Suggests, and a plain resubmission. No user-facing functionality has changed in the visible window, and the three older entries now backfilled are version-bump automation.
Where it's heading
This is a thin adapter package and behaves like one — it moves when CRAN or an upstream dependency forces it to. Between 2022 and 2024 the feed shows only version bumps, and the 2025 releases are packaging concerns rather than analysis changes. The newly surfaced 2022 entries reinforce rather than change that reading.
Prediction
Expect the next release to be triggered by a CRAN check failure or an {rbmi} update rather than by new tabulation features.

Recent moves

  1. 1y ago

    Vignette built only under gcc

    A packaging workaround restricting the vignette build to gcc so it does not break CRAN checks on other toolchains; analysis behaviour is unchanged.

    View source ↗
  2. 1y ago

    V8 added to Suggests

    A dependency declaration fix adding V8 to Suggests, alongside documentation housekeeping.

    View source ↗
  3. 1y ago

    CRAN resubmission with dependency and workflow updates

    A CRAN resubmission whose content is entirely workflow propagation, minimum-version bumps and a test tolerance adjustment.

    View source ↗
  4. 3y ago

    Automated release commit for 0.1.1

    A release-automation commit marking version 0.1.1. Backfilled into the feed years later; it records the release tooling rather than any change to the package.

    View source ↗
  5. 4y ago

    Development version bump to 0.1.0.9004

    A version bump to a development build, captured by CI. Note the title reads 2022_08_16 while the entry is dated 27 July — the date stamps on these automation entries are unreliable.

    View source ↗
  6. 4y ago

    CI automation commit, no release content

    A CI commit whose body is nothing but repeated skip-vbump markers, matching its sibling package's identical entry from the same day.

    View source ↗