• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 29 subscribers
  • Views 579 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.

IWR1642BOOST: The setting of [State Transition Parameters - det2 activeThre] of tm_play is not working properly

koji fukumoto
Intellectual 940 points
Part Number: IWR1642BOOST

Hello.

1. Execute tm_play.
2. fhist specifies "C:\ti\mmwave_industrial_toolbox_2_4_0\labs\lab0013_traffic_monitoring_16xx\gui\sample_fhist\fHistRT_0002.mat".
- This file starts from the 1000th frame.
- It is a detect state from the beginning.
3. Select [PC] for [Replay Option].
4. cfg file specifies "C:\ti\mmwave_industrial_toolbox_2_4_0\labs\lab0013_traffic_monitoring_16xx\chirp_configs\mmw_tm_demo_ph2.cfg".
5. Change [State Transition Parameters - det2activeThre] from 3 to 20.
6. Enter [-5, 0, 4] for [Other Mandatory Parameters].
7. Start.

As a result, tracking clustering is performed in the 1002nd frame.
Since [State Transition Parameters - det2activeThre] is 20, tracking clustering must be performed at the 1019th frame.
Why [State Transition Parameters - det2activeThre] setting is not reflected?

Thanks.

  • Former Member
    0 Former Member

    Hello Koji,

    The object is tracked and a bubble appears when the object is in the "detect" state. 

    Amanda

  • 0
    Intellectual 940 points

    Hello Amanda.
    Thank you for always replying.


    dev.ti.com/.../Tracking_radar_targets_with_multiple_reflection_points.pdf
    I read page 26 of this document and understand as follows.

    · The fact that the bubble is displayed means that it is being tracked.
    · Tracking is done when in the "ACTIVE" state. Tracking is not performed in "DETECT" state.
    · Tracking means that num is greater than or equal to 1 as a result of STEP processing on line 297 of tm_play.m.
    -----
    tm_play.m line 297
    [track, num, mIndex] = step(hRadarTrackingM, pointCloud, 0, numOutputPoints);
    -----


    Under Detect state, we understand that when the HIT event lasts the number of times specified by [det2activeThre] it will be in Active state.
    If [det2activeThre] is "3", it is correct to be tracked in 1002 frames as follows.
    -----
    1000 frame: Detection -> HIT event=1 (still object is not tracked)
    1001 frame: Detection -> HIT event=2
    1002 frame: Detection -> HIT event=3 -> transition to ACTIVE (object is tracked)
    -----

    However, if [det2activeThre] is 20, it should transition to ACTIVE at the 1019th frame.

    Where is my recognition incorrect?

    Thanks.

  • Former Member
    0 Former Member in reply to koji fukumoto
    Hello Koji,

    Yes your understanding of the state parameters appear to be correct. Except that the tracker is created from the Allocation step. The allocation step determines the Detect state and that is when the tm_play displays an object. To see this effect you can modify the setPointsThre allocation parameter to a very high number such as 20 and you will not see a tracked object created until it is close to the sensor and there are more reflections.

    If you only want to visualize objects that are in the active state you will need to modify the tm_play visualizer.

    Amanda