scverse / scverse/scverse-tutorials
Notebook Interactivity
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 22
- Forks
- 18
- Avg merge
- 3h 9m
- Merged PRs (30d)
- 9
Description
Splitting out the discussion on how we do interactivity of the notebooks.
There should be some sort of interactivity (i.e. the possibility to execute the notebooks online)
– @grstYes, please. We should design everything with this in mind. I think that we'll need GPU support though, right @adamgayoso ?
@Zethson
Originally posted by @Zethson in https://github.com/scverse/scverse-tutorials/issues/1#issuecomment-1331868291
Platforms
AFAICT, the two ways we could do this are colab and binder.
I think we could try to do both. The issue here is "how do we do dependencies" since we can specify an environment for binder, but not for colab.
Maybe there is some way to specify dependencies in an environment.yml, then have colab use them?
Dependencies more generally
I don't think we should have one environment that every notebook runs in. How can we manage this?
I think it should be possible to have multiple conda environments created on a binder image. Then notebooks could specify which environment to use with their kernel.
@Zethson, does the best practices manage this in anyway? I'm trying to figure it out right now, but the binder is taking a really long time to build 😅
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the proposed Colab and Binder approaches, focusing on how dependencies are specified in environment.yml and how multiple notebook environments or kernels might be managed. Done means the project has an agreed approach for notebook interactivity and dependency handling; the issue names no specific files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, python
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100