I’m using rasa for building my reminder chatbot where when a user gives a time , the time is extracted as the text what user gives instead of extracting timestamp…What is the issue and how it can be solved
Yes, this is the case in rasa==1.10. It’s actually more reliable though, because time can be a single value or an interval, and if it is an interval then in rasa<=1.10 it was represented in a pretty strange way in the value. The timestamp (or timestamps, if you get an interval) are still available in the additional_info portion of the entity. For an example of backward-compatible parsing of the duckling time entity, see parsing.py in the financial-demo bot custom actions
@mloubser Why is it that when I run DucklingHTTPExtractor on my local machine with rasa==1.10.1, I get different results than when I run it on my rasax server running on a GCP VM (I’m running duckling on the vm with docker).
Below is an example:
When I run the message “$2000-3000” using rasa shell nlu, I get the following output:
But when I run the same in the Interactive Learning section of the RasaX UI on my GCP VM, I don’t get any of these entities. In fact, it doesn’t even catch the same text as an entity.
Do you know why this is the case or how I can fix this?
I understand, but what I’m trying to say is that for some reason when I run rasa shell nlu on my local machine with $2000-3000 as text, DucklingHTTPExtractor extracts an amount-of-money entity, but on my GCP instance, it doesn’t even recognize $2000-3000 as an entity in the first place, so I can’t get any value from it at all.
I have a feeling this is happening because the Rasa/duckling fork doesn’t have the same rules as the main facebook version of duckling, because the facebook version is what I downloaded on my local machine and I believe the duckling docker image uses the Rasa fork.