• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 3 answers
  • Subscribers 30 subscribers
  • Views 219 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.

IWR6843: Traffic monitoring trackingParamSet and maxAccelration/accelerationParams

user5310849
Intellectual 730 points
Part Number: IWR6843

Hello TI,

I'm a bit confused by following:

  1. The second parameter of trackingCfg defines which predefined set will be used. Even your TM demo uses nr. 2 which is TRACKING_PEOPLE_COUNTING_PARAM_SET. When I try to set it to 1 (TRACKING_TRAFFIC_MONITORING_PARAM_SET) no tracking is happening at all. What does it mean?
  2. MaxAcceleration defined in cfg file is stored (at lest in case of TM demo) in gMmwMssMCB.trackerCfg.trackerDpuCfg.staticCfg.accelerationParams but it seems not to be used anywhere in the future. Only the MaxAcceleration from predefined set of parameters. Am I right? Why is it like this?

Thank you, Lukas

  • Former Member
    0 Former Member

    1. The predefined parameters are not used because the parameters are passed by CLI instead of the predefined set. You can ignore the predefined set parameters.

    2. The predefined parameters are not used.

  • 0 in reply to Former Member
    Intellectual 730 points

    Are you sure? Looking to the code, it seems that predefined sets are really used (and MaxAcceleartion commad is ignored).

    At least when changing second parameter of trackingCfg, the tracking stops. So it has some effect.

  • Former Member
    0 Former Member in reply to user5310849

    The parameters for scenery, gating, allocation, and state are all passed by CLI and not taken from the paramTable selection.

    Changing the second param changes the initialVelocity and maxAcceleration variables. The old values for TM assumed a specific direction and initial velocity. If this is the case for your application you can modify it so. However otherwise it should be left as 0 as in the predefined PC case.

     

  • 0 in reply to Former Member
    Intellectual 730 points

    Thus you mean, that maxAcceleration parameter is taken tom the table and not from CLI? With other parameters, I can see in the code, which are hard coded and which are taken from CLI.

    There is still problem with changing the second param to number 1 (TRACKING_TRAFFIC_MONITORING_PARAM_SET, 2, 20, 2 m/s maxAccelaration) , it stops tracking completely. The new TM demo has initial velocity set to zero by default. But also in the config, the new demo uses TRACKING_PEOPLE_COUNTING_PARAM_SET with 1, 1, 1 m/s maxAccelaration.

  • Former Member
    0 Former Member in reply to user5310849

    If you left the second parameter to 2 and changed the acceleration and initial velocity parameters this would have the same effect as changing the second param to 1.

    However this is not recommended. You can refer to to gtrack_create.c to see how the maxAcceleration value is used to determine the initial variance.