Le 24/07/2015 15:10, Jens Nielsen a écrit :
> In the mean time you can use the development version of the docs up
> here: http://matplotlib.org/devdocs/users/colormaps.html that contains
> the plots.
thanks !
--
Pierre
---
Hi,
I'm a bit confused with the colormap doc
http://matplotlib.org/users/colormaps.html
I often get to this page to select my colormaps and today I see no more
images of the colormaps, only text !
And when I look at the raw code
https://raw.githubusercontent.com/matplotlib/matplotlib/master/doc/u
Hi,
Le 01/03/2015 23:27, jni a écrit :
> As someone working with images, I think for displaying images you want a
> colormap that spans as much as possible of the luminance range. The colormap
> suggested by Michael Waskom would be quite perfect as-is. (recap: middle
> colormap here:
> http://earth
Hi,
Le 16/02/2015 23:01, Eric Firing a écrit :
> For a long time there has been discussion of replacing the matplotlib
> default color map [...]
I've started building a small interactive Lab point editor to build a
sequential colormap.
https://github.com/pierre-haessig/lab-colormap-c
Nice coincidence, I was also playing with this idea back in April.
http://nbviewer.ipython.org/gist/pierre-haessig/7e3e6a818edeb6819708
I was actually wondering whether this could interest other people in
other fields...
best,
Pierre
> It is
> useful when one has frequencies in a popula
Le 21/10/2014 10:09, Eric Firing a écrit :
That's the big question: what is the IP status?
So Nathaniel and I asked, and the blog post author, Steve Eddins, took
the time to answer :
Nathaniel and Pierre—Thanks for your interest in the new parula
colormap. /Parula is the end result of a
Hi,
Matlab is now shipping with a new default colormap, named "parula"
[1,2]. It is meant to overcome the many issues of the current default
"jet". It seems that the RGB values of this new colormap are already
onnline [3].
So my question is:
* is it worth adding this parula in the Matplotlib c
Hi,
Le 17/10/2014 15:38, Thomas Caswell a écrit :
> I have heard no complaints about the release candidate. Unless I hear
> otherwise I plan to tag and release 1.4.1 tomorrow.
I just got hit by https://github.com/matplotlib/matplotlib/issues/3553
today and I didn't see a definite feedback that t
Hi,
Le 08/10/2014 15:04, Pierre Haessig a écrit :
[...]
AttributeError: 'LogLocator' object has no attribute 'set_params'
[...]
Should I put an issue on Github ?
best,
Pierre
--
Comprehensive Se
Hello,
I was wondering if the following behavior is a bug of LogLocator class
or just a known limitation:
(mpl 1.3.1)
Input:
plt_scale = 'log'
#plt_scale = 'linear'
fig, (ax1) = plt.subplots(1, 1)
ax1.set(yscale=plt_scale)
# works for linear scale, not for log:
ax1.axes.l
stics Professional
>Build stunning WinForms apps today!
>Reboot your WinForms applications with our WinForms controls.
>Build a bridge from your legacy apps to the future.
>http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
>
>-------
Hi David,
Le 19/01/2014 18:31, David Reed a écrit :
> I've implemented a new feature called shade_color which will either
> brighten or darken a color based on a certain percentage. Compare URL
> is here:
>
> https://github.com/dvreed77/matplotlib/compare/master...shade_color
>
A nice helper func
Hi,
On the main doc page http://matplotlib.org/contents.html the "Examples"
section is misaligned (because it gets surrounded by a blockquote tag).
I guess it relates to the special treatment it gets in content.rst
(https://raw2.github.com/matplotlib/matplotlib/master/doc/contents.rst).
I don't kn
Le 25/10/2013 14:57, Pierre Haessig a écrit :
> 2) default NFFT value being hidden from views
>
> used to be def specgram(x, NFFT=256, Fs=2, ...
> now is def specgram(x, NFFT=None, Fs=None
>
> I think that NFFT is an important parameter of the spectrum
> computation. It
Hi,
Le 21/10/2013 15:58, Todd a écrit :
>
> 2) Should there be two separate functions for these two, or just one
> function, with a switch argument `unwrap` ? (I guess it would be
> True by
> default)
>
>
> I originally was going to do that, but decided against it. The
> problem i
Hello,
Now that that PR #2522 is merged, I don't know how much futher
commenting is useful, but I think there are two API details that I feel
could be better :
1) API dissymetry
The new pyplot/axes API is now:
* 1 function *spectgram* now uses a mode argument to tune this behavior :
*mode*:
Hi,
Le 22/10/2013 19:14, Todd a écrit :
>
> Thanks for the feedback. I agree that your documentation does make
> clear the distinction between "phase" and "angle" and that it has
> a consistency. I just feel that this distinction does not exist
> "outside" ...
>
> But beyond th
Hi,
Le 21/10/2013 15:58, Todd a écrit :
> On Mon, Oct 21, 2013 at 3:13 PM, Pierre Haessig
> mailto:pierre.haes...@crans.org>> wrote:
>
> 1) is the terminology "phase" vs. "angle" spectrum standardized ?
> I must
> say I've n
Hi,
Le 22/10/2013 12:31, Todd a écrit :
> Currently, both axes.psd and axes.csd return the same thing as
> mlab.psd and mlab.csd, namely the spectrum and frequency points. They
> do NOT return the line object that was plotted. This is different
> than specgram, which returns the AxesImage object
Hi,
Le 20/10/2013 09:45, Todd a écrit :
> I submitted a pull request #2522 [1]. It includes support for more
> basic spectrum plots like magnitude and phase spectrums. These are
> extremely commonly used in signal processing, acoustics, and many
> other fields, but are also very important for ed
Hi,
Le 16/04/2013 15:41, Detlef Maurel (IKP) a écrit :
> this works for me, too. Strange... I get the problem with the attached
> dataset using the command
>
> hist(loadtxt("data.txt"),bins=300,histtype="step")
Indeed, I could reproduce your problem using your specific dataset.
The automated sel
Hi,
Le 16/04/2013 12:14, Detlef Maurel (IKP) a écrit :
> there seems to be a bug in in pyplot.hist when using histtype="step".
>
> I am plotting the attached data to a histogram (see 1.png). In this
> case I set the limits on the y axis manually.
>
> When I don't do this (let the hist function cho
Hi Phil,
Le 13/09/2012 16:50, Phil Elson a écrit :
> Your issue looks legit, I have looked through the axes.py Axes.draw
> method, and there is no filtering based on the visibility toggle for
> anything but images. Seems like it could be a very easy fix, would you
> be willing to open an issue on
Le 10/09/2012 19:19, Pierre Haessig a écrit :
> Hello,
>
> This may be a silly question, but I'm wondering what happens in
> Matplotlib rendering when there is a "big" Line2D object (say 10**7
> points) added to an Axes, with *visibility set to false*.
>
> [..
Hello,
This may be a silly question, but I'm wondering what happens in
Matplotlib rendering when there is a "big" Line2D object (say 10**7
points) added to an Axes, with *visibility set to false*.
Here is an tiny script meant to be run interactively (say with Python in
pylab mode) step by step :
Hello,
I was playing a bit with the clippedline example
(http://matplotlib.org/examples/pylab_examples/clippedline.html) and I
feel it is not working anymore.
From what I understand of the traceback I got, there may be something
evil happening after setting
>>> self._marker = 's'
in the draw meth
26 matches
Mail list logo
