Skip to content
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

Fixed the padding calculation bug #443

Closed
wants to merge 17 commits into from
Closed

Fixed the padding calculation bug #443

wants to merge 17 commits into from

Conversation

sotanishy
Copy link
Contributor

When the padding is not an integer, like 1/2 or -1/2, it should be rounded up but instead it was rounded down, causing errors.

@Ram81
Copy link
Member

Ram81 commented Nov 10, 2018

@sotanishy GoogleNet export still doesn't work can you look into that. Can you also comment here a list of models which were not working in the original code and they are working after the fix, so that we can validate the models.

@sotanishy
Copy link
Contributor Author

Xception didn't work before but after the change it worked.

@Ram81
Copy link
Member

Ram81 commented Nov 10, 2018

@sotanishy can you test whether all the models mentioned in README are working fine or is there some model which is breaking.

@sotanishy
Copy link
Contributor Author

I haven't tested everything yet but GoogleNet export for keras worked.

@Ram81
Copy link
Member

Ram81 commented Nov 11, 2018

@sotanishy can you fix the Travis CI issues and test all the models listed in tested models (check if any other model which was working earlier is not breaking after the change). Once you are done with that we can go forward with the review.

@sotanishy
Copy link
Contributor Author

Importing keras models such as inception and VQA failed. I'm looking into why but I doubt it's related to the changes I made. Import and export for other models currently available in keras worked. GoogleNet and DenseNet, which were not available in keras before, were successfully exported to keras, too.

@Ram81
Copy link
Member

Ram81 commented Nov 13, 2018

@sotanishy the inception models were working fine before the change right?
I encountered a similar issue while fixing the bug can you please verify once again and if needed please fix the issue.

@sotanishy
Copy link
Contributor Author

I tried it on a different computer and everything worked fine. All models were imported and exported to keras successfully.

@thatbrguy
Copy link
Contributor

Hello @sotanishy, great work! It would be better to use np.ceil instead of math.ceil for consistency.

Also, I tried exporting Inception v4 and v3 from model zoo to Caffe and importing them again. The parameter counts were not equal to the master branch values (Issue #451 mentions some parameter count values for Caffe in the master branch). So I'm guessing some values are being calculated wrong in your branch. What do you think? @Ram81

@sotanishy
Copy link
Contributor Author

Exporting and importing them again in caffe worked, but the parameter count was more than what's mentioned in the issue.

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

Successfully merging this pull request may close these issues.

3 participants