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
I create long-running notebook servers on a remote node and run the front end on my laptop, using SSH port forwarding. This mostly works beautifully and takes the place of screen for me in many cases.
I have a problem when I evaluate a cell that takes a long time (say hours) to finish, and the connection between the front end and the notebook server drops out. In this case, the computation will finish (and even other pending cells will finish), but the stdout and results from the computation are not written into the notebook file. As a result, when I reconnect to the notebook, I am able to see variables (and generally kernel state) that resulted from the computation, but the stdout is lost.
I do not know if it would be challenging, but I would prefer that the outputs (and output number indicators) be written to the notebook file even if the front end is disconnected. This would make IPython even more powerful for interactive job control on remote machines.
Thank you.
The text was updated successfully, but these errors were encountered:
I create long-running notebook servers on a remote node and run the front end on my laptop, using SSH port forwarding. This mostly works beautifully and takes the place of screen for me in many cases.
I have a problem when I evaluate a cell that takes a long time (say hours) to finish, and the connection between the front end and the notebook server drops out. In this case, the computation will finish (and even other pending cells will finish), but the stdout and results from the computation are not written into the notebook file. As a result, when I reconnect to the notebook, I am able to see variables (and generally kernel state) that resulted from the computation, but the stdout is lost.
I do not know if it would be challenging, but I would prefer that the outputs (and output number indicators) be written to the notebook file even if the front end is disconnected. This would make IPython even more powerful for interactive job control on remote machines.
Thank you.
The text was updated successfully, but these errors were encountered: