Pipelines with input detections#590
Merged
Merged
Conversation
09a48fe to
69156f5
Compare
faa94d6 to
95efbcf
Compare
…ME/VIAME-Web into pipeline-existing-detections
subdavis
approved these changes
Mar 6, 2021
Contributor
subdavis
left a comment
There was a problem hiding this comment.
Looks great. I like the error for no detections.
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.
Adding in the capability to input detections/tracks into pipelines with the
uility_name.generate_pipelines are renamed toutility_and require user inputadd segmentation watershedandtrack user selectionsare the two pipelines that expect user input and will properly generate detections from that.add segementation watershedwill take existing detections and generate polygons for them.track user selectionswill take a single detection and create a track for it.