Disparity Confidence Threshold
See original GitHub issueBackground: Currently we hard-code in firmware the disparity confidence threshold to be 200 out of a configurable range of 0 to 255.
Improvement:
Allow this to be set from the host as a parameter in the depth
entry in config
: https://github.com/luxonis/depthai/blob/0611eb701fffbcd743644e4f0d2c7b92e60b7cd9/depthai.py#L382
Issue Analytics
- State:
- Created 3 years ago
- Comments:9
Top Results From Across the Web
StereoDepth - DepthAI documentation - Luxonis
For the final disparity map, a filtering is applied based on the confidence threshold value: the pixels that have their confidence score larger...
Read more >On the confidence of stereo matching in a deep-learning era
Abstract—Stereo matching is one of the most popular techniques to estimate dense depth maps by finding the disparity between matching pixels on two, ......
Read more >DEEP STEREO CONFIDENCE PREDICTION FOR DEPTH ...
In this step, predicting the confidence of an estimated disparity is one of the most important issues. Conventionally, the left-right consistency check or...
Read more >a novel confidence measure for disparity maps by pixel-wise ...
A NOVEL CONFIDENCE MEASURE FOR DISPARITY MAPS BY PIXEL-WISE COST ... In this paper, we introduce a novel confidence measure ... higher than...
Read more >Learning a confidence measure in the disparity domain from O ...
for confidence estimation based on features computed in the disparity domain, making our proposal ... The error threshold is set to τ =...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@Luxonis-Brandon It was more about curiosity and that I am also looking for other ways to communicate with the depthai board instead of using USB. Mainly so I can transition to utilizing a microcontroller instead of a raspberry PI for example.
When you say “hence why we made a fully-open-source API on the host and will be doing the same for I2C, SPI, and UART interface” does this mean you are adding those additional communication protocols in addition to USB? Or is this something that is already functional?
Also, this doesn’t really have anything to do with the Github issue so if you want, we can take this elsewhere but I just didn’t know where to start the convo.
Merged to master today.