Parametric umap worse than umap
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.3k
- Forks
- 871
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 5
Description
I carried out experiments with parametric umap and umap
umap
- Clusters spread out throughout the entire space.
- There are datapoints in between the clusters, that are representing the transition from one cluster to another {which I can notice in the data}
parametric umap:
- The final map has few dense clusters that are present only in a small region
- I can't observe any transitions
I used the default parameters for both umap and parametric umap.
I tried different model architectures.
I tried tuning the hyper-parameters for training such as batch size and number of epochs
Is there any reason that we are not able to get a good performance from p-umap similar to that of the umap ?
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 parametric UMAP entry point and compare it with standard UMAP using the default parameters described in the report. Reproduce the dense-cluster and missing-transition behavior, then inspect how model architecture, batch size, and epoch settings affect training. Done means identifying a reproducible cause or documenting the conditions under which both methods differ.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-visualization, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100