Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

SSD example has missing files #3805

Closed
lvaleriu opened this issue Nov 12, 2016 · 8 comments
Closed

SSD example has missing files #3805

lvaleriu opened this issue Nov 12, 2016 · 8 comments

Comments

@lvaleriu
Copy link
Contributor

Havent you forgotten to add the files related to the scale layer?

Here you can see them in the original mxnet-ssd repository.

image

Thanks!

@piiswrong
Copy link
Contributor

it is modified and these files are no longer needed.
See if you can run the version in mxnet/exmaple

@lvaleriu
Copy link
Contributor Author

lvaleriu commented Nov 12, 2016 via email

@piiswrong
Copy link
Contributor

@zhreshold

@zhreshold
Copy link
Member

These layers are not required any more here. What error did you get? @lvaleriu

@zhreshold
Copy link
Member

Well, I want to make it clear that in order to comply the mxnet example style, I made several changes here in the example/ssd, thus the model is now slightly incompatible with the original repo. You will need to modify .params and .json in order to transfer model between these two repos now. However I don't recommend to do this.

The divergence could be solved when I finally make a change to the original repo. I'm still reluctant to do so because breaking the compatibility in the same repo is not a good idea.

@lvaleriu
Copy link
Contributor Author

You are right. I've messed up the code by including the old weights with
some old train file execution. Sorry for that. So you've gived up your
Scale layer with an existing one from mxnet?

On Sun, Nov 13, 2016 at 7:54 PM, Joshua Z. Zhang [email protected]
wrote:

Well, I want to make it clear that in order to comply the mxnet example
style, I made several changes here in the example/ssd, thus the model is
now slightly incompatible with the original repo. You will need to modify
.params and .json in order to transfer model between these two repos now.
However I don't recommend to do this.

The divergence could be solved when I finally make a change to the
original repo. I'm still reluctant to do so because breaking the
compatibility in the same repo is not a good idea.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#3805 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA4o_yzxU9OXWlTy6bUX57EmTx5jTiSaks5q910AgaJpZM4KwdtI
.

@zhreshold
Copy link
Member

Yes, the Scale layer was replaced by broadcast_mul.

@yajiedesign
Copy link
Contributor

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants