vtk broken? #21

christianbrodbeck · 2017-01-25T23:34:47Z

I'm trying to write a recipe that depends on mayavi and hence vtk, and for Linux it ends with the traceback below. This looks like something is missing after the vtk install through conda-forge? Or is there a workaround for this, in which case maybe vtk could raise a better error message?

Traceback (most recent call last):
  File "/staged-recipes/build_artefacts/pysurfer_1485201053033/_t_env/bin/pysurfer", line 9, in <module>
    from surfer._commandline import parser
  File "/staged-recipes/build_artefacts/pysurfer_1485201053033/_t_env/lib/python2.7/site-packages/surfer/__init__.py", line 1, in <module>
    from .viz import Brain, TimeViewer  # noqa
  File "/staged-recipes/build_artefacts/pysurfer_1485201053033/_t_env/lib/python2.7/site-packages/surfer/viz.py", line 13, in <module>
    from mayavi import mlab
  File "/staged-recipes/build_artefacts/pysurfer_1485201053033/_t_env/lib/python2.7/site-packages/mayavi/mlab.py", line 27, in <module>
    from mayavi.tools.camera import view, roll, yaw, pitch, move
  File "/staged-recipes/build_artefacts/pysurfer_1485201053033/_t_env/lib/python2.7/site-packages/mayavi/tools/camera.py", line 25, in <module>
    from .engine_manager import get_engine
  File "/staged-recipes/build_artefacts/pysurfer_1485201053033/_t_env/lib/python2.7/site-packages/mayavi/tools/engine_manager.py", line 14, in <module>
    from mayavi.core.engine import Engine
  File "/staged-recipes/build_artefacts/pysurfer_1485201053033/_t_env/lib/python2.7/site-packages/mayavi/core/engine.py", line 12, in <module>
    import vtk
  File "/staged-recipes/build_artefacts/pysurfer_1485201053033/_t_env/lib/python2.7/site-packages/vtk/__init__.py", line 100, in <module>
    from .vtkRenderingOpenGL import *
  File "/staged-recipes/build_artefacts/pysurfer_1485201053033/_t_env/lib/python2.7/site-packages/vtk/vtkRenderingOpenGL.py", line 9, in <module>
    from vtkRenderingOpenGLPython import *
ImportError: No module named vtkRenderingOpenGLPython

The text was updated successfully, but these errors were encountered:

Korijn · 2017-01-26T06:08:05Z

I don't think Mayavi is on conda-forge yet so I don't think the one in defaults could work with this version of VTK.

christianbrodbeck · 2017-01-26T13:56:00Z

The reason I assumed it was a general vtk problem is that the error happens during a bare import vtk statement. Could this be due to mayavi?

Mayavi on defaults does misspecify its vtk dependency and I've opened an issue for that (ContinuumIO/anaconda-issues#1365)

However the output before the exception contains the following lines, suggesting that mayavi is coming from conda-forge (I think it was added very recently though):

The following packages will be downloaded:

...
    mayavi-4.5.0               |      np111py27_1        12.8 MB  conda-forge
...

