• If I subtract 2 StereoDepth frames from each other how to output in OpenCV

erik

That is the resolution of my camRgb preview for person detection that I got from this example:https://github.com/luxonis/depthai-experiments/blob/30e2460557a3209770eb8943db41bc997a423212/gen2-pedestrian-reidentification/api/main_api.py#L22

I think I found what you found. Even if you set a depth preview a certain size, it won't make the image that big. I see now that the biggest that comes out is 1920,1080.

If my camera preview is 1632x960, how can I rgb align so I can find the spatial location of each RGB pixel?

I am having trouble understanding how depthpreview, depth resolution, rgb align, and rgb resolution all play together.

I had at one point added a ValueError for the ML model if the input size was not the same as expected, but apparently that doesn't trigger anything in OpenVINO.

erik

If I have an rgb at 1632 x 960 preview and 1080p resolution

Does this mean if I do depth align it listens to the resolution not the preview? How can I use this for spatial location calculations, would I have to resize the depth frame?

  • erik replied to this.

    AdamPolak yes it aligns with resolution, not the preview. spatial loc calc knows image transformation (all crops/resizes/etc) so it will map to correct depth region.

    @erik how about if the depth has a more narrow field of view than RGB? Are the calcs returned N/A?

    • erik replied to this.

      AdamPolak it will scale/pad the depth frame. So if FOV is lower, it will pad it with "0" values (which means invalid depth).

      6 days later

      hello Adam, have you succeed in subtracting 2 depth frames in device yet?

        jeremie_m

        Yes I have.

        Turns out the issue was that the model I created was expecting the input I entered for the StereoDepth.preview size.

        But instead the depth frames output at the resolution you provide for the depth.

        Let me know if you have any questions I know it pretty well now.

          AdamPolak

          Thank you Adam, I have questions about the model 'diff_images_simplified_openvino_2021.4_4shave.blob', is it generated by the pytorch code here?

          AdamPolak This is the pytorch code.

          Is it still using the dummy input or the depth input here is the result of the subtraction?

          AdamPolak def forward(self, depth):

            AdamPolak depthFP16 = 256.0 * depth[:,:,:,1::2] + depth[:,:,:,::2]

            Is the subtraction executed here?

            jeremie_m

            1. This is the "final" version to do a diff between 2 depth map images:
            #! /usr/bin/env python3
            
            from pathlib import Path
            import torch
            from torch import nn
            import blobconverter
            import onnx
            from onnxsim import simplify
            import sys
            
            # Define the model
            class DiffImgs(nn.Module):
                def forward(self, img1, img2):
                    # We will be inputting UINT16 but interprets as UINT8
                    # So we need to adjust to account of the 8 bit shift
                    img1DepthFP16 = 256.0 * img1[:,:,:,1::2] + img1[:,:,:,::2]
                    img2DepthFP16 = 256.0 * img2[:,:,:,1::2] + img2[:,:,:,::2]
            
                    # Create binary masks for each image
                    # A pixel in the mask is 1 if the corresponding pixel in the image is 0, otherwise it's 0
                    img1Mask = (img1DepthFP16 == 0)
                    img2Mask = (img2DepthFP16 == 0)
            
                    # If a pixel is 0 in either image, set the corresponding pixel in both images to 0
                    img1DepthFP16 = img1DepthFP16 * (~img1Mask & ~img2Mask)
                    img2DepthFP16 = img2DepthFP16 * (~img1Mask & ~img2Mask)
            
                    # Compute the difference between the two images
                    diff = torch.sub(img1DepthFP16, img2DepthFP16)
            
                    # Square the difference
                    # square_diff = torch.square(diff)
            
                    # # Compute the square root of the square difference
                    # sqrt_diff = torch.sqrt(square_diff)
            
                    # sqrt_diff[sqrt_diff < 1500] = 0
            
                    return diff
            
            # Instantiate the model
            model = DiffImgs()
            
            # Create dummy input for the ONNX export
            input1 = torch.randn(1, 1, 320, 544 * 2, dtype=torch.float16)
            input2 = torch.randn(1, 1, 320, 544 * 2, dtype=torch.float16)
            
            onnx_file = "diff_images.onnx"
            
            # Export the model
            torch.onnx.export(model,               # model being run
                              (input1, input2),    # model input (or a tuple for multiple inputs)
                              onnx_file,        # where to save the model (can be a file or file-like object)
                              opset_version=12,    # the ONNX version to export the model to
                              do_constant_folding=True,  # whether to execute constant folding for optimization
                              input_names = ['input1', 'input2'],   # the model's input names
                              output_names = ['output'])
            
            # Simplify the model
            onnx_model = onnx.load(onnx_file)
            onnx_simplified, check = simplify(onnx_file)
            onnx.save(onnx_simplified, "diff_images_simplified.onnx")
            
            # Use blobconverter to convert onnx->IR->blob
            blobconverter.from_onnx(
                model="diff_images_simplified.onnx",
                data_type="FP16",
                shaves=4,
                use_cache=False,
                output_dir="../",
                optimizer_params=[],
                compile_params=['-ip U8'],    
            )

            Important to note! This does not take in dynamic image sizes. It must be a certain size. For some reason dynamic dimensions are not supported. So these 2 lines:

            # Create dummy input for the ONNX export

            input1 = torch.randn(1, 1, 320, 544 * 2, dtype=torch.float16)

            input2 = torch.randn(1, 1, 320, 544 * 2, dtype=torch.float16)

            Define what size of depth images are coming in. change 320 (height) and 544 (width) to your actual depth image size.

            1. These lines are what changes the depth input from U8 (1 byte) to U16 (2 bytes):

            depthFP16 = 256.0 * depth[:,:,:,1::2] + depth[:,:,:,::2]

            The reason is because the depth image comes into the model at U16. We then convert it to U8 when it enters the model. We tell the nn to do that by this compile command: compile_params=['-ip U8']

            So the data comes in twice as big because it changes from U16 to U8. It needs twice as many bytes to represent the image. What that operation does is a little trick to turn the U8 data into FP16 data (which is required by the NN). So what that does is it unconverts the input data back from U8 to U16 (in this case FP16).

            What is your use case, do you also want to diff a "control depth" from new depth or something else.

              AdamPolak

              Thank you Adam, that helps a lot!

              I thought the image size is always the same once the camera config is fixed.

              And the transforms from U16 to U8, then unconverted to FP16, the procedure seems tricky.

              I will try to understand the dynamic dimensions and the procedure of transform.

              In fact, my case is just as your 'control depth', I want to make a subtraction of 2 successive depth frames to find the moving pixels, but I'm not so skilled at the NN model, and the subtraction must be done by NN model in the device.

              Adam, you help a lot 😃

                jeremie_m

                You are right, the image is the same size once it is fixed. I just meant that if all of a sudden you wanted to increase/decrease resolution on your depth frame to improve, you would need to create a new model.

                Heads up, you need to have quite a lot of depth filters enabled to make this diff work, the original depth frames are too noisy without post processing.

                And when you do basically any type of depth processing, like MedianFilter, it slows down the depth FPS to ~9-11.

                But it will take your diff from this (no processing):
                (2 identical frames, nothing moved in the scene)

                to this (median filter 7x7 and high_density):

                To this ( a lot of processing):

                  AdamPolak quite a lot of depth filters enabled to make this diff work

                  Thanks, Adam, 9-11 FPS maybe enough for me, I have to try to make the filters work in the host if the rate is too low.

                  Is the config of depth filters is set as you mentioned in the code here or it's more complex than the parameters here?

                  AdamPolak This is the depthai code

                  jakaskerl

                  Thank you for reply.

                  1. As the subtraction of depth frames as we mentioned here.

                  2. Selection of the farthest or nearest area of pixels in depth frame.

                  3. Mask of specific shape from or to depth frame.

                    (4. Some NN models use both depth and RGB image maybe.)

                    .etc

                    Some thoughts for now, thank you 😃

                  • erik replied to this.

                    jeremie_m does the code Adam provided above not work? Besides the tutorials we have on documentation / depthai-experiments, we don't have any additional ones.

                      erik

                      Thank you erik.

                      I'm not sure if the first code works, cause it doesn't match the inputs with the second code.

                      And I'm looking into how to generate the shave.blob, I'm not clear in processing the NN model.