We followed the steps for running VTune as given in the following link on Ubuntu 16.04 :
We are able to get results for human_pose_estimation_3d but we are getting error while running human_pose_estimation_demo (2D). The screenshot is attached.
In vtune gui, for Application field we have given /home/amit/human_pose_estimation_3d_demo/human_pose_estimation_3d_demo.py
In Application parameter field,
-m /path/to/Human_pose_python/human-pose-estimation-3d-0001.xml -i /path/to/TestVideo.mp4 -d CPU
For human_pose_estimation_demo (2D),
-m /opt/intel/openvino_2020.1.023/deployment_tools/tools/model_downloader/intel/human-pose-estimation-0001/FP32/human-pose-estimation-0001.xml -i /home/amit/TestVideo.mp4 -d CPU
After running human_pose_estimation_demo (2D) , we are getting error as shown in screenshot attached.
vTune version : Intel(R) VTune(TM) Profiler 2020 (build 605129)
GCC version : 5.4.0
Thanks for reaching out to us. We would need a few clarifications to help us debug your issue.
1)For "human_pose_estimation_3D" you have mentioned that you are passing the python file(.py file) as the application. But for profiling python applications the right way should be to pass "python" as the application and the python script(.py file) as application parameter. So is that a typo in your question about the application and application parameter, as you have mentioned "human_pose_estimation_3D" does work for you.
2)For human_pose_estimation_demo 2D, are you running the application build from the sample code made available with openvino or have you made any changes to the source code?.
3)Could you verify if the human_pose_estimation_demo 2D application is working fine in your system when running the application without using vtune
We have tried profiling human_pose_estimation_demo 2D sample and could observe the profiling works without issues.Could you please provide an update on the clarifications to debug your issue.
Thanks for the update.
Actually human_pose_estimation_demo 2D is running fine now. We were providing wrong path in the application parameters due to which the error was occuring.