On Fri, May 11, 2012 at 2:23 PM, Espen Hagen <espen...@umb.no
> Hi again, Michele
> Yes, I only had to rewrite the class quite a bit though, as I don't use
> the p3d-information from NEURON, and use the endpoint coordinates of the
> segments which I collect in the LFPy.Cell-class, where also the
> 3d-positions of the different neurons, corresponding rotations etc are
> set. I also had to add some stuff to be able to feed numpy arrays
> containing the time-variable values from each segment, say the membrane
Maybe I don't get this. Neuronvisio job is exactly this one:
visualizing in 3d the NEURON model, and being able to show the
variables (recorded through a VecRef) with a color coded scale.
Maybe there is a ton of extra information that is in the
LFpy.Cell-Class, which it's specific to your user cases, otherwise you
could just use the class visio to show that.
> I'm not suggesting in any way that my changes should be in neuronvisio,
> what I did probably broke the old functionality completely. A big hack
> basically, but very useful for me to understand a bit on what's going on
> with all that mayavi.pipeline stuff. I do like what I end up with though,
> as in the attached plot with my cells and some electrode geometry of which
> I calculate the LFPs.
> What could be useful however would be a class method somewhere in class
> Visio taking some input;
>>>> def setWindowHeighWidth(self, height=500, width=600):
>>>> '''set the window height and width and scale the scene contents
> I could not find the proper way to do this though. I don't think your
> method was ever meant to be called by the user in the way I do, so this is
> perhaps not something you should worry about.
if you fire it up visio, mayavi widget is embedded in a Qt container,
which you could resize