Picon
Gravatar

Re: Mayavi2 status

Fernando Perez wrote:
>> Many thanks for the great job, Prabhu.
>> You rock.

Many thanks Fred!

> Heartily seconded.  I'm very excited that M2 finally crossed such a

Thanks Fernando!

> significant threshold (feature parity with M1, so it can be a "no
> excuses" move forward).   I'm looking forward to Gael's return (and

Just one word of warning.  The old .mv format for Mayavi-1.x saved 
visualizations *will not work* with mayavi2.  There is no backwards 
compatibility on that front.  I guess a very elementary converter could 
be written but I'd rather not do that -- it is too much headache.

> his visit to Berkeley) to pull M2 into my regular workflow the way I
> used to use M1.

Great to hear.  Do let us know how that goes.

> Have a great and well deserved vacation!

Thanks.

cheers,
prabhu
(Continue reading)

Picon
Gravatar

Re: poor TVTK performance with LabeledDataMapper

jelle feringa wrote:
> I think you've touched upon something rather fundamental.
> I guess it would be a _really_ good idea to post this on the TVTK wiki.
> Being able to control the traits overhead is a pretty big issue, so +1 
> for a nice API call for that!

The _in_set hack is not well tested but feel free to update the wiki. 
I'll put this in my todo list to look into for later.  Putting up a 
ticket for it just so we don't forget might also be a good idea.

Thanks.
prabhu
Picon
Gravatar

Re: poor TVTK performance with LabeledDataMapper

Prabhu Ramachandran wrote:
> jelle feringa wrote:
>> I think you've touched upon something rather fundamental.
>> I guess it would be a _really_ good idea to post this on the TVTK wiki.
>> Being able to control the traits overhead is a pretty big issue, so +1 
>> for a nice API call for that!
> 
> The _in_set hack is not well tested but feel free to update the wiki. 
> I'll put this in my todo list to look into for later.  Putting up a 
> ticket for it just so we don't forget might also be a good idea.

Come to think of it I did have plans to look at removing the __del__ 
method and this would help.  So there is a good chance I will look at 
this before the sprint if I get the chance.

cheers,
prabhu
Fernando Perez | 1 Jun 09:18
Picon
Gravatar

Re: Mayavi2 status

On Sat, May 31, 2008 at 11:12 PM, Prabhu Ramachandran
<prabhu@...> wrote:

> Just one word of warning.  The old .mv format for Mayavi-1.x saved
> visualizations *will not work* with mayavi2.  There is no backwards
> compatibility on that front.  I guess a very elementary converter could
> be written but I'd rather not do that -- it is too much headache.

At least for me, that's not an issue.  I don't have any significant
.mv files around that I might need, fortunately.

Cheers,

f
Dave Peterson | 2 Jun 07:09

Re: Mayavi2 status

fred wrote:
Prabhu Ramachandran a écrit :
Hi, Over May I've made a huge number of changes to mayavi2. Here is a brief summary.
Many thanks for the great job, Prabhu. You rock.

+1.  You rock!

-- Dave
_______________________________________________
Enthought-dev mailing list
Enthought-dev@...
https://mail.enthought.com/mailman/listinfo/enthought-dev
Picon
Gravatar

Re: Mayavi2 status

Dave Peterson wrote:
>> Many thanks for the great job, Prabhu.
>> You rock.
> 
> +1.  You rock!

Thanks!  Hopefully, I haven't rocked anyone's boat in the process. ;-D

cheers,
prabhu
fred | 2 Jun 13:17
Picon

array_editor.py issue.

Hi,

I get an issue using ArrayEditor,
because typecode can not be imported from numpy anymore.

Is it a bug ?

I have attached a patch.

Cheers,

--

-- 
Fred
Attachment (array_editor.patch): text/x-diff, 745 bytes
_______________________________________________
Enthought-dev mailing list
Enthought-dev@...
https://mail.enthought.com/mailman/listinfo/enthought-dev
fred | 2 Jun 13:23
Picon

Re: [T2] array_editor.py issue.

fred a écrit :
> Hi,
> 
> I get an issue using ArrayEditor,
> because typecode can not be imported from numpy anymore.
> 
> Is it a bug ?
I forgot to mention: this is only available for Traits from branch,
not from trunk.

Cheers,

--

-- 
Fred
Lars Friedrich | 2 Jun 13:24

Chaco2 img_plot xbounds, ybounds

Hello,

starting from

https://svn.enthought.com/enthought/browser/Chaco/tags/enthought.chaco2_2.0.0b2/examples/basic/cmap_image_plot.py

I added an enthought.chaco2.api.Plot.img_plot to my application. From 
the example I get that I can set the extensions of my data array using 
the xbounds and ybounds paramters in the call to img_plot. I would like 
to change the extensions of the data afterwards. How can I do this? From 
my intention, I searched for it in the fields of my chaco.ArrayPlotData 
object, but I could not find something. Of course, I also looked in my 
plot.plots['plot0'][0] object, but I could not manage to set the x and y 
extension of my data. Any hint?

Thanks
Lars

-- 
Dipl.-Ing. Lars Friedrich

Photonic Measurement Technology
Department of Microsystems Engineering -- IMTEK
University of Freiburg
Georges-Köhler-Allee 102
D-79110 Freiburg
Germany

phone: +49-761-203-7531
fax:   +49-761-203-7537
room:  01 088
email: lars.friedrich <at> imtek.de

_______________________________________________
Enthought-dev mailing list
Enthought-dev <at> mail.enthought.com
https://mail.enthought.com/mailman/listinfo/enthought-dev
fred | 2 Jun 14:17

Re: Chaco2 img_plot xbounds, ybounds

Lars Friedrich a écrit :

> object, but I could not find something. Of course, I also looked in my 
> plot.plots['plot0'][0] object, but I could not manage to set the x and y 
> extension of my data. Any hint?

Try:

plot.range2d.x_range.set_bounds(-10, 10)
plot.range2d.y_range.set_bounds(-10, 10)

HTH.

Cheers,

--

-- 
Fred

Gmane