Conversation
Signed-off-by: Lacewell, Chaunte W <chaunte.w.lacewell@intel.com>
Signed-off-by: Lacewell, Chaunte W <chaunte.w.lacewell@intel.com>
Signed-off-by: Lacewell, Chaunte W <chaunte.w.lacewell@intel.com>
Signed-off-by: Lacewell, Chaunte W <chaunte.w.lacewell@intel.com>
Signed-off-by: cwlacewe <chaunte.w.lacewell@intel.com>
Signed-off-by: cwlacewe <chaunte.w.lacewell@intel.com>
…pipeline Signed-off-by: Lacewell, Chaunte W <chaunte.w.lacewell@intel.com>
Signed-off-by: Lacewell, Chaunte W <chaunte.w.lacewell@intel.com>
Signed-off-by: Lacewell, Chaunte W <chaunte.w.lacewell@intel.com>
Signed-off-by: Lacewell, Chaunte W <chaunte.w.lacewell@intel.com>
Signed-off-by: Lacewell, Chaunte W <chaunte.w.lacewell@intel.com>
…point, convert fastapi Dockerfile to multistage, update basis of video clip writer and sending metadata to vdms (WIP) Signed-off-by: Lacewell, Chaunte W <chaunte.w.lacewell@intel.com>
…ars/capabilities, Update docs, Fix color conversion, decoding, and retry for rtsp, Move model download script and leverage in application, Fix SF test script, [ALL] Format code Signed-off-by: Lacewell, Chaunte W <chaunte.w.lacewell@intel.com>
…api] Add endpoint for model classes, enable querying, change how video clips are saved (use ffmpeg segment) Signed-off-by: Lacewell, Chaunte W <chaunte.w.lacewell@intel.com>
…unch.json; [FASTAPI] Update include scripts, update defaiults in default_config, updated test scripts to leverage handler class directly Signed-off-by: Lacewell, Chaunte W <chaunte.w.lacewell@intel.com>
Signed-off-by: Lacewell, Chaunte W <chaunte.w.lacewell@intel.com>
Signed-off-by: Lacewell, Chaunte W <chaunte.w.lacewell@intel.com>
Signed-off-by: Lacewell, Chaunte W <chaunte.w.lacewell@intel.com>
…g on gpu path, fix Signed-off-by: Lacewell, Chaunte W <chaunte.w.lacewell@intel.com>
Signed-off-by: Lacewell, Chaunte W <chaunte.w.lacewell@intel.com>
cwlacewe
marked this pull request as ready for review
June 11, 2026 14:42
s-gobriel
approved these changes
Jun 11, 2026
s-gobriel
left a comment
There was a problem hiding this comment.
I see a lot of threads being created, communicating on shared memory and hardware resources are pre-allocated. I don't know if there will be deadlocks but if the demo runs fine then no need to debug all the cases unless there are some issue with the threading. .. Can we track visually the area submitted to object tracking (not objects discovered) .. I want to make sure that for each frame there is some area being sent to YOLO for each frame and no frame is skipped because the threads are blocked ... maybe you can also explain to me how we are queuing the frames and what will happen if this queue is building up in the pipeline
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
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.
The overall flow of application has changed and now leverages fastapi.
This version is ready for demo and can be merged into main.
There is still room for improvement: