-
Notifications
You must be signed in to change notification settings - Fork 7.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
example runtime error:message_lite.cc:123 Can't parse message of type "caffe.NetParameter" #787
Comments
I'm experiencing the same issue with master branch of Caffe. I think this was introduced by BVLC/caffe@dc6d330 - it added a clip layer which seems to cause problems. |
There appear to be other commits before that one that also mention a clip layer. I just changed from master to f019d0dfe86f49d1140961f8c7dec22130c83154 in the two relevant places: Line 616 in f49e184
and Line 651 in f49e184
It probably makes sense to switch to a specific tag or commit rather than master to avoid this type of issue in the future. Especially since from the look of it, the only way to be compatible with master now is to update the weights file. |
@jpapon you are right,thanks,by the way,I can't checkout:f019d0dfe86f49d1140961f8c7dec22130c83154,so checkout another commit:864520713a4c5ffae7382ced5d34e4cadc608473,rebuild caffe and openpose,it works fine |
@AlexLuya Please reopen this, it’s a bad bug that breaks new checkouts of Openpose, or any build that uses Caffe master. It needs to be fixed. I would submit a pull request, but the owners of the repo need to decide what commit or tag of Caffe they want to use. |
[libprotobuf ERROR google/protobuf/message_lite.cc:123] Can't parse message of type "caffe.NetParameter" because it is missing required fields: layer[0].clip_param.min, layer[0].clip_param.max |
I meet the same problem,I have reinstall the caffe,the problem is still |
Same issue here |
Same issue here |
Actually, I solved by select "Build Caffe" and do what exactly #787 (comment). So for me, not use your own Caffe even built with older commit instead of 'master'. Just let openpose build its own Caffe with older Caffe commit by changing the CMakeList.txt of OpenPose. I am using ubuntu 18.04. |
这是由于openpose版本与你自己下载的caffe版本不兼容所造成的(最新的caffe加了一个层,导致与openpose中原有的模型不兼容),解决办法:1.用openpose里自带的caffe来build。2.把你的caffe卸载,然后用这个版本: https://github.com/BVLC/caffe/tree/f019d0dfe86f49d1140961f8c7dec22130c83154 其他方法正常配置就可以了。 This is your openpose is incompatible with your caffe. The solution is : 1.use the openpose 's caffe ; 2.use this caffe: https://github.com/BVLC/caffe/tree/f019d0dfe86f49d1140961f8c7dec22130c83154 |
FYI, I tried to build my own version of caffe with that specific commit and did not "Build Caffe" in Openpose's CMakeLists.txt. It just doesn't work for me. The only way for me is to change the CMakeList.txt in Openpose and clone that specific version of caffe, and select "Build Caffe" to let Openpose build its own Caffe with that specific commit/version. 😸 |
This error only happens in some Ubuntu machines. Following #787, compile your own Caffe with an older version of it. The hacky (quick but not recommended way) is to follow #787#issuecomment-415476837, the elegant way (compatible with future OpenPose versions) is to build your own Caffe independently, following doc/installation.md#custom-caffe-ubuntu-only. (This message will be added to the doc/faq.md doc) |
My solution is compiling openpose 's caffe first, then setting the compiled caffe lib and include directory in cmake-gui. |
I got OpenPose demo to work on FreeBSD using the master branch of Caffe as of today (Oct-2-2022): I had to modify and remove some caffe files which I stated on the issue section: can't find it now... I first built caffe on it's own directory. I then linked it to OpenPose using with cmake:
|
Executed Command (if any)
cd /path/to/openpose/build/examples/openpose/
./openpose.bin --face --logging_level 0
OpenPose Output (if any)
Type of Issue
Your System Configuration
Latest GitHub code
The text was updated successfully, but these errors were encountered: