This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TIDEP-01012: The number of point clouds produced by real-time processing demo is much less than that produced by post-processing.

Part Number: TIDEP-01012

When I use cascade_radar_object_detect usecase in PROCESSOR_SDK_RADAR (V3.8.0.0) to generate the point clouds, it can be found that the number of point clouds is always less than 40.

However, when I use mmWave studio to collect raw signals, the number of point clouds generated by MATLAB demo (cascade_MIMO_signalProcessing.m) is mostly greater than 200.

When verifying the point cloud generation results of the two, it is ensured that the configuration of chirp and frame remains the same. 

What caused the large gap in the number of point clouds generated by real-time processing and post-processing demo (MIMO)?

  • Hi,

                 The data doesn't seem correct, can you confirm if you ignoring the first frame data or not? Also, the data capture seems to be corrupted.

    Regards

  • Hi  Abhed, 

    How can I be sure that data capture is corrupted? 

    When we use Cascade_Configuration_MIMO.lua and set nframes_master and nframes_slave to n, the number of frames we collect is always (n-1).  Is this what you describe ignoring the first frame data? If yes, how to modify the example script, Cascade_Configuration_MIMO.lua, configuration to avoid this?

    Regards

  • Hi,

             I was referring to process 2nd frame onwards. Please confirm if your script takes care of the same.

    Regards

  • Hi Abhed, 

    I was using the official demo script Cascade_Configuration_MIMO.lua located in mmwave_studio_03_00_00_14\mmWaveStudio\Scripts\Cascade, which only modified the variables nframes_master and nframes_slave. How can I confirm if there are problems with the processing of the second frame?

    Regards