Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 31 16:26
    kmuehlbauer commented #1568
  • Jan 31 16:15
    kmuehlbauer commented #1568
  • Jan 31 15:53
    djhoese commented #1568
  • Jan 31 15:46
    kmuehlbauer edited #1568
  • Jan 31 15:44
    kmuehlbauer opened #1568
  • Jan 31 15:32
    djhoese commented #1566
  • Jan 31 15:30
    djhoese commented #1567
  • Jan 31 14:18
    GuillaumeFavelier commented #1561
  • Jan 31 14:15
    GuillaumeFavelier commented #1561
  • Jan 31 12:46
    opekar synchronize #1130
  • Jan 31 09:54
    kmuehlbauer commented #1567
  • Jan 31 09:53
    kmuehlbauer synchronize #1567
  • Jan 31 09:37
    kmuehlbauer labeled #1567
  • Jan 31 09:37
    kmuehlbauer labeled #1567
  • Jan 31 09:37
    kmuehlbauer labeled #1563
  • Jan 31 09:36
    kmuehlbauer labeled #1563
  • Jan 31 09:28
    kmuehlbauer commented #1567
  • Jan 31 09:27
    kmuehlbauer synchronize #1567
  • Jan 31 09:19
    kmuehlbauer assigned #1563
  • Jan 31 09:17
    kmuehlbauer opened #1567
