-
Notifications
You must be signed in to change notification settings - Fork 442
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
能否添加clip层 #276
Comments
我编译提示如下错误:`[ 0%] Running C++/Python protocol buffer compiler on /home/MobileNet-YOLO-master/src/caffe/proto/caffe.proto /home/MobileNet-YOLO-master/src/caffe/layers/clip_layer.cu(28): error: class "caffe::LayerParameter" has no member "clip_param" /home/MobileNet-YOLO-master/src/caffe/layers/clip_layer.cu(53): error: class "caffe::LayerParameter" has no member "clip_param" /home/MobileNet-YOLO-master/src/caffe/layers/clip_layer.cu(54): error: class "caffe::LayerParameter" has no member "clip_param" /home/MobileNet-YOLO-master/src/caffe/layers/clip_layer.cu(27): error: class "caffe::LayerParameter" has no member "clip_param" /home/MobileNet-YOLO-master/src/caffe/layers/clip_layer.cu(28): error: class "caffe::LayerParameter" has no member "clip_param" /home/MobileNet-YOLO-master/src/caffe/layers/clip_layer.cu(53): error: class "caffe::LayerParameter" has no member "clip_param" /home/MobileNet-YOLO-master/src/caffe/layers/clip_layer.cu(54): error: class "caffe::LayerParameter" has no member "clip_param" 8 errors detected in the compilation of "/tmp/tmpxft_00001518_00000000-6_clip_layer.cpp1.ii". src/caffe/CMakeFiles/caffe.dir/build.make:1120: recipe for target 'src/caffe/CMakeFiles/cuda_compile.dir/layers/cuda_compile_generated_clip_layer.cu.o' failed 我尝试编译BLVC版本是正确的。在YOLO这个版本中添加层与BLVC版本有区别么?需要额外做什么操作? |
e,看样子好像是你的caffe::LayerParameter没有写对,检查过了吗? |
1 similar comment
e,看样子好像是你的caffe::LayerParameter没有写对,检查过了吗? |
https://github.com/BVLC/caffe/blob/9b891540183ddc834a02b2bd81b31afae71b2153/docs/tutorial/layers/clip.md
BVLC版本中已经添加了这个层。
我自己尝试添加,修改proto文件。复制cpp、cu、hpp文件到对应目录,编译无法通过了。
The text was updated successfully, but these errors were encountered: