| [ease-dev] Jupyter Kernels |
Hi,
This week i mostly spend debugging the code execution. In principle everything worked correctly but several clients had some issues. It is now possible to run code from all standard clients (and therefore hopefully from any client). The only issue left to fix is that the notebook does not print messages from stdout or stderr. All other clients do this correctly so it should probably be a minor thing but especially the notebook is rather complicated and I haven't found the issue yet. I am hoping to find it tomorrow so I can finally move on to publishing data from the kernel.
The basic setup is already in place as it is also necessary for handling executions. I had an offline session with Christian and we decided to go with the plan from my last post. Additionally I will have a look at adapters to help with parsing objects to the desired format.
The last thing I did was to create a simple module to be able to launch a kernel from script code. For now it only consists of a single method launchKernel(IScriptEngine) but we might also add code to directly start a Jupyter notebook, etc.
I will keep you posted, regards
Martin