[Re] Weighted Voronoi Stippling
A replication of weighted Voronoi stippling, a geometric method for distributing sample points according to image intensity.
External publication. Published by its original venue; not published in our journal.
How closely do generated stipple densities match evaluator-defined synthetic intensity maps at fixed point counts?
An evaluator computes spatial-density discrepancies and domain-boundary checks from coordinates, independent of the rendered image or author score.
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
- Python 3.6.0, NumPy 1.12.0, SciPy 0.18.1, Matplotlib 2.0.0, tqdm 4.11.2, Pillow 4.0.0 (historical environment listed by the current README)
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.
Source and permission context
Rougier, Nicolas P.. [Re] Weighted Voronoi Stippling. ReScience 3(1), #4; 10.5281/zenodo.802285.
Catalog listing reviewed. This review covers the description and source links displayed here.
ReScience/Zenodo manuscript CC-BY-4.0 evidence; current BSD-3-Clause code observation is separately scoped and version-unmatched.
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 ↗code current repository · BSD-3-Clause
The current code/LICENSE.txt contains the three BSD conditions, including non-endorsement. This observes the code subtree's license separately from manuscript/image-data rights; correspondence to archived code bytes remains unresolved.
Inspect the license evidence ↗Before copying source material
- 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.
- Current repository license files were inspected, but their equivalence to the journal's DOI/SWH artifact version and all third-party notices remain unresolved.