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
(7) |
2
(12) |
3
(7) |
4
(23) |
5
(5) |
6
(7) |
7
(4) |
|
8
(7) |
9
(25) |
10
(17) |
11
(25) |
12
(11) |
13
(8) |
14
(6) |
|
15
(1) |
16
(22) |
17
(11) |
18
(12) |
19
(22) |
20
(32) |
21
(9) |
|
22
(4) |
23
(16) |
24
(5) |
25
(9) |
26
(26) |
27
(21) |
28
(14) |
|
29
(6) |
30
(8) |
31
(4) |
|
|
|
|
Hi, Could anyone tell me how can I remove matplotlib completely on Mac? I was on version 0.99 and I wanted to upgrade to version 1.0 so i removed the matplotlib directory and the egg file (besides the pylab.py, pylab.pyo, and pylab.pyc files), and installed the new version using .dmg file "matplotlib-1.0.0-python.org-py2.6-macosx10.4". Now, I can import and work with pylab when I call it from the terminal, but I can not import it other places like IDLE. I get the following error. Thanks in advance, Ahmad Process: Python [922] Path: /Library/Frameworks/Python.framework/Versions/2.6/Resources/Python.app/Contents/MacOS/Python Identifier: Python Version: ??? (???) Code Type: X86 (Native) Parent Process: Python [906] Date/Time: 2010年08月31日 14:58:39.849 -0400 OS Version: Mac OS X 10.6.4 (10F569) Report Version: 6 Interval Since Last Report: 309566 sec Crashes Since Last Report: 9 Per-App Crashes Since Last Report: 9 Anonymous UUID: 5F9B0D80-FF2A-4C21-B4A0-AD0FF7646D3E Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 ??? 0000000000 0 + 0 1 org.python.python 0x000dd2f7 _PyImport_LoadDynamicModule + 167 2 org.python.python 0x000dac83 load_module + 227 3 org.python.python 0x000db1ad import_submodule + 301 4 org.python.python 0x000db409 load_next + 201 5 org.python.python 0x000dbe03 PyImport_ImportModuleLevel + 419 6 org.python.python 0x000b4b5f builtin___import__ + 159 7 org.python.python 0x0000ed35 PyObject_Call + 85 8 org.python.python 0x000ba5be PyEval_CallObjectWithKeywords + 78 9 org.python.python 0x000bdb50 PyEval_EvalFrameEx + 9680 10 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 11 org.python.python 0x000c23f7 PyEval_EvalCode + 87 12 org.python.python 0x000d98ec PyImport_ExecCodeModuleEx + 188 13 org.python.python 0x000da58c load_source_module + 540 14 org.python.python 0x000db1ad import_submodule + 301 15 org.python.python 0x000db409 load_next + 201 16 org.python.python 0x000dbdb1 PyImport_ImportModuleLevel + 337 17 org.python.python 0x000b4b5f builtin___import__ + 159 18 org.python.python 0x0000ed35 PyObject_Call + 85 19 org.python.python 0x000ba5be PyEval_CallObjectWithKeywords + 78 20 org.python.python 0x000bdb50 PyEval_EvalFrameEx + 9680 21 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 22 org.python.python 0x000c23f7 PyEval_EvalCode + 87 23 org.python.python 0x000d98ec PyImport_ExecCodeModuleEx + 188 24 org.python.python 0x000da58c load_source_module + 540 25 org.python.python 0x000db1ad import_submodule + 301 26 org.python.python 0x000db757 ensure_fromlist + 439 27 org.python.python 0x000dc1ed PyImport_ImportModuleLevel + 1421 28 org.python.python 0x000b4b5f builtin___import__ + 159 29 org.python.python 0x0000ed35 PyObject_Call + 85 30 org.python.python 0x000ba5be PyEval_CallObjectWithKeywords + 78 31 org.python.python 0x000bdb50 PyEval_EvalFrameEx + 9680 32 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 33 org.python.python 0x000c23f7 PyEval_EvalCode + 87 34 org.python.python 0x000d98ec PyImport_ExecCodeModuleEx + 188 35 org.python.python 0x000da58c load_source_module + 540 36 org.python.python 0x000db1ad import_submodule + 301 37 org.python.python 0x000db757 ensure_fromlist + 439 38 org.python.python 0x000dc1ed PyImport_ImportModuleLevel + 1421 39 org.python.python 0x000b4b5f builtin___import__ + 159 40 org.python.python 0x0000ed35 PyObject_Call + 85 41 org.python.python 0x000ba5be PyEval_CallObjectWithKeywords + 78 42 org.python.python 0x000bdb50 PyEval_EvalFrameEx + 9680 43 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 44 org.python.python 0x000c23f7 PyEval_EvalCode + 87 45 org.python.python 0x000d98ec PyImport_ExecCodeModuleEx + 188 46 org.python.python 0x000da58c load_source_module + 540 47 org.python.python 0x000db1ad import_submodule + 301 48 org.python.python 0x000db409 load_next + 201 49 org.python.python 0x000dbe03 PyImport_ImportModuleLevel + 419 50 org.python.python 0x000b4b5f builtin___import__ + 159 51 org.python.python 0x0000ed35 PyObject_Call + 85 52 org.python.python 0x000ba5be PyEval_CallObjectWithKeywords + 78 53 org.python.python 0x000bdb50 PyEval_EvalFrameEx + 9680 54 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 55 org.python.python 0x000c23f7 PyEval_EvalCode + 87 56 org.python.python 0x000d98ec PyImport_ExecCodeModuleEx + 188 57 org.python.python 0x000da58c load_source_module + 540 58 org.python.python 0x000db1ad import_submodule + 301 59 org.python.python 0x000db409 load_next + 201 60 org.python.python 0x000dbdb1 PyImport_ImportModuleLevel + 337 61 org.python.python 0x000b4b5f builtin___import__ + 159 62 org.python.python 0x0000ed35 PyObject_Call + 85 63 org.python.python 0x000ba5be PyEval_CallObjectWithKeywords + 78 64 org.python.python 0x000bdb50 PyEval_EvalFrameEx + 9680 65 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 66 org.python.python 0x000c0a25 PyEval_EvalFrameEx + 21669 67 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 68 org.python.python 0x0003f746 function_call + 166 69 org.python.python 0x0000ed35 PyObject_Call + 85 70 org.python.python 0x000bdf2c PyEval_EvalFrameEx + 10668 71 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 72 org.python.python 0x000c034c PyEval_EvalFrameEx + 19916 73 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 74 org.python.python 0x000c23f7 PyEval_EvalCode + 87 75 org.python.python 0x000e888f PyRun_StringFlags + 287 76 org.python.python 0x000e898e PyRun_SimpleStringFlags + 78 77 org.python.python 0x000f929e Py_Main + 1486 78 org.python.python 0x00001f82 0x1000 + 3970 79 org.python.python 0x00001ea9 0x1000 + 3753 Thread 1: Dispatch queue: com.apple.libdispatch-manager 0 libSystem.B.dylib 0x93443942 kevent + 10 1 libSystem.B.dylib 0x9344405c _dispatch_mgr_invoke + 215 2 libSystem.B.dylib 0x93443519 _dispatch_queue_invoke + 163 3 libSystem.B.dylib 0x934432be _dispatch_worker_thread2 + 240 4 libSystem.B.dylib 0x93442d41 _pthread_wqthread + 390 5 libSystem.B.dylib 0x93442b86 start_wqthread + 30 Thread 2: 0 libSystem.B.dylib 0x934588da select$DARWIN_EXTSN$NOCANCEL + 10 1 libSystem.B.dylib 0x934f0d67 select + 92 2 select.so 0x007dd6e0 select_select + 480 3 org.python.python 0x000c0165 PyEval_EvalFrameEx + 19429 4 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 5 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 6 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 7 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 8 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 9 org.python.python 0x0003f746 function_call + 166 10 org.python.python 0x0000ed35 PyObject_Call + 85 11 org.python.python 0x00020b36 instancemethod_call + 422 12 org.python.python 0x0000ed35 PyObject_Call + 85 13 org.python.python 0x000beab7 PyEval_EvalFrameEx + 13623 14 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 15 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 16 org.python.python 0x0003f746 function_call + 166 17 org.python.python 0x0000ed35 PyObject_Call + 85 18 org.python.python 0x00020b36 instancemethod_call + 422 19 org.python.python 0x0000ed35 PyObject_Call + 85 20 org.python.python 0x000beab7 PyEval_EvalFrameEx + 13623 21 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 22 org.python.python 0x0003f746 function_call + 166 23 org.python.python 0x0000ed35 PyObject_Call + 85 24 org.python.python 0x00020b36 instancemethod_call + 422 25 org.python.python 0x0000ed35 PyObject_Call + 85 26 org.python.python 0x00075897 slot_tp_init + 87 27 org.python.python 0x000742c0 type_call + 176 28 org.python.python 0x0000ed35 PyObject_Call + 85 29 org.python.python 0x000beab7 PyEval_EvalFrameEx + 13623 30 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 31 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 32 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 33 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 34 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 35 org.python.python 0x0003f746 function_call + 166 36 org.python.python 0x0000ed35 PyObject_Call + 85 37 org.python.python 0x000bdf2c PyEval_EvalFrameEx + 10668 38 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 39 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 40 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 41 org.python.python 0x0003f746 function_call + 166 42 org.python.python 0x0000ed35 PyObject_Call + 85 43 org.python.python 0x00020b36 instancemethod_call + 422 44 org.python.python 0x0000ed35 PyObject_Call + 85 45 org.python.python 0x000ba5be PyEval_CallObjectWithKeywords + 78 46 org.python.python 0x000fbaef t_bootstrap + 63 47 libSystem.B.dylib 0x9344a81d _pthread_start + 345 48 libSystem.B.dylib 0x9344a6a2 thread_start + 34 Thread 0 crashed with X86 Thread State (32-bit): eax: 0x0155b440 ebx: 0x0208498b ecx: 0x01892200 edx: 0x0155b440 edi: 0x014e3150 esi: 0x0031dd88 ebp: 0xbfff8788 esp: 0xbfff874c ss: 0x0000001f efl: 0x00010246 eip: 0x00000000 cs: 0x00000017 ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 cr2: 0x00000000 Binary Images: 0x1000 - 0x1ff5 +org.python.python 2.6.4 (2.6.4) <4037E992-5FF7-89F8-C547-77DF78B19D35> /Library/Frameworks/Python.framework/Versions/2.6/Resources/Python.app/Contents/MacOS/Python 0x5000 - 0x130fe3 +org.python.python 2.6.4, (c) 2004-2008 Python Software Foundation. (2.6.4) <74126CA0-A482-4EDB-B195-CE276F49DA9E> /Library/Frameworks/Python.framework/Versions/2.6/Python 0x1f5000 - 0x1f6fff +time.so ??? (???) <CE38317A-468D-F3F1-D021-0360AD0CAF4A> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/time.so 0x3c0000 - 0x3c7fff +_socket.so ??? (???) <C1B22680-310E-C1E5-8BFE-4A7CB8E454ED> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_socket.so 0x3d0000 - 0x3d3ff7 +_ssl.so ??? (???) <4CB670AF-33F3-41BD-769C-F28FC27BB467> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_ssl.so 0x3d9000 - 0x3fffff libssl.0.9.7.dylib 0.9.7 (compatibility 0.9.7) <32607000-7573-6D51-ABC3-420B4A0D6629> /usr/lib/libssl.0.9.7.dylib 0x40e000 - 0x4c3fe7 libcrypto.0.9.7.dylib 0.9.7 (compatibility 0.9.7) <0B69B1F5-3440-B0BF-957F-E0ADD49F13CB> /usr/lib/libcrypto.0.9.7.dylib 0x509000 - 0x50aff9 +cStringIO.so ??? (???) <4C6A1DF3-FC4E-3E99-EB62-D9F4B455D23C> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/cStringIO.so 0x50f000 - 0x50fffc +_functools.so ??? (???) <F84F4FEF-3FB0-C7D5-DB89-E8419D70D30A> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_functools.so 0x513000 - 0x516ff3 +_collections.so ??? (???) <78B59DC9-8C1C-FD7F-1CA1-AAA38F6F70B3> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_collections.so 0x51c000 - 0x51ffff +operator.so ??? (???) <06B2B012-039B-F139-56A8-AEB0E9B94056> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/operator.so 0x526000 - 0x52affe +itertools.so ??? (???) <59707961-1A72-58D1-CAFA-C6A533F0FC87> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/itertools.so 0x533000 - 0x533ff5 +_bisect.so ??? (???) <B0BA9213-688E-F914-30A0-E0E57FC01B4E> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_bisect.so 0x537000 - 0x538ff9 +_heapq.so ??? (???) <D6155E99-1427-0DA4-80AC-B3E898C66AED> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_heapq.so 0x5f4000 - 0x5faff5 +_tkinter.so ??? (???) <F69893FD-D21D-24B9-2D85-979EBF155695> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_tkinter.so 0x601000 - 0x692fe7 Tcl 8.4.19 (8.4.19) <6FF5C975-96BA-3370-AD5D-AAE625BE5D9A> /System/Library/Frameworks/Tcl.framework/Versions/8.4/Tcl 0x6b0000 - 0x77afe7 Tk 8.4.19 (8.4.19) <4F15559E-41DD-54A7-81DC-216B5B743401> /System/Library/Frameworks/Tk.framework/Versions/8.4/Tk 0x7d2000 - 0x7d5ffc +strop.so ??? (???) <E2AD56A2-4C71-DDA9-D714-553270C062EE> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/strop.so 0x7db000 - 0x7ddfff +select.so ??? (???) <06E5920F-2F6A-B301-E6AA-A22A9F9F2A9D> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/select.so 0x7e3000 - 0x7e6ff7 +_struct.so ??? (???) <1D6CFA30-A56B-C2F2-42AD-AF363C54B793> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_struct.so 0x7ed000 - 0x7effff +math.so ??? (???) <06E35D7B-2246-9698-B12B-CC112597523B> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/math.so 0x7f5000 - 0x7fafff +binascii.so ??? (???) <F0A84DF3-E036-B7CA-C5CF-B7AE66F412CF> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/binascii.so 0x1340000 - 0x134efff +cPickle.so ??? (???) <440E0C46-62CF-5C05-15AF-17F94C922F9D> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/cPickle.so 0x13f6000 - 0x13f7fff +_random.so ??? (???) <D19D89FC-872B-6A7B-F936-886275F9D8ED> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_random.so 0x13fb000 - 0x13fcff0 +fcntl.so ??? (???) <21B2B1EE-58CF-E74F-B145-30EF50FB8D64> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/fcntl.so 0x1400000 - 0x1401ffe +_locale.so ??? (???) <D7A81337-6283-5088-4E05-CE9DE1EA845A> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_locale.so 0x1485000 - 0x1485ff5 +_weakref.so ??? (???) <945566A6-ACAF-BFD8-3474-03996C6F0D82> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_weakref.so 0x14c9000 - 0x14c9ff0 +_scproxy.so ??? (???) <660139D7-362C-FCC9-DE8F-F9E396F74FAE> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_scproxy.so 0x150d000 - 0x155afe7 +multiarray.so ??? (???) <78C13840-63F9-4DCC-8C47-A3C39675CAAB> /Library/Frameworks/GDAL.framework/Versions/1.7/Python/site-packages/numpy/core/multiarray.so 0x158b000 - 0x15baff7 +umath.so ??? (???) <4FED7F55-DBA0-994A-15E8-D946A4D74AEA> /Library/Frameworks/GDAL.framework/Versions/1.7/Python/site-packages/numpy/core/umath.so 0x15d8000 - 0x15e4ff7 +_sort.so ??? (???) <66D5D0B9-7ABD-C2A2-20FD-AEF794707AC2> /Library/Frameworks/GDAL.framework/Versions/1.7/Python/site-packages/numpy/core/_sort.so 0x15eb000 - 0x15eeff7 +_dotblas.so ??? (???) <9F6D6C18-4BCC-A2A1-741F-F99B5691147E> /Library/Frameworks/GDAL.framework/Versions/1.7/Python/site-packages/numpy/core/_dotblas.so 0x1632000 - 0x164aff7 +scalarmath.so ??? (???) <10190E35-C2FB-D1BB-9C02-57E71BB2139E> /Library/Frameworks/GDAL.framework/Versions/1.7/Python/site-packages/numpy/core/scalarmath.so 0x1657000 - 0x1659ff7 +_compiled_base.so ??? (???) <E3322AC7-5B7D-84F3-AD7E-3310AC05BF1E> /Library/Frameworks/GDAL.framework/Versions/1.7/Python/site-packages/numpy/lib/_compiled_base.so 0x169c000 - 0x169fff7 +lapack_lite.so ??? (???) <06413FE5-8107-33C5-1F43-FBA1882BD4CA> /Library/Frameworks/GDAL.framework/Versions/1.7/Python/site-packages/numpy/linalg/lapack_lite.so 0x16a3000 - 0x16acff7 +fftpack_lite.so ??? (???) <D6727649-8BDB-70AE-5385-E3553A750B7D> /Library/Frameworks/GDAL.framework/Versions/1.7/Python/site-packages/numpy/fft/fftpack_lite.so 0x16af000 - 0x16d4fe7 +mtrand.so ??? (???) <CBF7BC65-8344-EDA3-44FE-A9B0237F95DB> /Library/Frameworks/GDAL.framework/Versions/1.7/Python/site-packages/numpy/random/mtrand.so 0x16f4000 - 0x1706fff +_ctypes.so ??? (???) <7AFEFB64-D558-CCF0-1D6E-AC0CF96656A8> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_ctypes.so 0x1794000 - 0x179ffff +datetime.so ??? (???) <291E576D-4567-B936-C1C9-420B00BEB902> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/datetime.so 0x17ea000 - 0x17ebff5 +_hashlib.so ??? (???) <5D7347EB-1AB0-A64D-3D0B-9C05B0BA12B3> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_hashlib.so 0x17f0000 - 0x17f3ffe +_sha256.so ??? (???) <9366ADC0-98C8-0CB3-C6E5-FC08C9975D86> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_sha256.so 0x2000000 - 0x200dff1 +_sha512.so ??? (???) <63CF6A9E-230E-5EB1-4D1B-3BBE856F9155> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_sha512.so 0x2011000 - 0x2015ff9 +array.so ??? (???) <225C8EDE-27E3-F800-F3CE-B1C6D912187B> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/array.so 0x205d000 - 0x209aff2 +_path.so ??? (???) <36FC5144-4295-966E-5EAF-302158E923E1> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/matplotlib/_path.so 0x8fe00000 - 0x8fe4162b dyld 132.1 (???) <A4F6ADCC-6448-37B4-ED6C-ABB2CD06F448> /usr/lib/dyld 0x90003000 - 0x90273ffb com.apple.Foundation 6.6.3 (751.29) <E77D3906-99F4-FEF4-FBB0-86FB3C94073E> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation 0x904f0000 - 0x905e2ff7 libcrypto.0.9.8.dylib 0.9.8 (compatibility 0.9.8) <D2C86308-F998-C83D-F49B-CD484D4EFE6A> /usr/lib/libcrypto.0.9.8.dylib 0x90624000 - 0x90693ff7 libvMisc.dylib 268.0.1 (compatibility 1.0.0) <2FC2178F-FEF9-6E3F-3289-A6307B1A154C> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib 0x90694000 - 0x90744ff3 com.apple.ColorSync 4.6.3 (4.6.3) <AA1076EA-7665-3005-A837-B661260DBE54> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync 0x90745000 - 0x90749ff7 libGIF.dylib ??? (???) <3ECD4D2C-40FE-E9A0-A2D2-E36D1C00D3A8> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib 0x90c3c000 - 0x90c3dff7 com.apple.TrustEvaluationAgent 1.1 (1) <6C04C4C5-667E-2EBE-EB96-5B67BD4B2185> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent 0x90d7f000 - 0x90e01ffb SecurityFoundation ??? (???) <3670AE8B-06DA-C447-EB14-79423DB9C474> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation 0x90e02000 - 0x90eaffe7 libobjc.A.dylib 227.0.0 (compatibility 1.0.0) <DF8E4CFA-3719-3415-0BF1-E8C5E561C3B1> /usr/lib/libobjc.A.dylib 0x910b2000 - 0x910c0ff7 com.apple.opengl 1.6.9 (1.6.9) <4F06C166-00CF-5ACF-77E3-5A960A5E8AD3> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL 0x910c1000 - 0x910e3fef com.apple.DirectoryService.Framework 3.6 (621.3) <05FFDBDB-F16B-8AC0-DB42-986965FCBD95> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService 0x910e4000 - 0x910e4ff7 com.apple.Accelerate.vecLib 3.6 (vecLib 3.6) <1DEC639C-173D-F808-DE0D-4070CC6F5BC7> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib 0x910e5000 - 0x9110bfff com.apple.DictionaryServices 1.1.1 (1.1.1) <02709230-9B37-C743-6E27-3FCFD18211F8> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices 0x9110c000 - 0x91124ff7 com.apple.CFOpenDirectory 10.6 (10.6) <1537FB4F-C112-5D12-1E5D-3B1002A4038F> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory 0x91125000 - 0x91127ff7 libRadiance.dylib ??? (???) <AB06F616-E3EA-5966-029A-8AA44BBE5B28> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib 0x9114a000 - 0x9119bff7 com.apple.HIServices 1.8.0 (???) <10C85B88-C6AF-91DB-2546-34661BA35AC5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices 0x91399000 - 0x913e2fe7 libTIFF.dylib ??? (???) <9CFF48CC-4852-4D06-17AC-3C947C824159> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib 0x9141d000 - 0x9142aff7 com.apple.NetFS 3.2.1 (3.2.1) <5E61A00B-FA16-9D99-A064-47BDC5BC9A2B> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS 0x9142b000 - 0x9174bfeb com.apple.CoreServices.CarbonCore 861.13 (861.13) <52803668-3669-36BD-57DD-078FBA835081> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore 0x91912000 - 0x91915fe7 libmathCommon.A.dylib 315.0.0 (compatibility 1.0.0) <1622A54F-1A98-2CBE-B6A4-2122981A500E> /usr/lib/system/libmathCommon.A.dylib 0x91916000 - 0x9192bfff com.apple.ImageCapture 6.0 (6.0) <3F31833A-38A9-444E-02B7-17619CA6F2A0> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture 0x9192c000 - 0x91931ff7 com.apple.OpenDirectory 10.6 (10.6) <92582807-E8F3-3DD9-EB42-4195CFB754A1> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory 0x91d08000 - 0x91d28fe7 libresolv.9.dylib 41.0.0 (compatibility 1.0.0) <751955F3-21FB-A03A-4E92-1F3D4EFB8C5B> /usr/lib/libresolv.9.dylib 0x91d29000 - 0x91d44ff7 libPng.dylib ??? (???) <36A3D75E-5178-4358-7F02-444E276D61AD> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib 0x9226e000 - 0x9228afe3 com.apple.openscripting 1.3.1 (???) <DA16DE48-59F4-C94B-EBE3-7FAF772211A2> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting 0x9246e000 - 0x92479ff7 libGL.dylib ??? (???) <B87E0676-F5EF-8DA3-6DEE-13C43B3832A7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib 0x924ce000 - 0x924d8fe7 com.apple.audio.SoundManager 3.9.3 (3.9.3) <5F494955-7290-2D91-DA94-44B590191771> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.framework/Versions/A/CarbonSound 0x924d9000 - 0x924dcffb com.apple.help 1.3.1 (41) <67F1F424-3983-7A2A-EC21-867BE838E90B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help 0x925cc000 - 0x9260fff7 libGLU.dylib ??? (???) <2093A1FB-67BD-39E0-CDE5-A97A77BDDBCE> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib 0x92610000 - 0x92652ff7 libvDSP.dylib 268.0.1 (compatibility 1.0.0) <3F0ED200-741B-4E27-B89F-634B131F5E9E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib 0x927b4000 - 0x927bbff3 com.apple.print.framework.Print 6.1 (237.1) <97AB70B6-C653-212F-CFD3-E3816D0F5C22> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print 0x927ef000 - 0x92c24ff7 libLAPACK.dylib 219.0.0 (compatibility 1.0.0) <5E2D2283-57DE-9A49-1DB0-CD027FEFA6C2> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib 0x92e9b000 - 0x92ebcfe7 com.apple.opencl 12.1 (12.1) <DA2AC3FA-ED11-2D10-21E9-7BDF4778B228> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL 0x92ebd000 - 0x92f38fe7 com.apple.audio.CoreAudio 3.2.2 (3.2.2) <51D0E2DC-B15F-AF6C-70D8-026DDAD4E2A5> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio 0x92f5c000 - 0x92f5cff7 com.apple.CoreServices 44 (44) <AC35D112-5FB9-9C8C-6189-5F5945072375> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices 0x92f5d000 - 0x92f69ff7 libkxld.dylib ??? (???) <322A4B52-8305-3081-6B74-813C3A87A56D> /usr/lib/system/libkxld.dylib 0x9305f000 - 0x93090ff7 libGLImage.dylib ??? (???) <9340012D-595A-6243-9C97-7D30D76D9D9E> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib 0x932bb000 - 0x932dfff7 libJPEG.dylib ??? (???) <5CE96981-6B2A-D15B-4A17-E7BD329095B6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib 0x932e1000 - 0x93319ff7 libcups.2.dylib 2.8.0 (compatibility 2.0.0) <76C02F5C-98FD-BD64-B5FB-C698FB76EA25> /usr/lib/libcups.2.dylib 0x9331a000 - 0x9341bfe7 libxml2.2.dylib 10.3.0 (compatibility 10.0.0) <B4C5CD68-405D-0F1B-59CA-5193D463D0EF> /usr/lib/libxml2.2.dylib 0x9341c000 - 0x935c2feb libSystem.B.dylib 125.2.0 (compatibility 1.0.0) <3441F338-2218-6D36-3F95-3A16FBF6713D> /usr/lib/libSystem.B.dylib 0x935c3000 - 0x9366bffb com.apple.QD 3.35 (???) <B80B64BC-958B-DA9E-50F9-D7E8333CC5A2> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD 0x93686000 - 0x93792ff7 libGLProgrammability.dylib ??? (???) <1B315838-F477-5416-7504-67EC3433AD4A> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib 0x9380d000 - 0x93868ff7 com.apple.framework.IOKit 2.0 (???) <A013B850-6ECB-594A-CBD6-DB156B11871B> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit 0x938f8000 - 0x939a6ff3 com.apple.ink.framework 1.3.3 (107) <57B54F6F-CE35-D546-C7EC-DBC5FDC79938> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink 0x939a7000 - 0x93a39fe3 com.apple.print.framework.PrintCore 6.2 (312.5) <7729B4D7-D661-D669-FA7E-510F93F685A6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore 0x93a95000 - 0x93ac8ff7 com.apple.AE 496.4 (496.4) <7F34EC47-8429-3077-8158-54F5EA908C66> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE 0x93b38000 - 0x93b46fe7 libz.1.dylib 1.2.3 (compatibility 1.0.0) <3CE8AA79-F077-F1B0-A039-9103A4A02E92> /usr/lib/libz.1.dylib 0x93b8c000 - 0x93d46fe3 com.apple.ImageIO.framework 3.0.3 (3.0.3) <A93A514B-C1BF-21D0-FB03-CB775DE4FFAA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO 0x93d47000 - 0x93d65ff7 com.apple.CoreVideo 1.6.1 (45.4) <E0DF044D-BF31-42CE-B690-FD1FCE07E64A> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo 0x9405e000 - 0x94070ff7 com.apple.MultitouchSupport.framework 205.34 (205.34) <813475E3-B323-9405-F758-DDA1F5D63B20> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport 0x94b67000 - 0x94c44ff7 com.apple.vImage 4.0 (4.0) <64597E4B-F144-DBB3-F428-0EC3D9A1219E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage 0x94c45000 - 0x94caffe7 libstdc++.6.dylib 7.9.0 (compatibility 7.0.0) <411D87F4-B7E1-44EB-F201-F8B4F9227213> /usr/lib/libstdc++.6.dylib 0x94cb0000 - 0x94d4dfe3 com.apple.LaunchServices 362.1 (362.1) <885D8567-9E40-0105-20BC-42C7FF657583> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices 0x94d4e000 - 0x950b6ff7 com.apple.QuartzCore 1.6.2 (227.22) <4288F0D2-0C87-F054-C372-8764B44DE024> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore 0x950b7000 - 0x950b9ff7 com.apple.securityhi 4.0 (36638) <38D36D4D-C798-6ACE-5FA8-5C001993AD6B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI 0x950ba000 - 0x950fdff7 com.apple.NavigationServices 3.5.4 (182) <753B8906-06C0-3AE0-3D6A-8FF5AC18ED12> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationServices.framework/Versions/A/NavigationServices 0x95106000 - 0x95232fff com.apple.audio.toolbox.AudioToolbox 1.6.3 (1.6.3) <F0D7256E-0914-8E77-E37B-9720430422AB> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox 0x95233000 - 0x95233ff7 com.apple.Carbon 150 (152) <9252D5F2-462D-2C15-80F3-109644D6F704> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon 0x95234000 - 0x95284ff7 com.apple.framework.familycontrols 2.0.1 (2010) <B9762E20-543D-13B9-F6BF-E8585F04CA01> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyControls 0x95cfa000 - 0x95e7cfe7 libicucore.A.dylib 40.0.0 (compatibility 1.0.0) <2314BD12-0821-75BB-F3BC-98D324CFD30A> /usr/lib/libicucore.A.dylib 0x95ed5000 - 0x95ed5ff7 com.apple.vecLib 3.6 (vecLib 3.6) <7362077A-890F-3AEF-A8AB-22247B10E106> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib 0x95edd000 - 0x95ef1fe7 libbsm.0.dylib ??? (???) <14CB053A-7C47-96DA-E415-0906BA1B78C9> /usr/lib/libbsm.0.dylib 0x95fc3000 - 0x95fc7ff7 libGFXShared.dylib ??? (???) <2D32BDBF-C941-93FD-E233-F03D28DB9E94> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib 0x9600e000 - 0x96022ffb com.apple.speech.synthesis.framework 3.10.35 (3.10.35) <57DD5458-4F24-DA7D-0927-C3321A65D743> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis 0x960af000 - 0x96110fe7 com.apple.CoreText 3.1.0 (???) <1372DABE-F183-DD03-03C2-64B2464A4FD5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreText.framework/Versions/A/CoreText 0x96125000 - 0x96128ff7 libCoreVMClient.dylib ??? (???) <CA0BA8DC-0159-A808-A300-750358A6970C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib 0x96129000 - 0x961f3fef com.apple.CoreServices.OSServices 357 (357) <CF9530AD-F581-B831-09B6-16D9F9283BFA> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices 0x961f4000 - 0x96458fef com.apple.security 6.1.1 (37594) <3F68A006-6B30-85D5-1A75-8D748F72A6D5> /System/Library/Frameworks/Security.framework/Versions/A/Security 0x96478000 - 0x96488ff7 libsasl2.2.dylib 3.15.0 (compatibility 3.0.0) <C8744EA3-0AB7-CD03-E639-C4F2B910BE5D> /usr/lib/libsasl2.2.dylib 0x96519000 - 0x965b4ff7 com.apple.ApplicationServices.ATS 275.11.1 (???) <5FF65EC7-F512-530A-7771-3DE240EE6E43> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS 0x96696000 - 0x9672efe7 edu.mit.Kerberos 6.5.10 (6.5.10) <8B83AFF3-C074-E47C-4BD0-4546EED0D1BC> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos 0x9672f000 - 0x96730ff7 com.apple.audio.units.AudioUnit 1.6.3 (1.6.3) <959DFFAE-A06B-7FF6-B713-B2076893EBBD> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit 0x96c9c000 - 0x96c9cff7 com.apple.ApplicationServices 38 (38) <8012B504-3D83-BFBB-DA65-065E061CFE03> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices 0x96d99000 - 0x96d99ff7 com.apple.Accelerate 1.6 (Accelerate 1.6) <BC501C9F-7C20-961A-B135-0A457667D03C> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate 0x96d9a000 - 0x96da3ff7 com.apple.DiskArbitration 2.3 (2.3) <E9C40767-DA6A-6CCB-8B00-2D5706753000> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration 0x96da4000 - 0x96e5affb libFontParser.dylib ??? (???) <067DC1A2-764B-41EA-B07E-4205472749B7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib 0x97000000 - 0x97064ffb com.apple.htmlrendering 72 (1.1.4) <4D451A35-FAB6-1288-71F6-F24A4B6E2371> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering.framework/Versions/A/HTMLRendering 0x97065000 - 0x9706fffb com.apple.speech.recognition.framework 3.11.1 (3.11.1) <EC0E69C8-A121-70E8-43CF-E6FC4C7779EC> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition 0x97074000 - 0x9714ffe7 com.apple.DesktopServices 1.5.7 (1.5.7) <A69072AD-C47E-A00D-4A69-6E46A7FB2119> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv 0x97260000 - 0x97309ff7 com.apple.CFNetwork 454.9.8 (454.9.8) <DB2A5C33-E833-1B3A-4DE0-5FF172B2048B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork 0x9730a000 - 0x97350ff7 libauto.dylib ??? (???) <85670A64-3B67-8162-D441-D8E0BE15CA94> /usr/lib/libauto.dylib 0x97351000 - 0x9738eff7 com.apple.SystemConfiguration 1.10.2 (1.10.2) <398BB007-41FD-1A30-26D8-CB86ED5E467E> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration 0x9738f000 - 0x973d3fe7 com.apple.Metadata 10.6.3 (507.10) <630494FA-3BB3-EDD3-E10B-8DAAF4831E26> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata 0x974db000 - 0x97594fe7 libsqlite3.dylib 9.6.0 (compatibility 9.0.0) <16CEF8E8-8C9A-94CD-EF5D-05477844C005> /usr/lib/libsqlite3.dylib 0x97595000 - 0x979abff7 libBLAS.dylib 219.0.0 (compatibility 1.0.0) <C4FB303A-DB4D-F9E8-181C-129585E59603> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib 0x98aa1000 - 0x99290557 com.apple.CoreGraphics 1.545.0 (???) <DCED8E1A-7504-C31A-B6EF-98BFF1A61060> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics 0x992d1000 - 0x992f9ff7 libxslt.1.dylib 3.24.0 (compatibility 3.0.0) <769EF4B2-C1AD-73D5-AAAD-1564DAEA77AF> /usr/lib/libxslt.1.dylib 0x992fd000 - 0x99477fe3 com.apple.CoreFoundation 6.6.3 (550.29) <00373783-3744-F47D-2191-BEEA658F0C3D> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 0x99482000 - 0x997a6fef com.apple.HIToolbox 1.6.3 (???) <0A5F56E2-9AF3-728D-70AE-429522AEAD8A> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox 0x997a7000 - 0x997abff7 IOSurface ??? (???) <66E11D8E-CF4B-EFD0-37F9-20177C647021> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface 0x997b9000 - 0x997fdff3 com.apple.coreui 2 (114) <29F8F1A4-1C96-6A0F-4CC2-9B85CF83209F> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI 0x997fe000 - 0x9984bfeb com.apple.DirectoryService.PasswordServerFramework 6.0 (6.0) <BF66BA5D-BBC8-78A5-DBE2-F9DE3DD1D775> /System/Library/PrivateFrameworks/PasswordServer.framework/Versions/A/PasswordServer 0x998c5000 - 0x99945feb com.apple.SearchKit 1.3.0 (1.3.0) <9E18AEA5-F4B4-8BE5-EEA9-818FC4F46FD9> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit 0x99946000 - 0x9994cfff com.apple.CommonPanels 1.2.4 (91) <2438AF5D-067B-B9FD-1248-2C9987F360BA> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels 0x99953000 - 0x99964ff7 com.apple.LangAnalysis 1.6.6 (1.6.6) <97511CC7-FE23-5AC3-2EE2-B5479FAEB316> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis 0xffff0000 - 0xffff1fff libSystem.B.dylib ??? (???) <3441F338-2218-6D36-3F95-3A16FBF6713D> /usr/lib/libSystem.B.dylib Model: MacBookPro5,5, BootROM MBP55.00AC.B03, 2 processors, Intel Core 2 Duo, 2.53 GHz, 4 GB, SMC 1.47f2 Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB Memory Module: global_name AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.10.91.27) Bluetooth: Version 2.3.7f1, 2 service, 19 devices, 1 incoming serial ports Network Service: Ethernet, Ethernet, en0 Network Service: AirPort, AirPort, en1 Serial ATA Device: TOSHIBA MK2555GSXF, 232.89 GB Serial ATA Device: MATSHITADVD-R UJ-868 USB Device: Keyboard Hub, 0x05ac (Apple Inc.), 0x1006, 0x26200000 USB Device: Apple Keyboard, 0x05ac (Apple Inc.), 0x0221, 0x26220000 USB Device: Internal Memory Card Reader, 0x05ac (Apple Inc.), 0x8403, 0x26500000 USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06100000 USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8213, 0x06110000 USB Device: USB Flash Memory, 0x0930 (Toshiba Corporation), 0x6540, 0x24100000 USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8507, 0x24400000 USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x0237, 0x04600000 USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0x04500000
On 8/31/2010 6:30 AM, Thøger Emil Juul Thorsen wrote: > I'm putting together a quick animation to demonstrate some physics to my > students. I'm perfectly fine to just have it show in the default plot > window, but by default the window is drawn quite small on my screen. Does it not work to set figsize and dpi? http://matplotlib.sourceforge.net/api/pyplot_api.html#matplotlib.pyplot.figure Alan Isaac
Hi everyone.
I face a problem here, which I can't seem to handle by myself, so any help is really appreciated.
I would like to do a simple line plot of a huge dataset as an overview to quickly compare success of different measurement scenarios, and it seems that not every datapoint is displayed. I played a little with the lod parameter, both for the creation of the axis and the plot command. However timing the plot command and the display itself do not show differences. Here are a few lines of code that help to reproduce the problem.
import time
import matplotlib
matplotlib.use("Qt4Agg")
import matplotlib.pyplot as plt
import numpy as np
xData=np.linspace(0, 10.0, 1e6)
yData=np.zeros(xData.shape)
xDataDetail=np.linspace(0.0, 2*np.pi, 1000)
yDataDetail=np.exp(-xDataDetail)*np.sin(10.0*xDataDetail)
yData[100000:100000+len(yDataDetail)]=yDataDetail
fig=plt.figure()
axes=fig.add_subplot(111)
tic=time.time()
axes.plot(xData, yData, "b-")
toc=time.time()
axes.grid(True)
print "Plotting took %g s." % (toc-tic)
plt.show()
The code shows how I usually use the matplotlib environment and creates a simple dataset of 1 million zeros with a short non trivial peak within, that is to be plotted as a blue solid line.
You can see what happens, when you vary the width of the displaying window. On my system usually the minimum amplitude varies when resizing the window.
Is there any way to enforce plotting each and every point?
I use matplotlib version 1.0.0 on a 32 Bit windows XP system installed via the windows installer from sf.
A quick check on a opensuse 11.3 linux box showed the same issue. Using the "standard" TK backend instead of Qt4Agg behaves just the same.
Jens
Hello list; I'm putting together a quick animation to demonstrate some physics to my students. I'm perfectly fine to just have it show in the default plot window, but by default the window is drawn quite small on my screen. Is there a simple way to tell the placement and size of the plot window like e.g. there is in VPython? Cheers; Emil
On Mon, Aug 30, 2010 at 4:36 PM, Jeremy Conlin <jlc...@gm...> wrote: > I have a matplotlib plot that I saved to a pdf image. The plot > consists of 1E5 dots plotted with varying colors and opacities. > Actually 1E5 black dots with varying opacities and 64 colored markers. > The trouble is my image is 11 MB and takes a few seconds to fully > display in a PDF reader. I am using this figure in a presentation and > therefore need to reduce the file size so it will display more > quickly. Is there any way I can reduce the size of my image while > still keeping all the data? > > Thanks, > Jeremy > > > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > There a few pdf related parameters in the matplotlibrc file (e.g. resolution, compression). You could play around with them to see if you can get any lower-size output. -- Gökhan
If it is only one image, an easy low-tech workaround is to save it as PNG and then put it into a PDF. This way, you only have to load one element. On Mon, Aug 30, 2010 at 11:36 PM, Jeremy Conlin <jlc...@gm...> wrote: > I have a matplotlib plot that I saved to a pdf image. The plot > consists of 1E5 dots plotted with varying colors and opacities. > Actually 1E5 black dots with varying opacities and 64 colored markers. > The trouble is my image is 11 MB and takes a few seconds to fully > display in a PDF reader. I am using this figure in a presentation and > therefore need to reduce the file size so it will display more > quickly. Is there any way I can reduce the size of my image while > still keeping all the data? > > Thanks, > Jeremy > > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users >
I have a matplotlib plot that I saved to a pdf image. The plot consists of 1E5 dots plotted with varying colors and opacities. Actually 1E5 black dots with varying opacities and 64 colored markers. The trouble is my image is 11 MB and takes a few seconds to fully display in a PDF reader. I am using this figure in a presentation and therefore need to reduce the file size so it will display more quickly. Is there any way I can reduce the size of my image while still keeping all the data? Thanks, Jeremy
I don't think there is a release numpy that is compatible with Python 2.7 (though it is due shortly in the form of numpy 1.5) and matplotlib requires numpy. -- Russell In article <AANLkTikNi4k5qkRzt=0AM...@ma...>, Åke Kullenberg <ake...@gm...> wrote: > I've seen some posts asking for the same thing, but there's been quite some > time now. Does anyone know the progress? Should I wait, or just downgrade to > 2.6 for now? > > Thanks > --------------------------------------------------------------------- > ------------------------------------------------------------------------------ > Sell apps to millions through the Intel(R) Atom(Tm) Developer Program > Be part of this innovative community and reach millions of netbook users > worldwide. Take advantage of special opportunities to increase revenue and > speed time-to-market. Join now, and jumpstart your future. > http://p.sf.net/sfu/intel-atom-d2d-------------------------------------------- > ------------------------- > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users I
setupext.py contains the code:
if gotit:
print_status("Tkinter", "Tkinter: %s, Tk: %s, Tcl: %s" %
(Tkinter.__version__, Tkinter.TkVersion, Tkinter.TclVersion))
Because I built from source, the Tkinter.__version__ value is
'$Revision$'. It seems poor practice to assume specific formatting
of this field.
Also, I built my copy of Python using "ccache gcc" as the compiler.
The matplotlib build gets confused by this and tries to link with:
c++ gcc -pthread -shared build/temp.linux-x86_64-2.7/src/ft2font.o ...
I suspect somewhere that the "ccache" part is split off and "c++"
added.
Regards,
Neil
On Mon, Aug 30, 2010 at 4:44 AM, xyz <mi...@op...> wrote:
> On 30/08/10 03:51, Benjamin Root wrote:
>> maxy = max(max(y1), max(y2))
>> maxx = max(x)
>>
>> ax.set_xlim((0.0, maxx))
>> ax.set_ylim((0.0, maxy))
> Thank you, but unfortunately I have still the same problems:
> * plt.text appears outside x and y coordinates
> * and the coordinates starts not from 0
>
> with the updated code:
> from pylab import *
> import matplotlib.pyplot as plt
>
> x = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19,
> 20, 21, 22, 23, 24, 25, 26, 27, 28, 29]
> y1 = [20, 24, 8, 4, 12, 22, 31, 25, 15, 28, 12, 27, 22, 22, 27, 14, 32,
> 28, 8, 17, 2, 8, 29, 13, 14, 20, 11, 28, 8]
> y2= [2, 32, 28, 1, 22, 11, 14, 27, 3, 31, 12, 20, 32, 24, 24, 16, 7, 10,
> 12, 11, 3, 32, 10, 20, 14, 14, 3, 25, 14]
> point_labels1 = ['A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
> 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
> 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
> 'A=1']
> point_labels2 = ['B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
> 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
> 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
> 'B=1']
>
> fig = plt.figure()
> ax = fig.add_subplot(111)
>
> ax.set_title('The red point should be on the path')
>
> plt.plot(x, y1, 'bo', x, y2, 'go')
> ax.grid(True)
> maxy = max(max(y1), max(y2))
> maxx = max(x)
>
> ax.set_xlim((0.0, maxx))
> ax.set_ylim((0.0, maxy))
>
> fig.autofmt_xdate()
>
> plt.xticks(range(0, 40, 1))
>
> plt.yticks(range(0, 40, 1))
> plt.xlabel('Longitude')
> plt.ylabel('Latitude')
> plt.legend(('Model length', 'Data length'),
> 'best', shadow=True, fancybox=True)
>
> for i, label in enumerate(y1):
> plt.text (x[i], y1[i]+0.2, label,
> horizontalalignment='center' )
>
> for i, label in enumerate(y2):
> plt.text (x[i], y2[i]+0.2, label,
> horizontalalignment='center' )
>
>
> ax.autoscale_view()
> plt.savefig('test.png')
> plt.show()
>
> What did I wrong?
Like Eric said, the call to ax.autoscale_view() overrides the limits
you set by hand. Remove this line.
Ryan
--
Ryan May
Graduate Research Assistant
School of Meteorology
University of Oklahoma
I've seen some posts asking for the same thing, but there's been quite some time now. Does anyone know the progress? Should I wait, or just downgrade to 2.6 for now? Thanks
On 30/08/10 03:51, Benjamin Root wrote:
> maxy = max(max(y1), max(y2))
> maxx = max(x)
>
> ax.set_xlim((0.0, maxx))
> ax.set_ylim((0.0, maxy))
Thank you, but unfortunately I have still the same problems:
* plt.text appears outside x and y coordinates
* and the coordinates starts not from 0
with the updated code:
from pylab import *
import matplotlib.pyplot as plt
x = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19,
20, 21, 22, 23, 24, 25, 26, 27, 28, 29]
y1 = [20, 24, 8, 4, 12, 22, 31, 25, 15, 28, 12, 27, 22, 22, 27, 14, 32,
28, 8, 17, 2, 8, 29, 13, 14, 20, 11, 28, 8]
y2= [2, 32, 28, 1, 22, 11, 14, 27, 3, 31, 12, 20, 32, 24, 24, 16, 7, 10,
12, 11, 3, 32, 10, 20, 14, 14, 3, 25, 14]
point_labels1 = ['A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
'A=1']
point_labels2 = ['B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
'B=1']
fig = plt.figure()
ax = fig.add_subplot(111)
ax.set_title('The red point should be on the path')
plt.plot(x, y1, 'bo', x, y2, 'go')
ax.grid(True)
maxy = max(max(y1), max(y2))
maxx = max(x)
ax.set_xlim((0.0, maxx))
ax.set_ylim((0.0, maxy))
fig.autofmt_xdate()
plt.xticks(range(0, 40, 1))
plt.yticks(range(0, 40, 1))
plt.xlabel('Longitude')
plt.ylabel('Latitude')
plt.legend(('Model length', 'Data length'),
'best', shadow=True, fancybox=True)
for i, label in enumerate(y1):
plt.text (x[i], y1[i]+0.2, label,
horizontalalignment='center' )
for i, label in enumerate(y2):
plt.text (x[i], y2[i]+0.2, label,
horizontalalignment='center' )
ax.autoscale_view()
plt.savefig('test.png')
plt.show()
What did I wrong?
On Sun, Aug 29, 2010 at 6:29 AM, xyz <mi...@op...> wrote: > On 29/08/10 17:28, Eric Firing wrote: > > On 08/28/2010 06:40 PM, xyz wrote: > >> Hello, > >> If I use autoscale_view than: > >> * plt.text appears outside x and y coordinates > >> * and the coordinates starts do not from 0 whereas I use ax.set_xlim(0) > >> and ax.set_ylim(0) > >> > >> What did I wrong? > > The call to autoscale_view overrides the earlier calls to set_xlim and > > set_ylim. There is no built-in mechanism for autoscaling only the upper > > limit, and holding the lower limit fixed. You could make such a > > mechanism by writing a custom Locator, but it may make more sense to > > calculate the upper limit directly in your code based on your data, and > > then use set_xlim and set_ylim to set both ends of each axis. > > > > Eric > > > > Thank you for your answer. However, I do not how to calculate the upper > limit directly from my code based on my data, and then use set_xlim and > set_ylim to set both ends of each axis. Could you show me please how to > do it? > > Thank you in advance. > > You could try: maxy = max(max(y1), max(y2)) maxx = max(x) ax.set_xlim((0.0, maxx)) ax.set_ylim((0.0, maxy)) I hope that helps, Ben Root
On 29/08/10 17:28, Eric Firing wrote:
> On 08/28/2010 06:40 PM, xyz wrote:
>> Hello,
>> If I use autoscale_view than:
>> * plt.text appears outside x and y coordinates
>> * and the coordinates starts do not from 0 whereas I use ax.set_xlim(0)
>> and ax.set_ylim(0)
>>
>> What did I wrong?
> The call to autoscale_view overrides the earlier calls to set_xlim and
> set_ylim. There is no built-in mechanism for autoscaling only the upper
> limit, and holding the lower limit fixed. You could make such a
> mechanism by writing a custom Locator, but it may make more sense to
> calculate the upper limit directly in your code based on your data, and
> then use set_xlim and set_ylim to set both ends of each axis.
>
> Eric
>
Thank you for your answer. However, I do not how to calculate the upper
limit directly from my code based on my data, and then use set_xlim and
set_ylim to set both ends of each axis. Could you show me please how to
do it?
Thank you in advance.
from pylab import *
import matplotlib.pyplot as plt
x = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19,
20, 21, 22, 23, 24, 25, 26, 27, 28, 29]
y1 = [20, 24, 8, 4, 12, 22, 31, 25, 15, 28, 12, 27, 22, 22, 27, 14, 32,
28, 8, 17, 2, 8, 29, 13, 14, 20, 11, 28, 8]
y2= [2, 32, 28, 1, 22, 11, 14, 27, 3, 31, 12, 20, 32, 24, 24, 16, 7, 10,
12, 11, 3, 32, 10, 20, 14, 14, 3, 25, 14]
point_labels1 = ['A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
'A=1']
point_labels2 = ['B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
'B=1']
fig = plt.figure()
ax = fig.add_subplot(111)
ax.set_title('The red point should be on the path')
plt.plot(x, y1, 'bo', x, y2, 'go')
ax.grid(True)
ax.set_xlim(0.0)
ax.set_ylim(0.0)
fig.autofmt_xdate()
plt.xticks(range(0, 40, 1))
plt.yticks(range(0, 40, 1))
plt.xlabel('Longitude')
plt.ylabel('Latitude')
plt.legend(('Model length', 'Data length'),
'best', shadow=True, fancybox=True)
for i, label in enumerate(y1):
plt.text (x[i], y1[i]+0.2, label,
horizontalalignment='center' )
for i, label in enumerate(y2):
plt.text (x[i], y2[i]+0.2, label,
horizontalalignment='center' )
ax.autoscale_view()
plt.savefig('test.png')
plt.show()
On 29/08/10 17:28, Eric Firing wrote:
> On 08/28/2010 06:40 PM, xyz wrote:
>
>> Hello,
>> If I use autoscale_view than:
>> * plt.text appears outside x and y coordinates
>> * and the coordinates starts do not from 0 whereas I use ax.set_xlim(0)
>> and ax.set_ylim(0)
>>
>> What did I wrong?
>>
> The call to autoscale_view overrides the earlier calls to set_xlim and
> set_ylim. There is no built-in mechanism for autoscaling only the upper
> limit, and holding the lower limit fixed. You could make such a
> mechanism by writing a custom Locator, but it may make more sense to
> calculate the upper limit directly in your code based on your data, and
> then use set_xlim and set_ylim to set both ends of each axis.
>
> Eric
>
>
Thank you for your answer. However, I do not how to calculate the upper
limit directly from my code based on my data, and then use set_xlim and
set_ylim to set both ends of each axis. Could you show me please how to
do it?
Thank you in advance.
from pylab import *
import matplotlib.pyplot as plt
x = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19,
20, 21, 22, 23, 24, 25, 26, 27, 28, 29]
y1 = [20, 24, 8, 4, 12, 22, 31, 25, 15, 28, 12, 27, 22, 22, 27, 14, 32,
28, 8, 17, 2, 8, 29, 13, 14, 20, 11, 28, 8]
y2= [2, 32, 28, 1, 22, 11, 14, 27, 3, 31, 12, 20, 32, 24, 24, 16, 7, 10,
12, 11, 3, 32, 10, 20, 14, 14, 3, 25, 14]
point_labels1 = ['A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1']
point_labels2 = ['B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1']
fig = plt.figure()
ax = fig.add_subplot(111)
ax.set_title('The red point should be on the path')
plt.plot(x, y1, 'bo', x, y2, 'go')
ax.grid(True)
ax.set_xlim(0.0)
ax.set_ylim(0.0)
fig.autofmt_xdate()
plt.xticks(range(0, 40, 1))
plt.yticks(range(0, 40, 1))
plt.xlabel('Longitude')
plt.ylabel('Latitude')
plt.legend(('Model length', 'Data length'),
'best', shadow=True, fancybox=True)
for i, label in enumerate(y1):
plt.text (x[i], y1[i]+0.2, label,
horizontalalignment='center' )
for i, label in enumerate(y2):
plt.text (x[i], y2[i]+0.2, label,
horizontalalignment='center' )
ax.autoscale_view()
plt.savefig('test.png')
plt.show()
On 08/28/2010 06:40 PM, xyz wrote:
> Hello,
> If I use autoscale_view than:
> * plt.text appears outside x and y coordinates
> * and the coordinates starts do not from 0 whereas I use ax.set_xlim(0)
> and ax.set_ylim(0)
>
> What did I wrong?
The call to autoscale_view overrides the earlier calls to set_xlim and
set_ylim. There is no built-in mechanism for autoscaling only the upper
limit, and holding the lower limit fixed. You could make such a
mechanism by writing a custom Locator, but it may make more sense to
calculate the upper limit directly in your code based on your data, and
then use set_xlim and set_ylim to set both ends of each axis.
Eric
>
> from pylab import *
> import matplotlib.pyplot as plt
>
> x = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19,
> 20, 21, 22, 23, 24, 25, 26, 27, 28, 29]
> y1 = [20, 24, 8, 4, 12, 22, 31, 25, 15, 28, 12, 27, 22, 22, 27, 14, 32,
> 28, 8, 17, 2, 8, 29, 13, 14, 20, 11, 28, 8]
> y2= [2, 32, 28, 1, 22, 11, 14, 27, 3, 31, 12, 20, 32, 24, 24, 16, 7, 10,
> 12, 11, 3, 32, 10, 20, 14, 14, 3, 25, 14]
> point_labels1 = ['A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
> 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
> 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1']
> point_labels2 = ['B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
> 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
> 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1']
>
> fig = plt.figure()
> ax = fig.add_subplot(111)
>
> ax.set_title('The red point should be on the path')
>
> plt.plot(x, y1, 'bo', x, y2, 'go')
> ax.grid(True)
> ax.set_xlim(0.0)
> ax.set_ylim(0.0)
>
> fig.autofmt_xdate()
>
> plt.xticks(range(0, 40, 1))
>
> plt.yticks(range(0, 40, 1))
> plt.xlabel('Longitude')
> plt.ylabel('Latitude')
> plt.legend(('Model length', 'Data length'),
> 'best', shadow=True, fancybox=True)
>
> for i, label in enumerate(y1):
> plt.text (x[i], y1[i]+0.2, label,
> horizontalalignment='center' )
>
> for i, label in enumerate(y2):
> plt.text (x[i], y2[i]+0.2, label,
> horizontalalignment='center' )
>
>
> ax.autoscale_view()
> plt.savefig('test.png')
> plt.show()
Hello,
If I use autoscale_view than:
* plt.text appears outside x and y coordinates
* and the coordinates starts do not from 0 whereas I use ax.set_xlim(0)
and ax.set_ylim(0)
What did I wrong?
from pylab import *
import matplotlib.pyplot as plt
x = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19,
20, 21, 22, 23, 24, 25, 26, 27, 28, 29]
y1 = [20, 24, 8, 4, 12, 22, 31, 25, 15, 28, 12, 27, 22, 22, 27, 14, 32,
28, 8, 17, 2, 8, 29, 13, 14, 20, 11, 28, 8]
y2= [2, 32, 28, 1, 22, 11, 14, 27, 3, 31, 12, 20, 32, 24, 24, 16, 7, 10,
12, 11, 3, 32, 10, 20, 14, 14, 3, 25, 14]
point_labels1 = ['A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1']
point_labels2 = ['B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1']
fig = plt.figure()
ax = fig.add_subplot(111)
ax.set_title('The red point should be on the path')
plt.plot(x, y1, 'bo', x, y2, 'go')
ax.grid(True)
ax.set_xlim(0.0)
ax.set_ylim(0.0)
fig.autofmt_xdate()
plt.xticks(range(0, 40, 1))
plt.yticks(range(0, 40, 1))
plt.xlabel('Longitude')
plt.ylabel('Latitude')
plt.legend(('Model length', 'Data length'),
'best', shadow=True, fancybox=True)
for i, label in enumerate(y1):
plt.text (x[i], y1[i]+0.2, label,
horizontalalignment='center' )
for i, label in enumerate(y2):
plt.text (x[i], y2[i]+0.2, label,
horizontalalignment='center' )
ax.autoscale_view()
plt.savefig('test.png')
plt.show()
I just remembered that there has been a bug in old version of matplotlib that annotation_clip parameter is not correctly set when given as a keyword parameter of "annotate" function. The bug has been fixed. http://www.mail-archive.com/mat...@li.../msg15068.html As a workaround, use ann = pylab.annotate('',(-1,3.1),(0,3.1),va='center',ha='center', arrowprops=dict(arrowstyle='<->')) ann.set_annotation_clip(False) Regards, -JJ On Sun, Aug 29, 2010 at 5:59 AM, Stan Schymanski <ss...@bg...> wrote: > Hi JJ, > > Thanks for the advice. However, the annotation_clip=False addition does not > make a difference to me. I am using Matplotlib from within Sage, though; not > sure if this makes it behave differently. > > Cheers > Stan > > On 8/28/10 5:09 PM, Jae-Joon Lee wrote: >> >> I think this change has been there for a while. >> For recent versions of matplotlib, the default behavior of annotate is >> that, when xycoords=="data", the arrow is drawn only when the >> annotated point is inside the axes. >> To override this behavior, use annotation_clip keyword parameter. >> >> >> pylab.annotate('',(-1,3.1),(0,3.1),va='center',ha='center', >> arrowprops=dict(arrowstyle='<->'), annotation_clip=False) >> >> Regards, >> >> -JJ >> >> >> On Fri, Aug 27, 2010 at 9:21 PM, Stan Schymanski<ss...@bg...> >> wrote: >> >>> >>> Dear all, >>> >>> I don't know which update it was that broke it, but this used to work: >>> >>> import numpy >>> import pylab >>> pylab.clf() >>> fig = pylab.figure(1,figsize=(8,5)) >>> ax = fig.add_subplot(111, autoscale_on=False, xlim=(-1,5), >>> ylim=(-4,3)) >>> >>> t = numpy.arange(0.0, 5.0, 0.01) >>> s = numpy.cos(2*numpy.pi*t) >>> line, = ax.plot(t, s, lw=3, color='purple') >>> pylab.text(-0.5,3.2,'no data',ha='center') >>> >>> pylab.annotate('',(-1,3.1),(0,3.1),va='center',ha='center',arrowprops=dict(arrowstyle='<->')) >>> pylab.savefig('blah.png') >>> >>> This used to plot an arrow under the text 'no data' but above the main >>> plot. Now this arrow does not appear unless at least part of it is within >>> the plotting area. Change one of the '3.1' in the code above to, say, 3.0 >>> and the whole arrow is displayed. Is this a bug or is there a new way of >>> achieving what I want? >>> >>> Thanks for your help already! >>> >>> Cheers >>> Stan >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program >>> Be part of this innovative community and reach millions of netbook users >>> worldwide. Take advantage of special opportunities to increase revenue >>> and >>> speed time-to-market. Join now, and jumpstart your future. >>> http://p.sf.net/sfu/intel-atom-d2d >>> _______________________________________________ >>> Matplotlib-users mailing list >>> Mat...@li... >>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users >>> >>> > > -- > ________________________________________ > > Stan Schymanski > Scientist > Max Planck Institute for Biogeochemistry > PO Box 10 01 64 > D-07701 Jena, Germany > > Phone: +49.3641.576264 > Fax: +49.3641.577274 > WWW: http://www.bgc-jena.mpg.de/~sschym > > Biospheric Theory and Modelling Group > http://www.bgc-jena.mpg.de/bgc-theory/ > _________________________________________ > >
On 8/28/10 3:59 PM, Stan Schymanski wrote: > Hi JJ, > > Thanks for the advice. However, the annotation_clip=False addition does > not make a difference to me. I am using Matplotlib from within Sage, > though; not sure if this makes it behave differently. > FYI, matplotlib in Sage is still at matplotlib 0.99.3. We're working on upgrading it to 1.0.0. Stan, if you want, could you try installing the 1.0.0 Sage matplotlib spkg and seeing if that works? You can do it by doing: sage -i http://sage.math.washington.edu/home/jason/matplotlib-1.0.0.spkg (the ticket is http://trac.sagemath.org/sage_trac/ticket/9221 ) Matplotlib 1.0.0 changes how axes labels work, so if you want to do axes labels, then you'll have to also install the patch listed at the ticket. Thanks, Jason
Hi JJ,
Thanks for the advice. However, the annotation_clip=False addition does
not make a difference to me. I am using Matplotlib from within Sage,
though; not sure if this makes it behave differently.
Cheers
Stan
On 8/28/10 5:09 PM, Jae-Joon Lee wrote:
> I think this change has been there for a while.
> For recent versions of matplotlib, the default behavior of annotate is
> that, when xycoords=="data", the arrow is drawn only when the
> annotated point is inside the axes.
> To override this behavior, use annotation_clip keyword parameter.
>
>
> pylab.annotate('',(-1,3.1),(0,3.1),va='center',ha='center',
> arrowprops=dict(arrowstyle='<->'), annotation_clip=False)
>
> Regards,
>
> -JJ
>
>
> On Fri, Aug 27, 2010 at 9:21 PM, Stan Schymanski<ss...@bg...> wrote:
>
>> Dear all,
>>
>> I don't know which update it was that broke it, but this used to work:
>>
>> import numpy
>> import pylab
>> pylab.clf()
>> fig = pylab.figure(1,figsize=(8,5))
>> ax = fig.add_subplot(111, autoscale_on=False, xlim=(-1,5),
>> ylim=(-4,3))
>>
>> t = numpy.arange(0.0, 5.0, 0.01)
>> s = numpy.cos(2*numpy.pi*t)
>> line, = ax.plot(t, s, lw=3, color='purple')
>> pylab.text(-0.5,3.2,'no data',ha='center')
>> pylab.annotate('',(-1,3.1),(0,3.1),va='center',ha='center',arrowprops=dict(arrowstyle='<->'))
>> pylab.savefig('blah.png')
>>
>> This used to plot an arrow under the text 'no data' but above the main plot. Now this arrow does not appear unless at least part of it is within the plotting area. Change one of the '3.1' in the code above to, say, 3.0 and the whole arrow is displayed. Is this a bug or is there a new way of achieving what I want?
>>
>> Thanks for your help already!
>>
>> Cheers
>> Stan
>>
>>
>> ------------------------------------------------------------------------------
>> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
>> Be part of this innovative community and reach millions of netbook users
>> worldwide. Take advantage of special opportunities to increase revenue and
>> speed time-to-market. Join now, and jumpstart your future.
>> http://p.sf.net/sfu/intel-atom-d2d
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
>>
--
________________________________________
Stan Schymanski
Scientist
Max Planck Institute for Biogeochemistry
PO Box 10 01 64
D-07701 Jena, Germany
Phone: +49.3641.576264
Fax: +49.3641.577274
WWW: http://www.bgc-jena.mpg.de/~sschym
Biospheric Theory and Modelling Group
http://www.bgc-jena.mpg.de/bgc-theory/
_________________________________________
Thanks for reporting. It turns out a (major) bug in gridspec, which should be fixed in r8667 & r8668. You code should work (except the rowspan and colspan needs to be exchanged for ax3 and ax4). Regards, -JJ On Sat, Aug 28, 2010 at 2:17 PM, Erik Tollerud <eri...@gm...> wrote: > If been playing around with the new Gridspec and subplot2grid stuff, > and it's pretty cool... one thing is confusing me though: It doesn't > seem to make any sense if the grid is non-square. For example, > suppose a 2x6 grid, which I will number like so: > > 1 3 5 7 9 11 > 2 4 6 8 10 12 > I want ax1 to take up 1,2,3, and 4; ax2 to be 5,6,7,8; ax3 should be 9 > and 11; and ax4 should be 10 and 12. My assumption would be to do > this: > > ax1=plt.subplot2grid((2,6),(0,0),rowspan=2,colspan=2) > ax2=plt.subplot2grid((2,6),(0,2),rowspan=2,colspan=2) > ax3=plt.subplot2grid((2,6),(0,4),rowspan=2,colspan=1) > ax4=plt.subplot2grid((2,6),(1,4),rowspan=2,colspan=1) > > But instead, apparently random partterns of axes appear and some to > override each other so that only one subplot is present in the end... > what's going on here? > > -- > Erik Tollerud > > ------------------------------------------------------------------------------ > Sell apps to millions through the Intel(R) Atom(Tm) Developer Program > Be part of this innovative community and reach millions of netbook users > worldwide. Take advantage of special opportunities to increase revenue and > speed time-to-market. Join now, and jumpstart your future. > http://p.sf.net/sfu/intel-atom-d2d > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users >
I think this change has been there for a while.
For recent versions of matplotlib, the default behavior of annotate is
that, when xycoords=="data", the arrow is drawn only when the
annotated point is inside the axes.
To override this behavior, use annotation_clip keyword parameter.
pylab.annotate('',(-1,3.1),(0,3.1),va='center',ha='center',
arrowprops=dict(arrowstyle='<->'), annotation_clip=False)
Regards,
-JJ
On Fri, Aug 27, 2010 at 9:21 PM, Stan Schymanski <ss...@bg...> wrote:
> Dear all,
>
> I don't know which update it was that broke it, but this used to work:
>
> import numpy
> import pylab
> pylab.clf()
> fig = pylab.figure(1,figsize=(8,5))
> ax = fig.add_subplot(111, autoscale_on=False, xlim=(-1,5),
> ylim=(-4,3))
>
> t = numpy.arange(0.0, 5.0, 0.01)
> s = numpy.cos(2*numpy.pi*t)
> line, = ax.plot(t, s, lw=3, color='purple')
> pylab.text(-0.5,3.2,'no data',ha='center')
> pylab.annotate('',(-1,3.1),(0,3.1),va='center',ha='center',arrowprops=dict(arrowstyle='<->'))
> pylab.savefig('blah.png')
>
> This used to plot an arrow under the text 'no data' but above the main plot. Now this arrow does not appear unless at least part of it is within the plotting area. Change one of the '3.1' in the code above to, say, 3.0 and the whole arrow is displayed. Is this a bug or is there a new way of achieving what I want?
>
> Thanks for your help already!
>
> Cheers
> Stan
>
>
> ------------------------------------------------------------------------------
> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> Be part of this innovative community and reach millions of netbook users
> worldwide. Take advantage of special opportunities to increase revenue and
> speed time-to-market. Join now, and jumpstart your future.
> http://p.sf.net/sfu/intel-atom-d2d
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
On 8/27/2010 10:13 PM, Adam Gustafson wrote: > I found a web page in which someone has done the horrible task of > figuring out how the hell you compile in Cygwin. Details below: > > http://innuendopoly.org/arch/matplotlib-cygwin > > In short, the Cygwin compile runs into TONS of errors as is, and it > seems the matplotlib developers aren't really supporting it. Trying > their techniques to see if it works, but so far looking good.... > What a friendly message... Matplotlib builds and works fine on cygwin when disabling the tkagg backend in setup.cfg. -- Christoph
On 08/27/2010 05:17 PM, Chiara Caronna wrote:
> Ok, it is a backend issue:
> I checked and I was using Qt4Agg
> as soon as I changed to TkAgg the script worked fine...
> still is this normal or is it a bug?
> thanks for your suggestion and help!
Chiara,
As a workaround for Qt4Agg, you can follow p.draw() with
fig.canvas.flush_events().
I think this is a bug that will be fixed easily by incorporating the
flush functionality in the draw method, but I'm not ready to commit to
it yet.
I wonder whether you were using a different backend when you were using
0.99.1.1? Or a different version of PyQt4?
Eric
> Chiara
>
> ------------------------------------------------------------------------
> From: chi...@ho...
> To: ben...@ou...
> Date: 2010年8月28日 03:01:54 +0000
> CC: mat...@li...
> Subject: Re: [Matplotlib-users] realtime plotting was working with
> matplotlib 0.99.1.1 and it doesn't with matplotlib 1.0.0
>
> I think I am using TkAgg but I am not sure, how can I check it?
>
> ------------------------------------------------------------------------
> From: ben...@ou...
> Date: 2010年8月27日 21:50:19 -0500
> Subject: Re: [Matplotlib-users] realtime plotting was working with
> matplotlib 0.99.1.1 and it doesn't with matplotlib 1.0.0
> To: chi...@ho...
> CC: mat...@li...
>
> On Fri, Aug 27, 2010 at 9:26 PM, Chiara Caronna
> <chi...@ho... <mailto:chi...@ho...>> wrote:
>
> Hi all,
> I have a script to update a plot in real time. It was working fine
> with matplotlib 0.99.1.1 but it doesn't work anymore with the new
> version.
>
> Here is the script:
>
> import numpy as n
> import pylab as p
>
> x=n.arange(10)
> y=n.random.randn(10)
> p.ion()
> fig=p.figure(1)
> ax=fig.add_subplot(111)
> line,=ax.plot(x,y,'ko-')
> for i in range(10):
> y=n.random.randn(10)
> line.set_data(x,y)
> p.draw()
>
>
> it is updating the plot correctly with matplotlib 0.99.1.1
> when I run it with matplotlib 1.0.0
> it doesn't show any picture at all
>
> Interestingly, if I add a line raw_input('ok') then it shows the
> plot and it updates it inside the loop....
>
>
> x=n.arange(10)
> y=n.random.randn(10)
> p.ion()
> fig=p.figure(1)
> ax=fig.add_subplot(111)
> line,=ax.plot(x,y,'ko-')
> raw_input('ok?')
> for i in range(10):
> y=n.random.randn(10)
> line.set_data(x,y)
> p.draw()
> raw_input('ok?')
>
> Any idea why it is doing this? Is it a bug or am I missing something?
>
> Thanks for your help,
> Chiara
>
>
> It seems to work fine for me using the GTKAgg backend. Which backend are
> you using? Also, admittedly, this is the trunk build, so it might have
> some fixes that weren't in the release.
>
> Ben Root
>
> ------------------------------------------------------------------------------
> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be
> part of this innovative community and reach millions of netbook users
> worldwide. Take advantage of special opportunities to increase revenue
> and speed time-to-market. Join now, and jumpstart your future.
> http://p.sf.net/sfu/intel-atom-d2d
> _______________________________________________ Matplotlib-users mailing
> list Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>
>
> ------------------------------------------------------------------------------
> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> Be part of this innovative community and reach millions of netbook users
> worldwide. Take advantage of special opportunities to increase revenue and
> speed time-to-market. Join now, and jumpstart your future.
> http://p.sf.net/sfu/intel-atom-d2d
>
>
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
If been playing around with the new Gridspec and subplot2grid stuff, and it's pretty cool... one thing is confusing me though: It doesn't seem to make any sense if the grid is non-square. For example, suppose a 2x6 grid, which I will number like so: 1 3 5 7 9 11 2 4 6 8 10 12 I want ax1 to take up 1,2,3, and 4; ax2 to be 5,6,7,8; ax3 should be 9 and 11; and ax4 should be 10 and 12. My assumption would be to do this: ax1=plt.subplot2grid((2,6),(0,0),rowspan=2,colspan=2) ax2=plt.subplot2grid((2,6),(0,2),rowspan=2,colspan=2) ax3=plt.subplot2grid((2,6),(0,4),rowspan=2,colspan=1) ax4=plt.subplot2grid((2,6),(1,4),rowspan=2,colspan=1) But instead, apparently random partterns of axes appear and some to override each other so that only one subplot is present in the end... what's going on here? -- Erik Tollerud