← Back to home
Comparison · Analytics

discretefdr vs piecepackr

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

Shared themes:r-package

discretefdr vs piecepackr: at a glance

Featurediscretefdrpiecepackr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesmultiple-testing, false-discovery-rate, discrete-statistics, r-packageboard-games, graphics, r-package, 3d-rendering
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 piecepackr?

A board game graphics package runs one of the most disciplined deprecation cycles in R.

piecepackr renders game pieces — piecepack, chess, dominoes and related systems — as 2D grid graphics, 3D meshes, animations, and print-and-play PDFs. Its interface is mature enough that most releases are about managing change rather than adding capability: features get deprecated with a named replacement, live through a release or two, then get removed on schedule. The current release completes the cycle opened a year earlier, retiring the new_device and style arguments in favour of open_device and the composable font, border, background_color and edge_color set.

Read the full piecepackr trajectory →

discretefdr vs piecepackr: 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.

P
piecepackr
ANALYTICS
0.0

A board game graphics package runs one of the most disciplined deprecation cycles in R.

◆ Current state

piecepackr renders game pieces — piecepack, chess, dominoes and related systems — as 2D grid graphics, 3D meshes, animations, and print-and-play PDFs. Its interface is mature enough that most releases are about managing change rather than adding capability: features get deprecated with a named replacement, live through a release or two, then get removed on schedule. The current release completes the cycle opened a year earlier, retiring the new_device and style arguments in favour of open_device and the composable font, border, background_color and edge_color set.

◆ Where it's heading

Two things dominate the log. The first is that deprecation discipline, unusually explicit for a package this size — every removal names its successor, and deprecations announced in one release are removed in a predictable later one. The second is defensive dependency management: version bumps pinned around bugs introduced upstream in rayrender and rayvertex, a warning class for known-buggy cairo versions with an option to suppress it, and suggested packages required for metadata embedding with clear messages when they are absent. Functionality still arrives — vectorised 3D object export that finally handles composite pieces, new crosshair grobs, a reworked colour palette — but it arrives inside that maintenance rhythm rather than driving it.

◆ Prediction

The features deprecated in this release — the preview_layout component and the 4x6 print-and-play size — are on the established path toward removal in a future version, with the documented ppdf-based replacement already in place.

Alternatives to discretefdr and piecepackr

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 piecepackr.

See all discretefdr alternatives → · See all piecepackr alternatives →

Recent activity from discretefdr and piecepackr

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

  1. 3mo agodiscretefdrDeprecated internal calls replaced
  2. 3mo agopiecepackrYear-old deprecations removed; new crosshair grobs added
  3. 10mo agopiecepackrExamples updated off the deprecated style argument
  4. 1y agopiecepackrSuit colours redrawn and piece styling made composable
  5. 1y agodiscretefdrDiscrete Benjamini-Yekutieli procedure added
  6. 1y agopiecepackr3D export vectorised, and composite pieces stop erroring
  7. 1y agodiscretefdrDatasets split out and step-up procedures sped up
  8. 1y agopiecepackrrayrender pinned around an upstream bug
  9. 2y agopiecepackrrayvertex pinned around an upstream mesh bug

Frequently asked questions

What is the difference between discretefdr and piecepackr?

Both compete on the same themes — r-package — within Analytics. discretefdr and piecepackr 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 piecepackr?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. discretefdr and piecepackr 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 piecepackr?

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