• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 393 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AWR1843: Range/Doppler CFAR Naming System

Emily A
Prodigy 10 points
Part Number: AWR1843

Hello,

I am seeking clarification on the naming convention used for Range/Doppler CFAR processing. I am looking at mmwave_sdk_03_06_00_00-LTS/packages/ti/datapath/dpc/dpu/cfarcaproc/docs/doxygen/html/index.html

- What does CFAR in 'Range domain' mean? If I have an RDM of 256 (range bins) x 64 (doppler bins), does the 'Range domain' CFAR loop over the 256 range bins, taking Doppler spectrum slices and applying the guard and noise window lengths to doppler bins? Or the other way around? (the other way around is illustrated in the image below)

- Similarly, when the documentation says the noise calculation is taken from the range CFAR HWA processing, is that from the phase of looping over range bins or taking range slices?

  • +1
    TI__Mastermind 20605 points

    Hi Emily,

    The image you have shared shows CFAR in the Range domain or range dimension.

    When CFAR is performed over range bins (across a complete range profile in a given RDM), the noise calculation is also done in the same direction and dimension.

    .

    Regards,

    Kaushik