#Jupyterlab logo install#
We install the stack that you use when you start up JupyterLab on Cori or Perlmutter "bare metal." For most users this is fine, but for others it is less than ideal. JupyterLab at NERSC is managed centrally. Note: This used to be called the Profiles service.
Expect them to develop over time, hopefully getting better, but there will be changes.Do not make them the mission-critical centerpiece of your project if they are listed here.
And finally, remember these are EXPERIMENTAL features: If you use these features, please be sure to check this page and the update history. A ticket is also the best way to get help if problems arise. If you have feedback, opening a ticket about it is just fine. For each case, there is a description of the problem it solves and how you can opt in/out of testing it. If they don't work out, well, at least we learned something!īelow you will find a list of currently experimental features that are available or under active development. If the experiments are successful we can proceed with integrating them into our production deployment. We have created this page to provide supplemental documentation of those experimental features. We like to experiment with new features, have users test them out and give us feedback. Some of the work we do involves customizing our Jupyter and JupyterHub deployment and contributing back to the broader community. Along the way we have expanded resources available to Jupyter users and added new features to improve their experience. Since 2015 Jupyter has been supported at NERSC in some form or fashion.
0 kommentar(er)
