# PySurfer stuff in MNE-Python

**URL:** <https://mne.discourse.group/t/pysurfer-stuff-in-mne-python/792>\
**Category:** Mailing List Archive (read-only)\
**Tags:** list-archive\
**Created:** [August 12, 2014, 7:21am UTC](https://mne.discourse.group/t/pysurfer-stuff-in-mne-python/792 "2014-08-12T07:21:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/mne/original/1X/85cc6bd2b69cb698a166dc6d880fb550510d0144.jpeg) [@system](https://mne.discourse.group/u/system)\
**Post date:** [August 12, 2014, 7:21am UTC](https://mne.discourse.group/t/pysurfer-stuff-in-mne-python/792/1 "2014-08-12T07:21:05Z")

</div>

Hi!

I hope that some of you have experience with PySurfer that you can help me with a couple of questions.

1) When I'm plotting estimates in the same window with brain.add\_data(), how come the brain seems to shrink before it visualizes the next estimate?

2) Why the old source estimates exist a short period of time even though the new estimates have been put to the cortex, even when using remove\_existing=True?

I guess that brain.add\_data() just works this way. If so, can it be changed in some time?

Sebastian  
-------------- next part --------------  
An HTML attachment was scrubbed...  
URL: [http://mail.nmr.mgh.harvard.edu/pipermail/mne\_analysis/attachments/20140812/01059d35/attachment.html](http://mail.nmr.mgh.harvard.edu/pipermail/mne_analysis/attachments/20140812/01059d35/attachment.html)

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/mne/original/1X/85cc6bd2b69cb698a166dc6d880fb550510d0144.jpeg) [@system](https://mne.discourse.group/u/system)\
**Post date:** [August 12, 2014, 7:27am UTC](https://mne.discourse.group/t/pysurfer-stuff-in-mne-python/792/2 "2014-08-12T07:27:43Z")

</div>

This is due to how the PySurfer backend (Mayavi) handles data. It's  
possible it could be improved -- might be worth opening an issue on the  
PySurfer github page. PySurfer might move away from using Mayavi at all due  
to some limitations, but it will be a number of months (at least) before it  
happens, if it happens at all.

FYI I'd suggest posting questions like this over on the PySurfer listserv  
or PySurfer site so as not to spam mne\_analysis with too many  
PySurfer-specific questions.

Eric

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/mne/original/1X/85cc6bd2b69cb698a166dc6d880fb550510d0144.jpeg) [@system](https://mne.discourse.group/u/system)\
**Post date:** [August 12, 2014, 8:34pm UTC](https://mne.discourse.group/t/pysurfer-stuff-in-mne-python/792/3 "2014-08-12T20:34:17Z")

</div>

if you want to do really fast visualization of dynamic source  
estimates you might have to hack your own mayavi code possibly using a  
low resolution surface ie avoiding the upsamling to full resolution  
freesurfer surface.

I also know that proof of concept code exists with vispy. If you want ask me.

Alex
