Bug in pcolor?
6 Ansichten (letzte 30 Tage)
Ältere Kommentare anzeigen
Hi,
Whenever I use pcolor for a checkerboard plot the lines of my x-axis and y-axis disappear. This problem can be reproduced even with the example in the matlab help!
Try this (looks OK):
figure;
pcolor(hadamard(20))
colormap(gray(2))
shading flat;
axis ij
axis square
and compare against this (x,y axis disappears):
figure;
pcolor(hadamard(20))
colormap(gray(2))
shading flat;
axis ij
For whatever reason using pcolor together with shading flat makes the axis disappear (only the axis on the bottom and left of the plot). Why is that and why does using the axis square command make a difference?
In principle the axis square command would fix the problem but I don't want my axes to be square. Using axis normal instead does NOT fix the problem...
Any ideas?
2 Kommentare
Walter Roberson
am 30 Dez. 2011
It took me a moment to see what you were describing; the solid line on the top and right sides are not present with a plain pcolor() if the OpenGL renderer is in effect. painters and zbuffer renderer do not have this difficulty.
Image Analyst
am 31 Dez. 2011
I was wondering why you're using pcolor() in the first place instead of image(). Do you know it's going to display a 19x19 grid and not a 20x20 grid? And the color of the tile in pcolor is not the value of the array you're displaying? When I ask I never have gotten a reason, all I get is people either not answering at all, or they say "No I never realized pcolor did that. That's not what I want."
Akzeptierte Antwort
Jan
am 30 Dez. 2011
It is not a problem of pcolor, but a bug in the OpenGL renderer. It appears in the standard 2D-view and with enabled stretch-to-fill behaviour (DataAspectRatioMode, PlotBoxAspectRatioMode, CameraViewAngleMode set to 'auto'): Rounding errors influence the clipping and lines of the box disappear for some combinations of axes size in pixels and limits of the axes. In addition the X-ticks appears at bad positions.
Workaround: Rotate the axes object by a tiny angle, which move the objects by less than a pixel:
% Display the problem:
figure('Renderer', 'OpenGL', 'Position', [360, 502, 560, 420]);
AxesH = axes;
pcolor(hadamard(20))
colormap(gray(2))
shading('flat');
pause(1);
% Fix the problem:
set(AxesH, 'CameraUpVector', ...
[-sin(0.0001), cos(0.0001), 0] .* get(AxesH, 'DataAspectRatio'));
Using the ZBuffer or Painters renderer is a simple and nice workaround, if you do not need transparency in the plot.
Changing the YLimits by some eps value works sometimes, but I have not been able to identify the underlying pattern. The consideration of the DataAspectRatio is important, because:
set(AxesH, 'CameraUpVector', [-sin(0.0001), cos(0.0001), 0]) % BAD!
can have very strange effects to the positions of the X- and Y-labels.
This bug existed in Matlab 6.5 already, so you are in touch with a very solid history.
1 Kommentar
Weitere Antworten (2)
Muhlbauer
am 3 Jan. 2012
1 Kommentar
Jan
am 3 Jan. 2012
It happens with LINE also, and to be exact, even *without* LINE:
figure('Renderer', 'OpenGL');
AxesH = axes('Units', 'pixels', 'Position', [40, 40, 200, 200], ...
'YLim', [0, 20.7], 'Box', 'on', 'XGrid', 'on', 'YGrid', 'on');
This shows, that it only depends on the limits and the extent of the AXES. PCOLOR is not the problem.
Siehe auch
Kategorien
Mehr zu 2-D and 3-D Plots finden Sie in Help Center und File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!