Skip to content

v0.22.1 - BME280 Filter Option for Analysis Scripts (2026-06-09)

What Changed?

This release adds the --include-invalid-bme280 option to check_bme280.py, check_event_rate.py, and check_coincidence.py. By default, rows where bme280_valid is False are excluded from analysis. Pass --include-invalid-bme280 to include all rows regardless of sensor validity. Also simplifies check_bme280.py by removing per-channel range checks from compute_stats, which are now handled upstream by the bme280_valid column.

What's New

Main Feature: --include-invalid-bme280 option

What it does: Filters out rows with out-of-range BME280 sensor values before analysis, using the bme280_valid column added by from_jsonl_to_parquet.py. Falls back gracefully with a warning when the column is absent (e.g. older Parquet files or JSONL input).

How to use it:

# Default: exclude invalid BME280 rows
uv run check_bme280.py ./data

# Include all rows (including out-of-range sensor values)
uv run check_bme280.py ./data --include-invalid-bme280

# Same option available in check_event_rate.py and check_coincidence.py
uv run check_event_rate.py ./data --include-invalid-bme280
uv run check_coincidence.py ./detA ./detB --include-invalid-bme280

Installation

Quick Start

# Get the release
git checkout v0.22.1

# Setup
task env:setup

# Run CLI
uv run kazunoko --help

What's Different from the Last Version?

🔧 Changed

  • check_bme280.py: added --include-invalid-bme280; removed vmin/vmax from compute_stats and BME280_CHANNELS
  • check_event_rate.py: added --include-invalid-bme280
  • check_coincidence.py: added --include-invalid-bme280 (applied to both detectors)

Is It Safe to Upgrade?

Backward Compatible: Yes

  • Default behavior changes: invalid BME280 rows are now excluded by default when bme280_valid column is present
  • Files without bme280_valid column (older data or JSONL) are unaffected — a warning is printed

Tests Passed

  • ✅ Builds without errors
  • ✅ Pre-commit hooks passed

Release Details

  • Date: 2026-06-09
  • Version: v0.22.1
  • Files Changed: 3 example scripts
  • Commits: 5354d51, 78c1532, c0fbb1f, d543963

Next Steps

No specific roadmap items at this time.