Project My Latest project using copilot.Refer to youtube videos.
You can use MyBinder to make this more useable to your viewers.
Here is an example:
Click this here to launch a session where the person can actively use the notebook without installing anything. (It’s not perfect because you didn’t include the original PDF file, but you should get a good idea how it would work if you had provided that. That original PDF or something like it could be included in the files the session will have and others could swap in their own PDF.)
You need to click some buttons, so you cannot just do ‘Run All’. (In general, this is an anti-pattern design. ‘Run All’ working should be the normal expectation. However, I understand what you are aiming for here.)
The repo is a fork of yours:
Although basically I deleted all your content because you didn’t provide a working notebook file. The history of commits steps through an overview of how I converted the fork to what you see working.
This way, as a bonus, you get static view made without needing to do anything:
(That particular example is here on GitHub. In general, nbviewer supports many more abilitie, such as javascript backed plots and animations, that GitHub’s preview does; however, ipywidgets need an active kernel and so rendering those is not an option nbviewer does.)
The key thing is as you update the notebook, you don’t need to do anything to make the new version in your repo the shared one. It is always the one you shared because the old at the URL one gets replaced. Importantly, this way users have the notebook to run themselves and don’t need to remake it. Your version at Project is not runnable as it isn’t even an .ipynb document. Additionally, the MyBinder sesson is useable with with the notbeook current version and all the necessary packages all ready to go for users. This is because I added requirements.txt file that list the PyPI packages you need, see more about configuraton files here. The requirements.txt file is the easiest as it is exactly just a list of each package on a separate line. Nothing more is necessary.
1 Like
Is there any way to include files for the binder just like we include packages using requirements.txt?
If you mean associated documents & files, that is what I tried to say about the .pdf file. If you put the Term-53.pdf, or a likeness of it with that name if you do want to share the actual one, and any other files in the repo, they’ll be available when the session launches. I think giant files are an issue, but typical files are not a problem at all. Content of the repo is avilable as content of the launched session unless you do some other tricks. That is why the index.ipynb and requirements.txt file will be visible in the running session upon launch.
For example, if you put basic versions of all the .pdf files in there that the code cells try to mine for data, then you can do Run all and the notebook will run through without erroring out before the end. Then you can advise the user to update the .pdf files as they work with their own versions during the session to test out what they want on their own content.