-
Notifications
You must be signed in to change notification settings - Fork 569
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Widgets not Exporting to HTML #920
Comments
Thank you for the positive feedback! You might want to take a look at #900 for embedding the widget state (and possibly #901 for embedding a png version of it). Would be great if you can test it out and give feedback. An easy way to install would be: |
Hi, I did the following (I guess this installs the version for #900? I must admit I'm still a bit new to this...):
Followed by:
Note that the To be honest, a png version would already be perfectly sufficient, my use case is going to eventually be to display progress bars (see here: https://github.com/tqdm/tqdm#ipython-jupyter-integration). I'd like to use this to monitor some long supercomputer simulations I have running. Should I instead try #901? If yes, how do I go about installing that one? Or should I provide some more information to understand why #900 doesn't work? |
I'd like to know why this does not work first. If you do: $ python -m nbconvert test.ipynb --to ipynb --execute Does your
|
Awesome! That seemed to do the trick! Thanks!!!!! It also works in my monitoring notebook that I had planned on using! The red progress bar is a widget instance: Very cool...I'd recommend that we can close this issue, but maybe it would be good if #900 gets merged into the main nbconvert? Then other people won't have to install it by hand. |
Great to hear it is working. Could you explain a bit more on what kind of workflow you have here? How is the notebook generated, from some cron job? |
Sure: I work in climate modelling, and we often have very long simulations. Walltimes for one experiment can range from 1 week to, in extreme cases, 3-4 months. The "normal" workflow in our department normally involves coming to the institute in the morning, logging on to whatever supercomputer your job is running on, and doing a bunch of maintenance and checks by hand. Since I'm lazy, I thought I should find a way for this to work automatically. I write a small template notebook which has some things I'd like to check. It uses paramiko to execute some remote commands to figure out the computing queue, opens some log files and parses out information from them. In principle, I could also make plots of some interesting climate quantities (temperature, precipitation, whatever else) I test this by hand for until it looks like I want, and then I have a cronjob running which automatically executes the notebook, converts it to html, and then moves the file to our webserver. So, now I can keep an eye on my simulations from anywhere with a browser and vpn access. Putting the widgets in is basically just beautification, I could just plot the progress with Matplotlib, but that looked (in my option) ugly. |
Thanks for sharing!
I translate that as 'I prefer to automate simple/dumb stuff' ;) |
Closing since the associated PR was merged a while back and released. |
Hello,
First off, I think that the jupyter project is fantastic, it's completely changed my workflow! Great work!
Currently, I'm trying to export widgets to a static html page. Note that these widgets are not expected to actually work (obviously I'd need to connect to a kernel to do that). For right now, I just want them to render.
I have installed the dev version (eb3b0a7) of nbconvert using the instructions from the README.
$ git log --pretty=format:'%h' -n 1 eb3b0a7 $ jupyter nbconvert --version 5.4.0.dev0
I also have installed jupyter and ipywidgets via Conda:
Unfortunately, if I try to export ipywidgets to html, they do not appear in my browser when I open the html file (see screenshots).
Any help would be greatly appreciated, and please let me know if I can provide any further information to help debug this problem.
Thanks!
Paul
The text was updated successfully, but these errors were encountered: