| |
| META TOPICPARENT |
name="Computing" |
Jupyter notebook server at Nevis |
| |
- The Jupyter notebooks inherit your user environment, that is, the variables that you define in your shell startup scripts. However, if you modify certain variables such as $LD_LIBRARY_PATH or run customization programs (such as
module load root) in your initialization, it can affect the execution of the notebook server. The typical symptoms are a notebook kernel that refuses to start or you get library load errors.
|
|
<
< |
- The software on
notebook was compiled under CentOS 7, but the software loaded by the environment modules was compiled under Scientific Linux 6. Also, some physics software is a “chimera”, a blend of software compiled in two languages; for example, the Neutrino Deep Learning group uses Python to call pre-compiled C++ routines. If you need libraries that were compiled for your workgroup server, you'll probably have to use them on your workgroup server. You'll know if this is the case if you get library errors when trying to use your own compiled libraries via notebook.
|
>
> |
- There's no guarantee that software compiled on your workgroup server will run on
notebook, especially if it relies of software libraries only found on that server. If you need libraries that were compiled for your workgroup server, you'll probably have to use them on your workgroup server. You'll know if this is the case if you get library errors when trying to use your own compiled libraries via notebook.
|
| |
The solution to most of these issues is to run Jupyter on your workgroup server, or consider a container-based distribution. |
| | module load root
|
|
<
< | This will load ROOT 06.12 or later. See the environment modules page for more information, including how to look up available ROOT versions. |
>
> | This will load ROOT 06.24 or later. See the environment modules page for more information, including how to look up available ROOT versions. |
| |
Once you set up ROOT, in theory you'll be able to run Jupyter: |
Copyright © 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.