<div class="gmail_quote">On 12 January 2012 08:18, Thomas Wiecki <span dir="ltr"><<a href="mailto:thomas.wiecki@googlemail.com">thomas.wiecki@googlemail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":16v">* Is it possible to change or disable the kernel time-out? I often<br>
start a long-running analysis in the notebook so I constantly get<br>
messages about an unresponsive kernel. Even worse, even after clicking<br>
on "Keep on running", the cell is not updated with new output (i.e.<br>
matplotlib plots) afterwards. Is that a bug?<br></div></blockquote><div><br>I thought the design was able to detect the kernel even when it was in long-running code - the 'heartbeat' runs in its own thread in C code.<br>
<br>The timeout is configurable - search for 'heart' in your ipython_config.py file. Others will be able to give you more details.<br> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div id=":16v">
* Is it possible to update all viewers when something changes? I'd<br>
like to use the notebook for collaborative coding and exploration of<br>
issues, so having the same IPython shell would be awesome. However, if<br>
two sessions are entering commands at the same time, I can access<br>
their variables, but I do not see new cells emerging or plots being<br>
generated as they are produced by the other party (would have to save<br>
and re-open).</div></blockquote></div><br>Not yet. Live collaboration is definitely planned, and the messaging architecture is designed to support it, but it's not been implemented yet.<br><br>Thomas<br>