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
(5) |
2
(4) |
|
3
|
4
(9) |
5
(4) |
6
(9) |
7
(13) |
8
(11) |
9
(7) |
|
10
(7) |
11
(22) |
12
(19) |
13
(11) |
14
(20) |
15
(21) |
16
(1) |
|
17
(1) |
18
(8) |
19
(3) |
20
(5) |
21
(5) |
22
(9) |
23
(3) |
|
24
(3) |
25
(14) |
26
(12) |
27
(29) |
28
(18) |
29
(11) |
30
(2) |
|
From: Daisy F. <eli...@ya...> - 2005-04-04 22:14:28
|
John, Thank you for your reply. A couple of issues though. I looked at the documentation and saw the alpha transperancy parameter, but for some reason I was still getting the same results. Maybe I am missing something very fundamental. If alpha is not provided then the default is for the candlestick box not to be transperant, correct? Even changing the alpha value wouldn't produced desired results, I can increase transperancy, but not eliminate it. I wasn't seeing that since I can still see the lines (wicks) go through the boxes that's why I asked here. Also, this may be another foolish oversight on my part, but how come when I have candlestick2(axMiddle, opens, closes, highs, lows, width=4, colorup='k', colordown='r') instead of getting a bar colored black when it closes above the open price I get the opposite --- red? It seems colorup should be black, colordown -- red as in colorup : the color of the lines where close >= open colordown : the color of the lines where close < open As far as the moving average calculation, I did see the disclaimer and didn't mean to be a stickler, it just seem a bit misleading to me as I was trying to do the Exponential Moving Average calculation and compare the results to the actual financial charts. They didn't match and I thought I would point that out. --- John Hunter <jdh...@ac...> wrote: > >>>>> "Daisy" == Daisy Fuentes <eli...@ya...> > writes: > > Daisy> I was looking at the example located @ > Daisy> > http://matplotlib.sourceforge.net/screenshots/finance_work2.py > Daisy> and was wondering if it's possible to > color the candlestick > Daisy> boxes so that the candlestick wicks are > not visible through > Daisy> them. > > Yes, the alpha argument to the candlestick plot > controls the > transparency. alpha is the traditional name for the > transparency > level, so look for it in documentation strings, eg > in > > http://matplotlib.sf.net/matplotlib.finance.html#-candlestick > > Daisy> Additionally, is it possible to have a > candlestick > Daisy> that's not just a plain line when the > open and the close > Daisy> prices are the same. Would it be possible > to add a > Daisy> horizontal tick mark? > Daisy> | > Daisy> | > Daisy> - > Daisy> | > Daisy> | > > You can add these marks fairly easily yourself by > adding an additional > plot command, and using the marker style TICKLEFT or > TICKRIGHT. In > other words, you can plot any kind of line you want > more or less. The > candlestick method may not support it directly, but > it is easy to > overlay. We should probably add a marker style > TICKCENTERX for this > kind of marker, and better add TICKCENTERY for > symmetry. It's only a > few lines of code that need to be added to the > lines.py module. > > Daisy> Also, I noticed that the simple moving > average is > Daisy> calculated based on the price open > instead of price close. > > I'm not attempting to make a financially meaningful > plot, but to > illustrate plotting techniques. You are free to do > moving averages > over open, close, average or random data. As I note > in the > finance_work screenshot text > > Some of the data in the plot, are real financial > data, some are > random traces that I used since the goal was to > illustrate plotting > techniques, not market analysis! > > Hope this helps, > JDH > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT > Products from real users. > Discover which products truly live up to the hype. > Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > __________________________________ Do you Yahoo!? Yahoo! Personals - Better first dates. More second dates. http://personals.yahoo.com |
|
From: Daisy F. <eli...@ya...> - 2005-04-04 22:13:03
|
John, Thank you for your reply. A couple of issues though. I looked at the documentation and saw the alpha transperancy parameter, but for some reason I was still getting the same results. Maybe I am missing something very fundamental. If alpha is not provided then the default is for the candlestick box not to be transperant, correct? Even changing the alpha value wouldn't produced desired results, I can increase transperancy, but not eliminate it. I wasn't seeing that since I can still see the lines (wicks) go through the boxes that's why I asked here. Also, this may be another foolish oversight on my part, but how come when I have candlestick2(axMiddle, opens, closes, highs, lows, width=4, colorup='k', colordown='r') instead of getting a bar colored black when it closes above the open price I get the opposite --- red? It seems colorup should be black, colordown -- red as in colorup : the color of the lines where close >= open colordown : the color of the lines where close < open As far as the moving average calculation, I did see the disclaimer and didn't mean to be a stickler, it just seem a bit misleading to me as I was trying to do the Exponential Moving Average calculation and compare the results to the actual financial charts. They didn't match and I thought I would point that out. --- John Hunter <jdh...@ac...> wrote: > >>>>> "Daisy" == Daisy Fuentes <eli...@ya...> > writes: > > Daisy> I was looking at the example located @ > Daisy> > http://matplotlib.sourceforge.net/screenshots/finance_work2.py > Daisy> and was wondering if it's possible to > color the candlestick > Daisy> boxes so that the candlestick wicks are > not visible through > Daisy> them. > > Yes, the alpha argument to the candlestick plot > controls the > transparency. alpha is the traditional name for the > transparency > level, so look for it in documentation strings, eg > in > > http://matplotlib.sf.net/matplotlib.finance.html#-candlestick > > Daisy> Additionally, is it possible to have a > candlestick > Daisy> that's not just a plain line when the > open and the close > Daisy> prices are the same. Would it be possible > to add a > Daisy> horizontal tick mark? > Daisy> | > Daisy> | > Daisy> - > Daisy> | > Daisy> | > > You can add these marks fairly easily yourself by > adding an additional > plot command, and using the marker style TICKLEFT or > TICKRIGHT. In > other words, you can plot any kind of line you want > more or less. The > candlestick method may not support it directly, but > it is easy to > overlay. We should probably add a marker style > TICKCENTERX for this > kind of marker, and better add TICKCENTERY for > symmetry. It's only a > few lines of code that need to be added to the > lines.py module. > > Daisy> Also, I noticed that the simple moving > average is > Daisy> calculated based on the price open > instead of price close. > > I'm not attempting to make a financially meaningful > plot, but to > illustrate plotting techniques. You are free to do > moving averages > over open, close, average or random data. As I note > in the > finance_work screenshot text > > Some of the data in the plot, are real financial > data, some are > random traces that I used since the goal was to > illustrate plotting > techniques, not market analysis! > > Hope this helps, > JDH > __________________________________ Do you Yahoo!? Yahoo! Personals - Better first dates. More second dates. http://personals.yahoo.com |
|
From: John H. <jdh...@ac...> - 2005-04-04 20:55:52
|
>>>>> "Daisy" == Daisy Fuentes <eli...@ya...> writes:
Daisy> I was looking at the example located @
Daisy> http://matplotlib.sourceforge.net/screenshots/finance_work2.py
Daisy> and was wondering if it's possible to color the candlestick
Daisy> boxes so that the candlestick wicks are not visible through
Daisy> them.
Yes, the alpha argument to the candlestick plot controls the
transparency. alpha is the traditional name for the transparency
level, so look for it in documentation strings, eg in
http://matplotlib.sf.net/matplotlib.finance.html#-candlestick
Daisy> Additionally, is it possible to have a candlestick
Daisy> that's not just a plain line when the open and the close
Daisy> prices are the same. Would it be possible to add a
Daisy> horizontal tick mark?
Daisy> |
Daisy> |
Daisy> -
Daisy> |
Daisy> |
You can add these marks fairly easily yourself by adding an additional
plot command, and using the marker style TICKLEFT or TICKRIGHT. In
other words, you can plot any kind of line you want more or less. The
candlestick method may not support it directly, but it is easy to
overlay. We should probably add a marker style TICKCENTERX for this
kind of marker, and better add TICKCENTERY for symmetry. It's only a
few lines of code that need to be added to the lines.py module.
Daisy> Also, I noticed that the simple moving average is
Daisy> calculated based on the price open instead of price close.
I'm not attempting to make a financially meaningful plot, but to
illustrate plotting techniques. You are free to do moving averages
over open, close, average or random data. As I note in the
finance_work screenshot text
Some of the data in the plot, are real financial data, some are
random traces that I used since the goal was to illustrate plotting
techniques, not market analysis!
Hope this helps,
JDH
|
|
From: John H. <jdh...@ac...> - 2005-04-04 20:48:41
|
>>>>> "David" == David Meggy <dav...@ya...> writes:
David> Hi I'm trying to produce bar graphs with the format of 3
David> per page all sharing a common x-axis. I have done this and
David> each graph properly has its own title, and y labels, while
David> only the bottom graph has x labels.
Have you seen examples/ganged_plots.py and
examples/shared_axis_demo.py? These specifically address sharing of
an axis (eg when navigating) and also illustrate some useful calls for
controlling ticking, etc...
David> My problem is that I would like to add a title to the
David> entire page, and add a box of information (legend or key I
David> guess) that applies to all 3 graphs, and not any in
David> particular. I hope that made sense.
If fig is a matplotlib.figure.Figure instance
fig.text : add text in figure coords; see examples/figtext.py
fig.legend : add a legend to the figure (rather than Axes); see
examples/figlegend_demo.py
See http://matplotlib.sf.net/matplotlib.figure.html for the Figure
class documentation.
David> the table function destroys my x-labels and doesn't format
David> very well.
The table can be placed in a number of different locations by passing
in the "loc" code. This can be one of
'upper right' 'upper left' 'lower left' 'lower right' 'center left'
'center right' 'lower center' 'upper center' 'center' 'top right'
'top left' 'bottom left' 'bottom right' 'right' 'left' 'top'
'bottom'
Also, try changing the size of your axes manually by using "axes"
rather than "subplot". See also the advice at
http://matplotlib.sourceforge.net/faq.html#TEXTOVERLAP
David> <my ascii drawing representation of what I'm looking for>
Now we just need to write an ascii backend to facilitate this kind of
communication :-)
JDH
|
|
From: Daishi H. <da...@eg...> - 2005-04-04 19:49:28
|
Thanks for your reply. On Apr 2, 2005, at 6:23 AM, John Hunter wrote: > On my power book ssh-ing into a linux box, I can run wx and wxagg > examples, and other backends as well. I'd be happy to find that the problem is in my local configuration; I just can't seem to figure out what to tweak locally. > How can I determine which window manager (twm vs quartz-wm) I am > running? I usually just do something like "ps auwx | grep wm" and look for a process that I recognize as a window manager. (Note this won't work if you're using one of those "modern" window managers that don't suffix their program name with "wm", like metacity or blackbox). If you're using the Apple-supplied X11 server then as a default you would be using quartz-wm. If this is working for you then the problem is almost certainly on my end. > JDH Thanks again, d |
|
From: John H. <jdh...@ac...> - 2005-04-04 13:39:01
|
>>>>> "kristen" == kristen kaasbjerg <co...@ya...> writes:
kristen> Hi John When I try to save any figure with a grid in .eps
kristen> format, I get an error message. I am using the 0.74
kristen> version.
Hi Kristen,
Hmm, I don't get the crash.
In [1]: plot([1,2,3])
Out[1]: [<matplotlib.lines.Line2D instance at 0x4202b26c>]
In [2]: grid()
In [3]: savefig('test.eps')
Sometimes it helps to delete site-packages/matplotlib and your build
subdirectory to insure a clean install, though I don't think that is
the problem here.
Could you post a complete script that exposes the bug, run it with the
--verbose-helpful flag and report the output, and attach an rc file if
you are doing any customizations to it besides changing the default
backend.
Thanks,
JDH
|
|
From: kristen k. <co...@ya...> - 2005-04-04 09:38:07
|
Hi John
When I try to save any figure with a grid in .eps
format, I get an error message. I am using the 0.74
version.
The error message:
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File
"/home/camp/s991416/lib/python/matplotlib/pylab.py",
line 720, in savefig
return fig.savefig(*args, **kwargs)
File
"/home/camp/s991416/lib/python/matplotlib/figure.py",
line 512, in savefig
self.canvas.print_figure(*args, **kwargs)
File
"/home/camp/s991416/lib/python/matplotlib/backends/backend_tkagg.py",
line 161, in print_figure
agg.print_figure(filename, dpi, facecolor,
edgecolor, orientation)
File
"/home/camp/s991416/lib/python/matplotlib/backends/backend_agg.py",
line405, in print_figure
ps.print_figure(filename, dpi, facecolor,
edgecolor, orientation)
File
"/home/camp/s991416/lib/python/matplotlib/backends/backend_ps.py",
line 742, in print_figure
self.figure.draw(renderer)
File
"/home/camp/s991416/lib/python/matplotlib/figure.py",
line 395, in draw
for a in self.axes: a.draw(renderer)
File
"/home/camp/s991416/lib/python/matplotlib/axes.py",
line 1362, in draw
self.xaxis.draw(renderer)
File
"/home/camp/s991416/lib/python/matplotlib/axis.py",
line 524, in draw
tick.draw(renderer)
File
"/home/camp/s991416/lib/python/matplotlib/axis.py",
line 136, in draw
if midPoint and self.gridOn:
self.gridline.draw(renderer)
File
"/home/camp/s991416/lib/python/matplotlib/lines.py",
line 286, in draw
lineFunc(renderer, gc, xt, yt)
File
"/home/camp/s991416/lib/python/matplotlib/lines.py",
line 572, in _draw_dotted
renderer.draw_lines(gc, xt, yt)
File
"/home/camp/s991416/lib/python/matplotlib/backends/backend_ps.py",
line 367, in draw_lines
self._draw_lines(gc,to_draw)
File
"/home/camp/s991416/lib/python/matplotlib/backends/backend_ps.py",
line 350, in _draw_lines
self._draw_ps("\n".join(ps), gc, None)
File
"/home/camp/s991416/lib/python/matplotlib/backends/backend_ps.py",
line 557, in _draw_ps
self.set_linewidth(gc.get_linewidth())
File
"/home/camp/s991416/lib/python/matplotlib/backends/backend_ps.py",
line 112, in set_linewidth
self._pswriter.write("%1.3f
setlinewidth\n"%linewidth)
TypeError: float argument required
__________________________________
Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun.
http://www.advision.webevents.yahoo.com/emoticontest
|
|
From: Robert L. <ro...@le...> - 2005-04-04 03:05:56
|
David Meggy wrote: > On Mon, 2005-04-04 at 11:03 +1000, Robert Leftwich wrote: > >>David Meggy wrote: >> >>>What functions should I be looking at to post this extra information? >> >>You can use the axis text() function to write arbitrary text on a graph. See the >>align text example (http://matplotlib.sourceforge.net/screenshots/align_text.py) >>and its image (http://matplotlib.sourceforge.net/screenshots/align_text_large.png). > > > That looks useful, but the text is still specific to a particular > subplot. I want the text totally separate. You can add text to the figure by using figure.text(..) as well (see figure.py in matplotlib). (Caveat - I've never actually used this approach) Robert |
|
From: David M. <dav...@ya...> - 2005-04-04 00:04:54
|
Hi I'm trying to produce bar graphs with the format of 3 per page all sharing a common x-axis. I have done this and each graph properly has its own title, and y labels, while only the bottom graph has x labels. My problem is that I would like to add a title to the entire page, and add a box of information (legend or key I guess) that applies to all 3 graphs, and not any in particular. I hope that made sense. the table function destroys my x-labels and doesn't format very well. What functions should I be looking at to post this extra information? <my ascii drawing representation of what I'm looking for> PAGE TITLE Bar graph 1 -title | y-labels | bar graph 1 | | | ---------------------------- Bar graph 2 -title | y-labels | bar graph 2 | | | ---------------------------- Bar graph 3 -title | y-labels | bar graph 3 | | | ---------------------------- x-labels Page information -legend/key </bad ascii art> -- David Meggy <dav...@ya...> |