This release is a pre-release and may not be stable for production use.
Cratermaker
Simulate the evolution of a landscape dominated by impact bombardment.
Cratermaker is a landscape evolution model that simulates the evolution of a planetary surface subjected to impact bombardment. It began as a modernized re-write of the older Cratered Terrain Evolution Model (CTEM), but in most ways it is far more capable1. While its core function is as a planetary cratering landscape evolution model, its various components can be used independently for crater to impactor scaling, modeling production functions, extracting lunar elevation models, and much more.
Note: Cratermaker is still in alpha stage of development. Not all components and models have been tested thoroughly, so please use caution and always double check the results when using the code for scientific purposes (which you should be doing anyway).
Getting Started with Cratermaker
Cratermaker is designed to be both user-friendly and highly configurable, ensuring that users can start simulations quickly with reasonable defaults or tailor their simulations to specific needs. It is built to be highly modular, and so many of the core components of Cratermaker can be run independently, outside of its core landscape evolution simulation.
Cratermaker is a Python package that is designed to work with Python 3.10 or later on MacOS, Linux, and Windows. It contains some Rust components for performance. You may need to install Rust before installing Cratermaker. Installation instructions for your operating system can be found in the Rust documentation.
Install dependencies
Some components of Cratermaker use OpenBLAS for linear algebra operations. On some systems, you may need to install OpenBLAS separately before installing Cratermaker. Installation instructions for your operating system can be found in the OpenBLAS documentation. You may also need to install OpenSSL development libraries for your system.
Cratermaker uses a number of packages which must be installed on the system before it can be built. If any are missing, they could cause a failure to build. Try one of the following, depending on what OS you are using:
Debian Linux (e.g. Ubuntu)
sudo apt-get update
sudo apt-get install pkg-config libssl-dev libopenblas-dev
Redhat Linux (e.g. Fedora) with yum
yum install epel-release
yum install pkgconfig openssl-devel openblas-devel
Redhat Linux (e.g. Fedora) with dnf
dnf install pkgconf-pkg-config openssl-devel flexiblas-devel
MacOS with Homebrew
brew install openssl@3 openblas
Windows with vcpkg
vcpkg install openblas intel-mkl --triplet x64-windows
Normal Installation
You can install Cratermaker using pip into the Python environment of your choice, provided it is at least Python 3.10 or above.
pip install cratermaker
Note: Cratermaker is undergoing active development, as it is still in alpha stage. You may need to update your installation frequently to get the latest features and bug fixes. You can do this using the following command:
pip install --upgrade cratermaker
Installing Cratermaker from Source
If you plan to contribute to Cratermaker, or want to try out the latest features that have not yet been released, you can install Cratermaker from source. You can find the latest source code from our GitHub repository <https://github.com/MintonGroup/cratermaker>__.
Some components of Cratermaker are built using Rust, and so you will need to have Rust installed on your system to build Cratermaker from source. Installation instructions for your operating system can be found in the Rust documentation <https://rust-lang.org/learn/get-started/>__.
The first time you install Cratermaker from source, you will need to generate the version file. Due to limitations of the Maturin build system, this must be done manually. You do this by running the following command in the root directory of the Cratermaker source code:
python buildscripts/set_version.py
For development, it's best to build and install the package in "editable" mode. To build and install an editable version you can install Cratermaker from source using the following command:
pip install -e .
Building documentation pages
The documentation pages are built using Sphinx. If you wish to build local versions of the documentation for testing, you will need to install additional dependencies that are not installed by default. We maintain a two requirements files for this purpose, one for pip, and the other for conda, which is used by the Read the Docs build system. You can install the documentation dependencies using the following command:
pip install -r environments/requirements-docdev.txt
or, you can generate a conda environment using the conda requirements file:
conda env create -f environments/cratermaker-docs.yml
Once you have installed the documentation dependencies, be sure that you also have installed Cratermaker as an editable install into the same environment. Then you can build the documentation using the following command:
cd docs
make clean
make rtdhtml
The documentation pages will be built in the docs/_build/html directory, which you can then open in your web browser to view.
Automatically rebuild Rust components
The build backend for the Rust components is Maturin. Maturin provides an import hook that can allow the Rust libraries to be automatically recompiled if they are changed, which is useful when Cratermaker installed in editable configuration. To use this, first install the package:
pip install maturin_import_hook
In the same virtual environment that you installed Cratermaker in, activate the import hook:
python -m maturin_import_hook site install
For more information, see the the Import Hook section of the Maturin documentation.
Common problems
Here are a few things you can try if you have trouble installing the Cratermaker project from source.
Make sure Rust is up-to-date
Be sure your rust install is up-to-date
rustup update --nightly
If you see errors related to linalg functions, you may have an old and incompatable linalg crate installed. The most expedient way I've found to deal with this is to remove the Cargo.lock file. You can do this in a clean way with the cargo-unlock crate:
cargo install cargo-unlock
cargo unlock
Installing polars on legacy hardware
If you ever see an error like this::
illegal hardware instruction (core dumped)
Or a message about polars and incompatible hardware, you may have to install the runtime-compatability version of polars.
pip install "polars[rtcompat]"
Documentation
For more detail, see the documentation page.
1 maintainer
Metadata
1 maintainer
Release files for cratermaker 2026.9.0a0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| cratermaker-2026.9.0a0.tar.gz | 260.0 kB | With provenance | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| cratermaker-2026.9.0a0-cp313-cp313-win_amd64.whl | CPython 3.13 | CPython 3.13 | Windows x86-64 | Details |
| cratermaker-2026.9.0a0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.13 | CPython 3.13 | Linux glibc 2.17+ x86-64 | Details |
| cratermaker-2026.9.0a0-cp313-cp313-macosx_11_0_arm64.whl | CPython 3.13 | CPython 3.13 | macOS 11.0+ ARM64 | Details |
| cratermaker-2026.9.0a0-cp312-cp312-win_amd64.whl | CPython 3.12 | CPython 3.12 | Windows x86-64 | Details |
| cratermaker-2026.9.0a0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.17+ x86-64 | Details |
| cratermaker-2026.9.0a0-cp312-cp312-macosx_11_0_arm64.whl | CPython 3.12 | CPython 3.12 | macOS 11.0+ ARM64 | Details |
Total release size: 7.1 MB
Release files / cratermaker-2026.9.0a0.tar.gz
| Download URL | cratermaker-2026.9.0a0.tar.gz |
|---|---|
| Size | 260.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b6171e8db4e3970dcf87c7a8e82866510f40c193d6bacd035dbc7ae2f777f9a0
|
|
BLAKE2b-256 checksum How to use checksums |
3d7621f03bbf0a681c3e7a8dc656c7f278df70e24637e09de9aa2fa82ebfc139
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 22, 2026.
Transparency logRelease files / cratermaker-2026.9.0a0-cp313-cp313-win_amd64.whl
| Download URL | cratermaker-2026.9.0a0-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 970.9 kB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
fc3ad749cb55b461b2d8321bc91a0750b35987d04ef5578823ca9372de02db38
|
|
BLAKE2b-256 checksum How to use checksums |
acc2e8354121f70c83872e98b423fb9fb2409664f9f86803401e924195fced4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 22, 2026.
Transparency logRelease files / cratermaker-2026.9.0a0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | cratermaker-2026.9.0a0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
6ed0d72e79a28e98407d2eeae52bdbb802e99fa98163c90b6b46c99c6df4ab97
|
|
BLAKE2b-256 checksum How to use checksums |
535be03ce688f962961bd420856b796a576d8a9fb64542e0e7b3df72868cebc5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 22, 2026.
Transparency logRelease files / cratermaker-2026.9.0a0-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | cratermaker-2026.9.0a0-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
c3bac9f2e742022ca19e200b2cca89da8406aebd1f22ecaf7b44c69125fe3d76
|
|
BLAKE2b-256 checksum How to use checksums |
7642a71c5db040ac2c72883fae94d889d16e0e69c2c70e88d1fafd0cb71126e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 22, 2026.
Transparency logRelease files / cratermaker-2026.9.0a0-cp312-cp312-win_amd64.whl
| Download URL | cratermaker-2026.9.0a0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 971.3 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
7222da187764d49a570b89c7e22b1d8fa3b523888f93838613cf0fb998464a98
|
|
BLAKE2b-256 checksum How to use checksums |
26fec5d7f1d2b0811c9a8951be361036c982d5528a286ac78b3cf14630ab2de2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 22, 2026.
Transparency logRelease files / cratermaker-2026.9.0a0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | cratermaker-2026.9.0a0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
a3920e31783574a39cddfe69b46b4c5465276675c12000b0372bac14ba878ee7
|
|
BLAKE2b-256 checksum How to use checksums |
710912ba9827de64866f2e34e1a2dc1d94223eb94d6045dd784359bba9222ef3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 22, 2026.
Transparency logRelease files / cratermaker-2026.9.0a0-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | cratermaker-2026.9.0a0-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
92af66314bac185ee4c9612f5f91817d438060d84488e945f5189842f1c35f11
|
|
BLAKE2b-256 checksum How to use checksums |
bab5b67e6899ae823c567869c5eb308f593d300f73f6f57ffd7410d2577dc991
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 22, 2026.
Transparency logSecurity for cratermaker 2026.9.0a0
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.
Full provenance
All 7 files in this release have been uploaded with provenance metadata.
Attestation for cratermaker-2026.9.0a0.tar.gz
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 Sep 22, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
