Improve Docs for LanguageModelFeaturizer
See original GitHub issueThere’s a lot of confusion on the forum this week on how to configure the LanguageModelFeautizer
. This suggests that we may want to add documentation that explains how to link models. I think part of the issue here is that it’s hard for a user to know what the model_name
of any given model on huggingface might be.
Issue Analytics
- State:
- Created 2 years ago
- Comments:16 (13 by maintainers)
Top Results From Across the Web
Components - Rasa
LanguageModelFeaturizer #. Short. Creates a vector representation of user message and response (if specified) using a pre-trained language model.
Read more >Better Intent Classification And Entity Extraction with ... - Botfront
Rasa's DIETClassifier provides state of the art performance for intent classification and entity extraction. In this post you will learn how this algorithm ......
Read more >How to Build a Chatbot Using Rasa: Use Case of an AI Driving ...
In this article, we will learn how to build a chatbot using Rasa and NLU. The tutorial covers the use case of an...
Read more >Can't load class for name 'HFTransformersNLP'. in rasa ...
pipeline: - name: LanguageModelFeaturizer model_name: "bert" model_weights: "rasa/LaBSE". See the documentation for further details.
Read more >rasa Changelog - pyup.io
Improved Documentation - [11571](https://github.com/rasahq/rasa/issues/11571): Rasa SDK documentation lives now in Rasa Open Source documentation under the ...
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 Free
Top 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
Closing this ticket since https://github.com/RasaHQ/rasa/pull/10616 has been merged to 3.0.x
This was another user forum question that might be relevant for improving the docs. Seemingly the error came from a HF model using a different tokenizer than what we expect (e.g.
BertModel
withAlbertTokenizer
), which breaks due to the hard coded mapping in registry.py.