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
{{ message }}
Repository navigation
[BUG] - Weird Data Padding in Processed Log Files #539
Describe the bug
When using the data processing script v2 on log files from logger board, There are cases where it seems extra data points are inserted where data has not actually been reported by CAN. The best example of this is the GPS and Stratologger altitude measurements. Images attached below.
To Reproduce
Steps to reproduce the behavior:
Use LOG_0052 from Comp 2026 folder on sharepoint as input data
run data processing script v2 with data in omnibus top level folder with uv run tools/data_processing_v2_beta/main.py logger LOG_0052.bin
Sort CSV data by data, board_inst_id, timestamp for Stratologger, message type, board_inst_id, timestamp for GPS
Expected behavior
Expect to only see actual altitude measurements rather than altitude measurements at 2Hz with bunch of nearly 0 data points in between.
Activity
[-][BUG] - [Short Description][/-][+][BUG] - Weird Data Padding in Processed Log Files[/+]Pdada1 commentedon Sep 14, 2026
Bug is actually in canlib, where timer is overflowing 16bit. Need a better solution