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: An error occurs when tracking processing of "tm_play.m" is operated with GtrackLib (MEX function)

Part Number: IWR1642BOOST

Hello everyone.

I am trying to build a vehicle tracking system with reference to the traffic monitor lab.
This system must satisfy the following requirements.
· GUI should be built with MATLAB.
· Tracking is done outside the sensor (done on the GUI).
· Use GtrackLib created in C language for tracking.
In other words, you have to make GtrackLib MEX and operate it.

Unfortunately, the following inquiries have revealed that the traffic monitor lab does not support MEXization of GtrackLib.
There is also no plan to support in the future.
e2e.ti.com/.../725819

So, I'm trying to fix it so that PCMex mode of tm_play works.
For that reason, it will be a great help if you answer the following questions.

------------------------------
1.
In the answer to the above URL I heard that "There are two different versions of GtrackLib".
What is the difference between the two versions?
(I need to think about which version I should use)

2.
MEXization of the traffic monitor lab is a recognition that has been completed halfway.
What kind of processing is not implemented?
------------------------------

I am very grateful to you.
Thank you.

  • Former Member
    0 Former Member
    Hello Koji,

    The gtracklib is still under development so it is continuing to be updated and evolving. The most stable version will be the one in the SDK - the one in the traffic monitoring or people counting labs may be a different flavor depending on the demo requirements.

    Can you clarify why you want to use PCMex instead of PCMatlab if you want to do all the tracking within the Matlab GUI?

    Amanda
  • Hello Amanda.
    Thank you very much for replying.

    About the reason why I have to use "PCMex" instead of "PCMatlab".

    The "traffic surveillance system" we are going to make requires that the GUI part be made in a language other than MATLAB.
    However, since it is still in the verification stage now, the GUI part uses "tm_demo / tm_play".
    (By verification, we will create a GUI part after GtrackLib and sensor are found to meet our requirements.)

    Also, as I said earlier, GtrackLib needs to be run from the GUI.

    In other words, our traffic monitoring system eventually does not use "GtrackLib made with MATLAB".
    (Because the GUI is not MATLAB)
    Therefore, now we need to execute and verify "GtrackLib made in C" from "tm_demo / tm_play".

    Thank you.
  • As a result of the survey, I found out why the MEX function does not work with tm_play.
    I linked "gtrack.h in SDK".
    But correctly you have to link "gtrack.h in the industrial tool box".
    (There are differences in the structure of these two header files)

    By linking the header file of the industrial tool box, tracking processing by PCMex mode was possible.
    There may still be problems, but I will let this question resolve.

    Thanks to your advice.
    I'm really thankful to you.