lmcinnes / lmcinnes/umap

Is DensMAP parallelized? If we set random_state, are the results still stochastic?

Open
#784 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
8.3k
Forks
871
Avg merge
1d 13h
Merged PRs (30d)
5

Description

This seems to be just as slow whether using `random_state=None` or a specific seed e.g. `random_state=42`.
```python
umap_trans = umap.UMAP(
densmap=True,
output_dens=True,
dens_lambda=self.dens_lambda,
n_neighbors=30,
min_dist=0,
n_components=2,
metric="precomputed",
random_state=random_state,
).fit(dm)
```
I'm also not sure if by setting `random_state=42` the results are actually deterministic.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the supplied UMAP configuration with densmap=True, output_dens=True, metric="precomputed", and both random_state=None and random_state=42. Inspect the DensMAP implementation and its parallel execution path to determine whether seeded runs are deterministic and whether parallelization changes runtime. Done means documenting the observed behavior and the relevant conditions.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.