You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/Learn/bskPrinciples/bskPrinciples-4.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ The recorder can also be configured to record only when the message payload cont
61
61
62
62
To turn off this mode use ``scRec.recordOnChange(False)``. The default argument of this method is ``True``.
63
63
64
-
This change-only mode is only available for message payload types that support field-wise equality comparison. Basilisk generates this support for payloads whose fields can be compared directly. If a payload contains an unknown field type, or a pointer field that cannot be compared safely, then ``recordOnChange()`` emits an error instead of silently falling back to normal interval recording. Use the regular recorder mode for these payloads, or add a ``PayloadEqualityTraits`` specialization when the payload can be compared safely.
64
+
This change-only mode is only available for message payload types that support field-wise equality comparison. Basilisk generates this support for payloads whose fields can be compared directly. If a payload contains an unknown field type, or a pointer field without explicit comparison semantics, then ``recordOnChange()`` emits an error instead of silently falling back to normal interval recording. Use the regular recorder mode for these payloads, or add a ``PayloadEqualityTraits`` specialization only when the payload comparison behavior can be defined safely. For example, ``CameraImageMsgPayload`` supports change-only recording through a shallow metadata comparison. Its image pointer is compared by address, but the pointed-to image buffer is not deep-copied or compared by the recorder.
65
65
66
66
That is all that is required to set up message recording. Next the code initializes the simulation and executes it.
- Updated message recorders so ``updateTimeInterval()`` reschedules the next recording opportunity when the minimum update time is changed between simulation runs.
2
2
- Added a message recorder mode to record only when message payload content changes after the minimum update time has elapsed.
3
3
- Added explicit errors when change-only recording is requested for payload types without supported equality comparison.
4
+
- Added shallow metadata comparison support for ``CameraImageMsgPayload`` without comparing pointed-to image bytes.
0 commit comments