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

Make imaging pipeline actually a pipeline #160

Open
EricPedley opened this issue Mar 20, 2024 · 0 comments
Open

Make imaging pipeline actually a pipeline #160

EricPedley opened this issue Mar 20, 2024 · 0 comments

Comments

@EricPedley
Copy link
Member

Rn we just process one image at a time sequentially, but I was thinking it might benefit us to make our architecture asynchronous. Here's my initial idea:

  • images come in at whatever FPS the camera can run at
  • we have some algorithm that decides which image tiles we should actually run object detection on. With our current speed I imagine most tiles will be discarded. Maybe it can take into account where we expect targets to be when prioritizing what tiles to process, but this would totally spaghettify our software architecture by coupling front-end detection to back-end geolocation and object tracking.
  • after object detection, all bounding box crops get fed into classification, or if there's too many maybe we again use tracking info to prioritize what to classify
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant