From tcaswell at gmail.com  Sat Mar  3 13:40:23 2018
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sat, 03 Mar 2018 18:40:23 +0000
Subject: [Matplotlib-devel] What minimum version of python3?
In-Reply-To: <CAA48SF9ScjoZmWJrnk0DbsZ2e+_Lk5APNHFCarb1mRg2ZOP1GQ@mail.gmail.com>
References: <CAA48SF95n_ZFp2iECnwVwT6DSmGiS0SwGhAKvg8jXyadhPnLLA@mail.gmail.com>
 <CAH6Pt5rA8w35d+Z5S7cRmnrExwTvrUdRdMY=P8U7hfOfz4y44Q@mail.gmail.com>
 <CAJXewOmMdV9CBcNUdZjNP3cTdGE-CTjk7CvXKssbxBCjTgC5rw@mail.gmail.com>
 <d9fca711-60f2-1f46-00a3-7fd68f5d0af9@gmail.com>
 <CALGmxE+pQQppTpStZQeteyDcDjvfdu7q0u-CJxb5i1a1jk_ZXA@mail.gmail.com>
 <CAA48SF9ScjoZmWJrnk0DbsZ2e+_Lk5APNHFCarb1mRg2ZOP1GQ@mail.gmail.com>
Message-ID: <CAA48SF_Nhs=gk0fE1eYxiBkqAmdpgTTeaiCS=Lhj7_51X4qfFQ@mail.gmail.com>

We discussed the minimum python again on the call this past week and
settled on:

 - support minor versions of python initially released in the previous 3
years
 - support minor versions of python initially released in the previous 3
years or oldest that supports the minimum python version (which ever is
higher)

We will bump the minimum python an numpy versions as we can every minor and
major release.

We did not discuss other dependencies, but I propose:
 - for system/c-dependencies (libpng, freetype, GUI frameworks, latex, gs,
ffmpeg) support as old as practical
 - for python dependencies with compiled extensions 3 years or the oldest
that support our minimum python + numpy
 - for python dependencies without complied extensions at least 2 years or
the oldest that supports our minimum python.

Bump these minimum versions as they no longer support our minimum python or
we want to use new features in them.

We should never bump minimum versions on a patch release.

For mpl 3.0 (July 2018) this means python 3.5 (released Sept 2015) and
numpy 1.10 (release in Oct 2015).  Python 3.4 was released Mar 2014 and
Numpy 1.9 was released Sept 2014

For mpl 3.1 (January 2019) this means python 3.6 (released Dec 2016) and
numpy 1.11 (March 2016).

Tom

On Mon, Feb 12, 2018 at 11:38 PM Thomas Caswell <tcaswell at gmail.com> wrote:

> We are talking about a release scheduled for July/August 2018 when 3.7
> will already be out and 3.6 will have been out for ~20 months so support
> coverage will only get better.
>
> From the point of view of distributions, I am mostly worried about running
> into an issue with a distribution that will not be able to package
> Matplotlib.  Are there any distributions that _will_ want to package mpl
> 3.0 in August and will _not_ have 3.6 available in August?
>
> If people are using system python / Matplotlib on older versions of OSs,
> then they are using the old version that is packaged and are OK.  If they
> want to build user-space envs there are a bunch of options (pyenv, conda,
> activestate) which all current support python 3.6 as well as PPAs / IUS /
> .. for system level 3.6.
>
> I think it is incumbent on those advocating we support 3.5 to produce any
> sort of estimate of the harm for dropping 3.5.
>
> I am advocating a policy of 'last 2 python feature releases' (which is
> what I remember from when I first started working on Matplotlib), what is
> the alternative proposal?
>
> As I have said before, I think the community's expectations have been
> warped by having to support and provide new features for an almost decade
> old version of python.
>
> As a final fallback, the 2.2 series will continue to support 3.4 and 3.5
> until 2020.
>
> Tom
>
> On Mon, Feb 12, 2018 at 9:00 PM Chris Barker - NOAA Federal <
> chris.barker at noaa.gov> wrote:
>
>> How many people are using the district-supplied python these days?
>>
>> Do they need the latest MPL?
>>
>> I have literally no idea.
>>
>> -CHB
>>
>> Sent from my iPhone
>>
>> > On Feb 12, 2018, at 3:54 PM, "vincent.adrien at gmail.com" <
>> vincent.adrien at gmail.com> wrote:
>> >
>> > Well, I do not know how accurate is the following script:
>> > https://github.com/Mariatta/python_versions_and_distros
>> > but looking at the list it returned on 2017-10-15, it looks like Python
>> 3.6+ may be quite common **outside of the usual left-behind distributions
>> ala Debian stable or CentOS**.
>> >
>> > Adrien,
>> > conda lover since he had to work with CentOS ^^...
>> >
>> >> On 02/12/2018 03:48 PM, Nathan Goldbaum wrote:
>> >> Ubuntu 14.04 (which admittedly goes EOL in April) is still on python
>> 3.4, for example.
>> >> On Mon, Feb 12, 2018 at 5:28 PM Matthew Brett <matthew.brett at gmail.com
>> <mailto:matthew.brett at gmail.com>> wrote:
>> >>    On Mon, Feb 12, 2018 at 10:40 PM, Thomas Caswell <
>> tcaswell at gmail.com
>> >>    <mailto:tcaswell at gmail.com>> wrote:
>> >>     > These are derived from today's call:
>> >>     >
>> >>     > Pro 3.6:
>> >>     >  - by the time we release, 3.7 will be out so will support "two
>> >>    most recent
>> >>     > python"
>> >>     >     - this gives 3 years of support on master of each python
>> version
>> >>     > (assuming python sticks
>> >>     >  - ordered, faster dictionaries (as implementation detail in 3.6,
>> >>    guaranteed
>> >>     > in 3.7)
>> >>     >  - guaranteed ordered kwargs / class definitions (do precedence
>> of
>> >>     > conflicting kwaargs)
>> >>     >  - fstrings
>> >>     >  - fspath / pathlib protocol
>> >>     >
>> >>     > Con 3.6:
>> >>     >  - feels a bit agressive as 3.7 is not out yet
>> >>     >  - might get ahead of some LTS releases
>> >>     >    - but older version of Matplotlib will still work
>> >>     >    - user-space environments go along way to fixing this
>> >>     >      - conda
>> >>     >      -
>> >>     >
>> >>
>> https://www.digitalocean.com/community/tutorials/how-to-install-python-3-and-set-up-a-local-programming-environment-on-centos-7
>> >>     >    - ubuntu 18.04 is planned to be py3.6 by default
>> >>     >
>> >>     > Pro 3.5:
>> >>     >  - more conservative approach
>> >>     >  - pypy3 support (but they will support 3.6 eventually)
>> >>     >
>> >>     > The consensus on the call and on gitter seems to be for 3.6 as
>> >>    the minimum.
>> >>    Man - that seems pretty extreme.   Are the 3.6 features really worth
>> >>    it?  There must be a lot of Linuces at Python 3.5, even at the most
>> >>    recent distribution.  Was there by any chance a majority of conda
>> >>    users on the call?
>> >>    Cheers,
>> >>    Matthew
>> >>    _______________________________________________
>> >>    Matplotlib-devel mailing list
>> >>    Matplotlib-devel at python.org <mailto:Matplotlib-devel at python.org>
>> >>    https://mail.python.org/mailman/listinfo/matplotlib-devel
>> >> _______________________________________________
>> >> Matplotlib-devel mailing list
>> >> Matplotlib-devel at python.org
>> >> https://mail.python.org/mailman/listinfo/matplotlib-devel
>> >
>> > _______________________________________________
>> > Matplotlib-devel mailing list
>> > Matplotlib-devel at python.org
>> > https://mail.python.org/mailman/listinfo/matplotlib-devel
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180303/74e2254e/attachment.html>

From matthew.brett at gmail.com  Sat Mar  3 13:49:30 2018
From: matthew.brett at gmail.com (Matthew Brett)
Date: Sat, 3 Mar 2018 18:49:30 +0000
Subject: [Matplotlib-devel] What minimum version of python3?
In-Reply-To: <CAA48SF_Nhs=gk0fE1eYxiBkqAmdpgTTeaiCS=Lhj7_51X4qfFQ@mail.gmail.com>
References: <CAA48SF95n_ZFp2iECnwVwT6DSmGiS0SwGhAKvg8jXyadhPnLLA@mail.gmail.com>
 <CAH6Pt5rA8w35d+Z5S7cRmnrExwTvrUdRdMY=P8U7hfOfz4y44Q@mail.gmail.com>
 <CAJXewOmMdV9CBcNUdZjNP3cTdGE-CTjk7CvXKssbxBCjTgC5rw@mail.gmail.com>
 <d9fca711-60f2-1f46-00a3-7fd68f5d0af9@gmail.com>
 <CALGmxE+pQQppTpStZQeteyDcDjvfdu7q0u-CJxb5i1a1jk_ZXA@mail.gmail.com>
 <CAA48SF9ScjoZmWJrnk0DbsZ2e+_Lk5APNHFCarb1mRg2ZOP1GQ@mail.gmail.com>
 <CAA48SF_Nhs=gk0fE1eYxiBkqAmdpgTTeaiCS=Lhj7_51X4qfFQ@mail.gmail.com>
Message-ID: <CAH6Pt5qRAwOwR7ezMH8XWrOnVVakiSwgcL3hVcrQ57QpE65JgA@mail.gmail.com>

Hi,

On Sat, Mar 3, 2018 at 6:40 PM, Thomas Caswell <tcaswell at gmail.com> wrote:
> We discussed the minimum python again on the call this past week and settled
> on:
>
>  - support minor versions of python initially released in the previous 3
> years
>  - support minor versions of python initially released in the previous 3
> years or oldest that supports the minimum python version (which ever is
> higher)
>
> We will bump the minimum python an numpy versions as we can every minor and
> major release.
>
> We did not discuss other dependencies, but I propose:
>  - for system/c-dependencies (libpng, freetype, GUI frameworks, latex, gs,
> ffmpeg) support as old as practical
>  - for python dependencies with compiled extensions 3 years or the oldest
> that support our minimum python + numpy
>  - for python dependencies without complied extensions at least 2 years or
> the oldest that supports our minimum python.
>
> Bump these minimum versions as they no longer support our minimum python or
> we want to use new features in them.
>
> We should never bump minimum versions on a patch release.
>
> For mpl 3.0 (July 2018) this means python 3.5 (released Sept 2015) and numpy
> 1.10 (release in Oct 2015).  Python 3.4 was released Mar 2014 and  Numpy 1.9
> was released Sept 2014
>
> For mpl 3.1 (January 2019) this means python 3.6 (released Dec 2016) and
> numpy 1.11 (March 2016).

That seems very reasonable to me ...

Cheers,

Matthew

From tcaswell at gmail.com  Mon Mar  5 00:25:26 2018
From: tcaswell at gmail.com (Thomas Caswell)
Date: Mon, 05 Mar 2018 05:25:26 +0000
Subject: [Matplotlib-devel] ANN v2.2.0 is tagged
Message-ID: <CAA48SF9dYp48qWzaytbG=kA=fV3AXm5oxo9Co1N19SuqDVMGmA@mail.gmail.com>

Folks,

Just tagged 2.2.0!  Will sort out docs and binaries + wider
announcement tomorrow or Tuesday.

Big thank you to everyone who worked on this release!

Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180305/018d0aa8/attachment.html>

From tcaswell at gmail.com  Mon Mar  5 15:51:29 2018
From: tcaswell at gmail.com (Thomas Caswell)
Date: Mon, 05 Mar 2018 20:51:29 +0000
Subject: [Matplotlib-devel] Call notes from 2018-03-05
Message-ID: <CAA48SF-dLW74gZ8OrnfxwZofvkGpx6Vijp4vCdYzRFVfPee4dg@mail.gmail.com>

Tom, Hannah, Jody, Eric

 - Discussed backlog of PRs
 - Discussed projects for a summer students
   - units working with Ryan?
   - improve image comparison test
 - Discussed planning for documentation mini-workshop
   (notes from Hannah)
   - inventory of docs + more detailed plan of work
   - task: page or two plan of what the tasks would be for the docathon
     1) outline of what the documentation should be
     2) here's the 7things you want to do per domain
   - figuring out the user stories/narratives
   - more book like? cookbook vs narrative
   - expectation setting/transparency about what the library can do -
     sign post external libraries
   - clearer statement of matplotlib's purpose
   - price out hotels + travel + loop in james powell for food
   - who to invite
   - how it interact with BIDS
 - Discussed centralizing tight_bounding_box
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180305/e36167fa/attachment.html>

From tcaswell at gmail.com  Tue Mar  6 20:44:23 2018
From: tcaswell at gmail.com (Thomas Caswell)
Date: Wed, 07 Mar 2018 01:44:23 +0000
Subject: [Matplotlib-devel] ANN: Matplotlib 2.2.0 released
Message-ID: <CAA48SF-XfJ_S5S6Rmcn_brf83Q-fZjJqr+ut=Csncr_U_wAwuA@mail.gmail.com>

Folks,

We are happy to announce the release of Matplotlib 2.2.0!

The first release of the v2.2 LTS series and the last version of
Matplotlib to support python2.  There will be bug-fix release for this
series until 2020.

This release includes new features including:

 - An experimental constrained layout manager
 - Color blind friendly color map (cividis) and color cycle
   (tableau-colorblind10)
 - native support for numpy.datetime64 types
 - animated gif writing via pillow
 - TkAgg now works with pypy
 - cairo based backends for Qt, Tk, and WX

For full details see https://matplotlib.org/users/whats_new.html

There are several API changes in this release:

 - To support the constrained layout Matplotlib has a new required
   dependency (kiwisolver).
 - The `matplotlib.finance` module has been removed, development has
   moved to a stand-alone project.

For more details see https://matplotlib.org/api/api_changes.html

The next feature release of Matplotlib will be 3.0, targeted for July 2018
will support python 3.5+.

We are looking for a release manager for the 2.2.x series.

Thank you again to everyone (~100) people who helped to get the release
done and out the door!

Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180307/c23fb85e/attachment.html>

From tcaswell at gmail.com  Thu Mar  8 11:40:34 2018
From: tcaswell at gmail.com (Thomas Caswell)
Date: Thu, 08 Mar 2018 16:40:34 +0000
Subject: [Matplotlib-devel] 2.2 LTS backport policy
Message-ID: <CAA48SF8D_0vuhWb76k4XRqAKqQqfhNx2UQXh5Typ0E1t8tOp0Q@mail.gmail.com>

Folks,

I propose the following criteria for backporting PRs to the 2.2.x branch.
We always will backport

 - critical bug fixes (segfault, failure to import, things that the user
can not work around)
 - fixes for regressions against 2.0 or 2.1

Everything else (regressions against 1.x versions, bugs/api inconsistencies
the user can work around in their code) are on a case-by-case basis, should
be low-risk, and need someone to advocate for and shepherd through the
backport.

Thoughts?

Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180308/48a13545/attachment.html>

From pmhobson at gmail.com  Thu Mar  8 12:14:56 2018
From: pmhobson at gmail.com (Paul Hobson)
Date: Thu, 8 Mar 2018 09:14:56 -0800
Subject: [Matplotlib-devel] 2.2 LTS backport policy
In-Reply-To: <CAA48SF8D_0vuhWb76k4XRqAKqQqfhNx2UQXh5Typ0E1t8tOp0Q@mail.gmail.com>
References: <CAA48SF8D_0vuhWb76k4XRqAKqQqfhNx2UQXh5Typ0E1t8tOp0Q@mail.gmail.com>
Message-ID: <CADT3MEAx3H8MQaK+i_rsmBQTpAmnPes6ZsXcQ3tseQoJj6ERwQ@mail.gmail.com>

That's a sound approach, IMO.
-paul

On Thu, Mar 8, 2018 at 8:40 AM, Thomas Caswell <tcaswell at gmail.com> wrote:

> Folks,
>
> I propose the following criteria for backporting PRs to the 2.2.x branch.
> We always will backport
>
>  - critical bug fixes (segfault, failure to import, things that the user
> can not work around)
>  - fixes for regressions against 2.0 or 2.1
>
> Everything else (regressions against 1.x versions, bugs/api
> inconsistencies the user can work around in their code) are on a
> case-by-case basis, should be low-risk, and need someone to advocate for
> and shepherd through the backport.
>
> Thoughts?
>
> Tom
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180308/b89329e1/attachment.html>

From rmay31 at gmail.com  Thu Mar  8 13:17:45 2018
From: rmay31 at gmail.com (Ryan May)
Date: Thu, 8 Mar 2018 11:17:45 -0700
Subject: [Matplotlib-devel] 2.2 LTS backport policy
In-Reply-To: <CAA48SF8D_0vuhWb76k4XRqAKqQqfhNx2UQXh5Typ0E1t8tOp0Q@mail.gmail.com>
References: <CAA48SF8D_0vuhWb76k4XRqAKqQqfhNx2UQXh5Typ0E1t8tOp0Q@mail.gmail.com>
Message-ID: <CAKH0P+UOR-tgPBiBuM8FOsTyhgVZDs+w9BTPw84kZPxK6if3WA@mail.gmail.com>

Seems generally reasonable to me.

Ryan

On Thu, Mar 8, 2018 at 9:40 AM, Thomas Caswell <tcaswell at gmail.com> wrote:

> Folks,
>
> I propose the following criteria for backporting PRs to the 2.2.x branch.
> We always will backport
>
>  - critical bug fixes (segfault, failure to import, things that the user
> can not work around)
>  - fixes for regressions against 2.0 or 2.1
>
> Everything else (regressions against 1.x versions, bugs/api
> inconsistencies the user can work around in their code) are on a
> case-by-case basis, should be low-risk, and need someone to advocate for
> and shepherd through the backport.
>
> Thoughts?
>
> Tom
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>


-- 
Ryan May
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180308/bb48668e/attachment.html>

From swfiua at gmail.com  Fri Mar  9 12:08:33 2018
From: swfiua at gmail.com (swfiua at gmail.com)
Date: Fri, 9 Mar 2018 12:08:33 -0500
Subject: [Matplotlib-devel] py.test can't find ft2font
Message-ID: <CAO4m3c+_L20rvk5i5ttBBMzZPD7c7hchO60ridZBGeo5Hab3hg@mail.gmail.com>

I am trying to get tests passing again for this pull request:

https://github.com/matplotlib/matplotlib/pull/8325

They are failing due to differences in the images the latest code is
generating.

The tests themselves advise me to build with "local_freetype=True" in
setup.cfg  and I am doing this.

I am building/installing matplotlib with:

    python3.6 setup.py build

and

    python3.6 setup.py install --user

If I fire up python3.6 then

    from matplotlib import ft2font

works just fine.

But when I run py.test it fails to find it.

Curiously,

python3.6 -m matplotlib.ft2font

is also unable to find ft2font.

John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180309/f1bb69a8/attachment.html>

From swfiua at gmail.com  Fri Mar  9 14:00:38 2018
From: swfiua at gmail.com (swfiua at gmail.com)
Date: Fri, 9 Mar 2018 14:00:38 -0500
Subject: [Matplotlib-devel] py.test can't find ft2font
In-Reply-To: <CAO4m3c+_L20rvk5i5ttBBMzZPD7c7hchO60ridZBGeo5Hab3hg@mail.gmail.com>
References: <CAO4m3c+_L20rvk5i5ttBBMzZPD7c7hchO60ridZBGeo5Hab3hg@mail.gmail.com>
Message-ID: <CAO4m3cKFXp8rPkBhouOSBHBKKWOEG4xBstRgNWEE5e4BoC6X4A@mail.gmail.com>

Update:

Above should have read:

python3.6 setup.py develop --user

Installing with:

sudo pytthon3.6 setup.py develop

is running the tests ok.

On Fri, Mar 9, 2018 at 12:08 PM, swfiua at gmail.com <swfiua at gmail.com> wrote:

> I am trying to get tests passing again for this pull request:
>
> https://github.com/matplotlib/matplotlib/pull/8325
>
> They are failing due to differences in the images the latest code is
> generating.
>
> The tests themselves advise me to build with "local_freetype=True" in
> setup.cfg  and I am doing this.
>
> I am building/installing matplotlib with:
>
>     python3.6 setup.py build
>
> and
>
>     python3.6 setup.py install --user
>
> If I fire up python3.6 then
>
>     from matplotlib import ft2font
>
> works just fine.
>
> But when I run py.test it fails to find it.
>
> Curiously,
>
> python3.6 -m matplotlib.ft2font
>
> is also unable to find ft2font.
>
> John
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180309/e2aac6f4/attachment.html>

From phanikumar.ds at gmail.com  Mon Mar 12 09:19:18 2018
From: phanikumar.ds at gmail.com (Phani Kumar)
Date: Mon, 12 Mar 2018 18:49:18 +0530
Subject: [Matplotlib-devel] Need some help in 3D surface plotting...
Message-ID: <CAJTamcShgpgnXA2q6gpD4-Dyb7nsJUVVmFCBEo4F3QOop8A1jw@mail.gmail.com>

Hi All,

I am trying to 3D surface plot the data from a .csv file. there is already
a reference plot drawn with this data (seems it was done by some windows
app) and I am trying to do the same with linux (in fact on Raspberry Pi)
with matplot library.

I have attached the .csv file for reference.

Original plot (with some microsoft tool) is as below.

and when I plot the same data with matplotlib, the plot is as below.


Seems the plotting is ok, but for the layer of light orange patches - not
sure, what is causing this. My python code is as below. Let me know if you
have any suggestion for me.

from mpl_toolkits.mplot3d import Axes3D
import matplotlib
import matplotlib.pyplot as plt
from matplotlib import cm
from matplotlib.ticker import LinearLocator, FormatStrFormatter
import numpy as np
import csv

X = []
Y = []
Z = []

#Read the selected file
with open ('Plasma.csv', 'r') as csvfile:
plots = csv.reader (csvfile, delimiter=',')
for row in plots:
X.append(float(row[0]))
Y.append(float(row[1]))
Z.append(float(row[2]))

#Getting ready for the dispaly
fig = plt.figure()
ax = fig.gca(projection='3d')

#Set the labels...
ax.set_xlabel('X (mm)')
ax.set_ylabel('Y (mm)')
ax.set_zlabel('CPD (mV)')



#Setting the places properly...
tmp_planes = ax.zaxis._PLANES
ax.zaxis._PLANES = (tmp_planes[2], tmp_planes[3],
tmp_planes[0], tmp_planes[1],
tmp_planes[4],tmp_planes[5])

# Make data.
X, Y = np.meshgrid(X, Y)

#Plot
surf = ax.plot_surface(X, Y, Z, cmap=cm.coolwarm, linewidth=0)

plt.show()


With best regards,
Phani.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180312/c06ec568/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Plasma_PlotWithMatplotLib.jpg
Type: image/jpeg
Size: 65917 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180312/c06ec568/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Plasma_Original.jpg
Type: image/jpeg
Size: 153730 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180312/c06ec568/attachment-0003.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Plasma.csv
Type: application/vnd.ms-excel
Size: 3883 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180312/c06ec568/attachment-0001.xlb>

From vincent.adrien at gmail.com  Mon Mar 12 12:17:01 2018
From: vincent.adrien at gmail.com (vincent.adrien at gmail.com)
Date: Mon, 12 Mar 2018 09:17:01 -0700
Subject: [Matplotlib-devel] Need some help in 3D surface plotting...
In-Reply-To: <CAJTamcShgpgnXA2q6gpD4-Dyb7nsJUVVmFCBEo4F3QOop8A1jw@mail.gmail.com>
References: <CAJTamcShgpgnXA2q6gpD4-Dyb7nsJUVVmFCBEo4F3QOop8A1jw@mail.gmail.com>
Message-ID: <91239612-3353-a2fe-d77c-32a0d515333f@gmail.com>

Hi Phani,

Please find attached a modified version of your script that should help 
(hopefully). It produces the attached PNG. I think that your problem is 
how to reshape your data before feeding them to the 3d plotting routine.

Besides, I am no mplot3d expert, but I wonder if there would be a way to 
set the z-axis on the left **without** relying on private attributes 
(this is often very **not** future-proof as such features can be changed 
without warning in a future version of the library).

Best,
Adrien

On 03/12/2018 06:19 AM, Phani Kumar wrote:
> Hi All,
> 
> I am trying to 3D surface plot the data from a .csv file. there is 
> already a reference plot drawn with this data (seems it was done by some 
> windows app) and I am trying to do the same with linux (in fact on 
> Raspberry Pi) with matplot library.
> 
> I have attached the .csv file for reference.
> 
> Original plot (with some microsoft tool) is as below.
> 
> and when I plot the same data with matplotlib, the plot is as below.
> 
> 
> Seems the plotting is ok, but for the layer of light orange patches - 
> not sure, what is causing this. My python code is as below. Let me know 
> if you have any suggestion for me.
> 
> from mpl_toolkits.mplot3d import Axes3D
> import matplotlib
> import matplotlib.pyplot as plt
> from matplotlib import cm
> from matplotlib.ticker import LinearLocator, FormatStrFormatter
> import numpy as np
> import csv
> 
> X = []
> Y = []
> Z = []
> 
> #Read the selected file
> with open ('Plasma.csv', 'r') as csvfile:
> plots = csv.reader (csvfile, delimiter=',')
> for row in plots:
> X.append(float(row[0]))
> Y.append(float(row[1]))
> Z.append(float(row[2]))
> 
> #Getting ready for the dispaly
> fig = plt.figure()
> ax = fig.gca(projection='3d')
> 
> #Set the labels...
> ax.set_xlabel('X (mm)')
> ax.set_ylabel('Y (mm)')
> ax.set_zlabel('CPD (mV)')
> 
> 
> 
> #Setting the places properly...
> tmp_planes = ax.zaxis._PLANES
> ax.zaxis._PLANES = (tmp_planes[2], tmp_planes[3],
> tmp_planes[0], tmp_planes[1],
> tmp_planes[4],tmp_planes[5])
> 
> # Make data.
> X, Y = np.meshgrid(X, Y)
> 
> #Plot
> surf = ax.plot_surface(X, Y, Z, cmap=cm.coolwarm, linewidth=0)
> 
> plt.show()
> 
> 
> With best regards,
> Phani.
> 
> 
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: example.py
Type: text/x-python
Size: 1441 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180312/8a4bff35/attachment-0001.py>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plasma.png
Type: image/png
Size: 92856 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180312/8a4bff35/attachment-0001.png>

From antony.lee at berkeley.edu  Tue Mar 13 03:46:11 2018
From: antony.lee at berkeley.edu (Antony Lee)
Date: Tue, 13 Mar 2018 00:46:11 -0700
Subject: [Matplotlib-devel] mplcairo 0.1a1
Message-ID: <CAGRr6BE0TjEqXhe95XCfM_EWEdsGR0Mw0cKJZuZinqPhjf2yZg@mail.gmail.com>

Hi all,

I have just pushed a first pre-release of mplcairo to PyPI (
https://pypi.python.org/pypi/mplcairo).  As mentioned a few times on the
mailing list, it is a new Matplotlib backend based on the well-known cairo
library, supporting output to both raster (including interactively) and
vector formats.  In other words, it provides the functionality of
Matplotlib's {,qt5,gtk3,wx,tk,macos}agg, pdf, ps, and svg backends :-)  As
for any backend, use e.g. by calling
`matplotlib.use("module://mplcairo.qt")`, or setting your MPLBACKEND
environment variable to `module://mplcairo.qt`.  Please check the README
for additional information.

manylinux, osx, and windows wheels are available (3.6 only; may look into
older Python (3...) versions later).  On Linux and OSX, the wheels declare
a dependency on pycairo (which is how I get a handle onto libcairo); you
may want to get it e.g. from conda.  On Windows, the wheel includes cairo.

I am reasonably confident that the manylinux and windows wheels "work" (of
course, feedback is more than welcome), but would particularly appreciate
help regarding the OSX wheels.  Briefly speaking, for OSX, I have only
managed to coerce Travis to build a macos_10_12 wheel (corresponding to the
version from Homebrew, and apparently working with it), but conda's Python
only accepts wheels up to macos_10_9 (so basically conda's Python can't use
the wheels: you need to build mplcairo yourself); moreover, because it
appears impossible to statically link libc++ on OSX, mplcairo specifically
needs to be imported before matplotlib.  If you don't, mplcairo won't eat
your data, but may well segfault your process.  Any insight regarding the
intricacies of cross-version compatibility and/or dynamic loading on OSX
would be appreciated...

Enjoy (hopefully :-)),

Antony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180313/c75eed8b/attachment.html>

From phanikumar.ds at gmail.com  Tue Mar 13 06:49:50 2018
From: phanikumar.ds at gmail.com (phanids)
Date: Tue, 13 Mar 2018 03:49:50 -0700 (MST)
Subject: [Matplotlib-devel] Need some help in 3D surface plotting...
In-Reply-To: <91239612-3353-a2fe-d77c-32a0d515333f@gmail.com>
References: <CAJTamcShgpgnXA2q6gpD4-Dyb7nsJUVVmFCBEo4F3QOop8A1jw@mail.gmail.com>
 <91239612-3353-a2fe-d77c-32a0d515333f@gmail.com>
Message-ID: <1520938190585-0.post@n5.nabble.com>

Hi Adrien,

Thanks a lot. I tried your suggestion and initial got 

root at phani:/home/pi/SampleExample# python Trial1.py 
Traceback (most recent call last):
  File "Trial1.py", line 46, in <module>
    surf = ax.plot_surface(xx, yy, zz, cmap="inferno")
  File "/usr/lib/python2.7/dist-packages/mpl_toolkits/mplot3d/axes3d.py",
line 1637, in plot_surface
    polyc = art3d.Poly3DCollection(polys, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/mpl_toolkits/mplot3d/art3d.py",
line 476, in __init__
    PolyCollection.__init__(self, verts, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/matplotlib/collections.py", line
799, in __init__
    Collection.__init__(self, **kwargs)
  File "/usr/lib/python2.7/dist-packages/matplotlib/collections.py", line
107, in __init__
    cm.ScalarMappable.__init__(self, norm, cmap)
  File "/usr/lib/python2.7/dist-packages/matplotlib/cm.py", line 197, in
__init__
    self.cmap = get_cmap(cmap)
  File "/usr/lib/python2.7/dist-packages/matplotlib/cm.py", line 163, in
get_cmap
    % (name, ', '.join(cmap_d.keys())))
ValueError: Colormap inferno is not recognized. Possible values are:
Spectral, summer, coolwarm, Wistia_r, pink_r, Set1, Set2, Set3, brg_r,
Dark2, prism, PuOr_r, afmhot_r, terrain_r, PuBuGn_r, RdPu, gist_ncar_r,
gist_yarg_r, Dark2_r, YlGnBu, RdYlBu, hot_r, gist_rainbow_r, gist_stern,
PuBu_r, cool_r, cool, gray, copper_r, Greens_r, GnBu, gist_ncar, spring_r,
gist_rainbow, gist_heat_r, Wistia, OrRd_r, CMRmap, bone, gist_stern_r,
RdYlGn, Pastel2_r, spring, terrain, YlOrRd_r, Set2_r, winter_r, PuBu,
RdGy_r, spectral, rainbow, flag_r, jet_r, RdPu_r, gist_yarg, BuGn, Paired_r,
hsv_r, bwr, cubehelix, Greens, PRGn, gist_heat, spectral_r, Paired, hsv,
Oranges_r, prism_r, Pastel2, Pastel1_r, Pastel1, gray_r, jet, Spectral_r,
gnuplot2_r, gist_earth, YlGnBu_r, copper, gist_earth_r, Set3_r, OrRd,
gnuplot_r, ocean_r, brg, gnuplot2, PuRd_r, bone_r, BuPu, Oranges, RdYlGn_r,
PiYG, CMRmap_r, YlGn, binary_r, gist_gray_r, Accent, BuPu_r, gist_gray,
flag, bwr_r, RdBu_r, BrBG, Reds, Set1_r, summer_r, GnBu_r, BrBG_r, Reds_r,
RdGy, PuRd, Accent_r, Blues, autumn_r, autumn, cubehelix_r, nipy_spectral_r,
ocean, PRGn_r, Greys_r, pink, binary, winter, gnuplot, RdYlBu_r, hot,
YlOrBr, coolwarm_r, rainbow_r, Purples_r, PiYG_r, YlGn_r, Blues_r, YlOrBr_r,
seismic, Purples, seismic_r, RdBu, Greys, BuGn_r, YlOrRd, PuOr, PuBuGn,
nipy_spectral, afmhot
root at bitscope:/home/pi/SampleExample#

So I thought the color scheme "inferno" is not supported (or may be not
installed in my pi). So I changed it to "coolwarm" and I see the image as
below.

<http://matplotlib.1069221.n5.nabble.com/file/t5142/plasma.png> 

Though this is way better than my initial version, still I see only 2 color
combination... may be I need to check with color schemes provided in the
error message. 

Thanks a lot any way. Also let me know if you think any suitable color
scheme for this kind of gradient.

Will check with you on other technical questions after I finish this.

Thanks again,

With best regards,
Phani.



--
Sent from: http://matplotlib.1069221.n5.nabble.com/matplotlib-devel-f28077.html

From ben.v.root at gmail.com  Tue Mar 13 09:29:07 2018
From: ben.v.root at gmail.com (Benjamin Root)
Date: Tue, 13 Mar 2018 09:29:07 -0400
Subject: [Matplotlib-devel] Need some help in 3D surface plotting...
In-Reply-To: <1520938190585-0.post@n5.nabble.com>
References: <CAJTamcShgpgnXA2q6gpD4-Dyb7nsJUVVmFCBEo4F3QOop8A1jw@mail.gmail.com>
 <91239612-3353-a2fe-d77c-32a0d515333f@gmail.com>
 <1520938190585-0.post@n5.nabble.com>
Message-ID: <CANNq6Fk8B7smMtV0vwFbyh8tvCR3EoMFdr4JvHQ_g6eBk4bOYA@mail.gmail.com>

The error message means you have an old version of matplotlib. Inferno was
added in version 1.5. We are currently at verson 2.2.1 (supposedly will be
released today?). I would also wonder if your install of numpy is old as
well. Chances are, you are hitting on some old forgotten bug. Could you try
updating your packages?

On Tue, Mar 13, 2018 at 6:49 AM, phanids <phanikumar.ds at gmail.com> wrote:

> Hi Adrien,
>
> Thanks a lot. I tried your suggestion and initial got
>
> root at phani:/home/pi/SampleExample# python Trial1.py
> Traceback (most recent call last):
>   File "Trial1.py", line 46, in <module>
>     surf = ax.plot_surface(xx, yy, zz, cmap="inferno")
>   File "/usr/lib/python2.7/dist-packages/mpl_toolkits/mplot3d/axes3d.py",
> line 1637, in plot_surface
>     polyc = art3d.Poly3DCollection(polys, *args, **kwargs)
>   File "/usr/lib/python2.7/dist-packages/mpl_toolkits/mplot3d/art3d.py",
> line 476, in __init__
>     PolyCollection.__init__(self, verts, *args, **kwargs)
>   File "/usr/lib/python2.7/dist-packages/matplotlib/collections.py", line
> 799, in __init__
>     Collection.__init__(self, **kwargs)
>   File "/usr/lib/python2.7/dist-packages/matplotlib/collections.py", line
> 107, in __init__
>     cm.ScalarMappable.__init__(self, norm, cmap)
>   File "/usr/lib/python2.7/dist-packages/matplotlib/cm.py", line 197, in
> __init__
>     self.cmap = get_cmap(cmap)
>   File "/usr/lib/python2.7/dist-packages/matplotlib/cm.py", line 163, in
> get_cmap
>     % (name, ', '.join(cmap_d.keys())))
> ValueError: Colormap inferno is not recognized. Possible values are:
> Spectral, summer, coolwarm, Wistia_r, pink_r, Set1, Set2, Set3, brg_r,
> Dark2, prism, PuOr_r, afmhot_r, terrain_r, PuBuGn_r, RdPu, gist_ncar_r,
> gist_yarg_r, Dark2_r, YlGnBu, RdYlBu, hot_r, gist_rainbow_r, gist_stern,
> PuBu_r, cool_r, cool, gray, copper_r, Greens_r, GnBu, gist_ncar, spring_r,
> gist_rainbow, gist_heat_r, Wistia, OrRd_r, CMRmap, bone, gist_stern_r,
> RdYlGn, Pastel2_r, spring, terrain, YlOrRd_r, Set2_r, winter_r, PuBu,
> RdGy_r, spectral, rainbow, flag_r, jet_r, RdPu_r, gist_yarg, BuGn,
> Paired_r,
> hsv_r, bwr, cubehelix, Greens, PRGn, gist_heat, spectral_r, Paired, hsv,
> Oranges_r, prism_r, Pastel2, Pastel1_r, Pastel1, gray_r, jet, Spectral_r,
> gnuplot2_r, gist_earth, YlGnBu_r, copper, gist_earth_r, Set3_r, OrRd,
> gnuplot_r, ocean_r, brg, gnuplot2, PuRd_r, bone_r, BuPu, Oranges, RdYlGn_r,
> PiYG, CMRmap_r, YlGn, binary_r, gist_gray_r, Accent, BuPu_r, gist_gray,
> flag, bwr_r, RdBu_r, BrBG, Reds, Set1_r, summer_r, GnBu_r, BrBG_r, Reds_r,
> RdGy, PuRd, Accent_r, Blues, autumn_r, autumn, cubehelix_r,
> nipy_spectral_r,
> ocean, PRGn_r, Greys_r, pink, binary, winter, gnuplot, RdYlBu_r, hot,
> YlOrBr, coolwarm_r, rainbow_r, Purples_r, PiYG_r, YlGn_r, Blues_r,
> YlOrBr_r,
> seismic, Purples, seismic_r, RdBu, Greys, BuGn_r, YlOrRd, PuOr, PuBuGn,
> nipy_spectral, afmhot
> root at bitscope:/home/pi/SampleExample#
>
> So I thought the color scheme "inferno" is not supported (or may be not
> installed in my pi). So I changed it to "coolwarm" and I see the image as
> below.
>
> <http://matplotlib.1069221.n5.nabble.com/file/t5142/plasma.png>
>
> Though this is way better than my initial version, still I see only 2 color
> combination... may be I need to check with color schemes provided in the
> error message.
>
> Thanks a lot any way. Also let me know if you think any suitable color
> scheme for this kind of gradient.
>
> Will check with you on other technical questions after I finish this.
>
> Thanks again,
>
> With best regards,
> Phani.
>
>
>
> --
> Sent from: http://matplotlib.1069221.n5.nabble.com/matplotlib-devel-
> f28077.html
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180313/2e090603/attachment-0001.html>

