cellpy-core
The core engine of cellpy: fast, thread-safe processing of battery-cycling raw data. Given a raw data frame (polars, native schema — or pandas via the legacy bridge), it finds all steps and cycles and builds per-step and per-cycle summary tables. It is designed to be small, schema-injected, and easy for cellpy developers to build on and extend; instrument loaders, file IO, and unit handling stay out of the core.
import polars as pl
from cellpycore import Data, make_step_table, make_summary
data = Data.from_raw_frame(pl.read_parquet("my_native_raw.parquet"))
make_step_table(data, nom_cap=1.0)
make_summary(data)
print(data.steps, data.summary)
Installing
Available on PyPI as cellpycore:
pip install cellpycore
Source: https://github.com/cellpy/cellpy-core
Documentation
Full documentation (built with Zensical, hosted on Read the Docs): https://cellpy-core.readthedocs.io/
Key pages:
- Using cellpy-core standalone (slim-consumer guide) — get step tables and per-cycle summaries from a native-schema polars frame without full cellpy.
- Harmonized raw format specification
- The Data object
- API reference (autogenerated from docstrings)
- Example notebooks
Build the docs locally with uv run --group docs zensical serve (config in
zensical.toml; notebook-regeneration instructions in docs/examples/index.md).
Developing
This project uses uv as the package manager and build tool. uv is a fast Python package installer and resolver, written in Rust.
Prerequisites
- Install
uv:
pip install uv
Development Workflow
- Install all dependencies (creates
.venvautomatically):
uv sync
- Adding new dependencies:
# Add a new package
uv add <package-name>
# Add a new development package
uv add --dev <package-name>
- Running tests:
uv run pytest
Common Commands
- Reinstall dependencies from the lock file:
uv sync - Remove a package:
uv remove <package-name> - Upgrade all packages within constraints:
uv sync --upgrade - Show the dependency tree:
uv tree
For more information about uv, visit the official documentation.
Metadata
Release files for cellpycore 0.2.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| cellpycore-0.2.5.tar.gz | 883.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cellpycore-0.2.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 976.2 kB
Release files / cellpycore-0.2.5.tar.gz
| Download URL | cellpycore-0.2.5.tar.gz |
|---|---|
| Size | 883.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f3d5b612f98ca59f56b482f2e62149ad9ef90273df759a9ea376cbea3b269829
|
|
BLAKE2b-256 checksum How to use checksums |
cd8490f17fb223c80ce5b8460bc19e5436443b057a2e06561dce66091f9ed181
|
| 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 8, 2026.
Transparency logRelease files / cellpycore-0.2.5-py3-none-any.whl
| Download URL | cellpycore-0.2.5-py3-none-any.whl |
|---|---|
| Size | 92.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e2c02c207a9c7a3f87a3b65a6dcc635d324b0f441ece6e22444a0c879ec1ee84
|
|
BLAKE2b-256 checksum How to use checksums |
0bd4f114496d86d86c4b1f0b34f82831d5cb542fc44dd0ad5a56fa7ac428b0af
|
| 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 8, 2026.
Transparency log