-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jupyter kernel not functional following install instructions on Linux #40
Comments
@ivan-gomes: Can you address this? |
problem still exists, running the default install.sh shows this on a clean install of linux mint 20.3
Stangely enough,installation succeeded when i first installed jupyter using:
|
well this failed last attempt I installed this ARM64 and work great Python 3.10.6 install Debian 11 |
I have the same problem with the error
System:
The solution proposed by @jbohren worked out for me but it was quite a hassle. |
the same problem still exists on Windows 10 in the SysML-v2-Release-2024-01 release.
|
Summary
Install of jupyter SysMLv2 pilot on Ubuntu 20.04 following instructions does not result in functioning kernel.
Context
Expected Behavior
After following install instructions ,
jupyter lab
should present a functional SysML kernel.Observed Behavior
After following install instructions ,
jupyter lab
does not present a functional SysML kernel.Workaround
Pass 1
The kernel is installed to conda, but not available to jupyter, so it can be installed:
This makes the kernel available, but upon execution, the following error occurs:
Pass 2
After uninstalling the kernel from jupyter, locate the occurrences of the above invalid jarfile path, and replace it with the correct one in the installation.
info/recipe/meta.yaml
info/paths.json
info/has_prefix
share/jupyter/kernels/sysml/kernel.json
Reinstall the kernel to jupyter (
jupyter kernelspec install
).Kernel is now available and fully functional.
Comments
It's not clear to me if this is an issue with the conda distribution or the install process. Either way, the above workaround is definitely a hack.
Also, this effort to make the SysMLv2 spec and pilot implementations so accessible is awesome!
The text was updated successfully, but these errors were encountered: