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

[Api inference] Split up tasks by modality #1461

Closed
wants to merge 2 commits into from
Closed

Conversation

NielsRogge
Copy link
Contributor

@NielsRogge NielsRogge commented Oct 19, 2024

This PR proposes to split up the inference API tasks by modality, similar to the docs of Transformers.

Before

Screenshot 2024-10-19 at 17 09 58

After

Screenshot 2024-10-19 at 17 09 37

@NielsRogge NielsRogge requested a review from Wauplin October 19, 2024 15:06
@HuggingFaceDocBuilderDev

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@Wauplin
Copy link
Contributor

Wauplin commented Oct 21, 2024

We thought about doing so with @osanseviero when writing up these docs but to be honest I find the split to be more confusing than being really helpful. Typically Chat completion can be considered "NLP" or "Multimodel" depending of if you are working with an LLM or a VLM. Someone could also search "Automatic Speech Recognition" under "Audio" while it's rightfully under "Multimodal". Also, I feel that the most demanded tasks for Inference API (e.g. text to image, chat completion, image text to text) are in the same category (multimodal) which will eventually be peaking up on the rest. Keeping things simple with only 1 layer avoids having to think about these questions.

@julien-c
Copy link
Member

yes i agree with @Wauplin

@NielsRogge
Copy link
Contributor Author

Ok fair :) will close this one

@NielsRogge NielsRogge closed this Oct 21, 2024
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.

4 participants