Feat/norm stats compatibility report - #1026
Open
TheRealBaoBao wants to merge 1 commit into
Open
Conversation
TheRealBaoBao
force-pushed
the
feat/norm-stats-compatibility-report
branch
from
August 27, 2026 02:49
7a6d6a6 to
1bcc9fc
Compare
jimmyt857
removed their request for review
August 29, 2026 04:05
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a read-only CLI that compares post-transform training samples with the normalization statistics selected by an OpenPI training config.
The report identifies:
q01–q99boundsExample:
The command reuses the existing config and normalization-stat data loaders. It does not modify the dataset, statistics, model, configuration, or training path.
Motivation
When adapting π0 or π0.5 to a custom robot dataset, reused checkpoint statistics can be structurally valid but poorly matched to the transformed state/action distribution. This report makes that mismatch visible before a long fine-tuning run.
This is related to the normalization questions and failures discussed in #773, #814, and #832.
Tests
uv run pytest -q src/openpi/training/norm_stats_report_test.py— 7 passeduv run ruff check scripts/check_norm_stats.py src/openpi/training/norm_stats_report.py src/openpi/training/norm_stats_report_test.pyuv run pre-commit run --files scripts/check_norm_stats.py src/openpi/training/norm_stats_report.py src/openpi/training/norm_stats_report_test.pyuv run scripts/check_norm_stats.py --helpScope
This intentionally excludes dataset mutation, automatic normalization-stat selection, general dataset-quality checks, and changes to normalization or training behavior.
I would appreciate feedback on whether maintainers prefer this as a separate CLI or as an optional mode of
compute_norm_stats.py.