feat: Implement Target Word Context Drift Visualizer using BERT
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- fastapi, nextjs, python, typescript
- Domain
- api, frontend, full-stack, machine-learning
Research direction
Start with the proposed FastAPI /api/context-drift endpoint and Next.js /context-drift route. Define the model-output and visualization flow from the checklist, then verify that two contexts produce target-word representations, a 2D comparison, cosine similarity, and the specified visual display.
Written by the indexing model from the issue text.
Description
Description
Word2Vec produces static vectors where "bank" (savings) and "bank" (river) share the same representation. This issue aims to build a feature where a user can enter a target word and two distinct sentences to visualize how the target word's embedding "drifts" in space based on semantic context.
Implementation Checklist
- Python API Endpoint:
- Create a FastAPI endpoint
/api/context-driftthat accepts:word(string)context_a(string containingword)context_b(string containingword)
- Load a lightweight transformer model (e.g.,
bert-base-uncasedordistilbert-base-uncased). - Extract the token representation for the target word from the final layer in both contexts.
- Return the raw dimensions (projected via PCA/t-SNE to 2D) and the cosine similarity between the two contextual states.
- Create a FastAPI endpoint
- Next.js Frontend:
- Build a clean interface at
/context-driftwith form inputs. - Render a visual 2D vector comparison graph (using SVG or Framer Motion) showing the displacement/drift between the two contexts.
- Display the cosine similarity score with dynamic color-coding (closer = bright gold, further = faded cyan).
- Build a clean interface at
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from scheuclu/language_drift
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
scheuclu/language_drift#38 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
scheuclu/language_drift#34 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
scheuclu/language_drift#32 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
scheuclu/language_drift#31 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
scheuclu/language_drift#30 ·
All issues in scheuclu/language_drift
Similar issues
-
comp/dashboard P3 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
NousResearch/hermes-agent#117722 ·
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·