Weights when combining multiple UMAP models
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.3k
- Forks
- 871
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 5
Description
In this example https://github.com/lmcinnes/umap/issues/58#issuecomment-419682509 there was a `mix_weight` parameter to set a specific intersection weight.
When using the new `*` operator (https://umap-learn.readthedocs.io/en/latest/composing_models.html), is there a way to set a specific weight?
Could something like `mapper1 * mapper2 * mapper1` give a higher weight to `mapper1` (since we intersect it 2 times)? What is the proper way to do this?
Thank you :)
Contributor guide
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.
Research direction
Start with the composing_models documentation linked in the issue and compare its `*` operator behavior with the historical `mix_weight` example in issue #58. Determine whether weighted intersections are currently supported and define the expected semantics for repeated models before identifying the implementation and documentation changes needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100