matplotlib-devel Mailing List for matplotlib (Page 2)

Hi,
Attached is a patch to support some primitive image filtering (e.g.,
gaussian blur) for agg backend.
The idea is similar to how rasterization is done.
Instead of plotting the rasterized image on the vector backend, it
plots the image (after filtering) on the same agg backend.
The demo image is attached.
It is simple image processing filter and only available for agg
backend. However, you can use this by rasterization (pdf, svg, ps).
For example, saving the demo as pdf works, except the misaligned texts.
Although this is only for the agg backend, I guess this is rather
useful and want to push into the trunk.
The big question is its api. Right now, its api is mostly similar to
rasterization api and it utilizes the "allow_rasterization" decorator.
I think one of the key thing to be considered is how filtering in
other back ends will be implemented (if they are going to).
Right now, the filtering is done by simple function that does some
array arithmetic, but different back end will require different
functions.
Maybe, we need some filter classes which implements filtering function
for each backends.
So, it would be great if others test the patch and give some feedback.
Regards,
-JJ
ps. somehow the filter is not applied if lines are drawn with markers
which is very weird.

Sounds good as well, so I just removed it.
Cheers,
Reinier
On Mon, Jun 15, 2009 at 10:35 PM, John Hunter<jd...@gm...> wrote:
> On Mon, Jun 15, 2009 at 3:33 PM, John Hunter<jd...@gm...> wrote:
>> On Mon, Jun 15, 2009 at 3:28 PM, Reinier Heeres<re...@he...> wrote:
>>> John,
>>>
>>> Shall I update this file and change the error to say something like
>>> "mplot3d is now available as a toolkit, use import
>>> mpl_toolkits.mplot3d"?
>>>
>>> The other option would be to just do a "from mpl_toolkits.mplot3d.axes3d".
>>
>> I prefer the first option.
>
> Actually, I prefer removing axes3d from the matplotlib dir directly.
> After the release, I will make sure it gets plenty of visibility in
> the announcement and in the news box on the website main page.
> Between that and the gallery, people will be able to find it.
>
> So please just go ahead and remove lib/matplotlib/axes3d.py
>
> JDH
-- 
Reinier Heeres
Bleijenburg 64
2511 VD Den Haag
The Netherlands
Tel: +31 6 10852639

On Mon, Jun 15, 2009 at 3:33 PM, John Hunter<jd...@gm...> wrote:
> On Mon, Jun 15, 2009 at 3:28 PM, Reinier Heeres<re...@he...> wrote:
>> John,
>>
>> Shall I update this file and change the error to say something like
>> "mplot3d is now available as a toolkit, use import
>> mpl_toolkits.mplot3d"?
>>
>> The other option would be to just do a "from mpl_toolkits.mplot3d.axes3d".
>
> I prefer the first option.
Actually, I prefer removing axes3d from the matplotlib dir directly.
After the release, I will make sure it gets plenty of visibility in
the announcement and in the news box on the website main page.
Between that and the gallery, people will be able to find it.
So please just go ahead and remove lib/matplotlib/axes3d.py
JDH

On Mon, Jun 15, 2009 at 3:28 PM, Reinier Heeres<re...@he...> wrote:
> John,
>
> Shall I update this file and change the error to say something like
> "mplot3d is now available as a toolkit, use import
> mpl_toolkits.mplot3d"?
>
> The other option would be to just do a "from mpl_toolkits.mplot3d.axes3d".
I prefer the first option.
JDH

John,
Shall I update this file and change the error to say something like
"mplot3d is now available as a toolkit, use import
mpl_toolkits.mplot3d"?
The other option would be to just do a "from mpl_toolkits.mplot3d.axes3d".
Regards,
Reinier
On Mon, Jun 15, 2009 at 2:13 AM, Gökhan SEVER<gok...@gm...> wrote:
> On Sat, Jun 13, 2009 at 4:17 PM, Reinier Heeres <re...@he...> wrote:
>>
>> Hi,
>>
>> I just fixed this issue and implemented setting/unsetting of the grid.
>> I also added a parameter axes3d.grid to matplotlibrc, which defaults
>> to True. Is that ok?
>>
>> Cheers,
>> Reinier
>
> Ok, that strange line doesn't show anymore. Thanks for the fix.
>
> axes3d.grid works well from matplotlibrc file.
>
> Could you tell me how to import axes3d module from within Ipython?
>
> I get the following error when I try: (Seems to me something needs to be
> updated?)
>
> In [3]: from matplotlib import axes3d
> ---------------------------------------------------------------------------
> NotImplementedError            Traceback (most recent call last)
>
> /home/gsever/Desktop/python-repo/matplotlib/examples/mplot3d/text3d_demo.py
> in <module>()
> ----> 1
>    2
>    3
>    4
>    5
>
> /home/gsever/Desktop/python-repo/matplotlib/lib/matplotlib/axes3d.py in
> <module>()
> ----> 1
>    2
>    3 raise NotImplementedError('axes3d is not supported in
> matplotlib-0.98. You may want to try the 0.91.x maintenance branch')
>    4
>    5
>
> NotImplementedError: axes3d is not supported in matplotlib-0.98. You may
> want to try the 0.91.x maintenance branch
>
> gs
>
-- 
Reinier Heeres
Bleijenburg 64
2511 VD Den Haag
The Netherlands
Tel: +31 6 10852639

On Sun, Jun 14, 2009 at 7:13 PM, Gökhan SEVER <gok...@gm...> wrote:
>
> Could you tell me how to import axes3d module from within Ipython?
>
from mpl_toolkits.mplot3d import axes3d
Ryan
-- 
Ryan May
Graduate Research Assistant
School of Meteorology
University of Oklahoma

Hi all,
In order to proceed with contacting speakers, we'd now like to get
some feedback from you. This Doodle poll should take no more than a
couple of minutes to fill out (no password or registration required):
http://doodle.com/hb5bea6fivm3b5bk
So please let us know which topics you are most interested in, and
we'll do our best to accommodate everyone. Keep in mind that speaker
availability and balancing out the topics means that the actual
tutorials offered probably won't be exactly the list of top 8 voted
topics, but the feedback will certainly help us steer the decision
process.
Thanks for your time,
Dave Peterson and Fernando Perez
On Mon, Jun 1, 2009 at 10:21 PM, Fernando Perez<fpe...@gm...> wrote:
> Hi all,
>
> The time for the Scipy'09 conference is rapidly approaching, and we
> would like to both announce the plan for tutorials and solicit
> feedback from everyone on topics of interest.
>
> Broadly speaking, the plan is something along the lines of what we
> had last year: one continuous 2-day tutorial aimed at introductory
> users, starting from the very basics, and in parallel a set of
> 'advanced' tutorials, consisting of a series of 2-hour sessions on
> specific topics.
>
> We will request that the presenters for the advanced tutorials keep
> the 'tutorial' word very much in mind, so that the sessions really
> contain hands-on learning work and not simply a 2-hour long slide
> presentation. We will thus require that all the tutorials will be
> based on tools that the attendees can install at least 2 weeks in
> advance on all platforms (no "I released it last night" software).
>
> With that in mind, we'd like feedback from all of you on possible
> topics for the advanced tutorials. We have space for 8 slots total,
> and here are in no particular order some possible topics. At this
> point there are no guarantees yet that we can get presentations for
> these, but we'd like to establish a first list of preferred topics to
> try and secure the presentations as soon as possible.
>
> This is simply a list of candiate topics that various people have
> informally suggested so far:
>
> - Mayavi/TVTK
> - Advanced topics in matplotlib
> - Statistics with Scipy
> - The TimeSeries scikit
> - Designing scientific interfaces with Traits
> - Advanced numpy
> - Sparse Linear Algebra with Scipy
> - Structured and record arrays in numpy
> - Cython
> - Sage - general tutorial
> - Sage - specific topics, suggestions welcome
> - Using GPUs with PyCUDA
> - Testing strategies for scientific codes
> - Parallel processing and mpi4py
> - Graph theory with Networkx
> - Design patterns for efficient iterator-based scientific codes.
> - Symbolic computing with sympy
>
> We'd like to hear from any ideas on other possible topics of interest,
> and we'll then run a doodle poll to gather quantitative feedback with
> the final list of candidates.
>
> Many thanks,
>
> f
>

On Sat, Jun 13, 2009 at 4:17 PM, Reinier Heeres <re...@he...> wrote:
> Hi,
>
> I just fixed this issue and implemented setting/unsetting of the grid.
> I also added a parameter axes3d.grid to matplotlibrc, which defaults
> to True. Is that ok?
>
> Cheers,
> Reinier
>
Ok, that strange line doesn't show anymore. Thanks for the fix.
axes3d.grid works well from matplotlibrc file.
Could you tell me how to import axes3d module from within Ipython?
I get the following error when I try: (Seems to me something needs to be
updated?)
In [3]: from matplotlib import axes3d
---------------------------------------------------------------------------
NotImplementedError Traceback (most recent call last)
/home/gsever/Desktop/python-repo/matplotlib/examples/mplot3d/text3d_demo.py
in <module>()
----> 1
 2
 3
 4
 5
/home/gsever/Desktop/python-repo/matplotlib/lib/matplotlib/axes3d.py in
<module>()
----> 1
 2
 3 raise NotImplementedError('axes3d is not supported in
matplotlib-0.98. You may want to try the 0.91.x maintenance branch')
 4
 5
NotImplementedError: axes3d is not supported in matplotlib-0.98. You may
want to try the 0.91.x maintenance branch
gs

John Hunter <jd...@gm...> writes:
> On Sun, Jun 7, 2009 at 8:05 PM, Eric Firing<ef...@ha...> wrote:
>> This looks like a very good idea.
>
> I agree -- the presence of *args and **kwargs in the pyplot
> docstrings, the interface most people use, is a major wart. I suggest
> committing this to HEAD when you are ready to go.
I would like to ask the opinion of other developers before checking it
in. I now have two different implementations in two branches of my
github repository (patches attached):
http://github.com/jkseppan/matplotlib/tree/boilerplate
http://github.com/jkseppan/matplotlib/tree/autoboiler
The first one in an improved boilerplate.py as before, so it can be used
to write a large part of pyplot.py so that the signatures and docstrings
are all in there. I still haven't added any automation to call it while
building matplotlib, but that's something of a separate problem.
The second one is a version of pyplot.py that inspects the methods of
Axes objects and creates corresponding functions automatically. It uses
decorator.py, which I have included with the matplotlib source.
I think I personally like the boilerplate branch better. While the code
is a little hairy, you can see its output in pyplot.py, so if it ever
needs to be modified, there is something to run "diff" on. The code in
the autoboiler branch was more difficult to get right, and it creates
the functions at runtime via "exec" (which is how decorator.py can set
the signature of the functions it creates).
In the autoboiler branch, importing pyplot seems to be very slightly
slower. Here is the average time per example it took to run the examples
in the pylab_examples subdirectory in the three branches using the
template backend, in two different runs:
 master boilerplate autoboiler
run 1 1.013 1.028 1.043
run 2 1.028 1.027 1.043
It looks like there is a difference, but it is as large as the
difference between runs in the master branch; much more careful
experimentation would be needed to be sure about the magnitude of 
the difference.
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

I just committed a change to backend_driver.py that allows running a
subset of all tests by directory. In the process I changed the command
line parsing to use OptionParser, but I tried to keep it reasonably
backward compatible. Here are the options the script now takes:
Options:
 -h, --help show this help message and exit
 -d DIRS, --dirs=DIRS, --directories=DIRS
 Run only the tests in these directories; comma-
 separated list of one or more of: pylab (or
 pylab_examples), api, units, mplot3d
 -b BACKENDS, --backends=BACKENDS
 Run tests only for these backends; comma-separated
 list of one or more of: agg, ps, svg, pdf, template,
 cairo, cairo.png, cairo.ps, cairo.pdf, cairo.svg.
 Default is everything except cairo.
 --clean Remove result directories, run no tests
 -c, --coverage Run in coverage.py
 -v, --valgrind Run in valgrind
In addition to the list of backends given via the -b and --backends
options, any extra arguments are added to the list of backends, or
interpreted as switches to pass to the subprocess that runs each test.
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

Hi,
I just fixed this issue and implemented setting/unsetting of the grid.
I also added a parameter axes3d.grid to matplotlibrc, which defaults
to True. Is that ok?
Cheers,
Reinier
On Mon, Jun 8, 2009 at 11:43 PM, Gökhan SEVER<gok...@gm...> wrote:
> Hello,
>
> Please see the uploaded image:
> http://img40.imageshack.us/img40/3909/dashedline.png
>
> There is dashed line in the middle of the figure coming from the top of the
> plot. I didn't mean grid lines, however would be nice to add a functionality
> like pylot's x-yticks commands, ahh we also need zticks for your case :)
>
> gs
>
>
> On Mon, Jun 8, 2009 at 4:37 PM, Reinier Heeres <re...@he...> wrote:
>>
>> Hi,
>>
>> I'm not sure what line you are referring to; do you mean the grid
>> lines? If not, please provide an image.
>>
>> At the moment these lines can't be turned off, but it sounds like a
>> good plan to override the grid() function for that.
>>
>> Regards,
>> Reinier
>>
>> On Mon, Jun 8, 2009 at 10:48 PM, Gökhan SEVER<gok...@gm...>
>> wrote:
>> > Hi,
>> >
>> > Could you please tell me how not to see the dashed line in the middle of
>> > 3d
>> > plotting scene? It's also there on a saved png file as well.
>> >
>> > Next, could it be possible to plot 3d box-whiskers plots via mplot3d
>> > interface?
>> >
>> > Thanks...
>> >
>> > I really appreciate your good work.
>> >
>> > Gökhan
>> >
>> >
>> > On Sun, Jun 7, 2009 at 6:27 PM, Reinier Heeres <re...@he...>
>> > wrote:
>> >>
>> >> Hi all,
>> >>
>> >> I just updated mplot3d with some refactoring, more examples and the
>> >> start of documentation. Also semi-3D text is available again.
>> >>
>> >> Please let me know what you think, perhaps mostly about the
>> >> user-facing API. It would be good to get that 'right' so that we don't
>> >> have to change it in the future.
>> >>
>> >> Regards,
>> >> --
>> >> Reinier Heeres
>> >> Bleijenburg 64
>> >> 2511 VD Den Haag
>> >> The Netherlands
>> >>
>> >> Tel: +31 6 10852639
>> >>
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>> >> looking to deploy the next generation of Solaris that includes the
>> >> latest
>> >> innovations from Sun and the OpenSource community. Download a copy and
>> >> enjoy capabilities such as Networking, Storage and Virtualization.
>> >> Go to: http://p.sf.net/sfu/opensolaris-get
>> >> _______________________________________________
>> >> Matplotlib-devel mailing list
>> >> Mat...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>> >
>> >
>>
>>
>>
>> --
>> Reinier Heeres
>> Bleijenburg 64
>> 2511 VD Den Haag
>> The Netherlands
>>
>> Tel: +31 6 10852639
>
>
-- 
Reinier Heeres
Bleijenburg 64
2511 VD Den Haag
The Netherlands
Tel: +31 6 10852639

Hi,
I just committed a simple patch that introduces a "rotation_mode"
property for Text artist.
By default, mpl rotates the text first and then align it. The patch
let it (optionally) align then rotate (see
examples/pylab_examples/demo_text_rotation_mode.py).
I have chosen "anchor" as the mode name for the latter, but I'm not
sure if this name makes any sense. Any suggestion will be very
appreciated.
-JJ

On Wed, Jun 10, 2009 at 4:41 PM, John Hunter<jd...@gm...> wrote:
> Drop the tar.gz into release/win32 and then following the instructions
> in release/win32/README.txt
I should add one more detail here. distutils for python2.6 adds a
dependency to MSVCR90.DLL, and Charlie has a distutils hack in
release/win32/data/setupwin.py to try
and banish the msvcr90.dll which is not on most systems; he sets the
distutils dll_libraries to the empty list::
 from distutils import cygwinccompiler
 try:
 # Python 2.6
 # Replace the msvcr func to return an empty list
 cygwinccompiler.get_msvcr
 cygwinccompiler.get_msvcr = lambda: []
w/o this hack you will get a dll import error rather than a segfault.
You can toggle the hack on and off by changing in the Makefile::
 # on
 ${PYTHON} setupwin.py build_ext -c mingw32 -I ${PY_INCLUDE} -L
${PY_LINKER} bdist_wininst
 # off
 ${PYTHON} setup.py build_ext -c mingw32 -I ${PY_INCLUDE} -L
${PY_LINKER} bdist_wininst
The problem is that the dll cannot be found on the system and
apparently the right solution is to include it in a framework as
described by David in the link I posted
 http://cournape.wordpress.com/2008/09/02/how-to-embed-a-manifest-into-a-dll-with-mingw-tools-only/
but I think this is something of a red herring because w/ Charlie's
hack _png links against MSVCRT.DLL rather than MSVCR90.DLL but still
segfaults (only on python2.6) on the png_write_info call. I also
tried forcing 'msvcr71' in the distutils hack which is what python2.5
usesbut to no avail. When I said I wasted a lot of time chasing down
false leads, most of that was spent on trying various versions of mpl,
numpy, distutils, and the distutils MSVCR hacks, but in the end none
of it mattered.
But for the record I am including some notes I took while
experimenting with different things. When I write below
 Interestingly, depwalker can find the DLL where PYTHON26.DLL depends
 on, pointing to C:\WINDOWS\WinSxS.VC90.CRT_1fgobbledygook on my box,
 but cannot find it where _PNG.PYD depends on it.
this was before I discovered David's essay on side-by-side assemblies
which explains why the linker finds python's MSVCR90.DLL but not
_pngs. What it doesn't explain is why w/ Charlie's hack, when we link
against MSVCRT.DLL or MSVCR71.DLL, png is still segfaulting, and I
think the answer there is what I pointed to in my first post, the
broken time support in mingw MSVCR90.DLL. Support for this is in my
note below::
 This time it finds it, but two of the functions are colored red
 indicating a problem: _fstati64 and gmtime.
Notes on the _png segfault and the MSVCR hacks
======================================
I have been working on the windows installers for mpl 98.5.3. I am
able to build for python2.5 w/o problems, but when building for
python2.6, I get an DLL local error on any extension code
 cd matplotlib-0.98.5.3/build/lib.win32-2.6/matplotlib
 > /c/python26/python -c 'import _png'
 Traceback (most recent call last):
 File "<string>", line 1, in <module>
 ImportError: DLL load failed: The specified procedure could not be found.
when I open _PNG.PYD this file in dependency walker, I see a
dependency on MSVCR90.DLL which is flagged with a question mark "Error
opening file. The system cannot find the file specified". All the
*.PYD files have this dependency, including the numpy pyd files, but
most of them have it buried under a PYTHON26.DLL dependency, and
_PNG.PYD has it as a direct dependency (top level). Interestingly,
depwalker can find the DLL where PYTHON26.DLL depends on, pointing to
C:\WINDOWS\WinSxS.VC90.CRT_1fgobbledygook on my box, but cannot find
it where _PNG.PYD depends on it.
When I look at _PNG.PYD for python2.5 (which is working fine and I've
uploaded the installers) I see a dependency for MSVCR71.DLL located in
C:/windows/system32, and the functions it provides include fclose,
fopen, putc, etc. which libpng apparently needs for file I/O.
As mentioned above, my system *does* have MSVCR90.DLL deep in
C:\WINDOWS\WinSxS.VC90.CRT_1fgobbledygook, and when I move it into
C:\windows\system32 and then reopen _png.pyd in depdendency walker, I
still get an error. This time it finds it, but two of the functions
are colored red indicating a problem: _fstati64 and gmtime.
Charlie has a distutils hack in release/win32/data/setupwin.py. Wen I
build the installer using the hacked distutils I can load the DLL file
in mpl either by importing matplotlib._png or in dependency walker.
In depwalker, the msvcrt90.DLL is replaced by MSVCRT.DLL at the top
level _PNG.PYD dependency, but the MSVCR90.DLL is still buried deep
under PYTHON26.DLL. Unfortunately, use of this module triggers a
segfault.

I have uploaded binary installers for python2.5 for win32 to the
website, but python2.6 is a different beast all together. I have been
trying to make Charlie's support work for mingw32 for windows in
release/win32 work, but have hit a huge wall. Apparently, mingw
doesn't play nicely with MSVCR90.DLL abd Charlie's hack to simply
remove it from the dll_libraries list doesn't work because _png.pyd
needs these functions and the mingw support is broken. The dirty
details are at
 http://bugs.python.org/issue3308
 http://www.nabble.com/localtime()-and-MSVCRT9-td18329478.html
numpy went through what looks like a painful experience with some of
these issues detailed at
 http://www.mail-archive.com/num...@sc.../msg14552.html
 http://cournape.wordpress.com/2008/09/02/how-to-embed-a-manifest-into-a-dll-with-mingw-tools-only/
It looks like pygame is going to extreme lengths to work around these
problems, as you can see in this code
 http://github.com/ab3/pygame-mirror/blob/cf8aee7508194b0be734b080f866c5a24e242cec/msys_link_VC_2008_dlls.py
I've burnt a lot of time chasing false leads before I finally figured
out where the root of the problem is, and it appears to be in the
broken gmtime/localtime support in mingw and MSVCR90.DLL. I have
narrowed the segfault to png_write_info(png_ptr, info_ptr), and since
I believe png uses time support in the info processing, my guess is
this is where the code is failing, but my attempts to build libpng w/o
time support as a quick workaround
 CFLAGS = -Os -D_ftime=ftime64 -DPNG_NO_READ_tIME -DPNG_NO_WRITE_tIME
have not helped (this was mainly a stab in the dark from poking around
the png headers and src)
There are a variety of solutions offered in the links above ranging
from rebuilding a patched mingw from src to the approach taken by
pygame. Since the rest of mpl is working fine, I was hoping to simply
hack around the broken part of libpng itself (eg removing the time
calls) but have not succeeded yet. Unfortunately, I won't have a lot
more time to spend on this in the near future, so I was hoping that
someone with a fresh pair of eyes and a little time could find a
solution.
If you can take a look, to get started check out release/win32 from
the TRUNK and build the sdist from the branch with
 > python setup.py sdist --formats=gztar
Drop the tar.gz into release/win32 and then following the instructions
in release/win32/README.txt
Thanks,
JDH

Hi there,
On Mon, Jun 8, 2009 at 2:58 PM, John Hunter<jd...@gm...> wrote:
<snip>
> One other feature request that I think you could add w/o too much
> difficulty is colormapping on the surface plots (eg inherit from
> cm.ScalaraMappable. I did this in a local branch of the old axes3d
> code which I might be able to dig up, but I think it should be pretty
> forward to implement de novo.
Added, and I also improved the contour plotting code, which was slightly broken!
Bug reports are welcome.
Regards,
-- 
Reinier Heeres
Bleijenburg 64
2511 VD Den Haag
The Netherlands
Tel: +31 6 10852639

Hi,
Could you post the code that resulted in this image? I don't see the
dashed line here if I use the example. If it is the example, do you
perhaps have some extra settings in your rc file(s)?
Regards,
Reinier
On Mon, Jun 8, 2009 at 11:43 PM, Gökhan SEVER<gok...@gm...> wrote:
> Hello,
>
> Please see the uploaded image:
> http://img40.imageshack.us/img40/3909/dashedline.png
>
> There is dashed line in the middle of the figure coming from the top of the
> plot. I didn't mean grid lines, however would be nice to add a functionality
> like pylot's x-yticks commands, ahh we also need zticks for your case :)
>
> gs
>
>
> On Mon, Jun 8, 2009 at 4:37 PM, Reinier Heeres <re...@he...> wrote:
>>
>> Hi,
>>
>> I'm not sure what line you are referring to; do you mean the grid
>> lines? If not, please provide an image.
>>
>> At the moment these lines can't be turned off, but it sounds like a
>> good plan to override the grid() function for that.
>>
>> Regards,
>> Reinier
>>
>> On Mon, Jun 8, 2009 at 10:48 PM, Gökhan SEVER<gok...@gm...>
>> wrote:
>> > Hi,
>> >
>> > Could you please tell me how not to see the dashed line in the middle of
>> > 3d
>> > plotting scene? It's also there on a saved png file as well.
>> >
>> > Next, could it be possible to plot 3d box-whiskers plots via mplot3d
>> > interface?
>> >
>> > Thanks...
>> >
>> > I really appreciate your good work.
>> >
>> > Gökhan
>> >
>> >
>> > On Sun, Jun 7, 2009 at 6:27 PM, Reinier Heeres <re...@he...>
>> > wrote:
>> >>
>> >> Hi all,
>> >>
>> >> I just updated mplot3d with some refactoring, more examples and the
>> >> start of documentation. Also semi-3D text is available again.
>> >>
>> >> Please let me know what you think, perhaps mostly about the
>> >> user-facing API. It would be good to get that 'right' so that we don't
>> >> have to change it in the future.
>> >>
>> >> Regards,
>> >> --
>> >> Reinier Heeres
>> >> Bleijenburg 64
>> >> 2511 VD Den Haag
>> >> The Netherlands
>> >>
>> >> Tel: +31 6 10852639
>> >>
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>> >> looking to deploy the next generation of Solaris that includes the
>> >> latest
>> >> innovations from Sun and the OpenSource community. Download a copy and
>> >> enjoy capabilities such as Networking, Storage and Virtualization.
>> >> Go to: http://p.sf.net/sfu/opensolaris-get
>> >> _______________________________________________
>> >> Matplotlib-devel mailing list
>> >> Mat...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>> >
>> >
>>
>>
>>
>> --
>> Reinier Heeres
>> Bleijenburg 64
>> 2511 VD Den Haag
>> The Netherlands
>>
>> Tel: +31 6 10852639
>
>
-- 
Reinier Heeres
Bleijenburg 64
2511 VD Den Haag
The Netherlands
Tel: +31 6 10852639

Hello,
Please see the uploaded image:
http://img40.imageshack.us/img40/3909/dashedline.png
There is dashed line in the middle of the figure coming from the top of the
plot. I didn't mean grid lines, however would be nice to add a functionality
like pylot's x-yticks commands, ahh we also need zticks for your case :)
gs
On Mon, Jun 8, 2009 at 4:37 PM, Reinier Heeres <re...@he...> wrote:
> Hi,
>
> I'm not sure what line you are referring to; do you mean the grid
> lines? If not, please provide an image.
>
> At the moment these lines can't be turned off, but it sounds like a
> good plan to override the grid() function for that.
>
> Regards,
> Reinier
>
> On Mon, Jun 8, 2009 at 10:48 PM, Gökhan SEVER<gok...@gm...>
> wrote:
> > Hi,
> >
> > Could you please tell me how not to see the dashed line in the middle of
> 3d
> > plotting scene? It's also there on a saved png file as well.
> >
> > Next, could it be possible to plot 3d box-whiskers plots via mplot3d
> > interface?
> >
> > Thanks...
> >
> > I really appreciate your good work.
> >
> > Gökhan
> >
> >
> > On Sun, Jun 7, 2009 at 6:27 PM, Reinier Heeres <re...@he...>
> wrote:
> >>
> >> Hi all,
> >>
> >> I just updated mplot3d with some refactoring, more examples and the
> >> start of documentation. Also semi-3D text is available again.
> >>
> >> Please let me know what you think, perhaps mostly about the
> >> user-facing API. It would be good to get that 'right' so that we don't
> >> have to change it in the future.
> >>
> >> Regards,
> >> --
> >> Reinier Heeres
> >> Bleijenburg 64
> >> 2511 VD Den Haag
> >> The Netherlands
> >>
> >> Tel: +31 6 10852639
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
> >> looking to deploy the next generation of Solaris that includes the
> latest
> >> innovations from Sun and the OpenSource community. Download a copy and
> >> enjoy capabilities such as Networking, Storage and Virtualization.
> >> Go to: http://p.sf.net/sfu/opensolaris-get
> >> _______________________________________________
> >> Matplotlib-devel mailing list
> >> Mat...@li...
> >> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> >
> >
>
>
>
> --
> Reinier Heeres
> Bleijenburg 64
> 2511 VD Den Haag
> The Netherlands
>
> Tel: +31 6 10852639
>

Hi,
I'm not sure what line you are referring to; do you mean the grid
lines? If not, please provide an image.
At the moment these lines can't be turned off, but it sounds like a
good plan to override the grid() function for that.
Regards,
Reinier
On Mon, Jun 8, 2009 at 10:48 PM, Gökhan SEVER<gok...@gm...> wrote:
> Hi,
>
> Could you please tell me how not to see the dashed line in the middle of 3d
> plotting scene? It's also there on a saved png file as well.
>
> Next, could it be possible to plot 3d box-whiskers plots via mplot3d
> interface?
>
> Thanks...
>
> I really appreciate your good work.
>
> Gökhan
>
>
> On Sun, Jun 7, 2009 at 6:27 PM, Reinier Heeres <re...@he...> wrote:
>>
>> Hi all,
>>
>> I just updated mplot3d with some refactoring, more examples and the
>> start of documentation. Also semi-3D text is available again.
>>
>> Please let me know what you think, perhaps mostly about the
>> user-facing API. It would be good to get that 'right' so that we don't
>> have to change it in the future.
>>
>> Regards,
>> --
>> Reinier Heeres
>> Bleijenburg 64
>> 2511 VD Den Haag
>> The Netherlands
>>
>> Tel: +31 6 10852639
>>
>>
>> ------------------------------------------------------------------------------
>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>> looking to deploy the next generation of Solaris that includes the latest
>> innovations from Sun and the OpenSource community. Download a copy and
>> enjoy capabilities such as Networking, Storage and Virtualization.
>> Go to: http://p.sf.net/sfu/opensolaris-get
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
-- 
Reinier Heeres
Bleijenburg 64
2511 VD Den Haag
The Netherlands
Tel: +31 6 10852639

Hi,
Could you please tell me how not to see the dashed line in the middle of 3d
plotting scene? It's also there on a saved png file as well.
Next, could it be possible to plot 3d box-whiskers plots via mplot3d
interface?
Thanks...
I really appreciate your good work.
Gökhan
On Sun, Jun 7, 2009 at 6:27 PM, Reinier Heeres <re...@he...> wrote:
> Hi all,
>
> I just updated mplot3d with some refactoring, more examples and the
> start of documentation. Also semi-3D text is available again.
>
> Please let me know what you think, perhaps mostly about the
> user-facing API. It would be good to get that 'right' so that we don't
> have to change it in the future.
>
> Regards,
> --
> Reinier Heeres
> Bleijenburg 64
> 2511 VD Den Haag
> The Netherlands
>
> Tel: +31 6 10852639
>
>
> ------------------------------------------------------------------------------
> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
> looking to deploy the next generation of Solaris that includes the latest
> innovations from Sun and the OpenSource community. Download a copy and
> enjoy capabilities such as Networking, Storage and Virtualization.
> Go to: http://p.sf.net/sfu/opensolaris-get
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

On Mon, Jun 08, 2009 at 10:30:09AM -0700, Fernando Perez wrote:
> Reinier, I'm sure if you ping Gael he'd be happy to share some
> thoughts with you, he's very interested in code reusability (he may be
> on this list for all I know, but I did CC him just to be safe).
I am around. :)
Have a look at 
http://code.enthought.com/projects/mayavi/docs/development/html/mayavi/mlab.html
for an overview on the mlab API. 
You might also be interested in
http://code.enthought.com/projects/mayavi/docs/development/html/mayavi/auto/mlab_reference.html#module-enthought.mayavi.mlab
for the reference of all functions.
Indeed, it would be great if mayavi.mlab and the 3D plotting module of
matplotlib were drop-in replacements, with regards to the simple API. We
really designed mlab's API looking at matplotlib's API and used the
similar API where possible.
Gaël

On Mon, Jun 8, 2009 at 3:25 PM, Gökhan SEVER<gok...@gm...> wrote:
> I have updated installing_faq.rst file accordingly as a result of these
> conversations. Thanks to Jouni, and IPython documentation (stolen some words
> from there :))
>
> Could you please tell me how can I submit this to database? OK, this is the
> last time I am asking about patches, and will not disturb anybody for such a
> simple matter again ;)
See http://matplotlib.sourceforge.net/faq/howto_faq.html#contributing-howto
Thanks,
JDH

Hello,
I have updated installing_faq.rst file accordingly as a result of these
conversations. Thanks to Jouni, and IPython documentation (stolen some words
from there :))
Could you please tell me how can I submit this to database? OK, this is the
last time I am asking about patches, and will not disturb anybody for such a
simple matter again ;)
Thanks...
Gökhan
On Mon, Jun 8, 2009 at 2:48 PM, Jouni K. Seppänen <jk...@ik...> wrote:
> Gökhan SEVER <gok...@gm...> writes:
>
> > One more question: After svn co completes checking out the main trunk it
> > says:
> >
> > Checked out revision 7203.
> >
> > However when I do:
> >
> > In [1]: matplotlib.__revision__
> > Out[1]: '$Revision: 6887 $'
> >
> > Which one is correct?
>
> The svn output is arguably more correct. The matplotlib.__revision__
> uses the svn $Revision$ keyword, and its content is only updated when
> matplotlib/__init__.py changes, so it reflects the latest revision in
> which that file was changed. It would be possible (but no-one has
> probably thought it worthwhile) to make setup.py determine the overall
> revision of the checked-out tree (which is more complicated than it
> sounds, since it might not even be a single revision number; but there
> is a program called svnversion that does this) and update __init__.py
> accordingly.
>
> --
> Jouni K. Seppänen
> http://www.iki.fi/jks
>
>
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables unlimited
> royalty-free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Gökhan SEVER <gok...@gm...> writes:
> One more question: After svn co completes checking out the main trunk it
> says:
>
> Checked out revision 7203.
>
> However when I do:
>
> In [1]: matplotlib.__revision__
> Out[1]: '$Revision: 6887 $'
>
> Which one is correct?
The svn output is arguably more correct. The matplotlib.__revision__
uses the svn $Revision$ keyword, and its content is only updated when
matplotlib/__init__.py changes, so it reflects the latest revision in
which that file was changed. It would be possible (but no-one has
probably thought it worthwhile) to make setup.py determine the overall
revision of the checked-out tree (which is more complicated than it
sounds, since it might not even be a single revision number; but there
is a program called svnversion that does this) and update __init__.py
accordingly.
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

Gökhan SEVER wrote:
> One more question: After svn co completes checking out the main trunk 
> it says:
>
> Checked out revision 7203.
>
> However when I do:
>
> In [1]: matplotlib.__revision__
> Out[1]: '$Revision: 6887 $'
>
> Which one is correct?
The __revision__ in from matplotlib is the revision number on 
matplotlib's __init__.py file, which will always lag behind the revision 
of the most recently-changed file in the source tree (which is what SVN 
tells you).
Mike
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

On Mon, Jun 8, 2009 at 2:14 PM, Gökhan SEVER<gok...@gm...> wrote:
> Hello,
>
> How do you add you automatically check-out new added files from matplotlib
> trunk? Is there a specific svn command for this?
Check out svn as indicated here::
 http://matplotlib.sourceforge.net/faq/installing_faq.html#install-from-svn
Once you have a checkout, you can get updates with ::
 > svn up
JDH