pygcc
A tool for thermodynamic calculations and geochemical database generation
pyGeochemCalc (pygcc) is a python-based program for thermodynamic calculations and producing the Geochemist's Workbench (GWB), EQ3/6, PHREEQC, TOUGHREACT, and PFLOTRAN thermodynamic database from ambient to deep Earth temperature and pressure conditions
pygcc is developed for use in the geochemical community by providing a consolidated set of existing and newly implemented functions for calculating the thermodynamic properties of gas, aqueous, and mineral (including solid solutions and variable-formula clays) species, as well as reactions amongst these species, over a broad range of temperature and pressure conditions, but is also well suited to being modularly introduced into other modeling tools as desired. The documentation is continually evolving, and more examples and tutorials will gradually be added (feel free to request features or examples; see Contributing below).
Installation
$ pip install pygcc
Examples
Check out the documentation for galleries of examples General Usage,
Integration with GWB and Integration with EQ3/6.
If you would prefer to flip through notebooks on Bitbucket, these same examples can be found in the folder docs/.
Contributing
Interested in contributing? Check out the contributing guidelines. Please note that this project is released with a Code of Conduct. By contributing to this project, you agree to abide by its terms. For more information, see the documentation, particularly the Contributing page and Code of Conduct.
License
pygcc was created by Adedapo Awolayo and Benjamin Tutolo. It is licensed under the terms of the GNU General Public License v3.0 license.
Citation
If you use pygcc for your research, citation of the software would be appreciated. It helps to quantify the impact of pygcc, and build the pygcc community. For information on citing pygcc, see the relevant docs page
Credits
pygcc Logo was designed by Yury Klyukin, pygcc was created with cookiecutter and the py-pkgs-cookiecutter template.
Metadata
Release files for pygcc 1.5.4
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 |
|---|---|---|---|---|
| pygcc-1.5.4.tar.gz | 1.6 MB | Without provenance | Details for pygcc-1.5.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pygcc-1.5.4-py3-none-any.whl | Python 3 | none | any | Details for pygcc-1.5.4-py3-none-any.whl |
Total release size: 3.4 MB
Release files / pygcc-1.5.4.tar.gz
| Download URL | pygcc-1.5.4.tar.gz |
|---|---|
| Size | 1.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a25da76ff02ba8480fab6da7abdde093c2d0796836e9f6dc0a345ca33942764b
|
|
BLAKE2b-256 checksum How to use checksums |
0c08b074d85aaa5ac816a0682c80e775f3a7768572272b3be1a48dba1e7fb2a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.2.1 CPython/3.11.9 Darwin/25.6.0
|
Release files / pygcc-1.5.4-py3-none-any.whl
| Download URL | pygcc-1.5.4-py3-none-any.whl |
|---|---|
| Size | 1.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1b30c095b28f84e0e327349371a386a11a20745785d841beff6e19cfef3596c3
|
|
BLAKE2b-256 checksum How to use checksums |
a2361bf27a2b88a10a75eda7086dbad50c75f585ab1468462baf9500d7ce3d0e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.2.1 CPython/3.11.9 Darwin/25.6.0
|
Security for pygcc 1.5.4
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.