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
When running fitsne Python wrapper, it is common that you want to kill the process (say you screwed a parameter, etc.). However, while you can use CTRL-C to send a kill signal, this won't actually kill the c C-code that's running. Is there a way to fix this ? It seems important that you should be able to terminate the code even though it is just a wrapper.
The text was updated successfully, but these errors were encountered:
This is a great question. I frequently struggle with this in other packages as well: when calling C code in R, it does not seem to check for signals (e.g. ctrl-c). It looks like this might be a solution.
I will leave this open and add an enhancement label, as I think this would be a great feature. Perhaps at every iteration it can check signals.
When running fitsne Python wrapper, it is common that you want to kill the process (say you screwed a parameter, etc.). However, while you can use CTRL-C to send a kill signal, this won't actually kill the c C-code that's running. Is there a way to fix this ? It seems important that you should be able to terminate the code even though it is just a wrapper.
The text was updated successfully, but these errors were encountered: