LoginSign Up
← Back to all sparks
O

ordinalsimr

INFRA · APIS
Velocity0.0

Compare Ordinal Endpoints Using Simulations

github.com/NeuroShepherd/ordinalsimr ↗

A Shiny app for choosing the right ordinal test reached CRAN in a single 90-minute burst of tags.

ordinal-datashinysimulationstatistical-testsr-packageclinical-endpoints
◆Current state
ordinalsimr compares ordinal endpoints by simulation — you specify probability distributions, sample sizes and iterations, and it runs the candidate statistical tests against them so you can see which behaves best. It is delivered as a Shiny application with a data-entry grid, and its entire release history spans six days in January 2025: three tags inside 90 minutes on the 20th, then a CRAN-compliance release on the 26th.
◆Where it's heading
The release bodies are auto-generated pull-request lists covering the repository's whole history, so they read as a build log rather than a changelog: data entry UI, an rhandsontable statistics module, iteration and sample-size modules, binomial confidence intervals, plot tests, and a rename to the current package name late in development. What that log shows is a single-author project built to completion privately and then published all at once, with the public version history existing mainly to satisfy CRAN.
◆Prediction
With the CRAN submission accepted and no post-release entries in the feed, the next move is most likely a maintenance release; the PR log gives no signal of planned work beyond the tests already implemented.

◆Recent moves

  1. 1y ago

    v0.1.3 CRAN submission

    A single pull request making the changes CRAN required, six days after the submission itself. It is what actually got the package over the line, but contains no functional change.

    View source ↗
  2. 1y ago

    Ordinal endpoint simulator submitted to CRAN

    ⚡ SPARK

    The tag that submits the finished application to CRAN. Its body is the full repository history — every module of the app in one list — because this is the first time any of it is published. The devel tag 90 minutes earlier carries the identical list minus the finalisation commit.

    View source ↗
  3. 1y ago

    README refreshed and DOI added to the citation file

    A README refresh and a DOI added to the CITATION file, tagged 23 minutes before the CRAN submission. Preparation for being cited, not a change to the app.

    View source ↗
  4. 1y ago

    Development tag ahead of the CRAN submission

    A development tag whose body is the same full pull-request history as the CRAN submission that follows it, differing by a single finalisation commit. It marks the point the build was considered done rather than shipping anything on its own.

    View source ↗