pybamm-param: PyBaMM Parameter Optimization Tool
WARNING: this package is still under development and significant API changes might take please in the upcoming releases.
This package is provides parameter optimization for PyBaMM (Python Battery Mathematical Modelling) using different optimization techniques. Examples on how to run this package can be found in the examples folder
🚀 Installing pybamm-param
Using pip
The recommended way to install pybamm-param is by installing the latest release from PyPI. This can be done running
pip install pbparam
We strongly recommend using virtual environments, see more detailed instructions below (steps 1 and 2).
Install from source
Another option is to install from source. This is not recommended, unless you want to make edits to the code.
The first step is to install virtualenv in order to create virtual environments
pip install virtualenv
The module dependencies are listed in pyproject.toml, the dependancies which are non optional which are installed with the package.
The optional dependancies are split into dev and docs. dev are used for testing and linting, docs are used for building the sphinx documentation.
Linux & MacOS
-
Create a virtual environment (this is strongly recommended to avoid clashes with the dependencies)
virtualenv --python="<path to python 3.11>" env
-
Activate the virtual environment
source env/bin/activate
The virtual environment can later be deactivated (if needed) by running
deactivate
-
Install packages into the virtual envronment
pip install -e ./[dev,docs]
Windows
-
Create a virtual environment (this is strongly recommended to avoid clashes with the dependencies)
python -m virtualenv env
-
Activate the virtual environment
env\Scripts\activate.bat
The virtual environment can later be deactivated (if needed) by running
deactivate
-
Install package from Github
pip install -e .\\[dev,docs]
🛠️ Contributing to pybamm-param
If you'd like to help us develop pybamm-param by adding new methods, writing documentation, or fixing embarrassing bugs, please have a look at these guidelines first.
Metadata
Release files for pbparam 0.1
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 |
|---|---|---|---|---|
| pbparam-0.1.tar.gz | 367.3 kB | Without provenance | Details for pbparam-0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pbparam-0.1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for pbparam-0.1-py2.py3-none-any.whl |
Total release size: 755.8 kB
Release files / pbparam-0.1.tar.gz
| Download URL | pbparam-0.1.tar.gz |
|---|---|
| Size | 367.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fa32b467aad9e28df202eb5b30c813c37a99de9108a6b1a583e996248cba1bc0
|
|
BLAKE2b-256 checksum How to use checksums |
a90c7b38616c5756b0664e692c30b472e215964214ffefcb3ac549496f0a56b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.6
|
Release files / pbparam-0.1-py2.py3-none-any.whl
| Download URL | pbparam-0.1-py2.py3-none-any.whl |
|---|---|
| Size | 388.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
5cc2128c949fefc17c468896244e2c923ed6b1bce3e667cec036248b59fd3734
|
|
BLAKE2b-256 checksum How to use checksums |
de9e723e1384236ddc09b3e0e1eec9c9bdf7a8691ca8dfa3f484e383a967c91a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.6
|
Security for pbparam 0.1
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.