pyIncore is a component of IN-CORE. It is a python package consisting of two primary components: 1) a set of service classes to interact with the IN-CORE web services described below, and 2) IN-CORE analyses. The pyIncore allows users to apply various hazards to infrastructure in selected areas, propagating the effect of physical infrastructure damage and loss of functionality to social and economic impacts.
Installation with conda
Installing pyincore with Conda is officially supported by IN-CORE development team.
To add conda-forge channel to your environment, run
conda config –-add channels conda-forgeTo install pyincore package, run
conda install -c in-core pyincoreTo update pyIncore, run
conda update -c in-core pyincoreYou can find detail information at the Installation section at IN-CORE manual.
Installation with pip
Installing pyincore with pip is NOT supported by IN-CORE development team. Please use pip for installing pyincore at your discretion.
Installing pyincore with pip is only tested on linux environment.
Prerequisite
GDAL C library must be installed to install pyincore. (for Ubuntu, gdal-bin and libgdal-dev)
ipopt executable must be installed to run some analyses such as seaside CGE, joplin CGE, etc.
For developers, pre-install must be installed. If not, run brew install pre-commit or pip install pre-commit.
To install pyincore package, run
pip install pyincoreTesting and Running
Please read the Testing and Running section at IN-CORE manual.
Documentation
pyIncore documentation can be found at https://tools.in-core.org/doc/incore/pyincore.html
pyIncore technical reference (API) can be found at https://tools.in-core.org/doc/pyincore/.
Acknowledgement
This work herein was supported by the National Institute of Standards and Technology (NIST) (Award No. 70NANB15H044). This support is gratefully acknowledged. The views expressed in this work are those of the authors and do not necessarily reflect the views of NIST.
Release files for pyincore 1.22.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 | Provenance | Actions |
|---|---|---|---|---|
| pyincore-1.22.0.tar.gz | 722.2 kB | Without provenance | Details for pyincore-1.22.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyincore-1.22.0-py3-none-any.whl | Python 3 | none | any | Details for pyincore-1.22.0-py3-none-any.whl |
Total release size: 1.6 MB
Release files / pyincore-1.22.0.tar.gz
| Download URL | pyincore-1.22.0.tar.gz |
|---|---|
| Size | 722.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
07fae192ae4b015d3511367811024a23e8cec7990e27c631d0ebb9329ad8f53a
|
|
BLAKE2b-256 checksum How to use checksums |
50abff21cc1cce28d50387e841e7d58818d5361bf3a695be8b328a4dc21725ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Release files / pyincore-1.22.0-py3-none-any.whl
| Download URL | pyincore-1.22.0-py3-none-any.whl |
|---|---|
| Size | 851.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
89c1df6aa762f3097bab6395b55d73b21b67b49b39c5f107b74f7faac0ec1e65
|
|
BLAKE2b-256 checksum How to use checksums |
f0f4e4c622981f50f022d7e674e5fdecf35fbeefee84554b39c04f0747700061
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Security for pyincore 1.22.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
