question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Wrong error message during finetuning

See original GitHub issue

Rasa Open Source version

3.0.0rc2

Rasa SDK version

No response

Rasa X version

No response

Python version

3.8

What operating system are you using?

OSX

What happened?

Started with a rasa init project which trained an initial model. I made changes to the NLU training data by adding a new intent:

- intent: new_intent
  examples: |
    - yes i am new
    - can i break you
    - i don't think i want to do this
    - but its exciting

Ran rasa train --finetune. The process exits with:

InvalidConfigException: Cannot finetune because more than just the 'epoch' keys have been changed in the configuration. Please revert your configuration and only change the 'epoch' settings where needed.

whereas according to 2.8.x, the log should have been:

2021-11-16 15:44:23 INFO     rasa.model  - Data (nlu_labels) for finetune section changed.
NLU model can not be finetuned.

which is the correct info as we only changed the data and added a new intent label which should disallow finetuning.

Command / Request

rasa train --finetune

Relevant log output

No response

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:9 (9 by maintainers)

github_iconTop GitHub Comments

2reactions
dakshvar22commented, Nov 18, 2021

It still doesn’t explain why you got the config mismatch error message, rather than the nlu mismatch error message

Yep, that should be investigated and fixed 😄

0reactions
ka-bucommented, Nov 18, 2021

Problem seems to be that in the default project, we fill in [“debug_plots”, “augmentation_factor”] but for some reason those parameters are not set when running rasa init – Guess that comes from some mismatch of defaults for those cli parameters.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Errors when fine-tuning T5 - Beginners - Hugging Face Forums
Hi everyone, I'm trying to fine-tune a T5 model. I followed most (all?) the tutorials, notebooks and code snippets from the Transformers ...
Read more >
Error while fine-tuning Q/A model #287 - GitHub
While using the prescribed annotator and trying to fine-tune the model I keep on getting this error. This is the annotator I used...
Read more >
Chapter 9 Fine Tuning, Error Messages, and Troubleshooting
Problem — Occasionally you see CHECKSUM ERROR, WRITE ERROR, or READ ERROR messages in the messages files of the daemons. Possible cause —...
Read more >
How to fine tune failure detection | Dynatrace news
Typically, when things go badly wrong, unexpected exceptions are triggered and they won't be caught by the code so Dynatrace will detect them....
Read more >
Errors while fine tuning InceptionV3 in Keras - Stack Overflow
The error is caused because my labels r integers, I gotta compile it by sparse_categorical_crossentropy which is set for integer labels ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found