-
Notifications
You must be signed in to change notification settings - Fork 723
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
Darknet/YOLO or Caffe/R-FCN + Squeezenet #15
Comments
Great idea! I'm definitely interested in this. Perhaps Mr Darknet (@pjreddie) may also care to weigh in. The Darknet google group might also be a good place to ask this question: https://groups.google.com/forum/#!forum/darknet I'm not that experienced with Darknet yet. Do we know if it can handle DAG-shaped CNNs, or only linked lists? I guess this might be the point of the "route" layer, but I haven't looked at |
We may could invite the R-FCN author too, what do you think @daijifeng001? |
@forresti I think Darknet implements a DAG style except there is no bi-directional sense of nodes connections. In other works, .cfg processing is procedural, but shortcut and route layers allow us to connect previous nodes/connections to the current one. |
I found some errors on my previous Darknet/squeezenet.cfg... still got stuck at 5~6 loss error.
|
Thank you for sharing. However, your model triggers a seg fault when running the yolo training. Have you changed the source code as well ? thx. |
@djebm2, I have not modified the source code to run it. By the way I have a newer version that is now training with loss errors below 1.
|
Cfg file looks good, I think the first layer is 7x7 though right? Have you On Sep 7, 2016 7:23 PM, "Luiz Vitor Martinez Cardoso" <
|
@pjreddie it is good to hear from you buddy! Please check my latest versions of SqueezeNet for Darknet with route layers and batchnormalization. Please the check following variants:
OR
|
the avgpool layer will be really bad for detection since you throw out all Also, just so you know, squeezenet is good in terms of the number of On Wed, Sep 7, 2016 at 9:41 PM, Luiz Vitor Martinez Cardoso <
|
@pjreddie, yes. What about enabling xnor=1? Is it working? |
@pjreddie, by removing
Something went totally wrong:
Any idea? |
You can also check out the tiny-yolo model, it's based on the darknet http://pjreddie.com/darknet/yolo/#tiny On Wed, Sep 7, 2016 at 10:35 PM, Luiz Vitor Martinez Cardoso <
|
@pjreddie, I got a push notification about your commit and already started training it. Thanks! |
@Grabber I think squeezeNet has specially been designed for mimicking AlexNet which natively address the problem of classification. Therefore, as @pjreddie said it, average polling isn't a good idea for detection. I only see an FC layer that could overcome this, but I am afraid the number of parameters would explode and thereby compromise the pruning process. |
Do avgpooling on a cropped area (where the detected object is) might be useful? |
@pjreddie Dear pjreddie |
I think a very interesting combination with SqueezeNet is RFCN or YOLO for object detection. I'm trying to port SqueezeNet from Caffe to Darknet + YOLO.
Could someone help to review it?
It is a port from v1.1
squeezenet.cfg
I'm no sure how to exactly port these cases:
Concat layers are strange too, don't know what index use on [route] frame=-?
The text was updated successfully, but these errors were encountered: