Add colorized depth map
See original GitHub issueThe current depth map is grayscale, but we can support a better-looking colorized depth map based on https://github.com/luxonis/depthai-python-extras/commit/0fd2cc61c6be1b75ad5eed07424a2ad509f48074#diff-b284a28710cce90d9d9be3a7f4cabc8eR165.
Add this back to the test.py
script.
/cc @GergelySzabolcs
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Colorization of Depth Map via Disentanglement ... - GitHub
Colorization of Depth Map via Disentanglement (ECCV 2020 accepted). This is the PyTorch implementation for our ECCV'20 paper:.
Read more >Automatic Depth-Map Colorization - GitHub Pages
Abstract. We present a system for automatically generating custom, structured image-maps for input depth-maps. Our sys- tem thus allows quick fitting of ...
Read more >What's the proper way to colorize a 16-bit depth image?
It is not exact, but you can modify the colormap or change the stretch. Basically, I create a 7 color LUT with colors:...
Read more >Colorization of Depth Map via Disentanglement - ECVA
In this paper, we propose a depth map colorization method via disentangling appearance and structure factors, so that our model could 1) learn...
Read more >How to use the brand new DEPTH MAP tool in Davinci ...
Check out SCANS Nvidia Studio Systems here : https://bit.ly/SCANNVIDIAStudioNVIDIA: @NVIDIAGeForceUKSCAN: @SCANComputers☕☕☕ SAY THANKS ...
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
This was added on master a while ago. python3 test.py -s depth_sipp or colorized disparity python3 test.py -s depth_color_h
Thanks @chris-piekarski - we’re working on this in #37.