Feature 'active_form_sales_form_form' could not be found in feature map.
rasa_core.featurizers - Feature 'active_form_sales_form_form' (value: '1.0') could not be found in feature map. Make sure you added all intents and entities to the domain
Hi Azizullah, Did you find an answer to these messages? I am starting to see those in my bot and not sure what it is, and what should I correct. Any help, much appreciated
Thanks
@azizullah2017 I should probably reference with the user tag, my mistake Hi Azizullah, Did you find an answer to these messages? I am starting to see those in my bot and not sure what it is, and what should I correct. Any help, much appreciated
Thanks
I do face the same warning
Having the same problem
try to check the domain.json
in the model created after make train-core
to check that it exists.
you might find it in models/dialogue/domain.json
Thank you @hossa95 in my case. I can see âactive_form_agenda_formâ as the very last item on the domain.json
Shaii I delete that? or having âactive_form_agenda_formâ in the domain.json is the expected behavior?
I am not sure I am understanding the reason of this warning, and by the way it is printed twice on the log screen.
WARNING rasa_core.featurizers - Feature âactive_form_agenda_formâ could not be found in feature map.
Thanks again
I am also facing the same issue (training time) for all the forms defined in my domain.yml. Additionally I get the same warnings during run time as well (http api) and seems to impact the responses I get back from the bot. Has anyone faced the same issue at the run time as well?
@akelad do you have any thoughts on this one? explain and chitchat sample here GitHub - RasaHQ/conversational-ai-workshop-18: Example showing generalisation is not working or get a wrong response from bot on my data set when I use EmbeddingPolicy. Also any pointer in general to implement explain intent - how does nlu identify explain intent?
@apurva I would recommend to use keras policy without using the parameter of â argument 0
Any update on this one?
"Thank you @hossa95 in my case. I can see âactive_form_agenda_formâ as the very last item on the domain.json
Shall I delete that? or having âactive_form_agenda_formâ in the domain.json is the expected behavior?
I am not sure I am understanding the reason of this warning, and by the way it is printed twice on the log screen.
WARNING rasa_core.featurizers - Feature âactive_form_agenda_formâ could not be found in feature map.
Thanks again"
@azizullah2017 Thanks for your input but I would like to use EmbeddingPolicy or at least would like to understand why I am getting that warning. In either case trying to see how i can implement âexplain/chitchatâ intents. Based on the article it seems attention model in EmbeddingPolicy should perform better functionally. @Juste do you have any thoughts on the issue I have reported earlier on this thread?
I really donât know whatâs wrong ⌠you should see it in the domain.json
⌠can you post ur nlu pipeline and your train_dialogue
function may be we can find something missing
thank you @hossa95 for your answer and I am not sure I am understanding all the information you are requesting Below is an extract of my domain.json where you can see at the end the âactive_form_agenda_formâ
âstatesâ: [ âintent_affirmâ, ⌠⌠âprev_agenda_formâ, âactive_form_agenda_formâ ] }
Here the NLU pipeline
pipeline:
- name: tokenizer_whitespace
- name: ner_crf
- name: ner_synonyms
- name: intent_featurizer_count_vectors token_pattern: (?u)\b\w+\b
- name: intent_classifier_tensorflow_embedding epochs: 100
- name: âner_duckling_httpâ url: âhttp://localhost:8000â locale: âes_MXâ dimensions: [âtimeâ,âPhoneNumberâ]
the train dialogue I am using is in the makefile train-nlu: python -m rasa_nlu.train -c config_tf.yml --fixed_model_name current --data data/nlu.md -o models --project nlu/default --verbose
train-core: python -m rasa_core.train -s data/stories.md -d domain.yml -o models/dialogue -c policy_config.yml --augmentation 0 --debug --dump_stories --debug_plots
hope this helps to clarify @Juste hope you can add some light here
Thanks everybody
Hi @amsolu, Have you resolved the issue?