Repository navigation
[codex] add neutral MTR interfaces and lifecycle scaffold - #37
Merged
Merged
Conversation
RyanL2
marked this pull request as ready for review
June 29, 2026 16:48
lucasreljic
approved these changes
Jun 30, 2026
lucasreljic
left a comment
Contributor
There was a problem hiding this comment.
Looks good just remove the addition to README.md
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
deep_msgsdeep_mtrcomponent that accepts scenes but intentionally publishes no predictionsIntentional limitation
Working MTR inference is excluded from this change. The node logs a throttled diagnostic for incoming scene requests and deliberately emits no result until per-track history, tensor packing, ONNX Runtime execution, and output decoding are implemented by the inference owner.
Validation
pre-commit run --all-filesIS_CI=1onlinux/amd64