From vincent.adrien at gmail.com  Tue Mar 13 11:16:44 2018
From: vincent.adrien at gmail.com (Adrien VINCENT)
Date: Tue, 13 Mar 2018 08:16:44 -0700
Subject: [Matplotlib-devel] Need some help in 3D surface plotting...
In-Reply-To: <CANNq6Fk8B7smMtV0vwFbyh8tvCR3EoMFdr4JvHQ_g6eBk4bOYA@mail.gmail.com>
References: <CAJTamcShgpgnXA2q6gpD4-Dyb7nsJUVVmFCBEo4F3QOop8A1jw@mail.gmail.com>
 <91239612-3353-a2fe-d77c-32a0d515333f@gmail.com>
 <1520938190585-0.post@n5.nabble.com>
 <CANNq6Fk8B7smMtV0vwFbyh8tvCR3EoMFdr4JvHQ_g6eBk4bOYA@mail.gmail.com>
Message-ID: <08361147-4645-4134-BAF2-14EC36B3383B@gmail.com>

Hi Phani,

I would make the same analysis and suggestion as Ben about the error that you got.

About the color map, any rather recent version of Matplotlib (let's say 1.5.3+ or 2+) should have a list of color maps close to the list here:
https://matplotlib.org/tutorials/colors/colormaps.html
A few of them may be missing if you are not using Matplotlib 2.2+, but that is really a few of them.

As your data seem to have only values of the same sign, I would advise for any sequential color scheme rather than a diverging one like "coolwarm" (except if the mid-range value has a very specific meaning that you would want to emphasize). The point of the "viridis" family? ("viridis", "inferno", "plasma", "magma", and recently "cividis") is to be perceptually uniform, which should thus be felt quite the same in color or gray scale printing, as well as by colorblind people.

Best,
Adrien


On March 13, 2018 6:29:07 AM PDT, Benjamin Root <ben.v.root at gmail.com> wrote:
>The error message means you have an old version of matplotlib. Inferno
>was
>added in version 1.5. We are currently at verson 2.2.1 (supposedly will
>be
>released today?). I would also wonder if your install of numpy is old
>as
>well. Chances are, you are hitting on some old forgotten bug. Could you
>try
>updating your packages?
>
>On Tue, Mar 13, 2018 at 6:49 AM, phanids <phanikumar.ds at gmail.com>
>wrote:
>
>> Hi Adrien,
>>
>> Thanks a lot. I tried your suggestion and initial got
>>
>> root at phani:/home/pi/SampleExample# python Trial1.py
>> Traceback (most recent call last):
>>   File "Trial1.py", line 46, in <module>
>>     surf = ax.plot_surface(xx, yy, zz, cmap="inferno")
>>   File
>"/usr/lib/python2.7/dist-packages/mpl_toolkits/mplot3d/axes3d.py",
>> line 1637, in plot_surface
>>     polyc = art3d.Poly3DCollection(polys, *args, **kwargs)
>>   File
>"/usr/lib/python2.7/dist-packages/mpl_toolkits/mplot3d/art3d.py",
>> line 476, in __init__
>>     PolyCollection.__init__(self, verts, *args, **kwargs)
>>   File "/usr/lib/python2.7/dist-packages/matplotlib/collections.py",
>line
>> 799, in __init__
>>     Collection.__init__(self, **kwargs)
>>   File "/usr/lib/python2.7/dist-packages/matplotlib/collections.py",
>line
>> 107, in __init__
>>     cm.ScalarMappable.__init__(self, norm, cmap)
>>   File "/usr/lib/python2.7/dist-packages/matplotlib/cm.py", line 197,
>in
>> __init__
>>     self.cmap = get_cmap(cmap)
>>   File "/usr/lib/python2.7/dist-packages/matplotlib/cm.py", line 163,
>in
>> get_cmap
>>     % (name, ', '.join(cmap_d.keys())))
>> ValueError: Colormap inferno is not recognized. Possible values are:
>> Spectral, summer, coolwarm, Wistia_r, pink_r, Set1, Set2, Set3,
>brg_r,
>> Dark2, prism, PuOr_r, afmhot_r, terrain_r, PuBuGn_r, RdPu,
>gist_ncar_r,
>> gist_yarg_r, Dark2_r, YlGnBu, RdYlBu, hot_r, gist_rainbow_r,
>gist_stern,
>> PuBu_r, cool_r, cool, gray, copper_r, Greens_r, GnBu, gist_ncar,
>spring_r,
>> gist_rainbow, gist_heat_r, Wistia, OrRd_r, CMRmap, bone,
>gist_stern_r,
>> RdYlGn, Pastel2_r, spring, terrain, YlOrRd_r, Set2_r, winter_r, PuBu,
>> RdGy_r, spectral, rainbow, flag_r, jet_r, RdPu_r, gist_yarg, BuGn,
>> Paired_r,
>> hsv_r, bwr, cubehelix, Greens, PRGn, gist_heat, spectral_r, Paired,
>hsv,
>> Oranges_r, prism_r, Pastel2, Pastel1_r, Pastel1, gray_r, jet,
>Spectral_r,
>> gnuplot2_r, gist_earth, YlGnBu_r, copper, gist_earth_r, Set3_r, OrRd,
>> gnuplot_r, ocean_r, brg, gnuplot2, PuRd_r, bone_r, BuPu, Oranges,
>RdYlGn_r,
>> PiYG, CMRmap_r, YlGn, binary_r, gist_gray_r, Accent, BuPu_r,
>gist_gray,
>> flag, bwr_r, RdBu_r, BrBG, Reds, Set1_r, summer_r, GnBu_r, BrBG_r,
>Reds_r,
>> RdGy, PuRd, Accent_r, Blues, autumn_r, autumn, cubehelix_r,
>> nipy_spectral_r,
>> ocean, PRGn_r, Greys_r, pink, binary, winter, gnuplot, RdYlBu_r, hot,
>> YlOrBr, coolwarm_r, rainbow_r, Purples_r, PiYG_r, YlGn_r, Blues_r,
>> YlOrBr_r,
>> seismic, Purples, seismic_r, RdBu, Greys, BuGn_r, YlOrRd, PuOr,
>PuBuGn,
>> nipy_spectral, afmhot
>> root at bitscope:/home/pi/SampleExample#
>>
>> So I thought the color scheme "inferno" is not supported (or may be
>not
>> installed in my pi). So I changed it to "coolwarm" and I see the
>image as
>> below.
>>
>> <http://matplotlib.1069221.n5.nabble.com/file/t5142/plasma.png>
>>
>> Though this is way better than my initial version, still I see only 2
>color
>> combination... may be I need to check with color schemes provided in
>the
>> error message.
>>
>> Thanks a lot any way. Also let me know if you think any suitable
>color
>> scheme for this kind of gradient.
>>
>> Will check with you on other technical questions after I finish this.
>>
>> Thanks again,
>>
>> With best regards,
>> Phani.
>>
>>
>>
>> --
>> Sent from: http://matplotlib.1069221.n5.nabble.com/matplotlib-devel-
>> f28077.html
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>

