@p-i- Thanks for the suggestions. There is an issue on github already about updating the gallery for the vispy website with more of the example scripts (something on the todo list for the scipy sprint). The problem or confusion that notebooks cause is that vispy's jupyter widget is experimental and does not currently function very well. I would not want people to think that they should expect everything in vispy to work in a jupyter widget. If the widget backend wasn't used then a separate window is popped up which can just be awkward. Lastly, some of the cool stuff in vispy is done by embedding it into a larger Qt (or other GUI framework) application
And how to plot a large array of points, so that if multiple points land on the same pixel the intensities add?
Also two_qt_widgets.py segfaults:
RuntimeError: OpenGL got errors (Check before draw): GL_INVALID_VALUE
Everything else seems to work from /examples
For the oscilloscope you might need pyopengl installed.
Yes, it should be no separate Visuals but a collection. Each visual is treated as separate GL program and this affects performance if there are hundreds or thousands of them. A collection circumvent this by using only one program to draw all items. You might skim through the vispy issues. There have been discussions recently (this and last year I think).
pyopengl is a library and some parts of vispy use it. Other parts, most parts, use a custom linking to your systems GL libraries
@p-i- ^
the plotting interface as a whole is very limited and unfinished. It was put together by the original vispy developers as a proof of concept but needs a lot of work
I reverted to doing it with matplotlib for the time being (as I have a deadline):
https://stackoverflow.com/questions/68404385/dynamically-redraw-second-axis-subfigure-upon-click-event-in-first-in-matplotlib
I would be interested to know how much work it involves to achieve this with vispy.
If anyone's interested to take it on as a contract, do message me.
https://stackoverflow.com/questions/68404385/dynamically-redraw-second-axis-subfigure-upon-click-event-in-first-in-matplotlib
I would be interested to know how much work it involves to achieve this with vispy.
If anyone's interested to take it on as a contract, do message me.
@djhoese I like the pattern of 'doc-thru-code'.
I kinda wish all doc was centered around this.
It cuts out using English as an intermediate language.
I kinda wish all doc was centered around this.
It cuts out using English as an intermediate language.
@BaiSource Keep reading the documentation below that section. There is a Windows section and Linux section that describe switchable graphics for those platforms. The easiest solution is to configure your sysyem to use the nvidia gpu for everything. This isn't a vispy thing, it is up to your system to tell vispy what it should use.
@p-i- I'm not really sure what you expected, but coming to a volunteer open source project on a deadline is rarely going to go well. And I'm not sure if you're criticizing our documentation or saying you like the examples. I've already said we have limited time and that we're working on the documentation so repeating that our docs aren't up to your standards isn't accomplishing anything except making me feel bad. If you have improvements in mind and they aren't already in github issues please make some. Even better, submit a pull request to improve what you can.
Glad you got something working though.
is there a way to use Qt QML backend? Qt QML uses QML Item , Its also possible to get the QML to create framebuffer, I am very new to OpenGL , used Pyvista , Pyqtgraphs with Qt widgets, I am looking for options to move to QML (preferably with Qt6). Looks like pyvista with QML is complicated as the way VTK works, Vispy seems much promising with both 2d charts (line charts) and 3d charts (surface mesh).
Some more details are https://stackoverflow.com/questions/68517058/can-not-get-pyvista-render-to-work-with-qt-qml-qquickframebufferobject , I am willing to contribute but could not get where to start.
Is there an ambient_light_color attribute for a MarkersVisual, similar to what is discussed here? https://stackoverflow.com/questions/39112197/add-ambient-light-to-vispy-scene
My MarkersVisual appears to be lighted from a direction I can't figure out how to control, I'm just trying to figure out ambient lighting for my Visual.
@ericgyounkin If you are using VisPy 0.7+ then you should look at adding the ShadingFilter to your MeshVisual: https://vispy.org/api/vispy.visuals.filters.mesh.html#vispy.visuals.filters.mesh.ShadingFilter
You can access the default instance of this through the MeshVisual.shading property or you can create your own filter and attach it after you create the MeshVisual.
You can see examples of this in this example: https://vispy.org/gallery/scene/mesh_shading.html
@djhoese thanks for the suggestion, I am using a MarkersVisual similar to https://vispy.org/gallery/scene/point_cloud.html
I do see an attach() method, which can be used to attach a filter? So maybe that is the approach?
Oh! Sorry @ericgyounkin I didn't realize you were using a MarkersVisual. That is going to be more difficult. I don't know too much about the Markers implementation, but I think knowing what symbol you are using would be a good start. Maybe we can come up with some kind of hack for you. That said, I'm not super optimistic as the MarkersVisual seems rather limited as far as customizing the actual look of the individual marker points
I see that the ShadingFilter appears to let you align the light source with the camera direction. Maybe that is the right approach? And then attach() the Filter to the Visual?
If I rotate the camera to the sweet spot, the lighting is perfect.
@ericgyounkin Is the above screenshot with or without the filter? If not, I'm not sure the filter will work for any non-mesh visuals (like the Markers). The reason I asked about the symbol you're using is that doing what you want may require editing the OpenGL shader on the markers. I'm actually surprised there is any idea of lighting in the markers though. I wonder if this is just a side effect of depth testing or the edge color of the markers.
another thing you could try after making your Markers is to do
scatter.antialias = False and see if that fixes what you're seeing