Rasa: `rasa train` cannot detect changes on lookup tables

Created on 9 Apr 2020  Â·  5Comments  Â·  Source: RasaHQ/rasa

Rasa version: Rasa 1.9.5

Python version: Python 3.7.7

Operating system (windows, osx, ...): OSX

Issue:
When adding entries in the contents of the lookup table which is located on a separate file, as per the new standards, running rasa train will not detect these changes and outputs that you can reuse the existing model, instead. After verifying it through the rasa shell nlu, the added items in the lookup table are not detected.

Temporary solution: Delete your models and retrain using rasa train.

Other information: The lookup tables are not located on the data folder.

stale type

All 5 comments

Thanks for raising this issue, @JustinaPetr will get back to you about it soon✨

Please also check out the docs and the forum in case your issue was raised there too 🤗

Not sure if this is the same or a different issue, but we could not get our lookup tables to work at all with DIET classifier ( entity_recognition: True ). It wasn't until we implemented CRFEntityExtractor that the lookup tables were read during training. This seems like either a bug or, if this is known, maybe this information should be added to the documentation.

Rasa version: Rasa 1.9.6

Python version: Python 3.7.5

Operating system : OSX

config.yml:

language: es
pipeline:

  • name: WhitespaceTokenizer
  • name: RegexFeaturizer
  • name: LexicalSyntacticFeaturizer
  • name: CountVectorsFeaturizer
  • name: "CRFEntityExtractor"
    BILOU_flag: True
  • name: CountVectorsFeaturizer
    analyzer: "char_wb"
    min_ngram: 1
    max_ngram: 4
  • name: DIETClassifier
    entity_recognition: True
    epochs: 30
    number_of_transformer_layers: 4
    transformer_size: 256
    use_masked_language_model: True
    embedding_dimension: 30
  • name: EntitySynonymMapper
  • name: ResponseSelector
    epochs: 100
    policies:

    • name: MemoizationPolicy

    • name: TEDPolicy

    • name: MappingPolicy

    • name: FormPolicy

    • name: TwoStageFallbackPolicy

      nlu_threshold: 0.2

      core_threshold: 0.2

      fallback_core_action_name: action_default_fallback

      fallback_nlu_action_name: action_default_ask_affirmation

@bubjanes I think your issue is unrelated.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

This issue has been automatically closed due to inactivity. Please create a new issue if you need more help.

Was this page helpful?
0 / 5 - 0 ratings