[Rp] Fluctuation domains in adaptive evolution
A C/R reproduction report concerning fluctuation domains in an adaptive-evolution model.
External publication. Published by its original venue; not published in our journal.
How stable are selected distributional summaries across independent seeds and documented numerical settings?
An evaluator recomputes summaries and uncertainty from all runs, using model constraints and a simplified reference case where available.
What you could produce
- Versioned protocol, input and environment manifest, and independent per-case comparison table including uncertainty and incomplete cases.
Before you use it
- Exact article-specific dependencies, data and build requirements remain uninspected.
Limits to keep in view
- No research code was executed; no independent scientific verification has been performed.
- The current qualified pilot is self-contained Python 3.13 with a 90-second author deadline. This article's environment has not been qualified for that path.
- Published source metadata and a historical review do not establish compatibility, successful reproduction, operator independence or current scientific correctness.
- The language/runtime named by the upstream source is outside the current qualified Python-only pilot.
Source and permission context
Boettiger, Carl. [Rp] Fluctuation domains in adaptive evolution. ReScience C 6(1), #15; 10.5281/zenodo.4081202.
Catalog listing reviewed. This review covers the description and source links displayed here.
ReScience/Zenodo metadata reviewed; exact CC-BY-4.0 evidence is manuscript-scoped.
Reviewed 2026-09-14. Copying or adapting source files remains subject to their own terms.
manuscript · CC-BY-4.0
The exact Zenodo record cited by the journal declares cc-by-4.0; the journal separately identifies published manuscripts as CC BY. This records manuscript rights, not separate code/data licenses or archive contents.
Inspect the license evidence ↗Before copying source material
- The associated code's exact license and version-specific third-party notices have not been independently checked.
- Data licenses, permissions, consent restrictions and redistribution conditions have not been independently checked.
- Artifacts are referenced only; PDF/archive contents, dependency locks and bytes have not been inspected or executed.