← Back to home
Comparison · DevOps

jwst vs purrr

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

jwst vs purrr: at a glance

Featurejwstpurrr
SectorDevOpsDevOps
Velocity score3.80.0
Sparks · 30d10
Top themesastronomy, calibration-pipeline, jwst, spectroscopytidyverse, functional-programming, deprecations, parallelism
Last editorial update3h ago59m ago
WebsiteVisit →Visit →

What is jwst?

JWST's calibration pipeline extended adaptive trace modelling across its spectrographs

Version 3.0.0, the DMS B13.0 operational build, is the substantive release in this window. It extends the adaptive_trace_model step to NIRSpec MOS, fixed-slit and BOTS modes plus MIRI LRS, adds multiprocessing that cut one NIRSpec IFU case by roughly a factor of seven, and introduces chromaticity correction for NIRSpec IFU data via a new reference file type. It also removes several internal-only step parameters as breaking changes. The four release candidates preceding it contain only dependency pins and changelog freezes.

Read the full jwst trajectory →

What is purrr?

purrr finished a decade of deprecations and picked up a parallel backend.

purrr is at 1.2.2, and the last two releases are CRAN check fixes and vctrs compatibility. The substance sits in 1.2.0, which removed everything deprecated back in 0.3.0 and fully deprecated the invoke, lift, cross and splice families soft-deprecated in 1.0.0, while making map_chr() stop silently coercing logicals and numbers to strings. 1.1.0 before it raised the floor to R 4.1 and added in_parallel() on the mirai backend.

Read the full purrr trajectory →

jwst vs purrr: editorial side-by-side

J
jwst
DEVOPS
3.8

JWST's calibration pipeline extended adaptive trace modelling across its spectrographs

◆ Current state

Version 3.0.0, the DMS B13.0 operational build, is the substantive release in this window. It extends the adaptive_trace_model step to NIRSpec MOS, fixed-slit and BOTS modes plus MIRI LRS, adds multiprocessing that cut one NIRSpec IFU case by roughly a factor of seven, and introduces chromaticity correction for NIRSpec IFU data via a new reference file type. It also removes several internal-only step parameters as breaking changes. The four release candidates preceding it contain only dependency pins and changelog freezes.

◆ Where it's heading

Development is organised around periodic DMS operational builds rather than continuous delivery, with release candidates used purely to freeze dependencies. The direction inside the pipeline is toward per-mode calibration sophistication - trace modelling and chromaticity corrections that were previously unavailable or mode-limited - alongside a steady cleanup of parameters that only ever existed for internal plumbing.

◆ Prediction

Expect adaptive trace modelling to keep expanding across the remaining instrument modes, and the multiprocessing work applied there to spread to other slow steps. Further breaking removals of internal-use parameters are likely while the 3.x major version is open.

P
purrr
DEVOPS
0.0

purrr finished a decade of deprecations and picked up a parallel backend.

◆ Current state

purrr is at 1.2.2, and the last two releases are CRAN check fixes and vctrs compatibility. The substance sits in 1.2.0, which removed everything deprecated back in 0.3.0 and fully deprecated the invoke, lift, cross and splice families soft-deprecated in 1.0.0, while making map_chr() stop silently coercing logicals and numbers to strings. 1.1.0 before it raised the floor to R 4.1 and added in_parallel() on the mirai backend.

◆ Where it's heading

The direction is a smaller, stricter surface. Functions that predated the 1.0.0 redesign are being cleared out in stages, and the ones that remain are tightening their type contracts — map_chr() no longer coerces, every() and some() now demand a logical scalar. The parallel work is the one addition, and it arrives as a backend rather than a new way to write maps.

◆ Prediction

With the 1.0.0 soft deprecations now fully deprecated and marked for removal, the next release most likely deletes them rather than adding capability.

Alternatives to jwst and purrr

Other DevOps 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 jwst or purrr.

See all jwst alternatives → · See all purrr alternatives →

Recent activity from jwst and purrr

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

  1. 28d agojwstJWST 3.0.0 extends adaptive trace modelling across spectroscopic modes
  2. 1mo agojwst3.0.0rc4
  3. 1mo agojwst3.0.0rc3
  4. 1mo agojwststcal bumped to 1.19.1
  5. 1mo agojwstDependencies pinned to latest released versions
  6. 3mo agojwstNIRCam DHS stripe crash and multi-integration ramp fix
  7. 4mo agopurrrCRAN check fixes
  8. 7mo agopurrrCompatibility with upcoming vctrs 0.7.0
  9. 9mo agopurrrOld deprecations removed; map_chr() stops coercing
  10. 1y agopurrrin_parallel() adds parallel and distributed maps via mirai
  11. 3y agopurrrValgrind fix and lower map_chr() deprecation overhead
  12. 3y agopurrrIndexed map() errors gain a catchable class and fields

Frequently asked questions

What is the difference between jwst and purrr?

They serve adjacent needs but don't currently overlap on shipped themes. jwst is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is jwst better than purrr?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. jwst is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.

What are the best alternatives to jwst?

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

What are the best alternatives to purrr?

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