search

mne-tools / mne-python

MNE: Magnetoencephalography (MEG) and Electroencephalography (EEG) in Python
https://mne.tools
BSD 3-Clause "New" or "Revised" License
2.71k stars 1.32k forks source link

VTK / EPD python error on calling PySurfer #340

Closed dengemann closed 11 years ago

dengemann commented 11 years ago

Hi folks,

I was running plot_cluster_stats_spatio_temporal.py on the current master and got this one:

TraitError: The 'colormap' trait of a SurfaceFactory instance must be 'Accent' or 'Blues' or 'BrBG' or 'BuGn' or 'BuPu' or 'Dark2' or 'GnBu' or 'Greens' or 'Greys' or 'OrRd' or 'Oranges' or 'PRGn' or 'Paired' or 'Pastel1' or 'Pastel2' or 'PiYG' or 'PuBu' or 'PuBuGn' or 'PuOr' or 'PuRd' or 'Purples' or 'RdBu' or 'RdGy' or 'RdPu' or 'RdYlBu' or 'RdYlGn' or 'Reds' or 'Set1' or 'Set2' or 'Set3' or 'Spectral' or 'YlGn' or 'YlGnBu' or 'YlOrBr' or 'YlOrRd' or 'autumn' or 'binary' or 'black-white' or 'blue-red' or 'bone' or 'cool' or 'copper' or 'file' or 'flag' or 'gist_earth' or 'gist_gray' or 'gist_heat' or 'gist_ncar' or 'gist_rainbow' or 'gist_stern' or 'gist_yarg' or 'gray' or 'hot' or 'hsv' or 'jet' or 'pink' or 'prism' or 'spectral' or 'spring' or 'summer' or 'winter', but a value of array([[   0.        ,  255.        ,  255.        ,  255.        ],
       [   0.        ,  252.50976562,  255.        ,  255.        ],
       [   0.        ,  250.01953125,  255.        ,  255.        ],
       ..., 
       [ 255.        ,  247.52929688,    0.        ,  255.        ],
       [ 255.        ,  250.01953125,    0.        ,  255.        ],
       [ 255.        ,  252.50976562,    0.        ,  255.        ]]) <type 'numpy.ndarray'> was specified.

Can anyone reproduce this?

D

larsoner commented 11 years ago

Must be a problem with manually specifying the colormap. I didn't have it last time I tried it, but I'll check tomorrow. Are you on OSX or Linux? What versions of enthought / mayavi are you running?

larsoner commented 11 years ago

I do not get the error on Linux x86_64, mayavi version 4.1.0. I assume you're using a relatively recent version, though, so we should maybe put a try/catch in there. If you print the entire error message (so I can figure out the offending line number), I can put together a "fix" that tries to use the colormap, and if it fails, falls back to the default colormap (with a warning).

dengemann commented 11 years ago

hi eric, thanks!

it's just the recent 32bit epd 7.3 for mac ... don't you also use this on your mac? currently i'm not at my desk, i can post the error message later.

On 04.01.2013, at 17:38, Eric89GXL notifications@github.com wrote:

I do not get the error on Linux x86_64, mayavi version 4.1.0. I assume you're using a relatively recent version, though, so we should maybe put a try/catch in there. If you print the entire error message (so I can figure out the offending line number), I can put together a "fix" that tries to use the colormap, and if it fails, falls back to the default colormap (with a warning).

— Reply to this email directly or view it on GitHub.

larsoner commented 11 years ago

My OSX install doesn't currently have a working EPD/Mayavi on it. I'll probably just suck it up and change over to using EPD, although I was trying to stay with a standard install.

dengemann commented 11 years ago

too painful to compile the mayavi dependencies ... i at least hope the next epd will support mayavi with 64 bit.

On 04.01.2013, at 18:08, Eric89GXL notifications@github.com wrote:

My OSX install doesn't currently have a working EPD/Mayavi on it. I'll probably just suck it up and change over to using EPD, although I was trying to stay with a standard install.

— Reply to this email directly or view it on GitHub.

larsoner commented 11 years ago

I might go nuts and try installing EPD today, in which case I'll be able to test this. In the meantime, let me know if you find that error.

agramfort commented 11 years ago

FYI runs fine on my Mac EPD 7.2 32 bits.

larsoner commented 11 years ago

Which versions are you two running? @dengemann if you can send me the error, I can make a catch for it that will fall back to using the default colormap.

agramfort commented 11 years ago

import mayavi mayavi.version '4.1.0'

dengemann commented 11 years ago

EPD 7.3 32 Bit Python 2.7, pysurfer 0.4 dev (I should check whether updating its master will resolve the issue)

---------------------------------------------------------------------------
TraitError                                Traceback (most recent call last)
/Library/Frameworks/Python.framework/Versions/7.3/lib/python2.7/site-packages/IPython/utils/py3compat.py
in execfile(fname, *where)
    173             else:
    174                 filename = fname
--> 175             __builtin__.execfile(filename, *where)

/Users/denisaengemann/python/mne-python/examples/stats/plot_cluster_stats_spatio_temporal.py
in <module>()
    184 brain = stc_all_cluster_vis.plot('fsaverage', 'inflated', 'rh',
colormap,
    185                                  subjects_dir=subjects_dir,
--> 186                                  time_label='Duration significant
(ms)')
    187 brain.set_data_time_index(0)
    188 # The colormap requires brain data to be scaled -fmax -> fmax

/Library/Python/2.7/site-packages/mne/source_estimate.pyc in plot(self,
subject, surface, hemi, colormap, time_label, smoothing_steps, fmin, fmid,
fmax, transparent, time_viewer, subjects_dir)
    929                         smoothing_steps=smoothing_steps, fmin=fmin,
fmid=fmid,
    930                         fmax=fmax, transparent=transparent,
--> 931                         time_viewer=time_viewer,
subjects_dir=subjects_dir)
    932         return brain
    933

/Library/Python/2.7/site-packages/mne/viz.pyc in plot_source_estimates(stc,
subject, surface, hemi, colormap, time_label, smoothing_steps, fmin, fmid,
fmax, transparent, time_viewer, subjects_dir)
    957     brain.add_data(data, colormap=colormap, vertices=vertices,
    958                    smoothing_steps=smoothing_steps, time=time,
--> 959                    time_label=time_label)
    960
    961     # scale colormap and set time (index) to display

/Library/Python/2.7/site-packages/surfer/viz.pyc in add_data(self, array,
min, max, thresh, colormap, alpha, vertices, smoothing_steps, time,
time_label)
    391         surf = mlab.pipeline.surface(mesh, colormap=colormap,
    392                                      vmin=min, vmax=max,
--> 393                                      opacity=float(alpha))
    394
    395         # Get the colorbar

/Library/Frameworks/Python.framework/Versions/7.3/lib/python2.7/site-packages/mayavi/tools/pipe_base.py
in the_function(*args, **kwargs)
     35 def make_function(factory_class):
     36     def the_function(*args, **kwargs):
---> 37         factory = factory_class(*args, **kwargs)
     38         return factory._target
     39

/Library/Frameworks/Python.framework/Versions/7.3/lib/python2.7/site-packages/mayavi/tools/modules.py
in __init__(self, *args, **kwargs)
    152
    153     def __init__(self, *args, **kwargs):
--> 154         super(DataModuleFactory, self).__init__(*args, **kwargs)
    155         # We are adding data to the scene, reset the zoom:

    156         scene = self._scene.scene

/Library/Frameworks/Python.framework/Versions/7.3/lib/python2.7/site-packages/mayavi/tools/pipe_base.py
in __init__(self, parent, **kwargs)
    159         # Now calling the traits setter, so that traits handlers are

    160         # called

--> 161         self.set(**traits)
    162         if scene is not None:
    163             scene.disable_render = not self._do_redraw

/Library/Frameworks/Python.framework/Versions/7.3/lib/python2.7/site-packages/mayavi/tools/pipe_base.py
in set(self, trait_change_notify, **traits)
    167         unless trait_change_notify==False"""
    168         HasPrivateTraits.set(self,
trait_change_notify=trait_change_notify,
--> 169                                     **traits)
    170         if trait_change_notify==False:
    171             return

/Library/Frameworks/Python.framework/Versions/7.3/lib/python2.7/site-packages/traits/has_traits.py
in trait_set(self, trait_change_notify, **traits)
   1950         else:
   1951             for name, value in traits.items():
-> 1952                 setattr( self, name, value )
   1953
   1954         return self

/Library/Frameworks/Python.framework/Versions/7.3/lib/python2.7/site-packages/traits/trait_handlers.py
in error(self, object, name, value)
    168         """
    169         raise TraitError( object, name, self.full_info( object,
name, value ),
--> 170                           value )
    171
    172     def arg_error ( self, method, arg_num, object, name, value ):

TraitError: The 'colormap' trait of a SurfaceFactory instance must be
'Accent' or 'Blues' or 'BrBG' or 'BuGn' or 'BuPu' or 'Dark2' or 'GnBu' or
'Greens' or 'Greys' or 'OrRd' or 'Oranges' or 'PRGn' or 'Paired' or
'Pastel1' or 'Pastel2' or 'PiYG' or 'PuBu' or 'PuBuGn' or 'PuOr' or 'PuRd'
or 'Purples' or 'RdBu' or 'RdGy' or 'RdPu' or 'RdYlBu' or 'RdYlGn' or
'Reds' or 'Set1' or 'Set2' or 'Set3' or 'Spectral' or 'YlGn' or 'YlGnBu' or
'YlOrBr' or 'YlOrRd' or 'autumn' or 'binary' or 'black-white' or 'blue-red'
or 'bone' or 'cool' or 'copper' or 'file' or 'flag' or 'gist_earth' or
'gist_gray' or 'gist_heat' or 'gist_ncar' or 'gist_rainbow' or 'gist_stern'
or 'gist_yarg' or 'gray' or 'hot' or 'hsv' or 'jet' or 'pink' or 'prism' or
'spectral' or 'spring' or 'summer' or 'winter', but a value of array([[
0.        ,  255.        ,  255.        ,  255.        ],
       [   0.        ,  252.50976562,  255.        ,  255.        ],
       [   0.        ,  250.01953125,  255.        ,  255.        ],
       ...,
       [ 255.        ,  247.52929688,    0.        ,  255.        ],
       [ 255.        ,  250.01953125,    0.        ,  255.        ],
       [ 255.        ,  252.50976562,    0.        ,  255.        ]]) <type
'numpy.ndarray'> was specified.

On Sun, Jan 6, 2013 at 5:16 PM, Eric89GXL notifications@github.com wrote:

Which versions are you two running? @dengemann if you can send me the error, I can make a catch for it that will fall back to using the default colormap.

? Reply to this email directly or view it on GitHubhttps://github.com/mne-tools/mne-python/issues/340#issuecomment-11930331.

dengemann commented 11 years ago

In [7]: mayavi.version Out[7]: '4.2.0'

On Sun, Jan 6, 2013 at 5:20 PM, Alexandre Gramfort <notifications@github.com

wrote:

import mayavi mayavi.version '4.1.0'

— Reply to this email directly or view it on GitHubhttps://github.com/mne-tools/mne-python/issues/340#issuecomment-11930381.

larsoner commented 11 years ago

And it's the same if you import it as "from enthought import mayavi", right?

dengemann commented 11 years ago

yes, the same version

larsoner commented 11 years ago

Hmm, not sure why a newer version of either would cause a regression here, since array-based colormaps should work unless the underlying plotting call was changed. If it's easy to try the older freesurfrer, could you do that?

dengemann commented 11 years ago

... it does not seem to be a problem of pysurfer but of enthought traits, right?

On Sun, Jan 6, 2013 at 5:30 PM, Eric89GXL notifications@github.com wrote:

Hmm, not sure why a newer version of either would cause a regression here, since array-based colormaps should work unless the underlying plotting call was changed. If it's easy to try the older freesurfrer, could you do that?

— Reply to this email directly or view it on GitHubhttps://github.com/mne-tools/mne-python/issues/340#issuecomment-11930529.

larsoner commented 11 years ago

...Unless pysurfer changed which plotting function they used, which is possible but unlikely. I think that that is more likely than mayavi dropping support for generic colormaps they already had, though.

dengemann commented 11 years ago

Just pulled the recent PySurfer master, now the error moves to the underlying VTK...

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

colormap: fmin=5.00e+00 fmid=1.00e+01 fmax=1.50e+01 transparent=1
ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

colormap: fmin=-5.00e+01 fmid=0.00e+00 fmax=5.00e+01 transparent=0
ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Filtering/vtkImageData.cxx,
line 1467
vtkImageData (0x2175f130): GetScalarPointer: Pixel (0, 0, 0) not in memory.
 Current extent= (0, -1, 0, -1, 0, 0)

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Filtering/vtkImageData.cxx,
line 1467
vtkImageData (0x2175f130): GetScalarPointer: Pixel (0, 0, 0) not in memory.
 Current extent= (0, -1, 0, -1, 0, 0)

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/IO/vtkImageWriter.cxx,
line 493
vtkPNGWriter (0x1b5f9cb0): Ran out of disk space; deleting file(s) already
written

ERROR: In
/Users/builder/pisi-32bit/tmp/VTK-5.6.0-1/work/VTK/Rendering/vtkOpenGLTexture.cxx,
line 197
vtkOpenGLTexture (0x1ad3fad0): No scalar values found for texture input!

On Sun, Jan 6, 2013 at 5:36 PM, Eric89GXL notifications@github.com wrote:

...Unless pysurfer changed which plotting function they used, which is possible but unlikely. I think that that is more likely than mayavi dropping support for generic colormaps they already had, though.

— Reply to this email directly or view it on GitHubhttps://github.com/mne-tools/mne-python/issues/340#issuecomment-11930606.

larsoner commented 11 years ago

Ahh, so it probably does have to do with freesurfer changing their code. I should be able to check out out tomorrow or the next day if someone more familiar with freesurfer (ahem @agramfort) doesn't beat me to it...

dengemann commented 11 years ago

I would propose an alternative interpretation: The colormap error was a transient dev-master artifact and the VTK error might be due to a messed up library path / build-trash from my previous attempt to appropriately build VTK manually.

On Sun, Jan 6, 2013 at 5:46 PM, Eric89GXL notifications@github.com wrote:

Ahh, so it probably does have to do with freesurfer changing their code. I should be able to check out out tomorrow or the next day if someone more familiar with freesurfer (ahem @agramfort) doesn't beat me to it...

— Reply to this email directly or view it on GitHubhttps://github.com/mne-tools/mne-python/issues/340#issuecomment-11930722.

agramfort commented 11 years ago

I would propose an alternative interpretation: The colormap error was a transient dev-master artifact and the VTK error might be due to a messed up library path / build-trash from my previous attempt to appropriately build VTK manually.

LOL !

larsoner commented 11 years ago

I like this interpretation better :)

larsoner commented 11 years ago

I'll close this for now, then -- @dengemann feel free to re-open if it doesn't end up being a VTK compilation problem.

dengemann commented 11 years ago

... unfortunately wiping out build-residuals and reinstalling EPD a second time did not help. The VTK error message would return.

dengemann commented 11 years ago

... but it seems to be very general. It does not matter which example you choose unless it does not call PySurfer

dengemann commented 11 years ago

I have to hack into it a bit, hopefully I'll soon find an equally funny interpretation allowing us to close this one forever.

dengemann commented 11 years ago

... very interesting. Just learned that using the current debian pysurfer version one gets the same error (the initial one about the color map)... to wrap up:

dengemann commented 11 years ago

sorry, wrong button.

larsoner commented 11 years ago

Yeah, I cannot plot STCs (regardless of colormap) on my OSX install now, EPD32-bit. @agramfort pysurfer on OSX still work for you?

larsoner commented 11 years ago

