-
Notifications
You must be signed in to change notification settings - Fork 243
feature: Event Detection Log Block #1894
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
+1,264
−0
Conversation
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
lou-roboflow
reviewed
Jan 8, 2026
lou-roboflow
reviewed
Jan 8, 2026
inference/core/workflows/core_steps/analytics/detection_event_log/v1.py
Outdated
Show resolved
Hide resolved
lou-roboflow
reviewed
Jan 8, 2026
Collaborator
|
bugbot run |
|
Skipping Bugbot: Bugbot is disabled for this repository |
Collaborator
|
bugbot run |
|
Skipping Bugbot: Bugbot is disabled for this repository |
Contributor
|
bugbot run |
1 similar comment
Contributor
|
bugbot run |
inference/core/workflows/core_steps/analytics/detection_event_log/v1.py
Outdated
Show resolved
Hide resolved
inference/core/workflows/core_steps/formatters/property_definition/v1.py
Outdated
Show resolved
Hide resolved
grzegorz-roboflow
requested changes
Jan 8, 2026
inference/core/workflows/core_steps/formatters/hello_world/v1.py
Outdated
Show resolved
Hide resolved
inference/core/workflows/core_steps/formatters/property_definition/v1.py
Outdated
Show resolved
Hide resolved
inference/core/workflows/core_steps/analytics/detection_event_log/v1.py
Outdated
Show resolved
Hide resolved
inference/core/workflows/core_steps/analytics/detection_event_log/v1.py
Outdated
Show resolved
Hide resolved
inference/core/workflows/core_steps/analytics/detection_event_log/v1.py
Outdated
Show resolved
Hide resolved
inference/core/workflows/core_steps/analytics/detection_event_log/v1.py
Outdated
Show resolved
Hide resolved
inference/core/workflows/core_steps/analytics/detection_event_log/v1.py
Outdated
Show resolved
Hide resolved
Contributor
⚡️ Codeflash found optimizations for this PR📄 1,492% (14.92x) speedup for
|
inference/core/workflows/core_steps/analytics/detection_event_log/v1.py
Outdated
Show resolved
Hide resolved
tests/workflows/integration_tests/execution/test_workflow_with_detection_event_log.py
Outdated
Show resolved
Hide resolved
3fc3e21 to
dd952f7
Compare
grzegorz-roboflow
previously approved these changes
Jan 8, 2026
dd952f7 to
32ab6c6
Compare
grzegorz-roboflow
previously approved these changes
Jan 8, 2026
32ab6c6 to
7130576
Compare
- New analytics block that tracks detection events over time - Records when objects first appear, their class, and last seen time - Configurable frame_threshold, flush_interval, and stale_frames - Includes unit tests and integration tests Co-Authored-By: Claude Opus 4.5 <[email protected]>
7130576 to
320928c
Compare
grzegorz-roboflow
approved these changes
Jan 8, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This is a new workflow block which takes input from the bytetracker and stores a log of events. The events store the time an object (unique tracker id) was first seen, last seen, its tracker id, and class.
There are no dependencies for this change.
Type of change
Please delete options that are not relevant.
How has this change been tested, please provide a testcase or example of how you tested the change?
I created a simple workflow which sent the bytetracker output to the new block. I used the rfdetr model. Then, I logged to output of the event detection log block.
I tested these changes against three different videos
Any specific deployment considerations
For example, documentation changes, usability, usage/costs, secrets, etc.
Docs
Note
Adds an analytics block to maintain and expose a rolling log of tracked detection events.
roboflow_core/detection_event_log@v1block (analytics/detection_event_log/v1.py) tracks objects bytracker_id, recording first/last seen frame/timestamp and frame counts; logs events afterframe_threshold; periodically removes stale events based onflush_intervalandstale_framesevent_log(split intologgedandpending), passthroughdetections, and counts:total_logged,total_pending; declares engine compatibility>=1.3.0,<2.0.0DetectionEventLogBlockV1incore_steps/loader.pyso it’s available viaload_blocks()Written by Cursor Bugbot for commit 4c396ac. This will update automatically on new commits. Configure here.