You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We used a 2i2c-managed JupyterHub for our QGreenland workshop a couple weeks ago, and had a great experience. A JupyterHub is a cloud-based system for provisioning dedicated JupyterLab instances for users.
That left me wondering about how NSIDC could benefit from a similar set up. With the addition of real-time-collaboration (like Google Docs, but in Jupyter Notebooks), so many possibilities open up: small groups working on the same notebook together in a tutorial setting, offering live user support in a collaborative computing environment, pair programming between developers and scientists to explore a problem space.
JupyterLab 4 was announced the other day. This release also includes real-time-collaboration extension at 1.0.0.
The text was updated successfully, but these errors were encountered:
We used a 2i2c-managed JupyterHub for our QGreenland workshop a couple weeks ago, and had a great experience. A JupyterHub is a cloud-based system for provisioning dedicated JupyterLab instances for users.
That left me wondering about how NSIDC could benefit from a similar set up. With the addition of real-time-collaboration (like Google Docs, but in Jupyter Notebooks), so many possibilities open up: small groups working on the same notebook together in a tutorial setting, offering live user support in a collaborative computing environment, pair programming between developers and scientists to explore a problem space.
JupyterLab 4 was announced the other day. This release also includes real-time-collaboration extension at 1.0.0.
The text was updated successfully, but these errors were encountered: