I’m not positive but I think what’s happening here is you’re using seed terms that aren’t in your vectors table. This means you’re ending up with a 0 vector as the query. Does that sound likely, or are the terms broadband and internet definitely in your vectors file?
I am more than sure that it exists in the vectors file since I’m using the same file as earlier and that one worked fine. The only difference here is the upgraded version of spacy and prodigy.
Thanks! And okay, there seems to be something wrong with the similarity comparison – we'll look into this. It's possible that it just requires a small fix to the recipe, which you can patch yourself in the meantime.
Ah yes, what I meant was, the underlying thing that Python outputs here is a warning (UserWarning), not an error that stops the process. In other contexts, it could just mean that one word doesn’t have a word vector, which is totally fine. But in this case for some reason, spaCy thinks it’s comparing empty vectors, so you’ll see a warning and there are no suggestions. That’s why it’s stuck at “Loading…” and nothing comes up.
Anyway, we’ll hopefully have a fix for this today!
Just implemented the fix for this, which should be released today. I’ve implemented an extra check in the recipe to avoid iterating over words which don’t have a vector, to avoid the warning spam.
In the meantime, you can set the environment variable SPACY_WARNING_IGNORE="W008" to prevent the warnings from coming up. The warnings are really the only problem here: with so many warnings printed, the loop runs fairly slowly, which is why you’re not seeing anything coming up. If you suppress the warnings and let the similarity function run, you should see results.
Just released v1.8.2, which adds a fix to the recipe to automatically skip words with no vectors. This prevents the warning from being raised. So it should now also work as expected without the environment variable