Fix one hour summary bug and update dependencies#53
Merged
Conversation
bergsalex
requested review from
C-1337ka,
SkepticRaven,
gbeane,
keithshep and
ptuan5
SkepticRaven
approved these changes
Nov 12, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes a bug in JABS-postprocess where behavior summary tables were truncated to 60 minutes when bout data contains identical placeholder timestamps.
Users reported that behavior metrics were not being generated beyond 60 minutes, despite videos being 150+ minutes long. Investigation revealed that when all bouts in a bout table have identical timestamps (e.g.,
1970-01-01 00:00:00), thebouts_to_bins()method would only generate exactly 60 minutes of summary data.There was existing fallback logic that calculates time ranges based on frame counts only triggered on specific exceptions (KeyError, ValueError, TypeError), but not for this edge case.