-
Notifications
You must be signed in to change notification settings - Fork 263
Device metrics and control reorganization #2144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
|
We should do some sniffing to see what kind of bandwidth publishing at 1 hz uses. |
Upon further thinking, it might be all on the robot network, so we'll have to explore how NT handles that. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NPU > GPU > ?. Also consider showing bandwidth there as well, although that would have to be implemented as a metric.
On Rubik, GPU accel shows as unknown. In this case, the field should be hidden.
Cleans up the settings page by doing the following:
Before and after sample:
