Coerce frame interval columns to int before exploding#55
Merged
Conversation
bergsalex
requested review from
SkepticRaven,
gbeane,
keithshep,
michberger and
ptuan5
gbeane
approved these changes
Dec 6, 2025
michberger
approved these changes
Dec 6, 2025
keithshep
approved these changes
Dec 9, 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
5 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.
Fix for report from @michberger :
When GT annotations are missing, we synthesize “not-behavior” bouts covering the whole video. Concatenating those dummy rows onto an empty GT table makes pandas upcast numeric fields to float. Later,
_expand_intervals_to_framespassed those floats torange, raisingTypeError: 'float' object cannot be interpreted as an integer. The failure happened before any metrics/plots were produced.