← Back to home
Comparison · Infra & APIs

aftables vs JointFPM

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

aftables vs JointFPM: at a glance

FeatureaftablesJointFPM
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesaccessibility, spreadsheets, government-statistics, openxlsx2survival-analysis, recurrent-events, parametric-models, api-stability
Last editorial update6h ago56m ago
WebsiteVisit →Visit →

What is aftables?

Accessible government spreadsheets in R, rebuilt on openxlsx2 and renamed along the way.

aftables generates spreadsheets that meet the UK Analysis Function's accessibility guidance, taking structured input and producing a formatted workbook with cover, contents, notes and table sheets. Version 2.0.0 replaced the workbook engine with openxlsx2 and added configuration through a config.yaml file, with create_config_yaml() exporting a template and generate_workbook() gaining arguments to point at it. The package was previously called a11ytables and was renamed in 1.0.2, with function names changed to match.

Read the full aftables trajectory →

What is JointFPM?

Recurrent-event modelling settles, with mean_no() promoted to stable.

JointFPM fits joint flexible parametric models for a recurrent event process alongside a competing terminal event, and predicts the mean number of events. The visible history runs from bug fixes on the earliest CRAN releases through standardization, integration options and a summary method, ending with mean_no() declared stable. Several changes arrived through outside pull requests.

Read the full JointFPM trajectory →

aftables vs JointFPM: editorial side-by-side

A
aftables
INFRA · APIS
0.0

Accessible government spreadsheets in R, rebuilt on openxlsx2 and renamed along the way.

◆ Current state

aftables generates spreadsheets that meet the UK Analysis Function's accessibility guidance, taking structured input and producing a formatted workbook with cover, contents, notes and table sheets. Version 2.0.0 replaced the workbook engine with openxlsx2 and added configuration through a config.yaml file, with create_config_yaml() exporting a template and generate_workbook() gaining arguments to point at it. The package was previously called a11ytables and was renamed in 1.0.2, with function names changed to match.

◆ Where it's heading

The history reads in two phases. As a11ytables the work was about what belongs in an accessible spreadsheet, adding arbitrary pre-table metadata rows and enforcing rules such as rejecting tab titles that start with a numeral. Since the rename the work has been structural: a new backend, and configuration moved out of function arguments into a file that can be version-controlled and shared across a team. That second phase suits the audience, since government analysts producing recurring statistical releases want the same document properties applied every time rather than re-specified per run.

◆ Prediction

Expect the config.yaml surface to grow to cover more of what is currently passed as arguments, given it arrived alongside alternative author, title and keywords arguments that it plainly supersedes. With the openxlsx2 migration complete, further releases are likely to be formatting fixes surfaced by real departmental publications, as 2.0.1 already was.

J
JointFPM
INFRA · APIS
0.0

Recurrent-event modelling settles, with mean_no() promoted to stable.

◆ Current state

JointFPM fits joint flexible parametric models for a recurrent event process alongside a competing terminal event, and predicts the mean number of events. The visible history runs from bug fixes on the earliest CRAN releases through standardization, integration options and a summary method, ending with mean_no() declared stable. Several changes arrived through outside pull requests.

◆ Where it's heading

The arc runs from a working estimator toward a usable one: input validation and error messages first, then control over the numerical integration, then a summary method and pass-through arguments to the underlying rstpm2 fit. The latest release adds no code so much as a stability commitment to a function users were already calling.

◆ Prediction

With mean_no() stable, the next work most likely targets the prediction and standardization paths rather than the model fit itself.

Alternatives to aftables and JointFPM

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 aftables or JointFPM.

See all aftables alternatives → · See all JointFPM alternatives →

Recent activity from aftables and JointFPM

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

  1. 4mo agoaftablesrlang import restored for older R versions
  2. 5mo agoaftablesWorkbook engine moved to openxlsx2; config.yaml introduced
  3. 1y agoJointFPMmean_no() promoted to a stable interface
  4. 1y agoaftablesPackage renamed from a11ytables to aftables
  5. 2y agoJointFPMsummary() method and control arguments passed to rstpm2
  6. 2y agoaftablesTab titles beginning with a numeral now rejected
  7. 2y agoJointFPMGaussian quadrature option for the mean-events integration
  8. 2y agoaftablescustom_rows allows arbitrary pre-table metadata
  9. 2y agoaftablesTable count spelled out; README spelling corrected
  10. 2y agoJointFPMStandardized marginal estimates plus input validation
  11. 2y agoJointFPMBug fixes for differences between mean-event functions

Frequently asked questions

What is the difference between aftables and JointFPM?

They serve adjacent needs but don't currently overlap on shipped themes. aftables and JointFPM 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 aftables better than JointFPM?

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

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

What are the best alternatives to JointFPM?

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