Skip to content
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

Add option to disable auto-update on selected cells? #971

Closed
oschulz opened this issue Mar 5, 2021 · 2 comments
Closed

Add option to disable auto-update on selected cells? #971

oschulz opened this issue Mar 5, 2021 · 2 comments

Comments

@oschulz
Copy link

oschulz commented Mar 5, 2021

In some applications, the computational cost of evaluating some cells can be so high that using Pluto instead of Jupyter is currently not an option (for example cells that do expensive statistical inference, run a simulation for minutes, etc.). However, the number of such cells in a notebook is typically (very) small.

Would it be possible to allow the user to disable auto-update for selected cells? The cells could be color coded or so to make this obvious. And if the output of the cell becomes out-of-date, the output could simply be "greyed-out" or so (same for all cells depending on it). Then the user could choose when to manually trigger re-evaluation of the cell (which would, of course, then also trigger evaluation of all "normal" cells depending on it).

I feel this would not break the philosophy of Pluto, since things would still be auto-updated for the most part, while it would open up Pluto for an entire class of applications (those involving heavier computing). It would also be quite natural to use, I think: While the user is playing around with some cells that (e.g.) define the input of a calculation, and to some initial check and plots, they typically will not want their (maybe chain of) expensive "main calculation" cells to be re-run all the time. However, when they're happy with their (e.g.) input stage, they will want to trigger their (maybe chain of) main calculation cells, and of course they will also want all their follow-up analysis and plotting code to run.

In some contexts, e.g. where cluster or clould job submissions are involved, running certain cells might actually consume limited computation budgets (or money, in the case of cloud). Even if not, it might load a system heavily, affecting other users. So allowing for optional control of the update-mechanism would also be resource-friendly.

My apologies if this has already been discussed.

@marius311
Copy link
Contributor

This has been discussed some, check out #298. Agree it would be really nice.

@oschulz
Copy link
Author

oschulz commented Mar 5, 2021

Thanks! Closing this one in favor of #298.

@oschulz oschulz closed this as completed Mar 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants