Skip to content

Add configurable cooldown between mined images#8

Open
edblu1 wants to merge 2 commits into
mainfrom
feature/ab#2311-mining-candidate-cooldown
Open

Add configurable cooldown between mined images#8
edblu1 wants to merge 2 commits into
mainfrom
feature/ab#2311-mining-candidate-cooldown

Conversation

@edblu1

@edblu1 edblu1 commented Jul 13, 2026

Copy link
Copy Markdown

AB#2311

What

Adds a configurable cooldown_seconds interval to the detection selector.

After a frame passes the existing mining filters, it is forwarded only if the
configured interval has elapsed since the last forwarded frame.

Configuration

The cooldown has to be added to the AI Control settings in the SAE Helm
deployment:

aiControl:
  settingsYaml:
    cooldown_seconds: 5

I recommend starting with 5 seconds. Without this configuration, the
cooldown defaults to 0 and is disabled.

Why

AI Cockpit mining can produce bursts of nearly identical frames. These frames
are unwanted during review, especially when images are sent directly from
Cockpit to CVAT, and are generally not needed for training.

This is a first, simple change to reduce near-duplicate images while keeping
the implementation and runtime state minimal.

Comment thread settings.template.yaml Outdated
Comment thread sae_ai_control/config.py Outdated
Comment thread sae_ai_control/config.py Outdated
@edblu1
edblu1 requested a review from flonix8 July 22, 2026 10:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants