-
Notifications
You must be signed in to change notification settings - Fork 2
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
Create a Jupyter Notebook out of the current code.... #22
Comments
I've recently pushed new code to the
It'd be good for someone with more expertise to modify the Markdown / add Markdown in the |
We had a little luck using google colab in some testing |
This is mostly done in tim's branch https://github.com/timr11/project-data-visualizations or captured in #55 |
Hi, sorry, seeing this just now. For local Jupyter environments, I think the best thing to do would be to install Jupyter Lab using Pip or Conda. This is the best way to set up a Jupyter environment. There's also the standalone Jupyterlab Desktop, which combines the server application and browser client into one app. For people who are terminal-only, Jupyter Console provides an interactive TUI interface to work with notebooks. VSCode and Pycharm Professional also have good notebook support. If you're already using either of these IDEs, then you can run your notebooks directly in it. I would advise against relying on GitHub Codespaces or Google Colab, unless there is funding to move to paid tiers. The free tiers come with terms and conditions which are always shifting, and I don't think these can exist as free products indefinitely. |
Our goal here is to allow the ease that Jupyter Notebook provides for outsiders to run our code, as well as offering some graphical capability in the Notebook.
We may host this in CoCalc, but would like to make a "plain vanilla" Jupyter Notebook that can be run in many containers.
This issue is confined to the act of demonstrating the run of a "supply problem" as documented in the film in the "doc" directory in a Notebook. No doubt there will be many enhancements, but this issue is just to get us started here.
It is unclear to me if this code can be kept in the repo with a single source of truth and be used in the notebook; but figuring that out is not part of this issue.
The text was updated successfully, but these errors were encountered: