In my domain, I specified: slots: log: type: unfeaturized subtrahend: type: unfeaturized num_1: type: unfeaturized num_2: type: unfeaturized Then in my actions.py, I defined: def slot_mappings(self): return {“num_1”: self.from_entity(entity=“num”, intent=“caculate”), “num_2”: self.from_entity(entity=“num”, intent=“caculate”)} ‘num’ is entity recognized correctly by the intent ‘caculate’. However, when I run it, it reports: 2019-06-26 19:53:35 INFO rasa_sdk.interfaces - Tried to access non existent slot ‘num_1’ 2019-06-26 19:53:35 INFO rasa_sdk.interfaces - Tried to access non existent slot ‘num_2’ According to the documentation, it says custom mapped slot should also be specified in stories. However, how to specify it? The current examples all are categorical or bool values, so that it can specify the slot as a dictionary.However, in my case, the “num_1” and “num_2” are two numbers used in a caculator, whose values are unknown, and can’t be specified beforehand. My story looks like: ## caculate * caculate - action_caculate Should I include the slots below “action_caculate”? If yes, what’s the correct format?

Hi @twittmin are you using a FormAction or a CustomAction? As documented here: [image] Domain you are able to to something like: # calculate * calculate {"num_1": "59376"} - slot{"num_1": "59376"} - action_caculate Try to retrain your model with a story like this and see if it helps! Regards

@JulianGerhard , it’s a subclass of Action, not intended for FormAction. Do you mean the ‘59376’ can be an arbitrary number for the training?

Hi @twittmin if it is derived from Action, then you should be able to use my story suggestion. The 59376 is just an arbitrary sample that tells the story, that it should/could expect not only a triggered intent rather than an intent and an entity. If you mention “5555” instead in your utterance, then the slot would be filled accordingly. Does that answer you question?

Yes. Thank you, @JulianGerhard . Could you also take a look at my other question regarding “forgetting” entity history for each new utterance? [image] How to not remember entities in history? Rasa Open Source In one of my cases, I don’t want the tracker to remember any entities. For each new utterance, I want to only use newly extracted entities and slots. I remember somewhere I read it and there is a way to configure that, through domain or configuration file. Is there an actual way to do that? Do you have experience in dealing with this situation? It seems a common need. Thank you.

Why doesn't this slot_mapping work?

Rasa Open Source

twittmin (mcm) June 28, 2019, 1:36pm 5

Yes. Thank you, @JulianGerhard. Could you also take a look at my other question regarding “forgetting” entity history for each new utterance?

Do you have experience in dealing with this situation? It seems a common need. Thank you.

Topic		Replies	Views
Extract other slots neglects custom slot mappings Rasa Open Source	8	1770	November 15, 2019
Slot_mapping for rasa12 Rasa Open Source	2	591	June 27, 2019
Slot_mapping Rasa Open Source	6	7874	July 27, 2019
Having only custom slot mapping in rasa 2.1.3 forms Rasa Open Source	4	820	July 5, 2021
If a slot is not requested, slot mapping doesn't work Rasa Open Source	7	1828	May 26, 2020

Why doesn't this slot_mapping work?

Related topics