Skip to main content

BDF-first converters for battery cycler data.

Project description

Battery Data Standard

battery-data-standard is a Python library and command-line tool for converting battery cycler exports into a consistent BDF-style tabular representation. It is intended for laboratories, battery test teams, and data pipelines that need a repeatable path from vendor files to analysis-ready CSV or Parquet outputs.

The package is vendor-neutral. It is not certified by any cycler vendor or by the Battery Data Alliance. Adapter support describes behavior implemented and validated by this project; users should verify representative exports from their own cycler software before using the package in automated production workflows.

Installation

Python 3.12 or newer is required.

pip install battery-data-standard

Optional extras are available for additional input formats:

pip install "battery-data-standard[yaml]"
pip install "battery-data-standard[matlab]"

The package installs the bds command and exposes both the full package name and a short import alias:

import battery_data_standard as bds
# or
import bds

Scope

The package provides:

  • conversion of supported battery cycler time-series exports to BDF-style CSV or Parquet files;
  • conversion of supported EIS tables to a standardized EIS table;
  • cycler detection, data-kind detection, validation, conversion reports, and batch manifests;
  • archive-aware batch conversion for directories, zip archives, and tar archives;
  • optional profile files for lab-specific column naming.

The package does not upload source data to an external service. It reads local files and writes local outputs.

Command-Line Usage

Inspect the installed version:

bds --version

Detect a cycler export:

bds detect raw_export.csv

Convert a time-series file:

bds convert raw_export.csv normalized.bdf.csv --cycler auto --report report.json

Validate a converted file:

bds validate normalized.bdf.csv

Convert a directory or archive and write a JSONL manifest:

bds batch raw_exports normalized_exports --recursive --manifest manifest.jsonl
bds batch raw_exports.zip normalized_exports --manifest manifest.jsonl

Inspect runtime adapter metadata and the pinned schema:

bds formats
bds inspect-schema

Python API

Read a supported time-series export into a Polars dataframe:

import bds

df = bds.read("raw_export.csv", cycler="auto")

Use an explicit cycler when the source format is known:

df = bds.read("arbin_export.csv", cycler="arbin")

Convert a file and keep the conversion report:

report = bds.convert(
    "raw_export.csv",
    "normalized.bdf.csv",
    cycler="auto",
    report_path="report.json",
)

Read data and report information in memory:

df, report = bds.read_with_report("raw_export.csv", cycler="auto", strict=False)

Create step-level or cycle-level summaries from a normalized dataframe:

steps = bds.summarize_steps(df)
cycles = bds.summarize_cycles(df)

Output Model

The converter standardizes supported cycler exports into a time-series table. Every successful BDF time-series conversion must contain three required fields:

Field Unit Description
Test Time / s s Elapsed time from the start of the test.
Voltage / V V Measured cell or channel voltage.
Current / A A Measured current.

Additional fields, such as cycle number, step number, capacity, energy, temperature, power, and internal resistance, are included when they are available in the source file.

The internal dataframe uses canonical BDF-style labels. Exported CSV and Parquet files use easier-to-read labels, for example Test Time (s), Voltage (V), and Current (A).

Supported Format Families

The package includes adapters for NEWARE, Arbin, Maccor, BioLogic, Novonix, BaSyTec, LANDT, and generic tabular exports. Generic readers support delimited text, Excel, MATLAB, and Parquet inputs where the file contains or can be mapped to time, voltage, and current columns.

BioLogic .mpt text exports are supported. Binary BioLogic .mpr files are not supported; export .mpt text files from EC-Lab before conversion.

See docs/supported-formats.md for adapter scope and support-tier definitions.

EIS Data

EIS files use a separate standardized table from row-wise BDF time-series data. Use EIS-specific commands or API functions for known impedance files:

bds detect-kind impedance.csv
bds convert-eis impedance.csv normalized.eis.csv
eis = bds.read_eis("impedance.csv")
report = bds.convert_eis("impedance.csv", "normalized.eis.csv")

read() and convert() are time-series entry points. batch and batch_convert() can route mixed directories and archives that contain time-series files, EIS files, and unsupported helper files.

Profiles

Profiles map lab-specific column names to canonical column names. JSON profiles are supported by the base installation. YAML profiles require the yaml extra.

{
  "columns": {
    "Test Time / s": "time_seconds",
    "Voltage / V": "cell_voltage",
    "Current / A": "cell_current"
  }
}

Use a profile from the CLI:

bds convert lab_export.csv normalized.bdf.csv --cycler generic --profile profile.json

Current Sign Convention

The default current convention is charge-positive and discharge-negative.

Use --current-sign preserve to retain the source sign convention, or --current-sign discharge-positive when a downstream workflow requires discharge-positive current. When a source file contains a recognizable charge/discharge status column, adapters use it to normalize current sign more explicitly.

Validation and Reports

Every conversion returns or writes a machine-readable report with schema version, row count, columns, validation status, warnings, provenance, adapter metadata, and repair operations.

Strict validation is enabled by default. Repairable issues are reported with the default repair_policy="warn". Use repair_policy="repair" or --repair-policy repair only when the pipeline explicitly accepts the documented normalizations.

Documentation

Public documentation is in the docs directory:

License and Attribution

This project is distributed under the MIT License.

The package targets a BDF-oriented output schema inspired by the Battery Data Format project from the Battery Data Alliance. This project is not an official Battery Data Alliance project and is not certified by the Battery Data Alliance.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

battery_data_standard-0.1.0.tar.gz (69.4 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

battery_data_standard-0.1.0-py3-none-any.whl (73.4 kB view details)

Uploaded Python 3

File details

Details for the file battery_data_standard-0.1.0.tar.gz.

File metadata

  • Download URL: battery_data_standard-0.1.0.tar.gz
  • Upload date:
  • Size: 69.4 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.10

File hashes

Hashes for battery_data_standard-0.1.0.tar.gz
Algorithm Hash digest
SHA256 c8f41df1ed7eaeae22e0b075e626417bd4eeccf73c0f87410ad3268fed57bf83
MD5 8f45bcffd02e267fee5a9d8ead3a0a69
BLAKE2b-256 917b91142819a2552b2e90b9009bf5d20f4e5750e86485734fa9e0372c9100b1

See more details on using hashes here.

File details

Details for the file battery_data_standard-0.1.0-py3-none-any.whl.

File metadata

File hashes

Hashes for battery_data_standard-0.1.0-py3-none-any.whl
Algorithm Hash digest
SHA256 5a695af3664cd77249dd69f8bed2cc751ce4dd914dfe7675008906956329eaaf
MD5 18fb2cd202601b9e09b0b1d7f0b6f870
BLAKE2b-256 d19921fb82f84fdf18c081d9d81576431c8e037c47dd458321651fa7cb646519

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page