Also, I never had PySurfer working on my system, so I cannot confirm this as a regression. As far as I can tell, EPD 32-bit just doesn't work well on OSX (and they advised using the 32-bit because the 64-bit VTK was unstable, sheesh). @dengemann did PySurfer ever work correctly on your system?

dengemann commented 11 years ago

I once had a build (macports + pip) that worked, even 64bit. But I upgraded Mac OS X, etc. and I then wasn't able to build VTK again, I think the last thing I understood was that most errors are due to matplotlib running with a backend not supported by the build options used for VTK. Does anyone by chance know how to use the TCL/TK/X backend under Mac OS X? Might give this a try. Well, 64 bit EPD works much nicer for me than 32bit (unresponsive interpreter, slow, buggy, plots would hang up, etc.), but as you say, no mayavi, a thorough dilemma. So for the time being Linux seems to be the only game in town... I hope EPD will soon improve the 64bit support for mayavi, especially as WX now is available for 64bit Mac.

On Mon, Jan 21, 2013 at 3:32 AM, Eric89GXL notifications@github.com wrote:

Also, I never had PySurfer working on my system, so I cannot confirm this as a regression. As far as I can tell, EPD 32-bit just doesn't work well on OSX (and they advised using the 32-bit because the 64-bit VTK was unstable, sheesh). @dengemann https://github.com/dengemann did PySurfer ever work correctly on your system?

— Reply to this email directly or view it on GitHubhttps://github.com/mne-tools/mne-python/issues/340#issuecomment-12482640.

agramfort commented 11 years ago

I don't have any problem with my EPD 32 on my mac and pysurfer.

what happened in the past is type issues with float32/64 and endianess. VTK would only accept float64 with a certain endianess.

larsoner commented 11 years ago

@dengemann I think this must be an issue with how you and I have Mayavi/Enthought configured, and not an MNE issue (since it works for @agramfort on 7.2 OSX 32-bit and for me on linux), so my vote is to close this issue.

dengemann commented 11 years ago

Fine with me, but at least we can say that our examples won't work on the current release of pysurfer. Just for the records

On Mon, Jan 21, 2013 at 7:45 PM, Eric89GXL notifications@github.com wrote:

@dengemann https://github.com/dengemann I think this must be an issue with how you and I have Mayavi/Enthought configured, and not an MNE issue (since it works for @agramfort https://github.com/agramfort on 7.2 OSX 32-bit and for me on linux), so my vote is to close this issue.

— Reply to this email directly or view it on GitHubhttps://github.com/mne-tools/mne-python/issues/340#issuecomment-12511595.

agramfort commented 11 years ago

does it work with master? if so iI can release a new pysurfer version

dengemann commented 11 years ago

Works with master --- on debian. Current release + mne 0.5 does not work. I'll try epd 7.2 later on my mac. If it works for you it should for me.

On 21.01.2013, at 21:15, Alexandre Gramfort notifications@github.com wrote:

does it work with master? if so iI can release a new pysurfer version — Reply to this email directly or view it on GitHub.

agramfort commented 11 years ago

Works with master --- on debian. Current release + mne 0.5 does not work. I'll try epd 7.2 later on my mac. If it works for you it should for me.

ok if it works with master than the problem has been solved recently.

let me release a new version of pysurfer during the next 2 days.

agramfort commented 11 years ago

pysurfer 0.3.1 released

http://pypi.python.org/pypi/pysurfer

dengemann commented 11 years ago

Good! Thanks, heaps!

On Tue, Jan 22, 2013 at 11:34 AM, Alexandre Gramfort < notifications@github.com> wrote:

pysurfer 0.3.1 released

http://pypi.python.org/pypi/pysurfer

— Reply to this email directly or view it on GitHubhttps://github.com/mne-tools/mne-python/issues/340#issuecomment-12538698.

larsoner commented 11 years ago

Closing this since @agramfort updated the release version of pysurfer.

dengemann commented 11 years ago

Yeah @Eric89GXL I found the culprit. A newer version of Wx linked against my path which was interfering with the IPyhton backend. I found it on importing wx and looking its origin. Now PySurfer is finally back ;-)