Inconsistency between demo and github vectors

Open
#162 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
machine-learning

Research direction

Compare the 2019 downloaded vectors with the demo for “eyries” and “Beekeeping|VERB”, using the issue examples as the starting point. Determine why the available terms and associations differ, then document a reproducible explanation or resolution.

Written by the indexing model from the issue text.

Description

Hi,

Thanks for providing the code for sense2vec! We noticed that for several examples, the output of the vectors we downloaded on sense2vec was different than the demo (we're using the 2019 version). For instance, the word "eyries" has no embedding when using the downloaded vectors, but the demo shows associations for this word. Additionally, the associations for "Beekeeping|VERB" in the downloaded vectors are available, but they are not available on the demo (Beekeeping|auto leads to weird associations, like "Throats").

If there are any insights behind this inconsistency, we would greatly appreciate it!

Dominant language
Python
Stars
1.7k
Forks
236
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from explosion/sense2vec

All issues in explosion/sense2vec

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.