Skip to content
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

Update "Tracking Unstable" Alert #578

Closed
jkbhagatio opened this issue Jun 26, 2024 · 1 comment
Closed

Update "Tracking Unstable" Alert #578

jkbhagatio opened this issue Jun 26, 2024 · 1 comment
Assignees
Labels
bonsai-workflow Requires modifications to the structural acquisition workflow bug Something isn't working

Comments

@jkbhagatio
Copy link
Member

The current "TrackingUnstable" alert gets triggered whenever there is a jump in ID position exceeding some threshold (currently 500 pixels) on consecutively inferred frames.

We discussed today reworking this so that only if both subjects are not found in the arena within 30 minutes, send an alert, and have no "AlertGate" buffer for this alert, since this will already be handled by the implicit 30 minute timer.

@jkbhagatio jkbhagatio added this to the Social Ongoing milestone Jun 26, 2024
@jkbhagatio jkbhagatio added bug Something isn't working bonsai-workflow Requires modifications to the structural acquisition workflow labels Jun 26, 2024
@jkbhagatio
Copy link
Member Author

We discussed today reworking this so that only if both subjects are not found in the arena within 30 minutes, send an alert, and have no "AlertGate" buffer for this alert, since this will already be handled by the implicit 30 minute timer.

We are going to do this in #590, and keep Tracking Unstable Alerts as they are currently, so closing this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bonsai-workflow Requires modifications to the structural acquisition workflow bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants