“UndefinedMetricWarning: F-score is ill-defined and being set to 0.0 in labels with no predicted samples. ‘precision’, ‘predicted’, average, warn_for)”
"c:\users\tjcol\appdata\local\programs\python\python37\lib\site-packages\sklearn\metrics\classification.py:1143: UndefinedMetricWarning: F-score is ill-defined and being set to 0.0 in labels with no predicted samples.
‘precision’, ‘predicted’, average, warn_for) "
After I get them, the training freezes and I’m not able to train my model.
I tried now with a bit smaller dataset but I still have the same problem, could someone look at my dataset maybe there is a problem with it that I’m overlooking?
I am suggestion this because the warning you see is familiar to me and usually doesnt lead to a freeze. However I experienced quite different problems with a python version equal and greater to 3.7. Maybe this is worth a try.
If that doesnt lead to a working system, feel free to publish your dataset / zip the bot such that I can test it.
Hi, that training is with supervised embedding and that works for us all the time.
We tried now your pipeline and got a model with 93% accuracy that works poorly, it doesn’t understand anything that isn’t literally written as it is in dataset.
We are trying to train on pretrained embedding option and that doesn’t work for us, check it out:
language: “en”
pipeline: “pretrained_embeddings_spacy”
policies:
epochs: 75
max_history: 10
name: KerasPolicy
max_history: 10
name: AugmentedMemoizationPolicy
name: “FallbackPolicy”
nlu_threshold: 0.2
core_threshold: 0.1
fallback_action_name: “action_default_fallback”
In addition, when I trained now once again with this pipeline I check the memory conditions when it freezes and it was around 1.5GB and my computer has 12GB of memory.
Can you please tell me step by step how to debug the source code after cloning it? I cannot find any info on to how to do that when I’m using it in another project as a dependency. Thank you.
I would suggest to run your training locally with rasa installed from the cloned repo, then debug the parts of code of rasa that are executed during training
I’ve done that and my error happens while running rasa train nlu --debug since it doesn’t offer any insight in to the freezing error as there are no additional information logged while training.
Training still freezes on: Fitting 3 folds for each of 6 candidates, totalling 18 fits
[Parallel(n_jobs=1)]: Using backend SequentialBackend with 1 concurrent workers.