← Back to home
Comparison · Analytics

discretefdr vs ojoregex

A side-by-side editorial comparison of discretefdr and ojoregex — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

discretefdr vs ojoregex: at a glance

Featurediscretefdrojoregex
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesmultiple-testing, false-discovery-rate, discrete-statistics, r-packagecriminal-justice, court-data, r-package, text-classification
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is discretefdr?

The discrete-data FDR package is being pared into one piece of a larger multiple-testing suite.

DiscreteFDR implements false discovery rate procedures adapted for discrete test statistics, where the standard continuous-case corrections are conservative. It now covers a discrete Benjamini-Yekutieli procedure alongside the Benjamini-Hochberg variants it started with, including adaptive versions. Its datasets and test-result classes have been moved out into companion packages, so it increasingly does one job and defers the rest.

Read the full discretefdr trajectory →

What is ojoregex?

Oklahoma's court-data nonprofit maintains the regex layer that turns charge text into categories.

ojoregex is Open Justice Oklahoma's pattern library for classifying criminal charge descriptions from court records — the unglamorous translation layer between free-text charge fields and analysable categories. Its entire release history reached this feed as four tags published within three minutes, so the feed order reflects a backfill rather than a shipping cadence. Release notes are merge references rather than descriptions, which limits how much can be read from the changelog alone.

Read the full ojoregex trajectory →

discretefdr vs ojoregex: editorial side-by-side

D
discretefdr
ANALYTICS
0.0

The discrete-data FDR package is being pared into one piece of a larger multiple-testing suite.

◆ Current state

DiscreteFDR implements false discovery rate procedures adapted for discrete test statistics, where the standard continuous-case corrections are conservative. It now covers a discrete Benjamini-Yekutieli procedure alongside the Benjamini-Hochberg variants it started with, including adaptive versions. Its datasets and test-result classes have been moved out into companion packages, so it increasingly does one job and defers the rest.

◆ Where it's heading

The direction is decomposition into a suite. The amnesia dataset went to DiscreteDatasets, summary output now interoperates with the DiscreteTestResults class from DiscreteTests, and match.pvals() stopped being exported — each release trims something that belongs elsewhere. What remains gets methodological additions at a slow, deliberate cadence, with performance work on the step-up procedures that dominate cost when the number of tests is large. Recent activity is maintenance: replacing deprecated calls the package still made of its own siblings. This is a mature statistical package whose release notes are short because the methods underneath them are settled.

◆ Prediction

Expect further alignment with the companion packages rather than new procedures, since the last substantive release was already about interoperating with DiscreteTests classes and the most recent one about clearing deprecations.

O
ojoregex
ANALYTICS
0.0

Oklahoma's court-data nonprofit maintains the regex layer that turns charge text into categories.

◆ Current state

ojoregex is Open Justice Oklahoma's pattern library for classifying criminal charge descriptions from court records — the unglamorous translation layer between free-text charge fields and analysable categories. Its entire release history reached this feed as four tags published within three minutes, so the feed order reflects a backfill rather than a shipping cadence. Release notes are merge references rather than descriptions, which limits how much can be read from the changelog alone.

◆ Where it's heading

What the notes do show is a package alternating between domain corrections and R tooling upkeep: a fix to property-crime matching in one release, dplyr select semantics in the next. That is the expected shape for a regex catalogue — accuracy work arrives as individual charge types get miscategorised in real analyses, and the rest is keeping the package installable against a moving tidyverse. Contributions come from a small internal team, and the vignette work referenced in the earliest tag suggests the pattern list doubles as documentation for analysts.

◆ Prediction

The visible pattern is incremental match fixes as charge types surface in use; the release notes carry too little detail to predict anything beyond that without reading the underlying pull requests.

Alternatives to discretefdr and ojoregex

Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either discretefdr or ojoregex.

See all discretefdr alternatives → · See all ojoregex alternatives →

Recent activity from discretefdr and ojoregex

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agoojoregexPatch for dplyr select semantics
  2. 1mo agoojoregexojoregex v0.10.0
  3. 1mo agoojoregexNamespace prefixes fixed, plus a property-crime match bug
  4. 1mo agoojoregexFirst tagged release, carrying the whole development history
  5. 3mo agodiscretefdrDeprecated internal calls replaced
  6. 1y agodiscretefdrDiscrete Benjamini-Yekutieli procedure added
  7. 1y agodiscretefdrDatasets split out and step-up procedures sped up

Frequently asked questions

What is the difference between discretefdr and ojoregex?

Both compete on the same themes — r-package — within Analytics. discretefdr and ojoregex are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is discretefdr better than ojoregex?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. discretefdr and ojoregex are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to discretefdr?

Top discretefdr alternatives in Analytics are ranked by recent ship velocity. Browse the "discretefdr alternatives" section above for the current picks, or visit /alternatives/discretefdr for the full list with editorial commentary on each.

What are the best alternatives to ojoregex?

Top ojoregex alternatives in Analytics are ranked by recent ship velocity. Browse the "ojoregex alternatives" section above for the current picks, or visit /alternatives/ojoregex for the full list with editorial commentary on each.