SynthPopCan
SynthPopCan is an early-stage project for building Canadian synthetic population tooling.
SynthPopCan is an independent research-software project. It is not affiliated with, endorsed by, or sponsored by Statistics Canada or the Government of Canada.
Near-term goals:
- Provide a Python library and CLI that can create synthetic populations through IPF from Statistics Canada margin/control tables.
- Build census microdata workflows for household- and person-level synthetic populations using a tree-based synthetic population generator plus calibration. The local 2016 Census material is the first available microdata source, but the tooling should be census-year agnostic.
- Maintain a local web app for configuring runs, inspecting controls, generating from prepared models, validating outputs, and downloading results.
Broader SynthEco-style enrichment with cohort, environmental, school, healthcare, and food-access layers is intentionally deferred until the base population synthesis workflow is stable.
Detailed documentation is published at
https://synthpopcan.readthedocs.io/. The source files live under
docs/; start with docs/index.rst for task-based
navigation to the web app, IPF from StatCan margin tables,
generated-from-model workflows, the beginner Python API, and advanced
microdata/model-training material.
Project planning and research notes are tracked separately:
PLANS.md: current roadmap, open work, sequencing, and design decisions.NOTES.md: research synthesis from local materials and external literature.CHANGELOG.md: public release notes and completed release highlights.CORRECTNESS.md: tested correctness claims, evidence, limitations, and reproducibility commands.
Quick Start
These commands use a Unix-style shell. Windows readers should first complete the WSL setup in the Installation guide, then run the same commands inside the Ubuntu terminal.
Install the published package from PyPI:
Network required for installation.
python3 -m pip install synthpopcan
Then inspect the command line:
synthpopcan --help
Run a small offline smoke test with the bundled fictional model:
Runnable teaching example. Enter both commands in order.
synthpopcan models generate demo-linked-household-person \
--households 10 \
--condition "geo=Demo North" \
--out synthpopcan-quickstart \
--random-seed 42
synthpopcan validate linked synthpopcan-quickstart
This verifies linked household/person generation, but it does not create a representative Canadian population. The documentation explains how to choose research sources, controls, and model packages.
For a one-off command without installing the tool into the current environment,
use uvx:
Network and uv required. See the Installation guide before using this
route if uvx --version is not already available.
uvx synthpopcan --help
uvx synthpopcan guide ipf
uvx synthpopcan guide model
uvx synthpopcan guide small-area
From a source checkout for development:
Source checkout, network, Git, and uv required.
git clone https://github.com/dlq/synthpopcan.git
cd synthpopcan
uv sync
uv run synthpopcan --help
For installation details, see docs/installation.md.
Where To Start
Most readers should start in the Sphinx documentation rather than in this README:
| Task | Documentation |
|---|---|
| Choose a first workflow | docs/getting-started.md |
| Start a reproducible command-line workflow | docs/command-line.md |
| Use the local browser app | docs/web-app.md |
| Generate with IPF from margin/control tables | docs/ipf.md, docs/controls.md, docs/statcan.md |
| Assign linked households and people to small areas | docs/small-area.md |
| Use the beginner Python API | docs/library-getting-started.md |
Work with local data layout and data doctor |
docs/data.md |
| Inspect source files safely | docs/data.md, docs/statcan.md, docs/microdata.md |
| Work with census microdata adapters | docs/microdata.md |
| Train, audit, package, or use tree models | docs/tree.md |
| Validate generated outputs | docs/validate.md |
| Understand correctness evidence and limitations | CORRECTNESS.md |
| Check current plans and implementation notes | PLANS.md, CHANGELOG.md |
Build the documentation locally with:
Source checkout required. Contributor setup is documented in
CONTRIBUTING.md.
uv run sphinx-build -W -b html docs docs/_build/html
Developer Benchmarks
Benchmark fixtures are developer tooling, not normal user workflows:
Source checkout required. The province-scale timing run can also require substantial time and memory.
uv run python scripts/benchmarks.py ipf
uv run python scripts/benchmarks.py small-area
uv run python scripts/benchmarks.py small-area --province-scale
uv run python scripts/benchmarks.py ipf-backends
Use --seed-records for smaller or larger IPF runs. The province-scale
small-area timing check is opt-in because it depends on the machine. Optional
SciPy CSR and Polars comparisons remain benchmark probes rather than runtime
backends, and full-data tree-model smoke tests remain outside the default suite.
The CLI, beginner Python API, and local web app call the same Python workflow
and domain implementations. Browser guidance and durable artifacts do not
define a separate computational tier; scale limits come from the selected
workflow, model, output size, and available machine resources.
Data Policy
Large, raw, private, or access-controlled data are not tracked in git.
data/raw/is a local ignored cache for central raw inputs, including public Census Profile and WDS downloads.data/private/is a local ignored cache for access-controlled or sensitive later-use datasets.references/is a local ignored cache for copied papers, proposals, and legacy code references.
Public geography, school, healthcare, road, and environmental layers should generally be fetched from authoritative public sources such as Statistics Canada, open.canada.ca, donneesquebec.ca, and municipal/provincial open-data portals rather than stored in this repository.
Local-only manifests may exist inside ignored data directories to document what is present on a development machine.
Model Packages
Reviewed model packages may be distributed with the project when they are
explicitly intended as public research artifacts. The installed package should
stay small: only the tiny demo model is bundled. Larger published models are
downloaded on demand with synthpopcan models fetch MODEL_ID.
Release assets are gzip-compressed to keep downloads small. The CLI handles decompression and stores a normal JSON model package in the local cache.
Bundled model packages are not raw Census microdata. They should still be treated as derived research artifacts with provenance, disclosure-risk checks, and limitations. A model package being marked as a publishable candidate means it passed the project's current checks; it is not a claim of official approval, legal privacy certification, or fitness for every research use.
Before publishing a new model package, review docs/data.md,
docs/tree.md, PLANS.md, and
CONTRIBUTING.md.
Metadata
Release files for synthpopcan 0.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| synthpopcan-0.6.0.tar.gz | 7.0 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| synthpopcan-0.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.3 MB
Release files / synthpopcan-0.6.0.tar.gz
| Download URL | synthpopcan-0.6.0.tar.gz |
|---|---|
| Size | 7.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3e84b8b11ddf23403a4c8d1e743c044e946a20e4f0325ddf0fbbdce088054cab
|
|
BLAKE2b-256 checksum How to use checksums |
3beddb75c3f87a1373f4fd42eb3af2e4af609203e33db726ad2f65baf83156e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.
Transparency logRelease files / synthpopcan-0.6.0-py3-none-any.whl
| Download URL | synthpopcan-0.6.0-py3-none-any.whl |
|---|---|
| Size | 285.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6f78cedf1b71b95411f6743c0e85bf38077270f636af3a6dac8b1e1bfebef18c
|
|
BLAKE2b-256 checksum How to use checksums |
50ed9c30e3348d50f84f290a3c2fade5556704ba827a06b25045b23c6c4ecc69
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.
Transparency log