You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/components/nodes/color_camera.rst
+37-8Lines changed: 37 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,7 @@ It interacts with the 3A algorithms: **auto-focus**, **auto-exposure**, and **au
57
57
adjustments such as exposure time, sensitivity (ISO), and lens position (if the camera module has a motorized lens) at runtime.
58
58
Click `here <https://en.wikipedia.org/wiki/Image_processor>`__ for more information.
59
59
60
-
**Image Post-Processing** converts YUV420 planar frames from the **ISP** into :code:`video`/:code:`preview`/:code:`still` frames.
60
+
**Image Post-Processing** converts YUV420 planar frames from the **ISP** into ``video``/ ``preview``/ ``still`` frames.
61
61
62
62
``still`` (when a capture is triggered) and ``isp`` work at the max camera resolution, while ``video`` and ``preview`` are
63
63
limited to max 4K (3840 x 2160) resolution, which is cropped from ``isp``.
@@ -69,13 +69,42 @@ For IMX378 (12MP), the **post-processing** works like this:
69
69
│ ISP ├────────────────►│ video ├───────────────►│ preview │
70
70
└─────┘ max 3840x2160 └─────────┘ and cropping └──────────┘
71
71
72
-
.. image:: /_static/images/tutorials/isp.jpg
73
-
74
-
The image above is the ``isp`` output from the ColorCamera (12MP resolution from IMX378). If you aren't downscaling ISP,
75
-
the ``video`` output is cropped to 4k (max 3840x2160 due to the limitation of the ``video`` output) as represented by
76
-
the blue rectangle. The Yellow rectangle represents a cropped ``preview`` output when the preview size is set to a 1:1 aspect
77
-
ratio (eg. when using a 300x300 preview size for the MobileNet-SSD NN model) because the ``preview`` output is derived from
78
-
the ``video`` output.
72
+
If the resolution is set to 12MP and video mode is used, a 4K frame (3840x2160) will be cropped from the center of the 12MP frame.
73
+
74
+
Full FOV
75
+
########
76
+
77
+
Some sensors, such as the IXM378, default to a 1080P resolution, which is a crop from the full sensor resolution. You can print sensor features to see how the field of view (FOV) is affected by the selected sensor resolution:
Copy file name to clipboardExpand all lines: docs/source/components/nodes/tof.rst
+90-6Lines changed: 90 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -30,20 +30,88 @@ Inputs and Outputs
30
30
.. code-block::
31
31
32
32
┌───────────┐ depth
33
-
inputConfig | ├────────►
34
-
───────────►│ | amplitude
35
-
input | ToF ├────────►
36
-
───────────►│ │ error
33
+
│ ├────────►
34
+
inputConfig | | amplitude
35
+
───────────►│ ├────────►
36
+
│ ToF │ phase
37
+
input | ├────────►
38
+
───────────►│ │ intensity
37
39
│ ├────────►
38
40
└───────────┘
39
41
42
+
40
43
**Message types**
41
44
42
45
- ``inputConfig`` - :ref:`ToFConfig`
43
46
- ``input`` - :ref:`ImgFrame`
44
-
- ``depth`` - :ref:`ImgFrame`
47
+
- ``depth`` - :ref:`ImgFrame` - Decoded depth map
45
48
- ``amplitude`` - :ref:`ImgFrame`
46
-
- ``error`` - :ref:`ImgFrame`
49
+
- ``phase`` - :ref:`ImgFrame` Phase image, useful for debugging (FP32)
50
+
- ``intensity`` - :ref:`ImgFrame`
51
+
52
+
ToF Settings
53
+
############
54
+
55
+
In :ref:`ToF depth` example we allow users to quickly configure ToF settings.
56
+
57
+
Here are the most important settings:
58
+
59
+
* Optical Correction: It's a process that corrects the optical effect. When enabled, the ToF returns depth map (represented by Green Line on graph below) instead of distance, so it matches :ref:`StereoDepth` depth reporting. It does rectification and distance to depth conversion (Z-map).
60
+
* Phase Unwrapping - Process that corrects the phase wrapping effect of the ToF sensor. You can set it to [0..5 are optimized]. The higher the number, the longer the ToF range, but it also increases the noise. Approximate max distance (for exact value, see :ref:`Max distance` below):
61
+
62
+
* `0` - Disabled, up to ~1.87 meters (utilizing 80MHz modulation frequency)
63
+
* `1` - Up to ~3 meters
64
+
* `2` - Up to ~4.5 meters
65
+
* `3` - Up to ~6 meters
66
+
* `4` - Up to ~7.5 meters
67
+
68
+
* Burst mode: When enabled, ToF node won't reuse frames, as shown on the graph below. It's related to post-processing of the ToF frames, not the actual sensor/projector. It's disabled by default.
69
+
* Phase shuffle Temporal filter: Averages shuffled and non-shuffled frames of the same modulation frequency to reduce noise. It's enabled by default. You can disable it to reduce :ref:`ToF motion blur` and system load.
If the time it takes for the light to travel from ToF sensor and back exceeds the period of the emitted wave (1.5m or 1.87m), the resulting measurement will "wrap" back to a lower value. This is called phase wrapping.
81
+
It's similar to how a clock resets after 12 hours. Phase unwrapping is possible as our ToF has two different modulation frequencies (80Mhz and 100MHz).
82
+
83
+
Phase unwrapping aims to correct this by allowing the sensor to interpret longer distances without confusion. It uses algorithms to keep track of how many cycles (round trips of the wave) have occurred,
84
+
thus correcting the "wrapped" phases. The downside is that the more cycles the sensor has to keep track of, the more noise it introduces into the measurement.
85
+
86
+
ToF motion blur
87
+
###############
88
+
89
+
To reduce motion blur, we recommend these settings:
90
+
91
+
- Increase camera FPS. It goes up to 160 FPS, which causes frame capture to be the fastest (6.25ms between frames). This will reduce motion blur as ToF combines multiple frames to get the depth. Note that 160FPS will increase system load significantly (see :ref:`Debugging <Debugging DepthAI pipeline>`). Note also that higher FPS -> lower exposure times, which can increase noise.
92
+
- Disable phase shuffle temporal filter. This will introduce more noise.
93
+
- Disable phase unwrapping. This will reduce max distance to 1.87 meters (utilizing 80MHz modulation frequency), so about 1 cubic meter of space will be visible (very limited use-cases).
94
+
- Enable burst mode. This is irrelevant if shuffle filter and phase unwrapping are disabled (see diagram above). When enabled, ToF node won't reuse frames (lower FPS).
95
+
96
+
In the diagram above, the less frames are combined (bottom of the diagram), the less motion blur there is. The more frames are combined (top of the diagram), there's more filtering (better accuracy) but it results in more motion blur.
97
+
98
+
Max distance
99
+
############
100
+
101
+
Maximum ToF distance depends on the modulation frequency and the phase unwrapping level. If phase unwrapping is enabled,
102
+
max distance is the shorter of both modulation frequencies (so max distance at 100MHz). Here's the formula:
103
+
104
+
.. math::
105
+
:nowrap:
106
+
107
+
\begin{align*}
108
+
c & = 299792458.0\quad\text{// speed of light in m/s} \\
Copy file name to clipboardExpand all lines: docs/source/samples/StereoDepth/rgb_depth_aligned.rst
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,12 @@ To align depth with **higher resolution color stream** (eg. 12MP), you need to l
16
16
do that with ``stereo.setOutputSize(w,h)``. Code `example here <https://gist.github.com/Erol444/25f374fa18efa7939ec9bb848b39249a>`__.
17
17
18
18
19
+
Host alignment
20
+
--------------
21
+
22
+
StereoDepth node aligns depth map to selected sensor (in this case, color sensor), on the OAK device itself. One can also do the same
23
+
on the host side. We have developed a simple `demo script here <https://github.com/luxonis/depthai-python/commit/94b3177f5f4b28e562f637dcf77baa47826ef643>`__.
* *FPPN Correction*; Turn on/off with `f`. It's a process that corrects the fixed pattern noise (FPN) of the ToF sensor. Should be enabled.
21
+
* *Wiggle Correction*: Turn on/off with `w`. It's a process that corrects the wiggle effect of the ToF sensor. Should be enabled.
22
+
* *Temperature Correction*: Turn on/off with `t`. It's a process that corrects the temperature effect of the ToF sensor. Should be enabled.
23
+
* *Optical Correction*: Turn on/off with `o`. It's a process that corrects the optical effect (On -> ToF returns distance represented by Green Line), so it matches stereo depth reporting.
24
+
* *Phase Unwrapping* - Process that corrects the phase wrapping effect of the ToF sensor. The higher the number, the longer the ToF range, but it also increases the noise.
0 commit comments