-- 
Envoy? de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma bri?vet?.

From phanikumar.ds at gmail.com  Thu Mar 15 05:54:42 2018
From: phanikumar.ds at gmail.com (phanids)
Date: Thu, 15 Mar 2018 02:54:42 -0700 (MST)
Subject: [Matplotlib-devel] Need some help in 3D surface plotting...
In-Reply-To: <08361147-4645-4134-BAF2-14EC36B3383B@gmail.com>
References: <CAJTamcShgpgnXA2q6gpD4-Dyb7nsJUVVmFCBEo4F3QOop8A1jw@mail.gmail.com>
 <91239612-3353-a2fe-d77c-32a0d515333f@gmail.com>
 <1520938190585-0.post@n5.nabble.com>
 <CANNq6Fk8B7smMtV0vwFbyh8tvCR3EoMFdr4JvHQ_g6eBk4bOYA@mail.gmail.com>
 <08361147-4645-4134-BAF2-14EC36B3383B@gmail.com>
Message-ID: <1521107682706-0.post@n5.nabble.com>

Hi Benjamin, Adrien,

You guys are awesome !!!

//Earlier versions
root at phani:/home/pi/SampleExample# python -c 'import matplotlib; print
matplotlib.__version__'
*1.4.2 *

root at phani:/home/pi/SampleExample# python -c "import numpy; print
(numpy.__version__)"
*1.8.2*

did *python -mpip install -U matplotlib* for update and then 

root at phani:/home/pi/SampleExample# python -c 'import matplotlib; print
matplotlib.__version__'
*2.2.0*

root at phani:/home/pi/SampleExample# python -c "import numpy; print
(numpy.__version__)"
*1.14.2*

But when I run it, I get below warning message... 

root at phani:/home/pi/SampleExample# python Trial1.py

*/usr/local/lib/python2.7/dist-packages/matplotlib/backends/backend_gtk3.py:181:
Warning: Source ID 7 was not found when attempting to remove it
  GLib.source_remove(self._idle_draw_id)*

1. Still the plotting happens (attached). Googling says there is nothing to
worry about the warning. Do you have any suggestion for me? 

2. Is there any way I can set the grid color to light blue (as in the
original image)? May be it helps in better highlighting the plot (than which
is currently white).

3. In original image, also there is a "shade" of the plot on X - axis. Is
there any way we can get the shade? Basically it would help to find the
range more exactly as the X-Axis would have the scale.

4. This python script, I am calling from QT. Is there any way, I can call
matplotlib libraries from QT itself? 

Thanks a lot,

With best regards,
Phani.

<http://matplotlib.1069221.n5.nabble.com/file/t5142/plasma.png> 



--
Sent from: http://matplotlib.1069221.n5.nabble.com/matplotlib-devel-f28077.html

From vincent.adrien at gmail.com  Thu Mar 15 15:38:06 2018
From: vincent.adrien at gmail.com (vincent.adrien at gmail.com)
Date: Thu, 15 Mar 2018 12:38:06 -0700
Subject: [Matplotlib-devel] Need some help in 3D surface plotting...
In-Reply-To: <1521107682706-0.post@n5.nabble.com>
References: <CAJTamcShgpgnXA2q6gpD4-Dyb7nsJUVVmFCBEo4F3QOop8A1jw@mail.gmail.com>
 <91239612-3353-a2fe-d77c-32a0d515333f@gmail.com>
 <1520938190585-0.post@n5.nabble.com>
 <CANNq6Fk8B7smMtV0vwFbyh8tvCR3EoMFdr4JvHQ_g6eBk4bOYA@mail.gmail.com>
 <08361147-4645-4134-BAF2-14EC36B3383B@gmail.com>
 <1521107682706-0.post@n5.nabble.com>
Message-ID: <ee47fb4d-e589-0ef9-a327-cbdbbd35e290@gmail.com>

Hi Phani,

1. The warning may be simply related to the backend that you are using. 
You could give a shot to other backends if there are avalaible on your 
setup. See for example the lines:
```python
mpl.use("Qt5Agg")  # or TkAgg or any other available backend
import matplotlib.pyplot as plt
```
at the top in the attached file `example_v2.png`.

2. For the edge line color, please have a look at the call of 
`ax.plot_surface` in that script. You can indeed pass keyword arguments 
like "edgecolor" or "linewidth".

3. I am not sure of what you mean about the shade on the x-axis.

4. I am out of my depth there :/.

Also I realized that the trick to pin the z-axis labels onto the left 
side produces weird grid lines for that axis. Maybe Ben would have a 
better solution (i.e. a real one...), but in the meantime, I suggested 
another workaround in the script, which leads to the attached PNG.

Best,
Adrien


On 03/15/2018 02:54 AM, phanids wrote:
> Hi Benjamin, Adrien,
> 
> You guys are awesome !!!
> 
> //Earlier versions
> root at phani:/home/pi/SampleExample# python -c 'import matplotlib; print
> matplotlib.__version__'
> *1.4.2 *
> 
> root at phani:/home/pi/SampleExample# python -c "import numpy; print
> (numpy.__version__)"
> *1.8.2*
> 
> did *python -mpip install -U matplotlib* for update and then
> 
> root at phani:/home/pi/SampleExample# python -c 'import matplotlib; print
> matplotlib.__version__'
> *2.2.0*
> 
> root at phani:/home/pi/SampleExample# python -c "import numpy; print
> (numpy.__version__)"
> *1.14.2*
> 
> But when I run it, I get below warning message...
> 
> root at phani:/home/pi/SampleExample# python Trial1.py
> 
> */usr/local/lib/python2.7/dist-packages/matplotlib/backends/backend_gtk3.py:181:
> Warning: Source ID 7 was not found when attempting to remove it
>    GLib.source_remove(self._idle_draw_id)*
> 
> 1. Still the plotting happens (attached). Googling says there is nothing to
> worry about the warning. Do you have any suggestion for me?
> 
> 2. Is there any way I can set the grid color to light blue (as in the
> original image)? May be it helps in better highlighting the plot (than which
> is currently white).
> 
> 3. In original image, also there is a "shade" of the plot on X - axis. Is
> there any way we can get the shade? Basically it would help to find the
> range more exactly as the X-Axis would have the scale.
> 
> 4. This python script, I am calling from QT. Is there any way, I can call
> matplotlib libraries from QT itself?
> 
> Thanks a lot,
> 
> With best regards,
> Phani.
> 
> <http://matplotlib.1069221.n5.nabble.com/file/t5142/plasma.png>
> 
> 
> 
> --
> Sent from: http://matplotlib.1069221.n5.nabble.com/matplotlib-devel-f28077.html
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: example_v2.py
Type: text/x-python
Size: 2083 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180315/bc947e56/attachment-0001.py>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plasma_v2.png
Type: image/png
Size: 114724 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180315/bc947e56/attachment-0001.png>

From marcidy at gmail.com  Fri Mar 16 05:15:24 2018
From: marcidy at gmail.com (Matt Arcidy)
Date: Fri, 16 Mar 2018 02:15:24 -0700
Subject: [Matplotlib-devel] Documentation
In-Reply-To: <CA+U3c5bEp4ugapfGNLWynb6f2SLJ_vgXPnOYfcqGzV6-=OuYvw@mail.gmail.com>
References: <CA+U3c5bSqOCK4T2Lx_XNc5qZMfm_NTokz7+xXrEhYO3jpGD42g@mail.gmail.com>
 <CAOuQ7j12+-kdSJNLAZrq69OuyYo-X+Zhhxpjd8BYM47OAobJyg@mail.gmail.com>
 <CA+U3c5asR__sYg=+jGhbN5JfzHgZmYgzUaCYCQnNmmz-UiOi=g@mail.gmail.com>
 <CAOuQ7j0pOXzt-djRm1-JbAi6N+D4_qE0SC4ZigdAUi_hcda1xw@mail.gmail.com>
 <CALGmxEJ7aV8rk9Mj2aVr_M=QOfqd7PqO9JpzD-q1wOyOMaZnrQ@mail.gmail.com>
 <CAOuQ7j2EG_Bz=8Lb=iA5eNUG9aefZmRp27DpviGAhJkHp8U8mg@mail.gmail.com>
 <CALGmxE+SQJvvUTmV5Rj6c_VarsECEAj0qbKGq=EdzZoWha04BA@mail.gmail.com>
 <CA+U3c5bggXp3H5sCgFq4SfPCb8KNN_q6kx=g=iS-vsRb8bo6VQ@mail.gmail.com>
 <CALGmxE+au7pg79wRj9noqVYhwk4kPUvk5JaJic8kcY=NEc8SJA@mail.gmail.com>
 <CAOuQ7j2hQ_CqerqdOZ=ofmnm1XkruK1Jv8HNUGvB5NKVHdEg+g@mail.gmail.com>
 <CA+U3c5bEp4ugapfGNLWynb6f2SLJ_vgXPnOYfcqGzV6-=OuYvw@mail.gmail.com>
Message-ID: <CA+U3c5Ze2G0cLT8WWdb7aBvO0ZcpO6U99ZhKjPmOMpdYVij4PQ@mail.gmail.com>

Hi all,

Sorry for the long wait, but I have some results to show.

Attached is programmatically generated ranking of  the examples based
on python complexity.

It was done by using the ast module to get every  statement, then each
file was ranked by a method I completely made up, but that can fit
whatever need we have.

It's very basic analysis compared to what is possible, so the ranking
here aren't perfect by any means.  I have not included ranking
matplotlib difficulty as that will require expert input.  As a funny
example,  contour3d.py comes up as one of the easiest tutorials.
That's because the code is easy., the concepts are much harder.
Ranking the mpl objects will provide a much richer and more useful
output.  And of course any dimension we think of can be ranked.

I'm not sure if this _output_ is useful as much as it's a proof of
concept.  But the examples do rank by python complexity now, so that's
good.  I included the ranking algorithm (ranking.py) to show how it
works and what is possible.  I'm doing really naive things like
existence and counts, but even that works to a degree.

There is plenty more information to use that is not in this run: class
inheritance, statement complexity (e.g. # of nested statements in one
expression), number lines of code, number of imports, etc.  many
things are available to use as factors.

Once the ranking is good, creating learning paths can be done,
allowing people to learn python in tandem to mpl, by creating paths
that introduce only 1 or 2 new items, be it a new arg to pyplot or an
object relatively close to another one in an inheritance tree.
Anything that can be programmatically found.  Or perhaps gaps will be
found as well.

And likewise, I can pull out any symbol to use as a search term or a
tag.  I can detect if they are from matplotlib package, or an external
package, and a list probably needs to be maintained to keep track of
what is considered complex and why, but that's a small price I think.

Feedfback?

More than happy to talk anyone's head off about it but I would like to
know if this is useful, and if so, what direction to take first, and
get it focused on specific tasks, etc..


as a note:
This can be used for much more, as I built it to do deep inspection
for other tasks mentioned.  For example, it can be used to look into
doc strings and check that all arguments of the function are in the
doc string.  It can go even further to look at the function body and
see if any arguments are consumed as literals, and then check if those
literals are mentioned in the docs.  And that can all be traced
through any call or attribute assignment (even dict keys, slicing,
etc) and trace things back to an entry point.  Entry point being a
script or scanning the whole package.  At this stage i have the core
functionality to do that, but those functions need to be built.

I also need to write tests and documentation (ha).  And I called it
doctor_doctor which is highly subject to change.


On Tue, Feb 13, 2018 at 4:20 PM, Matt Arcidy <marcidy at gmail.com> wrote:
> I will add args inspection to my Sphinx hacking.  That will also let me
> discriminate functions calls by tutorial/example as well, plus add that info
> to search parameters.  plt.plot() usage in examples will greatly benefit
> from this.
>
> On Tue, Feb 13, 2018, 15:24 Hannah <story645 at gmail.com> wrote:
>>
>>
>>> For instance, the first time a keyword argument is used, a link to a
>>> brief tutorial on keyword arguments. If people want to know more, they
>>> follow that link -- if they already understand kw args, then then skip on
>>> by...
>>
>>
>> I think this approach has a good balance of not reinventing the wheel
>> while also sign posting,
>>
>> And Matt, I think  creating a narrative of this is a figure, on a figure
>> we put axes, could probably go a ways towards helping with the "why?" of it
>> all.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ranking.py
Type: text/x-python
Size: 4277 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180316/2b4df5a7/attachment-0001.py>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rankings-test.csv
Type: text/csv
Size: 17333 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180316/2b4df5a7/attachment-0001.csv>

From tcaswell at gmail.com  Fri Mar 16 23:22:26 2018
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sat, 17 Mar 2018 03:22:26 +0000
Subject: [Matplotlib-devel] Matplotlib v2.2.2 tagged
Message-ID: <CAA48SF9V+1KsbtiHqKtNrBfDRED455c74sBnFnP8a8=nhg895g@mail.gmail.com>

Folks,

We tagged v2.2.2 (and v2.2.1) today, will rebulid the docs and make broader
announcement once wheels are up.

REL: v2.2.2 LTS

The second bug-fix release of the v2.2 LTS series.

This release fixes a number of critical bugs from 2.2.0:

 - restores matplotlib.verbose (fixing embedding in pycharm)
 - preserve precision when color mapping small portions of data with
   extreme outliers
 - fixes saving long movies with ffmpeg
 - fixes UnbourdLocal error in contour labeling
 - fixes import failure on python 3.4.0 and 3.4.1
 - fixes compile time failures with clang on 32bit platforms
 - fixes an icon in the Tk backends
 - fixes several issues with Tables
 - fixes expanding offset boxes with tight_layout
 - revert changes to the font caching to avoid a possible bug in
   backports.lru_cache
 - numerous docstring and documentation fixes

We have reverted the deprecation of `font_manager.TempCache`.

Due to an oversight v2.2.1 did not actually fix the first bullet point
which we caught after we pushed the tag, but before uploading to pypi.  At
this point I do not think we should upload / officially release v2.2.1.

Thank you to everyone who worked on this release to fix the inevitable
X.X.0 release bugs promptly!

Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180317/2dfdcc1d/attachment.html>

From tcaswell at gmail.com  Sat Mar 17 14:24:26 2018
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sat, 17 Mar 2018 18:24:26 +0000
Subject: [Matplotlib-devel] [REL] Matplotlib 2.2.2
Message-ID: <CAA48SF-76Yr3At=CaEnkjhNvjb+UpiOznfax=YPn=PjgcmkMww@mail.gmail.com>

Folks,

Happy to announce Matplotlib 2.2.2, the second bug-fix release of the v2.2
LTS series.

This release fixes a number of critical bugs from 2.2.0:

 - restores matplotlib.verbose (fixing embedding in pycharm)
 - preserve precision when color mapping small portions of data with
   extreme outliers
 - fixes saving long movies with ffmpeg
 - fixes UnbourdLocal error in contour labeling
 - fixes import failure on python 3.4.0 and 3.4.1
 - fixes compile time failures with clang on 32bit platforms
 - fixes an icon in the Tk backends
 - fixes several issues with Tables
 - fixes expanding offset boxes with tight_layout
 - revert changes to the font caching to avoid a possible bug in
   backports.lru_cache
 - numerous docstring and documentation fixes

We have reverted the deprecation of `font_manager.TempCache`.

Thank you to everyone who submitted bug reports and worked on this!

v2.2.1 is tagged, but we do not plan to release / publish to pypi.

Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180317/5b573559/attachment.html>

From tcaswell at gmail.com  Sat Mar 17 19:11:00 2018
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sat, 17 Mar 2018 23:11:00 +0000
Subject: [Matplotlib-devel] 2.2 LTS backport policy
In-Reply-To: <CAKH0P+UOR-tgPBiBuM8FOsTyhgVZDs+w9BTPw84kZPxK6if3WA@mail.gmail.com>
References: <CAA48SF8D_0vuhWb76k4XRqAKqQqfhNx2UQXh5Typ0E1t8tOp0Q@mail.gmail.com>
 <CAKH0P+UOR-tgPBiBuM8FOsTyhgVZDs+w9BTPw84kZPxK6if3WA@mail.gmail.com>
Message-ID: <CAA48SF9ZTG7ju4mvb4QgW=AtSxfPs=qs0k0Ps3ofXqLFWbWeHw@mail.gmail.com>

Put this into a PR to get it into the docs
https://github.com/matplotlib/matplotlib/pull/10822

Tom

On Thu, Mar 8, 2018 at 1:18 PM Ryan May <rmay31 at gmail.com> wrote:

> Seems generally reasonable to me.
>
> Ryan
>
> On Thu, Mar 8, 2018 at 9:40 AM, Thomas Caswell <tcaswell at gmail.com> wrote:
>
>> Folks,
>>
>> I propose the following criteria for backporting PRs to the 2.2.x
>> branch.  We always will backport
>>
>>  - critical bug fixes (segfault, failure to import, things that the user
>> can not work around)
>>  - fixes for regressions against 2.0 or 2.1
>>
>> Everything else (regressions against 1.x versions, bugs/api
>> inconsistencies the user can work around in their code) are on a
>> case-by-case basis, should be low-risk, and need someone to advocate for
>> and shepherd through the backport.
>>
>> Thoughts?
>>
>> Tom
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>>
>
>
> --
> Ryan May
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180317/cf7570ba/attachment.html>

From tcaswell at gmail.com  Sat Mar 17 19:36:16 2018
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sat, 17 Mar 2018 23:36:16 +0000
Subject: [Matplotlib-devel] What minimum version of python3?
In-Reply-To: <CAH6Pt5qRAwOwR7ezMH8XWrOnVVakiSwgcL3hVcrQ57QpE65JgA@mail.gmail.com>
References: <CAA48SF95n_ZFp2iECnwVwT6DSmGiS0SwGhAKvg8jXyadhPnLLA@mail.gmail.com>
 <CAH6Pt5rA8w35d+Z5S7cRmnrExwTvrUdRdMY=P8U7hfOfz4y44Q@mail.gmail.com>
 <CAJXewOmMdV9CBcNUdZjNP3cTdGE-CTjk7CvXKssbxBCjTgC5rw@mail.gmail.com>
 <d9fca711-60f2-1f46-00a3-7fd68f5d0af9@gmail.com>
 <CALGmxE+pQQppTpStZQeteyDcDjvfdu7q0u-CJxb5i1a1jk_ZXA@mail.gmail.com>
 <CAA48SF9ScjoZmWJrnk0DbsZ2e+_Lk5APNHFCarb1mRg2ZOP1GQ@mail.gmail.com>
 <CAA48SF_Nhs=gk0fE1eYxiBkqAmdpgTTeaiCS=Lhj7_51X4qfFQ@mail.gmail.com>
 <CAH6Pt5qRAwOwR7ezMH8XWrOnVVakiSwgcL3hVcrQ57QpE65JgA@mail.gmail.com>
Message-ID: <CAA48SF-BA11opp9jcYYOxjcu2rXOtmT+BHYLiHeE9ZUNeR2qKg@mail.gmail.com>

Put this into the docs via
https://github.com/matplotlib/matplotlib/pull/10824

Tom

On Sat, Mar 3, 2018 at 1:50 PM Matthew Brett <matthew.brett at gmail.com>
wrote:

> Hi,
>
> On Sat, Mar 3, 2018 at 6:40 PM, Thomas Caswell <tcaswell at gmail.com> wrote:
> > We discussed the minimum python again on the call this past week and
> settled
> > on:
> >
> >  - support minor versions of python initially released in the previous 3
> > years
> >  - support minor versions of python initially released in the previous 3
> > years or oldest that supports the minimum python version (which ever is
> > higher)
> >
> > We will bump the minimum python an numpy versions as we can every minor
> and
> > major release.
> >
> > We did not discuss other dependencies, but I propose:
> >  - for system/c-dependencies (libpng, freetype, GUI frameworks, latex,
> gs,
> > ffmpeg) support as old as practical
> >  - for python dependencies with compiled extensions 3 years or the oldest
> > that support our minimum python + numpy
> >  - for python dependencies without complied extensions at least 2 years
> or
> > the oldest that supports our minimum python.
> >
> > Bump these minimum versions as they no longer support our minimum python
> or
> > we want to use new features in them.
> >
> > We should never bump minimum versions on a patch release.
> >
> > For mpl 3.0 (July 2018) this means python 3.5 (released Sept 2015) and
> numpy
> > 1.10 (release in Oct 2015).  Python 3.4 was released Mar 2014 and  Numpy
> 1.9
> > was released Sept 2014
> >
> > For mpl 3.1 (January 2019) this means python 3.6 (released Dec 2016) and
> > numpy 1.11 (March 2016).
>
> That seems very reasonable to me ...
>
> Cheers,
>
> Matthew
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180317/0d994051/attachment.html>

From tcaswell at gmail.com  Mon Mar 19 17:43:35 2018
From: tcaswell at gmail.com (Thomas Caswell)
Date: Mon, 19 Mar 2018 21:43:35 +0000
Subject: [Matplotlib-devel] note from 2018-03-19 call
Message-ID: <CAA48SF8fy0cJCywdke+UGo9Bk1wKxc2dn7sN7jXEp6MMab6nVA@mail.gmail.com>

Folks,

On call, myself, Eric, Jody, Hannah, Ryan, and Antony.


Units:
 - Ryan taking a summer student is heavy lift
 - Ryan OK with BDFL-designate for units work

2.2.2 is out!

Discussion of colorbar overhaul
 - big improvement, minor tweaks on log formatter minor ticks

Discussion of rcparams overhaul
 - move to using python's import mechanism
 - cwd import already wins
 - use python's 'user install' to do user-level config
   - this is messier than we would hope
   - but can use `site.USER_SITE` to get the right path
   - can provide helper function to install template
 - install to env / system level for global
 - users can hack PYTHONPATH to put where ever they want
 - can gracefully decay to use existing system on failure to import
   - go though no warning -> warn -> break cycle over 2 years
 - module must provide function "apply_style(rc : RCParameters): -> None"
 - styles would work the same way
 - security concerns pushed back to "arbitrary code execution allows
   arbitrary code execution", if attacker can put this in the path,
   then they can modify other files in path.

Summer Student:
 - proposed projects
   - write altair data structure -> Matplotlib plot
     - Hannah (primary) and Tom (backup) can mentor, try to reach out to
Brian and Jake
 - details
   - 6k for 10 weeks
   - work from home remote
   - only take one student
 - Questions for NF
   - can we pay international students?
   - what is eligibility requirements on student?
     - familiar with matplotlib, pandas, jupyter notebooks,
       python/scipy in general
     - plus if have used declarative plotting
   - what level of reporting do you want?
   - sort out how / where to advertise?
 - rejected projects
   - Text / testing
     - sort out a way to make our tests independent of freetype version
     - freetype is already working on this
     - lots of discussion about different approaches to this
     - mentors?
 - TODO
   - write a statement of work
     - first goal is basic encoding
     - second goal is transforms
     - third goal is interactivity

Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180319/f7dac890/attachment.html>

From jklymak at uvic.ca  Mon Mar 26 16:37:30 2018
From: jklymak at uvic.ca (Jody Klymak)
Date: Mon, 26 Mar 2018 13:37:30 -0700
Subject: [Matplotlib-devel] Call Notes 26 Mar
Message-ID: <E4694DD9-9DDA-411E-B0EF-F7812AF0712F@uvic.ca>


Hi all,

Call notes are online at https://paper.dropbox.com/doc/Matplotlib-meeting-agenda-aAmENlkgepgsMeDZtlsYu

Folks are welcome to take a look and add items for next week?s agenda (if there is an Easter Monday meeting).  If the file doesn?t get too unwieldly, there was general agreement that Paper was a decent way to keep notes and an agenda, at least for now.

Cheers,   Jody

Notes: 26 Mar 2018

		? Antony, Hannah, Ryan, Jody
Ticks
		? issues with extra ticks outside viewlims.  Antony said they were due to roundoff errors.
		? maybe trim at Locator level. 
		? deprecate not visible:  
			? ticker.Locator would all need to change
			? deprecate out of range ticks first, and then expect proper list
			? epsilon out of viewlims?  Keep those.  
		? ticks and lines top and bottom: individual lines for each ticks.  
			? overhaul, single line for top and bottom ticks.  LineCollection for grids.
			? back compatibility?  Custom Axes subclass with new Axis subclass?.
			? each line call is slow (units support).
			? speed benefit? 
			? can?t manipulate individual tick visibility.  
Datetime formatting:
		? https://github.com/matplotlib/matplotlib/pull/10841
		? https://github.com/matplotlib/matplotlib/pull/9801
		? General agreement locator
		? General agreement formatter:
			? needs way to get old beghaviour
			? useful for teaching/default
		? @Antony L suggested naming convention
			? MPLxyDateFormatter
			? Alias AutoFormatter to current MPLXYDateFormatter
			? Document ?We reserve right to change formatter?
		? deprecate old linear scalar formatter? 
		? localization of month
			? Check if way?  

To merge:
	?  https://github.com/matplotlib/matplotlib/pull/10314
	?  https://github.com/matplotlib/matplotlib/pull/10158

--
Jody Klymak    
http://web.uvic.ca/~jklymak/