For slightly advanced users you can define your own kernel and modify PYTHONPATH by placing this content
{
"argv": [
"/cmmc/ptmp/pyironhb/pyiron_latest_env/bin/python",
"-m",
"ipykernel_launcher",
"-f",
"{connection_file}"
],
"display_name": "<yourname>",
"language": "python",
"metadata": {
"debugger": true
},
"env": {
"PATH": "/cmmc/ptmp/pyironhb/pyiron_latest_env/bin:${PATH}",
"CONDA_PREFIX": "/cmmc/ptmp/pyironhb/pyiron_latest_env/",
"PYTHONPATH": "/u/zora/software/pyiron_snippets:/u/zora/software/pyiron_phase_diagrams/:/u/zora/software/pyiron_potential_fit/:/u/zora/software/pyiron_base/:/u/zora/software/pyiron_continuum/:/u/zora/software/pyiron_contrib/:/u/zora/software/pyiron_atomistics/:${PYTHONPATH}"
}
}
into ~/.local/share/jupyter/kernels//kernel.json. Replace with whatever you want and obviously adapt the PYTHONPATH to remove my entries and add whatever you want. This will automatically point to the latest environment installed on the cluster as well.
For slightly advanced users you can define your own kernel and modify PYTHONPATH by placing this content
into ~/.local/share/jupyter/kernels//kernel.json. Replace with whatever you want and obviously adapt the PYTHONPATH to remove my entries and add whatever you want. This will automatically point to the latest environment installed on the cluster as well.