-
Notifications
You must be signed in to change notification settings - Fork 19.5k
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
Add ResNet [18, 34]
to keras.applications
#15269
Comments
Can I work on this? |
@quantumalaviya of course. Just send a PR. It should be welcomed. |
So, I just wrote the code but I notice some differences in the number of parameters when compared to https://github.com/qubvel/classification_models. Any suggestions on how to add weights? |
Thanks for opening the issue. Can you provide a paragraph as a proposal for justifying adding this model? If you can provide some context of how widely this is used or some citation, that would be helpful. |
@rchao @quantumalaviya could you please check out this implementation, it already exists in |
https://github.com/breadbread1984/resnet18-34 . you may try this implement. |
+1 |
@breadbread1984 It would be nice to send PR. WDYT? |
@LukeWood Will the new model be added to |
for now keras.applications. |
In the end, we added the model in keras-cv, see this PR |
System information.
TensorFlow version (you are using): 2.5
Are you willing to contribute it (Yes/No): Yes.
Describe the feature and the current behavior/state.
Currently, we have
ResNet 50/101/152
. However, sometimes it's needed to test the idea initially with some small models quickly and for that, if we want to choose a res-net-based model we can't just pick 50 because it's still too heavy to train. That's why we think it would be nice to have resnet18 and resnet34 as well with the keras packages.Will this change the current api? How?
Yes. It will include
Who will benefit from this feature?
ML engineers and researcher who uses
tf.keras
.Others
Others implementation: https://github.com/qubvel/classification_models
The text was updated successfully, but these errors were encountered: