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
Is your feature request related to a problem? Please describe.
The log file starts before the match and ends after the match ends, but usually, only the period of the match itself (or periods within it) are interesting.
Describe the solution you'd like
Add the time period filter from the odometry (etc.) tabs to the whole log file.
Describe alternatives you've considered
While this can be done using the "locking" to auto/teleop start/end behavior of the cursor, another button will be more convenient IMO.
The text was updated successfully, but these errors were encountered:
There are filtering options for the heatmap and statistics tab because both are summarizing data without regard to timing. Every other tab is based on time-series data, with relevant options for zooming to the relevant data and playing it back. I'm not sure exactly what you're looking for regarding navigation of time-series data given the options that are already provided.
I was thinking about some dropdown menu that will be available for all tabs:
So if "Enabled" is selected for the line graph it will lock the earliest time to the match start timestamp and the latest time to the match end time. In the console tab, it will only show messages logged during the match, etc.
Is your feature request related to a problem? Please describe.
The log file starts before the match and ends after the match ends, but usually, only the period of the match itself (or periods within it) are interesting.
Describe the solution you'd like
Add the time period filter from the odometry (etc.) tabs to the whole log file.
Describe alternatives you've considered
While this can be done using the "locking" to auto/teleop start/end behavior of the cursor, another button will be more convenient IMO.
The text was updated successfully, but these errors were encountered: