Skip to content

[BUG] - Weird Data Padding in Processed Log Files #539

Open

Description

@Pdada1

Bug Report

  • 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:

    1. Use LOG_0052 from Comp 2026 folder on sharepoint as input data
    2. 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
    3. 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.

  • Screenshots
    Data in CSV
    Stratologger

Image

GPS
Image

  • Environment:
    • OS Version: Windows 11 Pro
    • CPU Architecture: x86
    • Python Version : uv synced version

Activity

  1. added
    bugSomething isn't working
    help wantedExtra attention is needed
    on Sep 13, 2026
  2. changed the title [-][BUG] - [Short Description][/-] [+][BUG] - Weird Data Padding in Processed Log Files[/+] on Sep 13, 2026
  3. Pdada1 commented on Sep 14, 2026

    @Pdada1
    ContributorAuthor

    Bug is actually in canlib, where timer is overflowing 16bit. Need a better solution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinghelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions