consistent signature across core and nlu `persist` methods
See original GitHub issueBoth core policies and nlu components are persisted with a method called persist
, however their signatures are inconsistent, i.e. core persist
s usually take only a single string that is the path where the component should be saved (i.e. including the filename), while in nlu persist
s it is mixed between path and path+filename.
(Also the path variable sometimes called something else)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:10 (9 by maintainers)
Top Results From Across the Web
Command Line Interface - Rasa
Performs a 80/20 split of your NLU training data. Converts training data between different formats. Migrates 2.0 domain to 3.0 format. Checks ...
Read more >How Do Chatbots Understand?. Building a Chatbot with Rasa
We'll now talk about how Rasa implements bot understanding through intents. ... Rasa provides support for evaluating both the NLU and the Core...
Read more >CONSISTENT COACHING AND ALIGNMENT
practices built around common and consistent purposes, training and support for teachers and school administrators. My paper examines a system that provides ...
Read more >Assurance Argument - Exported on 10/18/2021
opportunity for students through innovative teaching, scholarship, ... As part of NLU's core commitment to building a culture that values ...
Read more >https://www.nl.edu/media/nlu/downloadable/nceonepo...
The AC assures that Signature/Key Assessments have been vetted through ... takers are consistent over repeated applications of a measurement procedure 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
Yes, my bad, path is in deed a dir. It would definitely be breaking but I think it’s worth considering for 2.0 as a having similar components of an api work in similar ways makes it more useable imo.
Will be tackled by the model architecture revamp.