Closed AustinHartman closed 2 years ago
My thoughts are: I completely overlooked this as a possible way of doing things (the increasingly horrid rat's nest of logic for all the possible ways to provide data to umap
and umap_transform
is a stellar example of how not to program a computer). Sorry for breaking this, and thank you for not only reporting it, but working out what the problem was. The error message was completely useless too, so whatever the opposite of kudos is to me all round.
I think this is now fixed on the master
branch. There will be a new submission to CRAN as soon as I also complete #96 (which should mean that I don't have to wait a couple of months before my next submission).
@AustinHartman version 0.1.14 of uwot
is now on CRAN and should contain this fix.
Great, this resolves my issue. Thank you for such a fast fix!
Hi - thanks for your work on this package. I've recently installed v0.1.13 and noticed some additional items in the returned UMAP models. It seems that when
umap
is called with precomputed nearest neighbors, the returned model can successfully be used as input toumap_transform
but whenumap
is called without precomputed nearest neighbors, the resulting model differs slightly andumap_transform
seems to error out somewhere around here. Increasing the num_precomputed_nns from 0 to 1 in the model which failed seemed to ameliorate the issue. Any thoughts on what's going on here? Thanks in advance!sessionInfo():