Thanks Tony for the answer. windows matplotlibrc is not this one, so no bug in windows.
I think I found the problem. Just look at the two screen shots, one in okular, one in foxitreader. this is the pdf which is attached in the first email. that is why I thought there is a problem with linux. In this day and age you can not trust your eyes
So by putting mew > 0, the problem would be solved I suppose. will try it Monday.
Once more, thanks for help,
Have a nice weekend,
On Fri, Aug 5, 2011 at 10:15 PM, Tony Yu <tsyu80@…287…> wrote:
On Fri, Aug 5, 2011 at 2:41 PM, Amir Jahanshahi <pajoohesh@…83…287…> wrote:
The code for image-windows and image-linx comes from here:
That is why I think the problem is in linux. And the pdf which is attached along with the png image named flow-rate are executed in linux which are different. in windows both are the same.
So I guess there’s two separate issues: 1) pdf vs png output. 2) windows vs linux output.
- I have no idea what could be causing the difference in pdf vs png output. They’re rendered the same on my system, so I can’t be of much help.
- I still think the linux output is correct—assuming you’re using the matplotlibrc file you attached. Yes, the example on the matplotlib website has arrows on the error bars, but in your matplotlibrc file, you’ve set lines.markeredgewidth to 0. Thus, you should expect the arrow heads/tails to disappear. The default matplotlibrc has a nonzero markeredgewidth, which is why the heads/tails are visible on the website. So to reiterate, linux seems to be giving the correct behavior. Now, for the windows output, are you certain you’re using the same matplotlibrc? In other words, are you setting markeredgewidth to 0. If so, then I’d say there’s a bug in the windows output.