-
Notifications
You must be signed in to change notification settings - Fork 28
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
Fully move from pyglet to visbrain #60
Comments
Yo Alex ! For curvature direction I have everything for that in my vector_field class + visualization with visbrain :-) There remains some tricky issues because there are troubles with vispy to manage a surface and vectors. The opacity of the mesh is lost and it is a big mess. See here for instance: I have found a temporary solution where points that are not visible from the camera location are hidden but it is not completely satisfactory. The best way would consist to use ray tracing to identify point that are really not visible (not based on a criterion with the vertex normals, whose only advantage is to be less costfull). Bon réveillon ! |
Super nice @JulienLefevreMars ! That definetly is a super basis to work on to have the final display we want. May be worth to discuss with @EtienneCmb next year :) Bon réveillon et à bientôt |
Hello guys ! Happy new year :D Sorry for the delay @JulienLefevreMars, but very nice figures ! Under the hood the VectorObj is using the ArrowVisual Vispy class. The vector is built using two elements : the line and the arrow head. The best would be to have a custom glsl shaders where the arrow is hidden when the camera is moving. From what I remember, the shaders should contain a |
The visualization code was removed from slam to focus on processing. Not longer relevant for slam but useful for slamviz |
Visbrain was chosen as the visualisation package for slam.
Furthermore, it would be the opportunity to discuss how to deal with visualisation dependence in the example and strategies that could be implemented
The text was updated successfully, but these errors were encountered: