You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Hi (currently doing some uni semestral work), running t-SNE with high amount of iterations (eg. 5k) may take a very long time, especially with medium to big data (mine is 10k 10-dims points) on not high-end PCs. My app provides way to stop such computation, which must be unfortunately handled by Thread#stop(), because the current code provides no progress listener nor checks for Thread#isInterrupted().
Describe the solution you'd like
Ideally provide listener with iterations granularity - sth like each X iterations call supplied Consumer<Integer>. This approach provides fine control to executor, which may also check for thread interruptions. Might also use Predicate<Integer> and throw InterruptedException
Describe alternatives you've considered
Or at least check for Thread#isInterrupted() periodically.
Additional context None, except having a nice day :)
Actually, there is also no way to control stream parallelism
The text was updated successfully, but these errors were encountered:
The update() method takes iterations parameter. Instead of stopping the computation, you may set a small value for iterations. If the results are not good enough, you can call update() again until the visualization looks good.
Is your feature request related to a problem? Please describe.
Hi (currently doing some uni semestral work), running t-SNE with high amount of iterations (eg. 5k) may take a very long time, especially with medium to big data (mine is 10k 10-dims points) on not high-end PCs. My app provides way to stop such computation, which must be unfortunately handled by
Thread#stop()
, because the current code provides no progress listener nor checks forThread#isInterrupted()
.Describe the solution you'd like
Ideally provide listener with iterations granularity - sth like each X iterations call supplied
Consumer<Integer>
. This approach provides fine control to executor, which may also check for thread interruptions.Might also use
Predicate<Integer>
and throw InterruptedExceptionDescribe alternatives you've considered
Or at least check for
Thread#isInterrupted()
periodically.Additional context
None, except having a nice day :)Actually, there is also no way to control stream parallelism
The text was updated successfully, but these errors were encountered: