• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 247 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.

IWR6843ISK: What’s the relations between point unique and point static

Wyatt Sun
Prodigy 10 points
Part Number: IWR6843ISK

C:\ti\mmwave_industrial_toolbox_4_3_2\labs\people_counting\68xx_Sense_and_Direct_HVAC_Control\src\mss\gtrack\src\gtrack_unit_score.c

I can’t understand the point set(not set) unique logic in following code at line145~169.

I translate line 156~158 as following. why when the point is static and the track_unit is not static, we do not clear the point unique property?

                        if staticIndication and (not self.isTargetStatic):

                            clearUniqueInd=False

                            point.isStatic=False

I translate line 164~165 as following. Why when the point is not static and the track_unit is static, we do not clear the point unique property? All other conditions, we set the point not unique?

                        if not staticIndication and self.isTargetStatic:

                            clearUniqueInd=False

Why clear point unique depends on the point static? What’s the relations between point unique and point static?

The whole translated code as following, point is the measure point object, self is the current track unit.

  • 0
    TI__Mastermind 28055 points

    Hi Wyatt,

    First, I want to quickly explain static and unique, because I don't believe they are properly explained outside of the code:

    Unique - point is unique if only one track is scoring it, i.e. only one track is potentially associated with the point. 

    Static - doppler = 0. These are generated differently than the non static points.

    Please also note the above comparison is for points, not tracks. In the code you reference, we are looking at whether the tracked person is static or not.

    When a person is static, we expect they are not generating dynamic points - so when we see that a point falls inside the gating function of a static track, we don't want to remove its uniqueness, as the static track didn't generate the point, it should be the dynamic track doing so. (164 - 165). When a point is static and the track is not static, we will not associate these, and do not want to clear the unique index (156-158).

    Regards,

    Justin