Add max ticks support for tickFPS computation #510
Merged
Conversation
This file contains 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.
Currently, FPS is calculated as the
time differencebetween the first and the last tick in the array divided by the length of the array. Default queue size is set to 100, which is problematic in 2 stage pipelines with slower 2nd NN, as the speed of the faster NN might prevail, resulting in higher FPS estimation of the pipeline.This PR adds flag
maxTicks = 100to the FPSHandler__init__. When initializing the FPSHandler, a lower value can be provided to reduce the effect of the first NN. UsingmaxTicks = 2should result in real time FPS.