rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
PowerTOST vs surveycore
A side-by-side editorial comparison of PowerTOST and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
PowerTOST vs surveycore: at a glance
What is PowerTOST?
A bioequivalence sample-size workhorse whose news is which regulator it now covers
PowerTOST computes power and sample size for bioequivalence and its changelog reads as a record of regulatory divergence more than statistical development. Version 1.5-3 added the Gulf Co-operation Council as a regulator setting; 1.5-4 and 1.5-6 stripped 'FDA' out of the narrow-therapeutic-index function names once China's CDE began requiring the same evaluation. The most recent release, 1.5-7, is a single fix to how nvec() splits a total sample size across sequences.
What is surveycore?
surveycore declared its API stable with every survey design type covered.
surveycore is the estimation engine of a two-package survey stack, handling design objects and variance estimation while surveytidy supplies the dplyr verbs on top. The June release marks it 1.0.0 and states the API is complete and stable across Taylor series linearization, replicate weights, two-phase and non-probability designs, with means, totals, frequencies, quantiles, ratios, correlations, regression, t-tests, ANOVA and effective sample size all in place.
PowerTOST vs surveycore: editorial side-by-side
PowerTOST
0.0INFRA · APIS
A bioequivalence sample-size workhorse whose news is which regulator it now covers
◆ Current state
PowerTOST computes power and sample size for bioequivalence and its changelog reads as a record of regulatory divergence more than statistical development. Version 1.5-3 added the Gulf Co-operation Council as a regulator setting; 1.5-4 and 1.5-6 stripped 'FDA' out of the narrow-therapeutic-index function names once China's CDE began requiring the same evaluation. The most recent release, 1.5-7, is a single fix to how nvec() splits a total sample size across sequences.
◆ Where it's heading
The package is in long maintenance with a widening regulatory surface: the statistical methods are settled, and releases arrive when an agency publishes a framework that can be expressed as a settings variant of an existing method. Function naming has been deliberately decoupled from any single agency, with the deprecated FDA-suffixed aliases carried for years before removal. Cadence has slowed to roughly one release every eighteen months.
◆ Prediction
The next release is most likely another regulator setting or a small fix; on the deprecation notice already given, the power.NTIDFDA()-style aliases are the obvious removal candidate.
surveycore
0.0INFRA · APIS
surveycore declared its API stable with every survey design type covered.
◆ Current state
surveycore is the estimation engine of a two-package survey stack, handling design objects and variance estimation while surveytidy supplies the dplyr verbs on top. The June release marks it 1.0.0 and states the API is complete and stable across Taylor series linearization, replicate weights, two-phase and non-probability designs, with means, totals, frequencies, quantiles, ratios, correlations, regression, t-tests, ANOVA and effective sample size all in place.
◆ Where it's heading
The last months before 1.0.0 were spent making the awkward designs behave like the ordinary ones. Non-probability designs gained jackknife replicate schemes and got their bootstrap repweights routed through the replicate-weight variance estimator in survey_glm(), matching every other estimation function. The survey_collection abstraction — several surveys treated as one pseudo-data-frame — was tightened rather than extended: divergent grouping across members now errors instead of stitching a patchwork with bind_rows(), and the missing-variable argument was renamed and given a stored default on the collection itself. A documentation audit before 1.0.0 turned up six dispatch and print bugs and corrections across forty-plus files, which is the kind of thing that surfaces when an API is being frozen rather than extended.
◆ Prediction
A declared-stable API means the next releases should be additive or corrective rather than breaking, and the pre-1.0.0 pattern of breaking renames should stop. The tight version pinning between the two packages means surveytidy releases will keep following surveycore's.
Alternatives to PowerTOST and surveycore
Other Infra & APIs 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 PowerTOST or surveycore.
massProps
A mass-properties rollup spends a year on documentation and follows its sibling's API
writeAlizer
Six months of releases and not one of them touched the scoring models
samplr
A cognitive-science sampling package ships once, then goes quiet for eighteen months
stochvol
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
midr
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all PowerTOST alternatives → · See all surveycore alternatives →
Recent activity from PowerTOST and surveycore
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agosurveycoreFirst stable release: all four survey design types complete ⚡
- 3mo agosurveycoreget_effective_n() computes effective sample size
- 3mo agosurveycoreCollections error on divergent grouping; .on_missing renamed
- 4mo agosurveycoreCRAN patch removing surveytidy from the vignette
- 10mo agoPowerTOSTFix for splitting total sample size across sequences
- 2y agoPowerTOSTNTID functions renamed off the FDA acronym; GCC guidance in vignettes
- 4y agoPowerTOSTpower.NTID() aliases added; FDA-suffixed names deprecated
- 5y agoPowerTOSTGulf Co-operation Council added as a regulator setting
- 5y agoPowerTOSTMaintenance release with vignette and documentation clarifications
- 5y agoPowerTOSTstringsAsFactors fix for older R in a vignette example
Frequently asked questions
What is the difference between PowerTOST and surveycore?
They serve adjacent needs but don't currently overlap on shipped themes. PowerTOST and surveycore 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 PowerTOST better than surveycore?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. PowerTOST and surveycore 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 Infra & APIs products to evaluate alongside.
What are the best alternatives to PowerTOST?
Top PowerTOST alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "PowerTOST alternatives" section above for the current picks, or visit /alternatives/powertost for the full list with editorial commentary on each.
What are the best alternatives to surveycore?
Top surveycore alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "surveycore alternatives" section above for the current picks, or visit /alternatives/surveycore for the full list with editorial commentary on each.