Repository navigation
Conversation
cboulay
marked this pull request as draft
November 16, 2026 07:52
This was referenced Nov 16, 2026
Merged
Merged
This branch was successfully deployed
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.
Stacked on #277 (
AxisArray.segment). This is the new top of the stack.What
AxisArraygainsconfig_id: int = 0, a digest of the stream's configuration. It travels with the message, including over shared memory, so a downstream stage can decide whether to reset with one integer compare instead of hashing the layout of every message.0means "not declared".Together with
segment(#277) this separates two questions:segmentchanges when there is a break in the data (a measured gap).config_idchanges when the stream itself is different (layout, dtype, axes, units).API
compute_config_id(message)digests: the key,dims,stream_dim, the dtype, the array backend (numpy, mlx, ...), and for each non-stream dim its name, length and axis (unit / gain / offset for aLinearAxis, thefingerprintfor aCoordinateAxis). For the stream dim only unit and gain are digested.attrs, the length of the stream dim, and the stream axis offset. These change per message.chain_config_id(parent, *parts)derives a new id from an input id plus whatever a stage adds (its settings, a device id, scaling). numpy scalars and arrays inpartsare converted to plain Python values first, sonp.float64(2.0)and2.0give the same id.array_backend(data)names the array library of a data buffer.0or-1.Details
str, sonp.str_("x")and"x"agree.Tests
tests/messages/test_axisarray.py: what does and does not change the id, stability across key and scalar types, chaining, and the round trip through pickling.Downstream
ezmsg-baseproc uses
config_idto decide resets and ezmsg-sigproc and the source packages stamp it. Those PRs follow and need a pre-release of this stack.