Skip to content

UMAP spectral initialization fallback to random on error#6750

Merged
rapids-bot[bot] merged 4 commits intorapidsai:branch-25.06from
aamijar:umap-spectral-fallback-fix
May 19, 2025
Merged

UMAP spectral initialization fallback to random on error#6750
rapids-bot[bot] merged 4 commits intorapidsai:branch-25.06from
aamijar:umap-spectral-fallback-fix

Conversation

@aamijar
Copy link
Copy Markdown
Member

@aamijar aamijar commented May 17, 2025

Resolves #6743

@aamijar aamijar requested a review from a team as a code owner May 17, 2025 01:34
@aamijar aamijar requested review from cjnolet and tfeher May 17, 2025 01:34
@aamijar aamijar requested review from csadorf, divyegala and jinsolp May 17, 2025 01:35
@aamijar aamijar self-assigned this May 17, 2025
@aamijar aamijar added bug Something isn't working non-breaking Non-breaking change labels May 17, 2025
@aamijar aamijar requested a review from btepera May 17, 2025 01:41
@divyegala
Copy link
Copy Markdown
Member

@btepera can you try your workflow with this PR and let us know how it goes?

Copy link
Copy Markdown
Contributor

@viclafargue viclafargue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, @aamijar, LGTM. It might be a good idea to double-check that everything in spectral init is allocated following RAII principles to prevent potential memory leaks when throwing the exception.

@divyegala
Copy link
Copy Markdown
Member

/merge

@rapids-bot rapids-bot Bot merged commit 565eee5 into rapidsai:branch-25.06 May 19, 2025
93 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working CUDA/C++ non-breaking Non-breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] UMAP spectral init fails to converge under certain conditions

4 participants