processbehavior 0.4.0__tar.gz → 0.6.0__tar.gz

{processbehavior-0.4.0 → processbehavior-0.6.0}/CHANGELOG.md

@@ -7,6 +7,181 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.6.0] - 2026-11-07
+
+### Added
+- **`validation/truth_report.py`.** It reports how closely the methods, as implemented, recover
+  answers known by construction: the PM INERT pure-noise data under all six missing-data
+  patterns, and Dr. Bishop's known-effects data. It is a report, not a gate.
+- **Two design-report lines.** In ADS 3 the report says how many cells hold a single reading,
+  since one is enough to switch R2 for the whole study to the differencing method. When
+  conditions were observed in different periods, it says how far apart their average periods
+  are, since condition effects then average over different times.
+- **`LossResult.reference`: what each loss part shows from noise alone.** The PDC, Time and
+  Interaction parts average squared deviations of estimated means, so with no effects each is
+  still above zero (about 14% interaction on the PM INERT pure-noise data). `reference` gives
+  the expected value of each under no effects for the study's own layout, exact for any
+  pattern of occupied cells and cell sizes, and the printed result shows it as a share of the
+  total. It is in `as_dict()` too. In ADS 2/3 the interaction is a remainder, so its reference
+  is `None`. Loss values are unchanged.
+- **Windowed capability shows the window's own noise.** `CapabilityResult.window_sigma_r2` is
+  σ̂ from the window's R2 values, printed beside the full-study `sigma_hat_r2` that the
+  potential indices use. It appears only on windowed results; the default result is unchanged.
+- **A Provenance sheet in Excel exports.** Written with the Summary sheet: library version,
+  time written, variables, input rows and rows analysed, design states, and a SHA-256
+  fingerprint of the analysed values. `AnalysisDataSet.n_input_rows` holds the input row count.
+- **`validation/chance_signals.py`.** It reports how often charts signal on pure noise: X/mR
+  charts under the default rules (and mR with all eight), and the R3-R5 effect charts, whose
+  limits sit between about 2.2 and 4.4 standard deviations of the plotted points depending on
+  the chart and layout. A report, not a gate; its tables are in the WECO rules reference and
+  the residuals guide.
+
+### Changed
+- **Manual citations follow the 11-7 edition.** Dr. Bishop's manual of 2026-11-07 has 20 chapters
+  (chapters 7 and up are one lower than before) and dot-numbered captions; every equation and
+  chapter citation in the code, docs and tests now uses its numbering, in the hyphen form the
+  manual repository checks ("11-7 manual Eq 13-8"). Seven equations it removed are cited by
+  their replacements. No behaviour changes.
+- **mR charts check Rule 1 only by default.** Wheeler reads the moving range chart for points
+  above its upper limit. The zone and run rules assume symmetric, independent points, and
+  successive moving ranges share a reading, so with all eight rules on, 95% of 100-point
+  pure-noise mR charts showed a signal (59% with Rule 1 alone). X charts still check all eight.
+  `rules='all'` restores the old behaviour. Signal counts on mR charts drop.
+- **The validation page says what is compared with VAS.** It claimed "every analytical
+  output"; the gate compares chart centres and limits, capability indices and loss shares. The
+  page now lists what is not compared (residual values one by one, signals, staged charts,
+  effects tables, calibrations, capability windows, the design report) and points to the truth
+  report. The `detect_signals()` docstring no longer says Rules 1-4 are the default.
+
+### Fixed
+- **Tutorial outputs match the library again.** The docs site shows each notebook's saved outputs,
+  and eight tutorials had drifted: limits from before 0.4.0 in the Design-State-1 analysis, flat
+  limits where they now vary by subgroup size in the reference validation, older process means and
+  signal counts. All were re-executed. The Derived Variables tutorial, saved without outputs, now
+  shows them. Prose that the new outputs contradicted was corrected; the Bishop reference values in
+  the reference validation now quote his VAS rerun of 13 October 2026.
+- **The factor x time interaction chart draws its lines in factor order on every machine.** It
+  sorted by time with an unstable sort, so the legend order, and the colour each line got, depended
+  on the numpy version.
+- **Three signal rules now match their definitions.** Rule 5 (trend) fired only on 7 rising or
+  falling points, not 6; Rule 6 (oscillation) only on 15 alternating points, not 14; and Rule 2
+  counted only points in Zone A, leaving out points beyond 3σ, which Western Electric and Wheeler
+  count as "beyond 2σ". The docs, the rule descriptions and the minimum-observation table already
+  said 6, 14 and "Zone A or beyond". X charts may show slightly more signals; on 100 points of
+  pure noise, the share with a signal under the eight default rules rises from 70% to 79%.
+- **The WECO rules page gives correct chance rates.** Six of its eight per-rule false-alarm rates
+  were wrong (for example 0.003% for 15 points hugging the centre, where it is 0.33%), and its
+  rule-set table had no source. The rates are now exact per-window figures, the table is measured
+  by `validation/chance_signals.py`, and the wording no longer says a signal is "almost certainly"
+  a special cause.
+- **Commas in numbers stored as text are no longer misread.** A comma was removed wherever it
+  appeared, so a decimal comma such as `10,4` became 104; and a lone `10,4` in a column of plain
+  numbers silently became missing. Commas are now read one way per column: as decimal points
+  when the column has no `.` and some comma is not a thousands group, otherwise only as
+  separators between groups of three digits. Any other comma value becomes missing and is named.
+- **The numeric-cleaning warning says what happened.** It counts the values actually reformatted
+  (it used to count every value in the column), gives examples, says when commas were read as
+  decimal points, and names the values that could not be read. A column of plain numeric strings
+  no longer warns.
+- **A factor nested in time is named.** When every time period holds one level of a factor (a
+  stage, a before/after split), the design report says so beside the empty-cell count, and
+  `loss_function()` warns that the PDC and Time parts both contain that factor's effect, so the
+  decomposition counts it more than once. It points to staged charts instead. Loss values are
+  unchanged.
+- **The design report no longer says "Complete structure" when there is nothing to compare.**
+  Without a sampling plan the structure line reads "Not checked (no sampling plan supplied)". It
+  used to say "Complete structure", even beside hundreds of empty cells.
+- **Potential capability says why it is unavailable.** A study with no factors (such as one
+  stream of subgroups) or no time variable got "R2 residuals not available (ADS 1)". It now
+  says that Cp/Cpk use the VAS R2 residuals, which need at least one factor (or a time
+  variable), and that the study has none.
+
+### Removed
+- **`examples/` and `validation/effects_visualization.ipynb`.** These demos predated the 0.2.0
+  API (`ProcessDataFrame`, `study.sds`, moved data files) and no longer ran; nothing linked to
+  them. The maintained, CI-executed tutorials are in `docs/tutorials/`.
+- **`tests/test_bishop_reference.py`.** Its one test compared residual values with a workbook
+  of Dr. Bishop's that is not in the repository, so it skipped on every run. Residual charts are
+  still compared with VAS through their limits.
+
+### CI / Infrastructure
+- **CI checks that docs notebooks match their saved outputs.** `scripts/refresh_notebooks.py`
+  re-executes the docs notebooks; with `--check` (in CI, replacing the nbmake run) it fails when a
+  notebook no longer runs or what a reader would see has changed, comparing printed text, tables
+  and each figure's data and labels. The `[test]` extra now needs nbclient, nbformat and ipykernel
+  instead of nbmake.
+- **Python 3.14 is tested** on Ubuntu and Windows, in CI and in the release gate, and listed in
+  the package classifiers.
+- **The truth report runs in CI.** `validation/truth_report.py` runs on every push (Ubuntu,
+  Python 3.13) and its output is kept as the `truth-report` artifact.
+
+## [0.5.0] - 2026-10-29
+
+This release adds staged (phased) Xbar and S charts, computed per stage as Dr. Bishop
+specified (2026-10-18), with `phase_statistics()` for the numbers behind each stage on both
+chart families. A column of values with no time is now charted in the order received.
+
+### Added
+- **A bare response is charted in the order received.** `formulate(response=...)` with no time,
+  factors or plan used to be refused. The values are now numbered 1..N in an `Observation` column
+  (the same numbers as `obs_id`) and the study is exactly the one `time='Observation'` gives: a
+  single stream, ADS 2, X/mR, sigma from N − 1 moving ranges. An NA response keeps its place as an
+  empty cell. The design report adds `Time: received order (no time column given)`. If the data
+  already has an `Observation` column, formulate asks you to pass it as `time=` or rename it (#129).
+- **Phased limits on Xbar and S charts.** `execute(chart='Xbar', phased=True)` gives each factor
+  combination its own centre line and limits on one chart, drawn as stepped lines with a divider at
+  each change, the way phased X/mR already does for its lanes. Each phase is computed as a separate
+  Xbar/S analysis, exactly as `by=[time]` computes one chart per condition: the centre is the mean of
+  the phase's subgroup means, with its own S-bar and sigma-hat (10-12 manual Eqs 11-5, 11-8, 11-9,
+  11-16, 11-17). `by=['stage', time]` pools the other factors into the subgroup and phases on the
+  stage; the centre is then the mean of the pooled subgroup averages, as Dr. Bishop specified
+  (2026-10-18). On Wheeler's four-cavity thickness data the per-cavity centres and limits match
+  Minitab's staged Xbar-S chart. Residual values, calibrations and `by=[time]` are refused with
+  messages that say what to use instead; a phase with no replicated subgroup keeps its points without
+  limits and is named in `metadata['insufficient_phases']`. (#144)
+- **`result.phase_statistics(chart, stratum=None)`.** One row per phase of a phased chart. Xbar/S:
+  `phase`, `subgroups`, `N`, `center`, `s_bar`, `sigma_hat`, `lpl`, `upl`. X/mR: `phase`, `points`,
+  `center`, `mR_bar`, `lpl`, `upl`, per stratum on a stratified chart (`stratum=`, or through
+  `focus()`). (#144)
+- **Docs: a Staged Charts tutorial**, executed in CI. On the bundled coffee-shop data, with the
+  stage derived by one `.bin()` call, it compares one set of limits with limits per stage on Xbar
+  and S, reads `phase_statistics()`, puts every reading on a phased X/mR chart, and pools or splits
+  a second factor. The chart-types guide's staged example now runs as written, and its pooling
+  example uses a study that has a factor to pool. (#144)
+
+### Changed
+- **`formulate(response=..., factors=[])` with no time is the same study.** It used to treat the
+  whole column as one replicated cell: ADS 1, a recommended one-point Xbar chart, the "within-cell
+  replication" series-length line, and an X chart plotted against the response values. Its chart
+  tables now start with `Observation` (#129).
+- **Xbar and S chart data carry `n`.** `get_chart('Xbar')` / `get_chart('S')`, and the Excel chart
+  sheets, gain an `n` column after the subgroup label. Unstratified Xbar/S metadata names the label
+  column as `group_col` (#143).
+- **Lane dividers on an Xbar or S chart are labelled with the phase.** These charts have no time
+  column and so no cell band under the axis, which is where X charts name their lanes. (#144)
+- **Phased chart data and `chart_table` carry a `phase` column** (the lane label) after the subgroup
+  label, on X/mR as well as Xbar/S. Phased Xbar/S metadata carries `phase_by`, `lane_boundaries`,
+  `single_point_phases` and `insufficient_phases`; `n_avg` is not reported on a phased chart, whose
+  `n_mode='average'` is applied per phase, so the per-phase mean size is `phase_statistics(chart)['N']`.
+  (#144)
+
+### Fixed
+- **Xbar/S `chart_table` keeps the subgroup label and `n` on every `by=`.** With a `by=` other than
+  time alone, such as a pooled subset (`by=['FACTOR 1', time]`), all factors, factors without time,
+  or one factor, the table dropped both columns, so a row couldn't be traced to its subgroup and
+  stepped limits went unexplained. `n` is now the aggregation's own count, which covers every cell
+  a pooled subgroup spans. This also corrects one row on residual charts whose limits rest on R2
+  (R1, R3, R4, R5) in a design with singletons: the stream's first cell, where R2 is undefined at
+  the first value, showed its cell size, not the one-fewer values its S and limits use. Limits,
+  centres and statistics are unchanged (#143).
+- **`execute()` no longer documents `phased=True` as requiring `by=[]`.** Stratified phasing of X/mR
+  (`by=['factor 1'], phased=True`) has been accepted since 75bcdd1; the docstring never caught up. (#144)
+- **The companion mR of a phased X chart reports `single_point_phases`.** Only the solo mR did. (#144)
+- **X/mR lane order honours an ordered pandas Categorical factor.** A stage column with categories
+  `before < after` already ordered the Xbar/S subgroups that way, but the canonical row order sorted
+  the raw labels, so X/mR lanes, phases and `strata` came out `after, before`. The canonical sort now
+  uses an ordered Categorical's category codes; plain string and numeric factors sort as before. (#144)
+
 ## [0.4.0] - 2026-10-14
 
 This release aligns the library with Bishop's VAS documentation manual dated 10-12-2026 and
@@ -1114,7 +1289,9 @@ and may change between minor versions until 1.0.
 - `natsort >= 8.0`
 - `plotly >= 5.18, < 7`
 
-[Unreleased]: https://github.com/cnicholas/processbehavior/compare/v0.4.0...HEAD
+[Unreleased]: https://github.com/cnicholas/processbehavior/compare/v0.6.0...HEAD
+[0.6.0]: https://github.com/cnicholas/processbehavior/compare/v0.5.0...v0.6.0
+[0.5.0]: https://github.com/cnicholas/processbehavior/compare/v0.4.0...v0.5.0
 [0.4.0]: https://github.com/cnicholas/processbehavior/compare/v0.3.3...v0.4.0
 [0.3.3]: https://github.com/cnicholas/processbehavior/compare/v0.3.2...v0.3.3
 [0.3.2]: https://github.com/cnicholas/processbehavior/compare/v0.3.1...v0.3.2

{processbehavior-0.4.0 → processbehavior-0.6.0}/CITATION.cff

@@ -17,7 +17,7 @@ authors:
 repository-code: "https://github.com/cnicholas/processbehavior"
 url: "https://cnicholas.github.io/processbehavior/"
 license: Apache-2.0
-version: 0.2.0
+version: 0.6.0
 keywords:
   - statistical process control
   - process behavior charts

{processbehavior-0.4.0 → processbehavior-0.6.0}/CONTRIBUTING.md

@@ -74,13 +74,7 @@ The full test suite is the gate: if it fails, the change is not ready.
 The file `validation/PBTESTDATABASE_T100.csv` is ground-truth Minitab output
 for DS 1–6 from Bishop's reference materials. Numerical changes that touch
 residuals (R1–R5), DS detection, limit calculations, or variance
-decomposition must keep the relevant Bishop-reference tests green:
-
-```bash
-pytest tests/test_bishop_reference.py -v   # skips unless Bishop's residual workbooks are present
-```
-
-There is also a full end-to-end check that compares every chart center, control
+decomposition must keep the end-to-end check green. It compares every chart center, control
 limit, capability index and loss component against Bishop's VAS runs for the
 10-12-2026 manual (PM SDS 1–6, PM INERT, his known-effects data and the Medicare data):
 
@@ -97,10 +91,24 @@ summary.
 If a Bishop check fails after your change, the change is wrong — not the
 reference.
 
+## Docs notebooks
+
+The docs site shows each notebook's saved outputs; it does not run them. After a change that
+alters what a notebook prints or plots, refresh the saved outputs:
+
+```bash
+python scripts/refresh_notebooks.py                 # every docs notebook
+python scripts/refresh_notebooks.py docs/tutorials/signal-detection.ipynb
+```
+
+CI runs `python scripts/refresh_notebooks.py --check` and fails when a notebook no longer runs or
+no longer matches its saved outputs. Then read the text around any changed output: the check
+compares outputs, not prose.
+
 ## Citing the methodology
 
 Code and docs cite Bishop's VAS documentation manual by edition and equation number:
-`(10-12 manual Eq 14-8)`, `Eqs 14-4..14-13`, `Eqs 11-16/17`. Name the edition once per file and use
+`(11-7 manual Eq 13-8)`, `Eqs 13-4..13-13`, `Eqs 10-16/17`. Name the edition once per file and use
 the chapter-number form; `tests/test_manual_citations.py` checks both. The citations are read
 against the manual itself, so a new edition reports every place in the library whose equation
 changed or moved.

{processbehavior-0.4.0 → processbehavior-0.6.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: processbehavior
-Version: 0.4.0
+Version: 0.6.0
 Summary: Python-native Process Behavior & Control Charts (spec-driven SPC with tidy outputs)
 Project-URL: Homepage, https://github.com/cnicholas/processbehavior
 Project-URL: Repository, https://github.com/cnicholas/processbehavior
@@ -21,6 +21,7 @@ Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
 Classifier: Topic :: Scientific/Engineering
 Classifier: Topic :: Scientific/Engineering :: Information Analysis
 Classifier: Typing :: Typed
@@ -33,12 +34,14 @@ Requires-Dist: typing-extensions>=4.0; python_version < '3.11'
 Provides-Extra: dev
 Requires-Dist: filelock>=3.20.3; extra == 'dev'
 Requires-Dist: ipykernel; extra == 'dev'
+Requires-Dist: ipykernel>=6; extra == 'dev'
 Requires-Dist: jupyter-book>=2.0; extra == 'dev'
 Requires-Dist: kaleido>=0.2; extra == 'dev'
 Requires-Dist: lxml>=6.1.0; extra == 'dev'
 Requires-Dist: mypy>=1.10; extra == 'dev'
+Requires-Dist: nbclient>=0.10; extra == 'dev'
 Requires-Dist: nbconvert>=7.17.1; extra == 'dev'
-Requires-Dist: nbmake>=1.5; extra == 'dev'
+Requires-Dist: nbformat>=5.10; extra == 'dev'
 Requires-Dist: openpyxl>=3.1; extra == 'dev'
 Requires-Dist: orjson>=3.11.6; extra == 'dev'
 Requires-Dist: pillow>=12.2.0; extra == 'dev'
@@ -73,7 +76,9 @@ Requires-Dist: pre-commit>=3.7; extra == 'lint'
 Requires-Dist: ruff>=0.5; extra == 'lint'
 Requires-Dist: virtualenv>=20.36.1; extra == 'lint'
 Provides-Extra: test
-Requires-Dist: nbmake>=1.5; extra == 'test'
+Requires-Dist: ipykernel>=6; extra == 'test'
+Requires-Dist: nbclient>=0.10; extra == 'test'
+Requires-Dist: nbformat>=5.10; extra == 'test'
 Requires-Dist: openpyxl>=3.1; extra == 'test'
 Requires-Dist: pyarrow>=14.0; extra == 'test'
 Requires-Dist: pytest-cov>=5; extra == 'test'
@@ -108,6 +113,22 @@ pip install "processbehavior[images]"  # kaleido, for static plot images
 
 ## Quickstart
 
+A column of values, charted in the order received, is an X/mR chart in two calls:
+
+```python
+import pandas as pd
+import processbehavior as pb
+
+df = pd.DataFrame({'weight': [50.2, 49.8, 50.5, 50.1, 49.6, 50.9, 50.3, 49.9, 50.4, 50.0, 49.7, 50.6]})
+
+study = pb.formulate(df, response='weight')   # no time column: rows are numbered 1..N as 'Observation'
+result = study.execute(companion=True)        # X chart with its mR companion
+print(result.statistics('X'))                 # {'N': 1, 'center': 50.167, 'lpl': 48.619, 'upl': 51.714}
+result.plot()
+```
+
+When the data has a time order, factors, or both, name them. The design state routes the analysis:
+
 ```python
 import processbehavior as pb
 
@@ -149,6 +170,20 @@ The whole pipeline is one expression when you don't need the intermediate object
 pb.formulate(df, response='y', factors=['factor 1'], time='time').execute().plot()
 ```
 
+A process that changed on purpose gets its own limits for each stage with `phased=True`:
+
+```python
+import processbehavior as pb
+
+# The bundled coffee-shop data: a new machine in week 8, a new POS in week 12, new baristas from week 14
+pbd = pb.load_coffee_shop().bin('week', method='breaks', breaks=[8, 12, 14],
+                                bin_labels=['baseline', 'new machine', 'new POS', 'new baristas'],
+                                label='stage')
+staged = pbd.formulate(response='wait_sec', factors=['stage'], time='date').execute(chart='Xbar', phased=True, companion=True)
+staged.phase_statistics('Xbar')   # one row per stage: center, S-bar, sigma-hat, limits
+staged.plot(chart='Xbar', title='Wait time: limits per stage')
+```
+
 Use `pb.ProcessBehavior(df)` directly when you want the fluent derived-variable verbs
 (`.transform(...)`, `.bin(...)`), which attach before formulating. With that object in hand,
 `pbd.cols.<column_name>` provides IDE auto-completion for column references.
@@ -251,7 +286,8 @@ The full report renders to `validation/e2e_bishop_report.html`.
 - **Variance decomposition**: R1-R6 residuals for factorial designs
 - **Effects analysis**: Main effects, time effects, and interaction effects
 - **Stratified charts**: Automatic per-stratum limits for grouped individual data
-- **Signal detection**: all eight Western Electric rules on X/mR; Rule 1 (3-sigma) on Xbar/S, where the run- and zone-based rules need a time order that subgroup comparisons don't have
+- **Staged charts**: `phased=True` gives each stage its own center and limits on X/mR and Xbar/S; `phase_statistics()` returns the numbers behind the steps
+- **Signal detection**: all eight Western Electric rules on X charts; Rule 1 (3-sigma) on mR, Xbar and S, where the run- and zone-based rules don't fit: subgroup comparisons have no time order, and successive moving ranges share a reading
 - **Beyond the charts**: capability indices (Cp/Cpk/Pp/Ppk), Taguchi loss decomposition, and maximum-information analysis — validated in the same Bishop-reference CI gate
 - **IDE support**: Column auto-completion via `ProcessBehavior(df).cols`
 - **Self-diagnostic errors**: Helpful messages that say what's available and how to fix it

{processbehavior-0.4.0 → processbehavior-0.6.0}/README.md

@@ -25,6 +25,22 @@ pip install "processbehavior[images]"  # kaleido, for static plot images
 
 ## Quickstart
 
+A column of values, charted in the order received, is an X/mR chart in two calls:
+
+```python
+import pandas as pd
+import processbehavior as pb
+
+df = pd.DataFrame({'weight': [50.2, 49.8, 50.5, 50.1, 49.6, 50.9, 50.3, 49.9, 50.4, 50.0, 49.7, 50.6]})
+
+study = pb.formulate(df, response='weight')   # no time column: rows are numbered 1..N as 'Observation'
+result = study.execute(companion=True)        # X chart with its mR companion
+print(result.statistics('X'))                 # {'N': 1, 'center': 50.167, 'lpl': 48.619, 'upl': 51.714}
+result.plot()
+```
+
+When the data has a time order, factors, or both, name them. The design state routes the analysis:
+
 ```python
 import processbehavior as pb
 
@@ -66,6 +82,20 @@ The whole pipeline is one expression when you don't need the intermediate object
 pb.formulate(df, response='y', factors=['factor 1'], time='time').execute().plot()
 ```
 
+A process that changed on purpose gets its own limits for each stage with `phased=True`:
+
+```python
+import processbehavior as pb
+
+# The bundled coffee-shop data: a new machine in week 8, a new POS in week 12, new baristas from week 14
+pbd = pb.load_coffee_shop().bin('week', method='breaks', breaks=[8, 12, 14],
+                                bin_labels=['baseline', 'new machine', 'new POS', 'new baristas'],
+                                label='stage')
+staged = pbd.formulate(response='wait_sec', factors=['stage'], time='date').execute(chart='Xbar', phased=True, companion=True)
+staged.phase_statistics('Xbar')   # one row per stage: center, S-bar, sigma-hat, limits
+staged.plot(chart='Xbar', title='Wait time: limits per stage')
+```
+
 Use `pb.ProcessBehavior(df)` directly when you want the fluent derived-variable verbs
 (`.transform(...)`, `.bin(...)`), which attach before formulating. With that object in hand,
 `pbd.cols.<column_name>` provides IDE auto-completion for column references.
@@ -168,7 +198,8 @@ The full report renders to `validation/e2e_bishop_report.html`.
 - **Variance decomposition**: R1-R6 residuals for factorial designs
 - **Effects analysis**: Main effects, time effects, and interaction effects
 - **Stratified charts**: Automatic per-stratum limits for grouped individual data
-- **Signal detection**: all eight Western Electric rules on X/mR; Rule 1 (3-sigma) on Xbar/S, where the run- and zone-based rules need a time order that subgroup comparisons don't have
+- **Staged charts**: `phased=True` gives each stage its own center and limits on X/mR and Xbar/S; `phase_statistics()` returns the numbers behind the steps
+- **Signal detection**: all eight Western Electric rules on X charts; Rule 1 (3-sigma) on mR, Xbar and S, where the run- and zone-based rules don't fit: subgroup comparisons have no time order, and successive moving ranges share a reading
 - **Beyond the charts**: capability indices (Cp/Cpk/Pp/Ppk), Taguchi loss decomposition, and maximum-information analysis — validated in the same Bishop-reference CI gate
 - **IDE support**: Column auto-completion via `ProcessBehavior(df).cols`
 - **Self-diagnostic errors**: Helpful messages that say what's available and how to fix it

{processbehavior-0.4.0 → processbehavior-0.6.0}/processbehavior/__init__.py

@@ -47,7 +47,7 @@ its ``.sds`` field. Internally some modules still use the legacy "SDS"
 prefix (e.g. ``sds_detector.py``); the model itself is three-state.
 """
 
-__version__ = '0.4.0'
+__version__ = '0.6.0'
 
 # Result object
 from processbehavior.analysis_result import AnalysisResult