Fix event equality by excluding zero_crossing_id from comparison #4045
+12
−6
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
This PR fixes issue #3907 where systems with identical continuous events were no longer considered equal after the v10 update.
The root causes were:
zero_crossing_idwas generated viagensym()for each callback, making otherwise identical callbacks unequalAffectSystemequality usedisequalfor its internalSystem, butSystemuses reference equality (===)Changes:
zero_crossing_idfromAbstractCallbackequality and hash (it's an internal identifier, not semantically meaningful for equality)isapproxinstead ofisequalfor system comparison inAffectSystemequality (sinceSystemhas a properisapproximplementation for structural comparison)AffectSystembased on semantic content (equations, observed) rather than system identityBefore this fix:
After this fix:
Test plan
isapproxFixes #3907
🤖 Generated with Claude Code