You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(12) |
Sep
(12) |
Oct
(56) |
Nov
(65) |
Dec
(37) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(59) |
Feb
(78) |
Mar
(153) |
Apr
(205) |
May
(184) |
Jun
(123) |
Jul
(171) |
Aug
(156) |
Sep
(190) |
Oct
(120) |
Nov
(154) |
Dec
(223) |
2005 |
Jan
(184) |
Feb
(267) |
Mar
(214) |
Apr
(286) |
May
(320) |
Jun
(299) |
Jul
(348) |
Aug
(283) |
Sep
(355) |
Oct
(293) |
Nov
(232) |
Dec
(203) |
2006 |
Jan
(352) |
Feb
(358) |
Mar
(403) |
Apr
(313) |
May
(165) |
Jun
(281) |
Jul
(316) |
Aug
(228) |
Sep
(279) |
Oct
(243) |
Nov
(315) |
Dec
(345) |
2007 |
Jan
(260) |
Feb
(323) |
Mar
(340) |
Apr
(319) |
May
(290) |
Jun
(296) |
Jul
(221) |
Aug
(292) |
Sep
(242) |
Oct
(248) |
Nov
(242) |
Dec
(332) |
2008 |
Jan
(312) |
Feb
(359) |
Mar
(454) |
Apr
(287) |
May
(340) |
Jun
(450) |
Jul
(403) |
Aug
(324) |
Sep
(349) |
Oct
(385) |
Nov
(363) |
Dec
(437) |
2009 |
Jan
(500) |
Feb
(301) |
Mar
(409) |
Apr
(486) |
May
(545) |
Jun
(391) |
Jul
(518) |
Aug
(497) |
Sep
(492) |
Oct
(429) |
Nov
(357) |
Dec
(310) |
2010 |
Jan
(371) |
Feb
(657) |
Mar
(519) |
Apr
(432) |
May
(312) |
Jun
(416) |
Jul
(477) |
Aug
(386) |
Sep
(419) |
Oct
(435) |
Nov
(320) |
Dec
(202) |
2011 |
Jan
(321) |
Feb
(413) |
Mar
(299) |
Apr
(215) |
May
(284) |
Jun
(203) |
Jul
(207) |
Aug
(314) |
Sep
(321) |
Oct
(259) |
Nov
(347) |
Dec
(209) |
2012 |
Jan
(322) |
Feb
(414) |
Mar
(377) |
Apr
(179) |
May
(173) |
Jun
(234) |
Jul
(295) |
Aug
(239) |
Sep
(276) |
Oct
(355) |
Nov
(144) |
Dec
(108) |
2013 |
Jan
(170) |
Feb
(89) |
Mar
(204) |
Apr
(133) |
May
(142) |
Jun
(89) |
Jul
(160) |
Aug
(180) |
Sep
(69) |
Oct
(136) |
Nov
(83) |
Dec
(32) |
2014 |
Jan
(71) |
Feb
(90) |
Mar
(161) |
Apr
(117) |
May
(78) |
Jun
(94) |
Jul
(60) |
Aug
(83) |
Sep
(102) |
Oct
(132) |
Nov
(154) |
Dec
(96) |
2015 |
Jan
(45) |
Feb
(138) |
Mar
(176) |
Apr
(132) |
May
(119) |
Jun
(124) |
Jul
(77) |
Aug
(31) |
Sep
(34) |
Oct
(22) |
Nov
(23) |
Dec
(9) |
2016 |
Jan
(26) |
Feb
(17) |
Mar
(10) |
Apr
(8) |
May
(4) |
Jun
(8) |
Jul
(6) |
Aug
(5) |
Sep
(9) |
Oct
(4) |
Nov
|
Dec
|
2017 |
Jan
(5) |
Feb
(7) |
Mar
(1) |
Apr
(5) |
May
|
Jun
(3) |
Jul
(6) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2025 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
|
1
(9) |
2
(8) |
3
|
4
(6) |
5
|
6
|
7
(41) |
8
(18) |
9
(25) |
10
(18) |
11
(10) |
12
(13) |
13
(7) |
14
(4) |
15
(12) |
16
(6) |
17
(9) |
18
(7) |
19
(2) |
20
(5) |
21
(7) |
22
(2) |
23
(11) |
24
(11) |
25
(14) |
26
(3) |
27
(3) |
28
(17) |
29
(7) |
30
(16) |
31
(8) |
|
|
Hello, I basically have a Chi-Squared distribution that is dependent on 3 variables. eg. X2(x, y, z) What I would like to do is be able to plot the chi-squared + 1 surface in 3-dimensions. eg. I would like to have the three axes as x, y and z. and then have a surface (its going to look like a closed blob effectively) that maps the chi-squared plus one surface. I have no idea how to do this though. Is it possible? any ideas? -- View this message in context: http://old.nabble.com/3d-Surface-Contour-Plot-tp31143849p31143849.html Sent from the matplotlib - users mailing list archive at Nabble.com.
For this to work correctly, you need to manually keep two axes in sync (you can use a callback). Also note that this approach cannot be used with aspect=1 & adjustable=bbox. Another way is to use axes_grid1 toolkit. Here is the modified version of your script w/ axes_grid1. Regards, -JJ import numpy as np import matplotlib import matplotlib.colorbar as cb import matplotlib.pyplot as plt y = np.reshape(np.arange(0, 1000000, 1), (20000, 50)) test = 'hot' f1 = plt.figure(1) f1.patch.set_facecolor('#c0c0c0') import mpl_toolkits.axes_grid1 as axes_grid1 # use axes_grid1.host_axes ax1 = axes_grid1.host_axes([0.09, 0.15, 0.82, 0.80]) axc = f1.add_axes([0.09, 0.05, 0.82, 0.05]) im1 = ax1.imshow(y, cmap=test, aspect='auto', origin='lower') cb.Colorbar(axc, im1, orientation='horizontal') # use twin() not twinx() ax2 = ax1.twin() # make ticklabels on the top invisible ax2.axis["top"].toggle(ticklabels=False) fmtr = matplotlib.ticker.FuncFormatter(lambda x,pos: "%.2f"% (x*2,)) ax2.yaxis.set_major_formatter(fmtr) plt.show() On Sat, Mar 12, 2011 at 9:01 AM, Thomas Brezinski <th...@ar...> wrote: > Jason Stone, on 2011年02月18日 14:39, wrote: >> Good afternoon all, >> One last matplotlib question for the group for today. On one of my GUI >> plots, I'm calling imshow on an array of data (to display it in the same >> way >> MATLAB's imagesc command does). I'd like to add a second y-axis to the >> right side of the plot that is completely dependent on the values on the >> primary y-axis. Essentially, for each y-axis tick point, I'll put the >> y-axis 'value' into a formula and then put the result on the second >> y-axis. >> I did this in MATLAB by essentially overlaying a second set of axes over >> the plot, but I haven't found the exact way to do it with matplotlib yet. >> I've seen a few examples online, but they all use the second overlaid >> plot >> to actually plot new data - I wouldn't be doing this. >> Would I need to use the twinx (or twiny) function? >> Are there examples of this on the web that I haven't found that somebody >> could point me towards? > > Hi Jason, > > here's an example that does what you want, using e^x as the > formula, change the paramter to fmtr to suit your needs: > > ax = plt.subplot(1,1,1) > ax.plot(np.sin(np.linspace(0,np.pi))) > ax2 = ax.twinx() > ax2._sharey = ax # share both x and y > fmtr = mpl.ticker.FuncFormatter(lambda x,pos: "%.2f"%np.exp(x)) > ax2.yaxis.set_major_formatter(fmtr) > plt.draw() > > best, > -- > Paul Ivanov > 314 address only used for lists, off-list direct email at: > http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 > > > Paul, > I am currently doing something very similar and was hoping I could ask for a > little clarification. I want to have two y axes where the ticks are in the > same locations and the 2nd y-axis labels are just twice the 1st y-axis > labels. When I implement your example, I don't quite understand how to > ensure the ticks are at the same locations. Also, when the data changes to a > new image, the 1st y-axis updates but the 2nd y-axis does not. Is there a > convenient way to force both to update each time, or does the figure need to > be cleared and essentially built from scratch each time. > > for example, with the following code: > > import numpy as np > import matplotlib > import matplotlib.colorbar as cb > import matplotlib.pyplot as plt > > y = np.reshape(np.arange(0, 1000000, 1), (20000, 50)) > test = 'hot' > f1 = plt.figure(1) > f1.patch.set_facecolor('#c0c0c0') > ax1 = f1.add_axes([0.09, 0.15, 0.82, 0.80]) > axc = f1.add_axes([0.09, 0.05, 0.82, 0.05]) > im1 = ax1.imshow(y, cmap=test, aspect='auto', origin='lower') > cb.Colorbar(axc, im1, orientation='horizontal') > ax2 = ax1.twinx() > ax2._sharey = ax1 # share both x and y > fmtr = matplotlib.ticker.FuncFormatter(lambda x,pos: "%.2f"%np.exp(x)) > ax2.yaxis.set_major_formatter(fmtr) > plt.show() > > The ticks on the right are obviously at different locations compared to the > left ticks. Also, if imshow was to be called a new array of data, the ticks > on the right would remain the same. So is there an easy way to force the > locations to be the same, and is there an easy way force the right y-axis to > update each time? Thank you very much for your time and help. > > -Thomas > > > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEARECAAYFAk1kEfIACgkQe+cmRQ8+KPe0vACfSMtFJ9KSRwqU34j6QevaSZqD > qM0An2WHMyKisrwDIyKaCcuygrsWvZbX > =OIU1 > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------------ > Free Software Download: Index, Search & Analyze Logs and other IT data in > Real-Time with Splunk. Collect, index and harness all the fast moving IT > data > generated by your applications, servers and devices whether physical, > virtual > or in the cloud. Deliver compliance at lower cost and gain new business > insights. http://p.sf.net/sfu/splunk-dev2dev > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > > > ------------------------------------------------------------------------------ > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > >
I would like to construct a 3d plot consisting of several 2d quiver plots on orthogonal, intersecting planes. Is this possible with matplotlib? In matlab I do it by construct several 2d graph and then reorienting them in the 3d space using the 'rotate' function. E.g. xaxis = [1 0 0]; h = quiver('v6', z, y, w, v, 'k'); rotate(h, xaxis, 90, [0 0 0]); This produces a 2d quiver plot of [v,w](y,z) oriented along the y,z axes of the 3d space, and then I do the same for x,y and x,z quiver plots. Any ideas for matplotib 3d? Thanks! John Gibson -- View this message in context: http://old.nabble.com/orienting-2d-plots-in-3d-tp31140854p31140854.html Sent from the matplotlib - users mailing list archive at Nabble.com.
Thanks much for the reply! I'll try your advice as soon as I can. BTW, I don't think this is a Solaris-related problem. If you look at the pointers in my original post, the same error can happen on other arch (I confess it can be for other reasons though). -n On Sun, Mar 13, 2011 at 1:03 PM, Jouni K. Seppänen <jk...@ik...> wrote: > Nicolas SCHEFFER <sch...@gm...> writes: > >> I didn't get much reply on this issue, so I'm just trying to resurrect >> the question. > > Probably not many devs using Solaris, so no-one has been able to > reproduce this. > >>> #12 0xfffffd7ff4a22fd8 in py_to_agg_transformation_matrix >>> (obj=0x774380, errors=<value optimized out>) at >>> src/agg_py_transforms.cpp:22 >>> #13 0xfffffd7ff4a32e7c in _path_module::update_path_extents >>> (this=<value optimized out>, args=...) at src/path.cpp:380 > > So it's in transforms-related code, but we can't see the locals. First > I'd try to recompile without optimizations and (hoping it still crashes) > inspect the local variables in these frames in gdb. Or maybe make the > functions print out their arguments and any other relevant locals. > > -- > Jouni K. Seppänen > http://www.iki.fi/jks > > > ------------------------------------------------------------------------------ > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users >