-
Notifications
You must be signed in to change notification settings - Fork 330
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Porting KerasAug into KerasCV #1939
Comments
@james77777778 thanks for the offer. Can you explain the source of the speedups? |
@jbischof Sure! I pick some layers for clarification:
Additionally:
If these improvements are in the plan of KerasCV, I can send the PR (maybe one fix/improvement one small PR?). |
Sounds great @james77777778! I would suggest starting with one or two layers with big improvements so that we can debug any issues early in the process. |
Thanks for reporting the issue! We have consolidated the development of KerasCV into the new KerasHub package, which supports image, text, and multi-modal models. Please read keras-team/keras-hub#1831. KerasHub will support all the core functionality of KerasCV. KerasHub can be installed with !pip install -U keras-hub. Documentation and guides are available at keras.io/keras_hub. With our focus shifted to KerasHub, we are not planning any further development or releases in KerasCV. If you encounter a KerasCV feature that is missing from KerasHub, or would like to propose an addition to the library, please file an issue with KerasHub. |
Hi KerasCV team,
I have worked on my own project KerasAug for a while to provide the powerful, performant and bug-free preprocessing/augmentation layers.
As I have noticed that
keras-core
is planning to refactor the preprocessing layers by incorporatingTFDataLayer
, it presents a opportunity to port some of the layers from KerasAug into KerasCV.You can visit benchmarks to see the improvement by KerasAug
Moreover, KerasAug addresses a lot of existing issues within KerasCV:
Will this project benefit the community? I'm willing to contribute!
The text was updated successfully, but these errors were encountered: