Liquepy
Python tools for solving problems related to soil liquefaction
Features
- Triggering:
Calculate liquefaction factor of safety according to Boulanger and Idriss (2014)
Calculate expected lateral strain and volumetric strain according to Zhang et al (2002)
- Settlement:
Calculate foundation settlement on liquefiable deposit according to Karamitros et al. (2013) or Bray et al. (2018)
- Element tests:
Calculate the dissipated energy required to liquefy
- Site response analysis
Perform equivalent linear site response analysis using the pysra package
Installation
pip install liquepy
Optional modules (sra, fig, spatial) require large third-party dependencies and therefore do not import unless dependencies are satisfied.
to install all dependencies for these optional modules run (example for installing sra dependencies)
pip install liquepy[sra]
Contributors
How do I get set up?
Run pip install -r requirements.txt
Code suggestions
Implementations of published liquefaction methods should be written as calc_<property>_<first_author>[_et_al]_<date>() for two authors include both.
Plotting and visualisation should be not included in computation objects. Instead plotting functions or objects should receive computation objects as inputs.
Formatting
Follow pep8 formatting standard (except for line character limit not strictly observed)
Docstrings written in numpy format
Tabulated data stored as comma separated or semi-colon separated files (not xlsx or xls)
Testing
Tests are run with pytest
Locally run: pytest on the command line.
Tests are run on every push using travis, see the .travis.yml file
To test the docs:
Install the check docs package: Run pip install collective.checkdocs
Run the check docs package and fix the errors: Run python setup.py checkdocs
Deployment
To deploy the package to pypi.com you need to:
Push to the pypi branch. This executes the tests on circleci.com
Create a git tag and push to github, run: trigger_deploy.py or manually:
git tag 0.5.2 -m "version 0.5.2" git push --tags origin pypi
Python 3.10+ and numpy 2.x are required. See pyproject.toml for full dependency and build requirements.
Code style and formatting are enforced with black and isort via pre-commit hooks. To set up development tools:
pip install -r requirements.txt
pip install .[test,maps,sra,fig]
pip install pre-commit
pre-commit install
All code contributions should include complete docstrings and type annotations for public APIs.
Metadata
Release files for liquepy 0.6.34
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 | Actions |
|---|---|---|---|---|
| liquepy-0.6.34.tar.gz | 84.8 kB | With provenance | Details for liquepy-0.6.34.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| liquepy-0.6.34-py3-none-any.whl | Python 3 | none | any | Details for liquepy-0.6.34-py3-none-any.whl |
Total release size: 165.6 kB
Release files / liquepy-0.6.34.tar.gz
| Download URL | liquepy-0.6.34.tar.gz |
|---|---|
| Size | 84.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b37825ab2bfb4409fdd2940247b2aa547c34ce533fddf08beef9a7d10b72e663
|
|
BLAKE2b-256 checksum How to use checksums |
8a54c8d6963aaf1145d89d0a469750b8614b7b8b323c81d602980c53dc2d1d3e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jan 12, 2026.
Transparency logRelease files / liquepy-0.6.34-py3-none-any.whl
| Download URL | liquepy-0.6.34-py3-none-any.whl |
|---|---|
| Size | 80.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f64a573e37ec8893e83c7f351f1951c1a07713b23d6e2c91226bc3f0f7a0a322
|
|
BLAKE2b-256 checksum How to use checksums |
d4233becc3361b021c76ae62aa2e370b2305507b2c39c2626da72165ab123652
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jan 12, 2026.
Transparency logSecurity for liquepy 0.6.34
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 2 files in this release have been uploaded with provenance metadata.
Attestation for liquepy-0.6.34.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 Jan 12, 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.