From: Humufr <hu...@ya...> - 2005-02-17 22:17:13
|
with: test = [ 32.539772 32.504516 32.47944 32.380905 32.31546 32.193687 32.20433 32.008384 32.081062 32.065277 31.934586 32.09236 31.952614 32.146781 31.724289 31.52745 31.535683 31.596657 31.543633 31.562935 31.882072 31.717575 31.675995 31.609718 31.52964 31.4748 31.325775 31.239838 31.350319 31.172882 31.58982 31.549728 31.277122 31.196587 31.15017 30.995155 30.917984 31.02172 30.932365 31.364365 31.20729 30.92582 ] toto = [ 4781.7 4813.9 4846.1 4878.3 4910.5 4942.7 4974.9 5007.1 5039.3 5071.5 5103.7 5135.9 5168.1 5200.3 5232.5 5264.7 5296.9 5329.1 5361.3 5393.5 5425.7 5457.9 5490.1 5522.3002 5554.5 5586.7 5618.9 5651.1 5683.3002 5715.5 5747.7 5779.9 5812.1 5844.3002 5860.4 5876.5 5908.7 5940.9 5973.1 6005.3002 6037.5 6069.7 ] max(test) = 36.347007 plot (toto,test) I obtain axes between: x= [4600,6200] y= [0,5000] matplotlib CVS version. |
From: John H. <jdh...@ac...> - 2005-02-18 15:28:41
|
>>>>> "Humufr" == Humufr <hu...@ya...> writes: Humufr> matplotlib CVS version. There was a bug in the autoscaler in CVS briefly before the 0.72 release, but this was fixed. I reformatted your example into python code and it runs fine with current CVS. I appreciate the report, but could I ask you to do 2 things next time? Please send proper python code which exposes the the bug (eg your lists are not python lists) and report either the matplotlib version that exposes the bug, or if you are using CVS, the revision number. For example, if you suspect a bug in the ticking (where the autoscaler lives) > cvs status lib/matplotlib/ticker.py =================================================================== File: ticker.py Status: Up-to-date Working revision: 1.14 Repository revision: 1.14 /cvsroot/matplotlib/matplotlib/lib/matplotlib/ticker.py,v There is a problem with sourceforge that non-developer CVS checkouts have long lags (eg the CVS version you get may be older than the latest release!) but sourceforge says they are trying to fix this. Thanks! JDH |