The Mayavi conda-forge recipe (https://github.com/conda-forge/mayavi-feedstock) explicitly requires vtk ==7.1.0 (https://github.com/conda-forge/mayavi-feedstock/blob/master/recipe/meta.yaml#L31)

Korijn · 2017-01-26T14:22:22Z

You are right.

I'm confused though; the mayavi-feedstock CI is passing on all platforms: conda-forge/mayavi-feedstock#2

You'd think this error would occur there as well, hm?

christianbrodbeck · 2017-01-26T14:46:35Z

Might the relevant difference be that PySurfer imports mlab from mayavi, which I don't think the mayavi feedstock test does? Unfortunately I don't have access to Linux to test this with vtk 7.

Korijn · 2017-01-26T15:29:06Z

Actually, I think VTK is being built with vtkRenderingOpenGL2 instead of 1, and Mayavi isn't compatible with that.

[Edit] No, scratch that... -DVTK_RENDERING_BACKEND=OpenGL

dfroger · 2017-01-27T12:17:26Z

requires vtk ==7.1.0

There is a discussion about that: conda-forge/mayavi-feedstock#1

dfroger · 2017-01-27T12:20:06Z

mayavi-feedstock CI is passing on all platforms: conda-forge/mayavi-feedstock#2

I just merged this PR, so mayavi should br available on Linux and Windows (in a few minutes), but not OSX (conda-forge/mayavi-feedstock#3)

dfroger · 2017-01-27T12:21:28Z

ImportError: No module named vtkRenderingOpenGLPython

I'll try to reproduce this

dfroger · 2017-01-27T12:38:45Z

Here https://circleci.com/gh/conda-forge/staged-recipes/12483?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link mayavi is installed from default (don't know the reason why).

On my Linux machine, this install mayavi from conda-forge:

conda create -n sufer mayavi python=2.7 imageio matplotlib mayavi nibabel numpy scipy

and this works:

source activate surfer
python -c 'import vtk'
python -c 'import mayavi'
mayavi --help

[EDIT] On last build https://circleci.com/gh/conda-forge/staged-recipes/12761?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link, mayavi is installed from conda-forge

dfroger · 2017-01-27T12:47:09Z

I think py-surfer recipe need to add libXt-devel and mesa-libGLU-devel to its yum_requirements.txt, like the mayavi one

[Edit] or just like vtk's yum_requirements.txt.

dfroger · 2017-01-27T12:54:27Z

Is it possible to modify VTK recipe so that it is checked? (post install script, or something like this)

Korijn · 2017-01-27T12:57:36Z

I think that is already the case?

test:
  imports:
    - vtk
    - vtk.vtkChartsCore
    - vtk.vtkCommonCore
    - vtk.vtkFiltersCore
    - vtk.vtkFiltersGeneric
    - vtk.vtkGeovisCore
    - vtk.vtkFiltersHybrid
    - vtk.vtkIOCore
    - vtk.vtkImagingCore
    - vtk.vtkInfovisCore
    - vtk.vtkRenderingCore
    - vtk.vtkViewsCore
    - vtk.vtkRenderingVolume
    - vtk.vtkInteractionWidgets

christianbrodbeck · 2017-01-27T13:30:57Z

Here https://circleci.com/gh/conda-forge/staged-recipes/12483?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link mayavi is installed from default (don't know the reason why).

Yes strange, this is still the same in the latest build, for the build it's pulling mayavi from defaults, but for the test it's pulling from conda-forge. The only difference in the requirements is that build also has setuptools, that can hardly be the reason? A difference in channel priorities?

Korijn · 2017-01-27T13:51:22Z

Care to share your conda config --get and conda info?

The latest few versions of conda and conda-build are notoriously buggy by the way, we've been having weird hiccups for the last two weeks for all sorts of stuff...

christianbrodbeck · 2017-01-27T15:00:02Z

@Korijn I was referring to the build on circleci (linked), not my machine.

christianbrodbeck · 2017-01-31T03:16:05Z

Closing, since updating yum_requirements solved my issue. Thanks!

dfroger · 2017-01-31T07:10:23Z

@christianbrodbeck thanks, I think we should find a way to make it more explicit, document it, or check it before the error occurs to provide to explict warning. Without a doubt, the error will reappear for other users...

Korijn · 2017-01-31T07:28:05Z

It was surprising for me to see that it raised an ImportError at the python level and not at the dll/so level... I'm having a hard time believing that the either of them was really missing. They just failed to load.

christianbrodbeck · 2017-01-31T14:19:50Z

Could a comment be added to the VTK feedstock readme? Something like "Projects that depend on VTK should add a yum_requirements.txt file like vtk-feedstock/recipe/yum_requirements.txt. Failure to do so can result in an ImportError: No module named vtkRenderingOpenGLPython."? That would show up when searching for "vtkRenderingOpenGLPython".

It was surprising for me to see that it raised an ImportError at the python level and not at the dll/so level

Yes that was confusing for me too, maybe VTK could be modified to raise a more meaningful error? I am not familiar with the VTK source though... searching for "vtkRenderingOpenGLPython" does not even yield any results...

dfroger · 2017-01-31T14:31:58Z

Could a comment be added to the VTK feedstock readme?

As README are generated by conda-smithy, is it ok to modify them?

christianbrodbeck · 2017-01-31T14:45:38Z

Right... is there any way to add notes to a feedstock except for comments in the meta.yaml which seem to be discouraged?

Korijn · 2017-01-31T15:14:34Z

@christianbrodbeck VTK autogenerates the Python wrappers with lots of CMake magic, see: https://github.com/Kitware/VTK/blob/0937c8a6be8a10b95828c31b289cd1cecce78432/CMake/vtkPythonWrapping.cmake

jakirkham · 2017-02-06T03:18:32Z

Comments in the recipe are ok. We just try to remove boilerplate comments that come from copying and tweaking the example at staged-recipes.

Also it is possible to add a README to the recipe directory. Here's an example (albeit not the prettiest one).

kazemSafari · 2017-11-12T19:37:46Z

Hi i'm trying to install "mayavi". So i installed all the prerequisite packages including vtk. But after type enter "pip install mayavi" into my ubuntu 16.04 shell, i get a similar error:
"from vtkOpenGLKitPython import *
ModuleNotFoundError: No module named 'vtkOpenGLKitPython'"

How can i fix this error. I did not get your solution "christianbrodbeck"?

mustafa-qamaruddin · 2018-04-20T14:33:03Z

ImportError: No module named 'vtkOpenGLKitPython'

christianbrodbeck · 2018-04-20T15:11:10Z

@kazemSafari sorry I missed your comment, this issue is about conda-forge recipes, not local install issues. It looks like your VTK install failed somehow?

christianbrodbeck closed this as completed Jan 31, 2017

christianbrodbeck mentioned this issue Mar 5, 2017

DOC: add readme #25

Merged

jakirkham mentioned this issue Sep 7, 2017

CFEP 04: proposed guidelines for X11-based software. conda-forge/cfep#7

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

vtk broken? #21

vtk broken? #21

christianbrodbeck commented Jan 25, 2017

Korijn commented Jan 26, 2017

christianbrodbeck commented Jan 26, 2017

Korijn commented Jan 26, 2017

christianbrodbeck commented Jan 26, 2017

Korijn commented Jan 26, 2017 •

edited

Loading

dfroger commented Jan 27, 2017

dfroger commented Jan 27, 2017 •

edited

Loading

dfroger commented Jan 27, 2017

dfroger commented Jan 27, 2017 •

edited

Loading

dfroger commented Jan 27, 2017 •

edited

Loading

dfroger commented Jan 27, 2017

Korijn commented Jan 27, 2017

christianbrodbeck commented Jan 27, 2017

Korijn commented Jan 27, 2017

christianbrodbeck commented Jan 27, 2017

christianbrodbeck commented Jan 31, 2017

dfroger commented Jan 31, 2017

Korijn commented Jan 31, 2017 •

edited

Loading

christianbrodbeck commented Jan 31, 2017

dfroger commented Jan 31, 2017

christianbrodbeck commented Jan 31, 2017

Korijn commented Jan 31, 2017

jakirkham commented Feb 6, 2017

kazemSafari commented Nov 12, 2017

mustafa-qamaruddin commented Apr 20, 2018

christianbrodbeck commented Apr 20, 2018

vtk broken? #21

vtk broken? #21

Comments

christianbrodbeck commented Jan 25, 2017

Korijn commented Jan 26, 2017

christianbrodbeck commented Jan 26, 2017

Korijn commented Jan 26, 2017

christianbrodbeck commented Jan 26, 2017

Korijn commented Jan 26, 2017 • edited Loading

dfroger commented Jan 27, 2017

dfroger commented Jan 27, 2017 • edited Loading

dfroger commented Jan 27, 2017

dfroger commented Jan 27, 2017 • edited Loading

dfroger commented Jan 27, 2017 • edited Loading

dfroger commented Jan 27, 2017

Korijn commented Jan 27, 2017

christianbrodbeck commented Jan 27, 2017

Korijn commented Jan 27, 2017

christianbrodbeck commented Jan 27, 2017

christianbrodbeck commented Jan 31, 2017

dfroger commented Jan 31, 2017

Korijn commented Jan 31, 2017 • edited Loading

christianbrodbeck commented Jan 31, 2017

dfroger commented Jan 31, 2017

christianbrodbeck commented Jan 31, 2017

Korijn commented Jan 31, 2017

jakirkham commented Feb 6, 2017

kazemSafari commented Nov 12, 2017

mustafa-qamaruddin commented Apr 20, 2018

christianbrodbeck commented Apr 20, 2018

Korijn commented Jan 26, 2017 •

edited

Loading

dfroger commented Jan 27, 2017 •

edited

Loading

dfroger commented Jan 27, 2017 •

edited

Loading

dfroger commented Jan 27, 2017 •

edited

Loading

Korijn commented Jan 31, 2017 •

edited

Loading