Enable Pipeline arguments for the models on the widget
See original GitHub issueWe have uploaded (still private) a model fine-tuned on a high quality Named Entity Recognition (NER) private dataset. Although the dataset is better than conll2002, in the examples like the one from here the widget provides weird values like “…Wolf (PER) gang (O)…”. This should be fixed with the pipeline parameters, more concretely with the aggregation_strategy
parameter.
I thoroughly checked this website and I have not found any way to alter this default pipeline parameter value. Maybe you could tackle this by introducing a new parameter to the widget.
By the way, I do not see the widget parameter here: https://github.com/huggingface/huggingface_hub/blame/main/modelcard.md
Issue Analytics
- State:
- Created 2 years ago
- Reactions:6
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Widgets - Hugging Face
Enabling a widget. A widget is automatically created for your model when you upload it to the Hub. To determine which pipeline and...
Read more >Building a Panel Pipeline - Quansight
To construct a Panel pipeline, we need to create parameterized classes (i.e., classes that inherit from the param. Parameterized class from the ...
Read more >panel.pipeline — Panel v0.14.1 - HoloViz Panel
[docs]class Pipeline(Viewer): """ A Pipeline represents a directed graph of stages, which each return a panel object to render.
Read more >Set secret variables - Azure Pipelines | Microsoft Learn
Go to the Pipelines page, select the appropriate pipeline, and then select Edit. Locate the Variables for this pipeline. Add or update the ......
Read more >Customize pipeline configuration - GitLab Docs
You can enable this in the project settings: ... If the pipeline succeeds, the coverage is shown in the merge request widget and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
i think we can definitely support this use case, and I think the way to go here would be to make the API calls configurable through the
inference:
attribute in the model card metadata.So something like:
(
widget:
sounds not appropriate to me because it controls the frontend, not the pipeline/API, and besides it would be hard to extend the current data type (an array of strings or objects to be used as simple inputs).inference:
is already defined but can only be false currently (to turn off the inference + widget))The parameters would then be set at the model repo level and not necessitate any frontend change (apart from tweaking the API call)
Thoughts?
(we should make sure that those options are documented consistently btw)
@julien-c yes I’ll work on this 👍