You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(33) |
Dec
(20) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(7) |
Feb
(44) |
Mar
(51) |
Apr
(43) |
May
(43) |
Jun
(36) |
Jul
(61) |
Aug
(44) |
Sep
(25) |
Oct
(82) |
Nov
(97) |
Dec
(47) |
2005 |
Jan
(77) |
Feb
(143) |
Mar
(42) |
Apr
(31) |
May
(93) |
Jun
(93) |
Jul
(35) |
Aug
(78) |
Sep
(56) |
Oct
(44) |
Nov
(72) |
Dec
(75) |
2006 |
Jan
(116) |
Feb
(99) |
Mar
(181) |
Apr
(171) |
May
(112) |
Jun
(86) |
Jul
(91) |
Aug
(111) |
Sep
(77) |
Oct
(72) |
Nov
(57) |
Dec
(51) |
2007 |
Jan
(64) |
Feb
(116) |
Mar
(70) |
Apr
(74) |
May
(53) |
Jun
(40) |
Jul
(519) |
Aug
(151) |
Sep
(132) |
Oct
(74) |
Nov
(282) |
Dec
(190) |
2008 |
Jan
(141) |
Feb
(67) |
Mar
(69) |
Apr
(96) |
May
(227) |
Jun
(404) |
Jul
(399) |
Aug
(96) |
Sep
(120) |
Oct
(205) |
Nov
(126) |
Dec
(261) |
2009 |
Jan
(136) |
Feb
(136) |
Mar
(119) |
Apr
(124) |
May
(155) |
Jun
(98) |
Jul
(136) |
Aug
(292) |
Sep
(174) |
Oct
(126) |
Nov
(126) |
Dec
(79) |
2010 |
Jan
(109) |
Feb
(83) |
Mar
(139) |
Apr
(91) |
May
(79) |
Jun
(164) |
Jul
(184) |
Aug
(146) |
Sep
(163) |
Oct
(128) |
Nov
(70) |
Dec
(73) |
2011 |
Jan
(235) |
Feb
(165) |
Mar
(147) |
Apr
(86) |
May
(74) |
Jun
(118) |
Jul
(65) |
Aug
(75) |
Sep
(162) |
Oct
(94) |
Nov
(48) |
Dec
(44) |
2012 |
Jan
(49) |
Feb
(40) |
Mar
(88) |
Apr
(35) |
May
(52) |
Jun
(69) |
Jul
(90) |
Aug
(123) |
Sep
(112) |
Oct
(120) |
Nov
(105) |
Dec
(116) |
2013 |
Jan
(76) |
Feb
(26) |
Mar
(78) |
Apr
(43) |
May
(61) |
Jun
(53) |
Jul
(147) |
Aug
(85) |
Sep
(83) |
Oct
(122) |
Nov
(18) |
Dec
(27) |
2014 |
Jan
(58) |
Feb
(25) |
Mar
(49) |
Apr
(17) |
May
(29) |
Jun
(39) |
Jul
(53) |
Aug
(52) |
Sep
(35) |
Oct
(47) |
Nov
(110) |
Dec
(27) |
2015 |
Jan
(50) |
Feb
(93) |
Mar
(96) |
Apr
(30) |
May
(55) |
Jun
(83) |
Jul
(44) |
Aug
(8) |
Sep
(5) |
Oct
|
Nov
(1) |
Dec
(1) |
2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(3) |
Sep
(1) |
Oct
(3) |
Nov
|
Dec
|
2017 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
(7) |
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
|
|
|
|
|
1
(1) |
2
|
3
(3) |
4
(2) |
5
(4) |
6
|
7
(5) |
8
|
9
(4) |
10
(8) |
11
|
12
(5) |
13
(4) |
14
(3) |
15
|
16
(1) |
17
(10) |
18
(3) |
19
(2) |
20
(10) |
21
(9) |
22
(4) |
23
|
24
(12) |
25
(2) |
26
(3) |
27
(8) |
28
(2) |
29
(4) |
30
(3) |
|
|
|
|
|
|
On Mon, Sep 24, 2012 at 7:23 PM, Russell E. Owen <ro...@uw...> wrote: > In article <506...@st...>, > Michael Droettboom <md...@st...> > wrote: > >> For the compilation problem, I am no Objective-C expert, but in C, line >> 3557 should certainly read: >> >> NSSize pxlSize = NSMakeSize(rep->pixelsWide, rep->pixelsHigh); >> >> I wonder if that fixes it -- but that's a total stab in the dark. This >> was a part of the code that was changed quite recently. > > I opened issue #1304 > <https://github.com/matplotlib/matplotlib/issues/1304> > but did not append your comment. Fixed in https://github.com/matplotlib/matplotlib/pull/1305. -- Damon McDougall http://www.damon-is-a-geek.com B2.39 Mathematics Institute University of Warwick Coventry West Midlands CV4 7AL United Kingdom
In article <506...@st...>, Michael Droettboom <md...@st...> wrote: > For the compilation problem, I am no Objective-C expert, but in C, line > 3557 should certainly read: > > NSSize pxlSize = NSMakeSize(rep->pixelsWide, rep->pixelsHigh); > > I wonder if that fixes it -- but that's a total stab in the dark. This > was a part of the code that was changed quite recently. I opened issue #1304 <https://github.com/matplotlib/matplotlib/issues/1304> but did not append your comment. -- Russell
On 09/24/2012 11:33 AM, Damon McDougall wrote: > On Mon, Sep 24, 2012 at 2:05 PM, Michael Droettboom <md...@st...> wrote: >> Thanks for pointing this out. It should now be fixed. >> > Nope, it still says 1.2.0rc1: http://matplotlib.org > Obviously my git skills are down today. Should be up there now. Mike
For the compilation problem, I am no Objective-C expert, but in C, line 3557 should certainly read: NSSize pxlSize = NSMakeSize(rep->pixelsWide, rep->pixelsHigh); I wonder if that fixes it -- but that's a total stab in the dark. This was a part of the code that was changed quite recently. Mike On 09/24/2012 01:01 PM, Russell E. Owen wrote: > In article <505...@st...>, > Michael Droettboom <md...@st...> > wrote: > >> I have tagged and created a tarball for 1.2.0rc2. The githash is >> 656c88f3e546. The tarball is on the github download page here: >> >> https://github.com/matplotlib/matplotlib/downloads >> >> This includes a number of important bugfixes, including things required >> for creating Macintosh and Windows binaries. The Travis tests are also >> now passing. >> >> I hope it will be easier for the binaries to be created this time. Once >> they are available at github, I will make an announcement to >> matplotlib-users and hopefully get some serious testing out of this thing. >> >> Thanks for all of the hard work! > I'm sorry that I missed the announcement until today -- I normally try > to check news every day or two, but got too busy last week. > > I'm even more sorry to report that I can't build the 32-bit Mac OS X > binary. I have appended the log. I suspect the issue is the need to use > an old compiler for that python. > > The 64-bit Mac binary built just fine and I'm uploading it now. I have > also appended the test results for it (which look fine to me). > > -- Russell > > Log of build failure on MacOS X 10.4 for python.org's 32-bit python 2.7 > > d-173-250-157-131:/Archives/PythonPackages/matplotlib-1.2.0rc2 rowen$ > bdist_mpkg > basedirlist is: ['/usr/local/', '/usr', '/usr/X11'] > ... > gcc-4.0 -fno-strict-aliasing -fno-common -dynamic -isysroot > /Developer/SDKs/MacOSX10.4u.sdk -arch ppc -arch i386 -g -O2 -DNDEBUG -g > -O3 -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 > -I/usr/local/include -I/usr/include -I/usr/X11/include > -I/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pa > ckages/numpy/core/include -I/usr/local/include -I/usr/include -I. > -I/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pa > ckages/numpy/core/include -Isrc -Iagg24/include -I. > -I/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c > src/_macosx.m -o build/temp.macosx-10.3-fat-2.7/src/_macosx.o > src/_macosx.m: In function 'FigureCanvas_write_bitmap': > src/_macosx.m:3557: error: request for member 'pixelsWide' in something > not a structure or union > src/_macosx.m:3557: error: request for member 'pixelsHigh' in something > not a structure or union > src/_macosx.m: In function 'FigureCanvas_write_bitmap': > src/_macosx.m:3557: error: request for member 'pixelsWide' in something > not a structure or union > src/_macosx.m:3557: error: request for member 'pixelsHigh' in something > not a structure or union > lipo: can't figure out the architecture type of: /var/tmp//ccpc0juI.out > error: command 'gcc-4.0' failed with exit status 1 > d-173-250-157-131:/Archives/PythonPackages/matplotlib-1.2.0rc2 rowen$ > > > > Log of test results for the MacOS X 10.6 python.org 64-bit python 2.7 > build: > > localhost$ python -c "import matplotlib as m ; m.test(verbosity=1)" > ......................................................................... > ......................................................................... > .........SSS.K................................K.......................... > ......................................................................... > ......................................................................... > ......................................................................... > ......................................................................... > ......................................................................... > ......................................................................... > ......................................................................... > ......................................................................... > ......................................................................... > ......................................................................... > ......................................................................... > ......................................................................... > ..................................................................../Libr > ary/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/ > matplotlib/gridspec.py:298: UserWarning: This figure includes Axes that > are not compatible with tight_layout, so its results might be incorrect. > warnings.warn("This figure includes Axes that are not " > ............................... > ---------------------------------------------------------------------- > Ran 1194 tests in 329.568s > > OK (KNOWNFAIL=2, SKIP=3) > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
In article <505...@st...>, Michael Droettboom <md...@st...> wrote: > I have tagged and created a tarball for 1.2.0rc2. The githash is > 656c88f3e546. The tarball is on the github download page here: > > https://github.com/matplotlib/matplotlib/downloads > > This includes a number of important bugfixes, including things required > for creating Macintosh and Windows binaries. The Travis tests are also > now passing. > > I hope it will be easier for the binaries to be created this time. Once > they are available at github, I will make an announcement to > matplotlib-users and hopefully get some serious testing out of this thing. > > Thanks for all of the hard work! I'm sorry that I missed the announcement until today -- I normally try to check news every day or two, but got too busy last week. I'm even more sorry to report that I can't build the 32-bit Mac OS X binary. I have appended the log. I suspect the issue is the need to use an old compiler for that python. The 64-bit Mac binary built just fine and I'm uploading it now. I have also appended the test results for it (which look fine to me). -- Russell Log of build failure on MacOS X 10.4 for python.org's 32-bit python 2.7 d-173-250-157-131:/Archives/PythonPackages/matplotlib-1.2.0rc2 rowen$ bdist_mpkg basedirlist is: ['/usr/local/', '/usr', '/usr/X11'] ... gcc-4.0 -fno-strict-aliasing -fno-common -dynamic -isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch ppc -arch i386 -g -O2 -DNDEBUG -g -O3 -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -I/usr/local/include -I/usr/include -I/usr/X11/include -I/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pa ckages/numpy/core/include -I/usr/local/include -I/usr/include -I. -I/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pa ckages/numpy/core/include -Isrc -Iagg24/include -I. -I/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c src/_macosx.m -o build/temp.macosx-10.3-fat-2.7/src/_macosx.o src/_macosx.m: In function 'FigureCanvas_write_bitmap': src/_macosx.m:3557: error: request for member 'pixelsWide' in something not a structure or union src/_macosx.m:3557: error: request for member 'pixelsHigh' in something not a structure or union src/_macosx.m: In function 'FigureCanvas_write_bitmap': src/_macosx.m:3557: error: request for member 'pixelsWide' in something not a structure or union src/_macosx.m:3557: error: request for member 'pixelsHigh' in something not a structure or union lipo: can't figure out the architecture type of: /var/tmp//ccpc0juI.out error: command 'gcc-4.0' failed with exit status 1 d-173-250-157-131:/Archives/PythonPackages/matplotlib-1.2.0rc2 rowen$ Log of test results for the MacOS X 10.6 python.org 64-bit python 2.7 build: localhost$ python -c "import matplotlib as m ; m.test(verbosity=1)" ......................................................................... ......................................................................... .........SSS.K................................K.......................... ......................................................................... ......................................................................... ......................................................................... ......................................................................... ......................................................................... ......................................................................... ......................................................................... ......................................................................... ......................................................................... ......................................................................... ......................................................................... ......................................................................... ..................................................................../Libr ary/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/ matplotlib/gridspec.py:298: UserWarning: This figure includes Axes that are not compatible with tight_layout, so its results might be incorrect. warnings.warn("This figure includes Axes that are not " ............................... ---------------------------------------------------------------------- Ran 1194 tests in 329.568s OK (KNOWNFAIL=2, SKIP=3)
On Mon, Sep 24, 2012 at 2:05 PM, Michael Droettboom <md...@st...> wrote: > Thanks for pointing this out. It should now be fixed. > Nope, it still says 1.2.0rc1: http://matplotlib.org -- Damon McDougall http://www.damon-is-a-geek.com B2.39 Mathematics Institute University of Warwick Coventry West Midlands CV4 7AL United Kingdom
On Mon, Sep 24, 2012 at 2:33 PM, Todd <tod...@gm...> wrote: > This sort of plot is used ubiquitously in neuroscience. It is used to show > the time of discrete neural (brain cell) events (called "spikes") over time > in repeated trials, and is generally called a spike raster, raster plot, or > raster graph. However, it can be used in any situation where you are only > concerned with the position of events but not their amplitude, especially if > you want to look for patterns in those events or look for differences > between multiple sequences of events. This is very closely related to "rug plots", which are often used as an axis annotation or elsewhere where it's nice to have a small 1-d density plot. Examples: https://www.cl.cam.ac.uk/~sjm217/projects/graphics/ http://rforge.org/2009/08/10/fancy-rugs-in-regression-plots/ -n
On Mon, Sep 24, 2012 at 3:51 PM, Nathaniel Smith <nj...@po...> wrote: > On Mon, Sep 24, 2012 at 2:33 PM, Todd <tod...@gm...> wrote: >> This sort of plot is used ubiquitously in neuroscience. It is used to show >> the time of discrete neural (brain cell) events (called "spikes") over time >> in repeated trials, and is generally called a spike raster, raster plot, or >> raster graph. However, it can be used in any situation where you are only >> concerned with the position of events but not their amplitude, especially if >> you want to look for patterns in those events or look for differences >> between multiple sequences of events. > > This is very closely related to "rug plots", which are often used as > an axis annotation or elsewhere where it's nice to have a small 1-d > density plot. Examples: > https://www.cl.cam.ac.uk/~sjm217/projects/graphics/ > http://rforge.org/2009/08/10/fancy-rugs-in-regression-plots/ The implementation I am thinking of for this plot type would also be able to handle these sorts of plots, although it would probably require creating horizontal and vertical variants.
I would like to add a new plot type to matplotlib. Of course I am willing to implement it myself, but I want to confirm that it is acceptable and iron out the implementation details and API first so there are no major surprises when I submit it. I tentatively am calling the plot type an "EventRaster" plot (name suggestions, along with any other suggestions, are welcome). The plot is made up if horizontal rows of identical vertical lines and/or markers. Each line or marker represents a discrete event, and each row represents a single sequence of events (such as a trial). The x-axis position of the line or marker identifies the location of the event by some measure. An example of what such a plot often looks like is below. http://hebb.mit.edu/courses/9.29/2003/athena/dylanh/quad-rast.gif This sort of plot is used ubiquitously in neuroscience. It is used to show the time of discrete neural (brain cell) events (called "spikes") over time in repeated trials, and is generally called a spike raster, raster plot, or raster graph. However, it can be used in any situation where you are only concerned with the position of events but not their amplitude, especially if you want to look for patterns in those events or look for differences between multiple sequences of events. Plotting the timing of events is an obvious use case, such as photons hitting photodetectors, radioactive decay events, arrival of patients to hospitals, calls to hotlines, or car accidents in cities. However, the events do not have to be relative to time. It could be position, for example, such as tree rings along bore holes, road crossings along railroad tracks, layers in sediment cores, or particular sequences along a DNA strands. I'll cover possible implementation details in the next email if everyone thinks this is a good idea.
We welcome all volunteers! The threshold for what requires a MEP is somewhat fuzzy, but generally it's for things in the core that affect the system as a whole. Why don't you just start discussing your thoughts and plans here and we can discuss the best way forward. Mike On 09/24/2012 06:17 AM, Todd wrote: > Hi, I am interested in implementing a new plot type for matplotlib. > Is there a specific process I should go through, or is just discussing > it on the mailing list sufficient? > > I see matplotlib has a MEP system similar to PEP, but there don't > appear to be that many MEPs so I don't know whether it is used in this > sort of situation or only for more fundamental changes. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Thanks for pointing this out. It should now be fixed. On 09/22/2012 01:55 PM, Damon McDougall wrote: > On Wed, Sep 19, 2012 at 6:53 PM, Michael Droettboom <md...@st...> wrote: >> I have tagged and created a tarball for 1.2.0rc2. The githash is >> 656c88f3e546. The tarball is on the github download page here: >> >> https://github.com/matplotlib/matplotlib/downloads >> >> This includes a number of important bugfixes, including things required >> for creating Macintosh and Windows binaries. The Travis tests are also >> now passing. >> >> I hope it will be easier for the binaries to be created this time. Once >> they are available at github, I will make an announcement to >> matplotlib-users and hopefully get some serious testing out of this thing. >> >> Thanks for all of the hard work! >> >> Mike > The website says the current development version is rc1. >
Hi, I am interested in implementing a new plot type for matplotlib. Is there a specific process I should go through, or is just discussing it on the mailing list sufficient? I see matplotlib has a MEP system similar to PEP, but there don't appear to be that many MEPs so I don't know whether it is used in this sort of situation or only for more fundamental changes.