brainrender: Runtime error?
Hi,
I wanted to run brainrender-gui and I am getting the following error. Could I be missing installing any python modules?
Thanks, Seita
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/pyinspect/exceptions.py", line 146, in excepthook
emanager.render_error()
File "/usr/local/lib/python3.9/site-packages/pyinspect/exceptions.py", line 79, in render_error
*inspect_traceback(
File "/usr/local/lib/python3.9/site-packages/pyinspect/_exceptions.py", line 291, in inspect_traceback
eline = read_single_line(fpath, f.f_lineno - 1)
File "/usr/local/lib/python3.9/site-packages/pyinspect/utils.py", line 135, in read_single_line
raise FileExistsError(
FileExistsError: When reading a single line from file: the file doesnt exist!
Original exception was:
Traceback (most recent call last):
File "/usr/local/bin/brainrender-gui", line 5, in <module>
from brainrender.gui.__init__ import clilaunch
File "/usr/local/lib/python3.9/site-packages/brainrender/__init__.py", line 15, in <module>
from brainrender.scene import Scene
File "/usr/local/lib/python3.9/site-packages/brainrender/scene.py", line 18, in <module>
from brainrender.render import Render
File "/usr/local/lib/python3.9/site-packages/brainrender/render.py", line 1, in <module>
from vedo import Plotter, closePlotter
ImportError: cannot import name 'closePlotter' from 'vedo' (/usr/local/lib/python3.9/site-packages/vedo/__init__.py)
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 29 (11 by maintainers)
load_mesh_from_file only supports loading of
.objand.stlfiles (and a couple others supported byvedo). The GUI currently doesn’t have a way to load.swcdata into it, though ti would be fairly easy to expandload_mesh_from_fileto use theNeuronclass to load neurons when a path to an.swcis passed, if you want to try creating a pull request with this new feature.The vtk branch was for a separate problem. Can you try
pip install PySide2?@FedeClaudi is this linked to the Python 3.9 discussion on #165? For me this problem only occurs with 3.9, 3.8 is fine.
@seitay, @raacampbell downgrading to Python 3.8 might be a quick fix.