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
Currently, YAGSL publishes poses and swerve states to NetworkTables using double arrays. A key advantage of the WPILib struct format is that it communicates data type (pose/swerve state/etc) and units (radians/degrees). The 2025 version of AdvantageScope will take advantage of this metadata to make it easier to mix and match fields for visualization, such as allowing 2D and 3D poses to be used interchangeably without user input.
WPILib is planning to switch to struct publishing for Field2d, so we've agreed to deprecate the double array formats in AdvantageScope this year (it will display a warning when they are used, and you need to manually select the data type and units). While data from YAGSL will continue to be accessible, upgrading to struct would ensure that users have the most seamless experience moving forward.
I see the telemetry class is currently using SmartDashboard put methods. To access struct publishing you'll probably need to switch to the full NT publishing API for the relevant fields (pose and swerve state fields). In regard to dashboard compatibility, see Gold872/elastic-dashboard#91.
The text was updated successfully, but these errors were encountered:
Currently, YAGSL publishes poses and swerve states to NetworkTables using double arrays. A key advantage of the WPILib struct format is that it communicates data type (pose/swerve state/etc) and units (radians/degrees). The 2025 version of AdvantageScope will take advantage of this metadata to make it easier to mix and match fields for visualization, such as allowing 2D and 3D poses to be used interchangeably without user input.
WPILib is planning to switch to struct publishing for
Field2d
, so we've agreed to deprecate the double array formats in AdvantageScope this year (it will display a warning when they are used, and you need to manually select the data type and units). While data from YAGSL will continue to be accessible, upgrading to struct would ensure that users have the most seamless experience moving forward.I see the telemetry class is currently using
SmartDashboard
put methods. To access struct publishing you'll probably need to switch to the full NT publishing API for the relevant fields (pose and swerve state fields). In regard to dashboard compatibility, see Gold872/elastic-dashboard#91.The text was updated successfully, but these errors were encountered: