ResNeXt Architecture

[DavidLandup0]

Short Description

ResNeXt is a pretty commonly used arch, had ~8k citations, and is oftentimes shown in comparison tables.
torchvision has ResNeXt as well. Might be a good fit.

Other Information

Signing up to work on it as well.

[innat]

It's been asked.
#917

@LukeWood could you please move above ticket here in kcv? And also these keras-team/keras#15267 keras-team/keras#15268 keras-team/keras#15816

[tanzhenyu]

Transferred.

[DavidLandup0]

While my PRs for WideResNet and ViT components are still being reviewed - could you assign this one to me too? :)
@LukeWood @tanzhenyu

[DavidLandup0]

Great, thanks! I'll work on this one in the upcoming days then while the rest is being reviewed.

[DavidLandup0]

Getting to this today/tomorrow. Could you formally assign me?

[IMvision12]

@DavidLandup0 are you still working on this?

[DavidLandup0]

Started but haven't finished it since I was focused on ViTs in the meantime. Want to collaborate on it? :)

[IMvision12]

Yeah!!

[DavidLandup0]

Can you reach out via LinkedIn/Twitter/something for easier comms and so we don't spam here?

[github-actions]

This issue is stale because it has been open for 180 days with no activity. It will be closed if no further activity occurs. Thank you.

[sachinprasadhs]

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.

[innat]

@sachinprasadhs

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.

Firstly, identifying which feature is required or missing can be done effectively, either by practitioners or the Keras team. Tickets in keras-cv were created only when such features were NOT available or when a specific need was encountered. Commenting after a significant delay and requesting the recreation of the same issue is neither efficient nor appropriate. Kindly move this ticket (and any other similar tickets with the same context) from keras-cv to keras-hub.