FORTH-ModelBasedTracker / PyOpenPose

Python bindings for the Openpose library
BSD 3-Clause "New" or "Revised" License
287 stars 80 forks source link

PyOpenPose failing due to error in OpenPoseWrapper():83 #56

Closed sandromario closed 6 years ago

sandromario commented 6 years ago

We had been using PyOpenPose successfully in one of our projects (deployed within a Docker image). However, one to two months ago, something must have changed which has resulted in PyOpenPose failing.

This is the error we get:

>>> op = OP.OpenPose((320, 240), (240, 240), (640, 480), "COCO", OPENPOSE_ROOT + os.sep + "models" + os.sep, 0, download_heatmaps)
/home/server/pyopenpose/PyOpenPoseLib/OpenPoseWrapper.cpp:OpenPoseWrapper():83
Starting initialization on thread. In src/openpose/pose/poseExtractorCaffe.cpp:netInitializationOnThread():177
Finished initialization on thread. In src/openpose/pose/poseExtractorCaffe.cpp:netInitializationOnThread():191
Starting initialization on thread. In src/openpose/pose/poseGpuRenderer.cpp:initializationOnThread():47
Finished initialization on thread. In src/openpose/pose/poseGpuRenderer.cpp:initializationOnThread():54
Starting initialization on thread. In src/openpose/face/faceExtractorCaffe.cpp:netInitializationOnThread():144
Finished initialization on thread. In src/openpose/face/faceExtractorCaffe.cpp:netInitializationOnThread():158
Starting initialization on thread. In src/openpose/face/faceGpuRenderer.cpp:initializationOnThread():36
Finished initialization on thread. In src/openpose/face/faceGpuRenderer.cpp:initializationOnThread():41
Starting initialization on thread. In src/openpose/hand/handExtractorCaffe.cpp:netInitializationOnThread():232
Finished initialization on thread. In src/openpose/hand/handExtractorCaffe.cpp:netInitializationOnThread():246
Starting initialization on thread. In src/openpose/hand/handGpuRenderer.cpp:initializationOnThread():36
Finished initialization on thread. In src/openpose/hand/handGpuRenderer.cpp:initializationOnThread():41

We can import cv2 and PyOpenPose successfully. The Openpose example script works too, writing keypoint files to disk.

Any idea where this idea might be coming from?

padeler commented 6 years ago

Do you have the latest openpose build? The API of openpose changes often and I try to update pyopenpose to work with the latest version. Current tested version is noted in the readme.

sandromario commented 6 years ago

We don't always update our setup immediately, but we always use a pair of OpenPose and PyOpenpose versions recommended by you. In this case we're talking about: Openpose: commit f430a7990df915ef92852e4b7744e06eecbd2b61 PyOpenpose: f8834f3

sandromario commented 6 years ago

We're sorry, actually it was a problem on our side, but we interpreted the above output as an error message procuded by PyOpenPose. Turns out that these messages had always been there, but they're merely warnings. Maybe it would help to actually have your application say it's a warning and not an error? Thanks!