Kai Mühlbauer
@kmuehlbauer
@djhoese @almarklein So true, looking at logs to find the offending lines is annoying. I'm very much open to any better solution.
Mark Harfouche
@hmaarrfk
@djhoese black is annoying for science, when it is useful to align arrays by adding spaces. Black is also an all or nothing. so you would have to invalidate all current PRs.
Juan Nunez-Iglesias
@jni
Yeah I'm not super in love with black tbh. And all of the extra whitespace can be so annoying that now instead of worrying about style, I worry about naming my variables and changing my expressions so that black won't mess them up quite so much. In scikit-image we have pep8speaks and it's not bad, though it would be good if it ran only on the diff.
(we use black on napari, not on skimage)
David Hoese
@djhoese
@hmaarrfk @jni Very interesting. I think the extra whitespace on kwargs would be extra bad in vispy where a lot of visuals have a ton of keyword arguments to control each aspect of the visual.
I'm going to try to finish some stuff this week for work, but next time I have time for vispy I'll play around with a non-black styling solution
But first... @astrofrog any chance you are on gitter? Can you take a look at my recent github issue on your failing test?
David Hoese
@djhoese
FYI I've removed the "feature" and "independent-feature" from the github labels. I prefer "enhancement" which already existed and don't see a benefit right now to distinguishing between the 3 of them. I re-labeled anything with the deleted labels to the enhancement label.
Thomas Robitaille
@astrofrog
@djhoese - I'm around!
Indeed there must be some kind of race condition, I think increasing the rtol of the comparison should fix it
On an unrelated note, I was looking at how VisPy builds wheels, and I wanted to mention that I've collaborated with someone else on an Azure Pipelines template that simplifies the boilerplate code for building wheels with cibuildwheel, and since VisPy uses Azure already to build the wheels you could easily switch if you wanted: https://github.com/OpenAstronomy/azure-pipelines-templates/
(if you are interested I could open a PR so you can see how this would work)
David Hoese
@djhoese
@astrofrog That would be appreciated. There was a cibuildwheel issue recently about adding sdist builds to cibuildwheel as an option. I don't remember where that ended up. That and uploading artifacts were the most difficult part of getting azure wheels to work
Igor Berinskii
@iberinsk
Hi! Does vispy works with the integrated GPU? I bought a new laptop with Intel IrisPlus graphics. Unfortunately, neither of the programs I used before with vispy don't show anything now. I realized that before I used a PC and a laptop with NVidia GPUs. Can it be a problem?
Kai Mühlbauer
@kmuehlbauer
@iberinsk There have been issues with Intel graphic cards in the past. Not sure if the intel card is your problem. What does "vispy.sys_info()" tells you?
Igor Berinskii
@iberinsk
'Platform: Windows-10-10.0.18362-SP0\nPython: 3.7.4 (default, Aug 9 2019, 18:34:13) [MSC v.1915 64 bit (AMD64)]\nNumPy: 1.16.5\nBackend: ipynb_webgl\npyqt4: None\npyqt5: (\'PyQt5\', \'5.9.2\', \'5.9.6\')\npyside: None\npyside2: None\npyglet: None\nglfw: None\nsdl2: None\nwx: None\negl: None\nosmesa: None\n_test: None\n\nGL version: \'\'\nMAX_TEXTURE_SIZE: ()\nExtensions: \'\'\nApp info-gathering error:\nTraceback (most recent call last):\n File "C:\Distrib\Anaconda\lib\site-packages\vispy\util\config.py", line 438, in sys_info\n canvas.close()\n File "C:\Distrib\Anaconda\lib\site-packages\vispy\app\canvas.py", line 457, in close\n self._backend._vispy_close()\n File "C:\Distrib\Anaconda\lib\site-packages\vispy\app\backends\_ipynb_webgl.py", line 203, in _vispy_close\n raise NotImplementedError()\nNotImplementedError\n'WARNING: QSocketNotifier: Multiple socket notifiers for same socket 1976 and type Read
Kai Mühlbauer
@kmuehlbauer
@iberinsk Can you put this in three backticks like this.
Which version of vispy are you running? How did you install it? Are you running vispy inside Anaconda base environment?
@iberinsk Backticks `
Igor Berinskii
@iberinsk
Thanks 'Platform: Windows-10-10.0.18362-SP0\nPython: 3.7.4 (default, Aug 9 2019, 18:34:13) [MSC v.1915 64 bit (AMD64)]\nNumPy: 1.16.5\nBackend: ipynb_webgl\npyqt4: None\npyqt5: (\'PyQt5\', \'5.9.2\', \'5.9.6\')\npyside: None\npyside2: None\npyglet: None\nglfw: None\nsdl2: None\nwx: None\negl: None\nosmesa: None\n_test: None\n\nGL version: \'\'\nMAX_TEXTURE_SIZE: ()\nExtensions: \'\'\nApp info-gathering error:\nTraceback (most recent call last):\n File "C:\\Distrib\\Anaconda\\lib\\site-packages\\vispy\\util\\config.py", line 438, in sys_info\n canvas.close()\n File "C:\\Distrib\\Anaconda\\lib\\site-packages\\vispy\\app\\canvas.py", line 457, in close\n self._backend._vispy_close()\n File "C:\\Distrib\\Anaconda\\lib\\site-packages\\vispy\\app\\backends\\_ipynb_webgl.py", line 203, in _vispy_close\n raise NotImplementedError()\nNotImplementedError\n'WARNING: QSocketNotifier: Multiple socket notifiers for same socket 1976 and type Read
Kai Mühlbauer
@kmuehlbauer
Three Backticks before and after :grin:
Platform: Windows-10-10.0.18362-SP0\nPython: 3.7.4 (default, Aug 9 2019, 18:34:13) [MSC v.1915 64 bit (AMD64)]\nNumPy: 1.16.5\nBackend: ipynb_webgl\npyqt4: None\npyqt5: (\'PyQt5\', \'5.9.2\', \'5.9.6\')\npyside: None\npyside2: None\npyglet: None\nglfw: None\nsdl2: None\nwx: None\negl: None\nosmesa: None\n_test: None\n\nGL version: \'\'\nMAX_TEXTURE_SIZE: ()\nExtensions: \'\'\nApp info-gathering error:\nTraceback (most recent call last):\n File "C:\\Distrib\\Anaconda\\lib\\site-packages\\vispy\\util\\config.py", line 438, in sys_info\n canvas.close()\n File "C:\\Distrib\\Anaconda\\lib\\site-packages\\vispy\\app\\canvas.py", line 457, in close\n self._backend._vispy_close()\n File "C:\\Distrib\\Anaconda\\lib\\site-packages\\vispy\\app\\backends\\_ipynb_webgl.py", line 203, in _vispy_close\n raise NotImplementedError()\nNotImplementedError\n'WARNING: QSocketNotifier: Multiple socket notifiers for same socket 1976 and type Read
But that doesn't look much better :cry:
Igor Berinskii
@iberinsk
@kmuehlbauer I use Win10, Anaconda. I launch the programs in Spyder. Vispy 0.6 installed using conda-forge. Also, I tryed WinPython before, but it was the same problem.
Kai Mühlbauer
@kmuehlbauer
First, it is very problematic to work from Anaconda base environment, due to the inherent mixing of channels. Best would be to create a dedicated vispy environment for this.
I'm wondering why you get a traceback from vispy.sys_info()
Can you just try this from the Anaconda command prompt without spyder?
Igor Berinskii
@iberinsk
I tried print(vispy.sys_info()) from spyder and the result was the following:
Platform: Windows-10-10.0.18362-SP0
Python:   3.7.4 (default, Aug  9 2019, 18:34:13) [MSC v.1915 64 bit (AMD64)]
NumPy:    1.16.5
Backend:  ipynb_webgl
pyqt4:    None
pyqt5:    ('PyQt5', '5.9.2', '5.9.6')
pyside:   None
pyside2:  None
pyglet:   None
glfw:     None
sdl2:     None
wx:       None
egl:      None
osmesa:   None
_test:    None

GL version:  ''
MAX_TEXTURE_SIZE: ()
Extensions: ''
App info-gathering error:
Traceback (most recent call last):
  File "C:\Distrib\Anaconda\lib\site-packages\vispy\util\config.py", line 438, in sys_info
    canvas.close()
  File "C:\Distrib\Anaconda\lib\site-packages\vispy\app\canvas.py", line 457, in close
    self._backend._vispy_close()
  File "C:\Distrib\Anaconda\lib\site-packages\vispy\app\backends\_ipynb_webgl.py", line 203, in _vispy_close
    raise NotImplementedError()
NotImplementedError

WARNING: QSocketNotifier: Multiple socket notifiers for same socket 1976 and type Read
Kai Mühlbauer
@kmuehlbauer
Can you just try this again from the Anaconda command prompt without spyder?
Spyder seems to pick ipynb_webgl backend automatically. But I think PyQt5 would be more reasonable...
Igor Berinskii
@iberinsk
@kmuehlbauer this is what I have in this case
"Platform: Windows-10-10.0.18362-SP0\nPython:   3.7.4 (default, Aug  9 2019, 18:34:13) [MSC v.1915 64 bit (AMD64)]\nNumPy:    1.16.5\nBackend:  PyQt5\npyqt4:    None\npyqt5:    ('PyQt5', '5.9.2', '5.9.6')\npyside:   None\npyside2:  None\npyglet:   None\nglfw:     None\nsdl2:     None\nwx:       None\negl:      None\nosmesa:   None\n_test:    None\n\nGL version:  '4.6.0 - Build 25.20.100.7102'\nMAX_TEXTURE_SIZE: 16384\nExtensions: 'GL_3DFX_texture_compression_FXT1 GL_AMD_depth_clamp_separate GL_AMD_vertex_shader_layer GL_AMD_vertex_shader_viewport_index GL_ARB_ES2_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_compatibility GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_bindless_texture GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_cl_event GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_compute_shader GL_ARB_conditional_render_inverted GL_ARB_conservative_depth GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_elements_base_vertex GL_ARB_draw_indirect GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_fragment_shader_interlock GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gl_spirv GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_polygon_offset_clamp GL_ARB_post_depth_coverage GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_robustness_isolation GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_bit_encoding GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_stencil_export GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_spirv_extensions GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_filter_anisotropic GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizz
Kai Mühlbauer
@kmuehlbauer
@iberinsk This looks much better, the GL output looks good to me. So this must have something to do with spyder choosing the wrong backend. I do not use spyder that much but maybe others here can help you with that issue.
Igor Berinskii
@iberinsk
Thanks.
David Hoese
@djhoese

@iberinsk @kmuehlbauer I was just going to point out that the GL version was empty in the initial sys_info() calls. That made me think OpenGL was installed incorrectly. I didn't realize that the WebGL background would break stuff like this.

@hmaarrfk created a pull request that I'm not sure we've fully decided on, but it is meant to avoid automatically picking the webgl backend in spyder. In the short term, it is best to explicitly say what backend you want to use when using Vispy.

Kai Mühlbauer
@kmuehlbauer
@djhoese Ahh, there was something in the back of my head, but I couldn't get it.
David Hoese
@djhoese
@kmuehlbauer If you care and have time, what is your opinion of @EtienneCmb 's proposed changes in #1769
Kai Mühlbauer
@kmuehlbauer
@djhoese Will get to this tomorrow. First glance, I would prefer speed.
David Hoese
@djhoese
:+1:
Igor Berinskii
@iberinsk
@djhoese , I am not sure I got your answer. What do you recommend me to do? Should I try to update the driver?
David Hoese
@djhoese
@iberinsk I thought it was working once you started using the pyqt5 backend?
basically, any vispy stuff you do in spyder (until we fix spyder causing vispy to default to the webgl backend) is explicitly tell vispy you want to use the pyqt5 backend
David Hoese
@djhoese
Vispy 0.6.3 being built now
Note: We can't build a python 3.8 wheel yet because of some missing dependencies on Windows
and since our build system depends on all wheels being built before releasing, not being able to build the Windows wheels for a single version of python means no wheels for any platform
David Hoese
@djhoese
vispy 0.6.3 is on PyPI!
Kai Mühlbauer
@kmuehlbauer
:+1:
David Hoese
@djhoese
@hmaarrfk I appreciate all of the work you've put in to vispy today, but I'm worried you are going to waste time doing something that is handled in another PR or something like that. Maybe I need to make a roadmap document
David Hoese
@djhoese
@kmuehlbauer @larsoner Not sure I've mentioned this yet, but I've been talking to @jni about writing a proposal to CZI for some funding. The funding would primarily go through my work to pay for me to do some maintenance and outreach to get more contributors. We've also talked about someone @jni knows (Owen) about getting some funding to him to become a contributor and transition his project to vispy. If you have any problems, worries, or other feedback about this feel free to PM me on gitter or bring it up here.
Eric Larson
@larsoner
@djhoese that would be great
Kai Mühlbauer
@kmuehlbauer
@djhoese Great!
NicoliHCorrea
@NicoliHCorrea
Hi
I'm trying to pass a test array to be plotted at The real time signal code. Just replacing The np.rand for The test array. but it doesn't work. Nothing is plotted. I need help