Skip to content
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

t-SNE errors when running sake with more than 1 cpu core #78

Open
psterk opened this issue Jan 28, 2020 · 2 comments
Open

t-SNE errors when running sake with more than 1 cpu core #78

psterk opened this issue Jan 28, 2020 · 2 comments

Comments

@psterk
Copy link

psterk commented Jan 28, 2020

If I use more than 1 CPU core, sake fails to produce t-SNE plots with the following error:

Library Rtsne loaded.
Library Rtsne loaded in cluster.

Timing stopped at: 2.894 0.368 7.259
Error in checkForRemoteErrors(val) : 
  2 nodes produced errors; first error: Operation not allowed without an active reactive context. (You tried to do something that can only be done from inside a reactive expression or observer.)

This happens on MacOS (Catalina) and on Ubuntu 18.04, both running R 3.6.1, shiny 1.4.0, Rtsne 0.15. NMF runs happily with multiple CPUs. I'm not sure whether this can be fixed easily, but I can live with just using one CPU core when I want to generate t-SNE plots.

@naikai
Copy link
Owner

naikai commented Jan 30, 2020

I'll take a look and get back to you. Thanks for reporting it.

@naikai
Copy link
Owner

naikai commented Mar 18, 2021

Hi @psterk ,

Sorry for the late reply. This is the message I got when I run t-SNE using 16 cores.
Can you tell me which back end you are using for running parallel jobs?
Thanks.


Library Rtsne loaded.
Library Rtsne loaded in cluster.


Stopping cluster

snowfall 1.84-6.1 initialized (using snow 0.4-3): parallel execution on 16 CPUs.

Library Rtsne loaded.
Library Rtsne loaded in cluster.


Stopping cluster

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants