lucidrains / lucidrains/vector-quantize-pytorch

LFQ: why can't we have projections?

Open
#192 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
4k
Forks
338
PR merge metrics
No merged PRs in 30d

Description

As title says, why can't we have projections in lfq? https://github.com/lucidrains/vector-quantize-pytorch/blob/5ae9c792e77b45751ac636eb72b310f09648aac3/vector_quantize_pytorch/residual_lfq.py#L86 they might be useful to have a better learning residual by residual

thanks

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with vector_quantize_pytorch/residual_lfq.py around line 86 and review how LFQ currently handles residuals. The issue needs clarification on the intended projection behavior; done would require an agreed scope for projections and evidence that the resulting residual-learning change works.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, pytorch
Domain
machine-learning
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.