-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
if batch = TRUE in training, fgraph of umap_transform is transposed if n_epoch is set to 0 #118
Comments
fgraph of umap_transform also transposed if
|
Thank you for the report! This was due to trying to avoid doing unnecessary processing when the UMAP optimization won't occur (but some of it actually is necessary either way). Should be fixed in the dev version now. |
Will be fixed in the next CRAN release |
amazing, thank you! |
The code above gives the transposed
|
Yeah I messed this one up and results were inconsistent between @PedroMilanezAlmeida I think I should have been clearer about my understanding of what the correct dimensions for |
@PedroMilanezAlmeida I've pushed a change (and added more tests) that should ensure that the output dim for |
Ugh sorry should have gotten back to you asap. I am not partial to which
dimension (rows or cols) the mapped obs “should” be. Just consistency would
be enough 👍 thanks again for the prompt response and action!
…Sent from my phone
On Sat, Sep 7, 2024 at 12:00 James Melville ***@***.***> wrote:
@PedroMilanezAlmeida <https://github.com/PedroMilanezAlmeida> I've pushed
a change (and added more tests) that should ensure that the output dim for
fgraph would always be (50, 100). Let me know if that's contrary to your
expectations, otherwise I will eventually close this. Not sure when the
next release of uwot will be.
—
Reply to this email directly, view it on GitHub
<#118 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADGZB7JZB6SCMUEJPZ62KP3ZVMPILAVCNFSM6AAAAABERAJJN2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZVGY4DOOJTHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
on my system, this is a reproducible example:
The text was updated successfully, but these errors were encountered: