Plot range of values as bars
Ältere Kommentare anzeigen
I'm trying to figure out how to plot a range of y values as bars. For example if my x-axis is days of the month, my bars would represent the range between the max and min temperatures for that day. The bar would be the shaded portion between the min and max values for each day. Kind of like a boxplot without all the statistical information included. Can't figure out how to do this. Any suggestions?
Akzeptierte Antwort
Weitere Antworten (4)
OK, the bar option works pretty easily, actually, with some handle-diving for how things are organized.
% first make up some data...
x=1:30; % 30 days hath...
y=[randi(90,size(x)); % max, min temp distributions
randi(70,size(x))];
ix=diff(y)<0; % fixup to make sure all
y(:,ix)=flipud(y(:,ix)); % max are > min
To use bar to get scaled as between min/max for the second bar, the bar definitions are intervals [0 L] and [L H-L] so the sum or max of second bar in the stacked plot is L+(H-L) = H instead of H+L if plot L,H as normal.
hB=bar([y(1,:); diff(y)].', ...
'stacked','FaceColor','flat','EdgeColor','w');
hB(1).CData=ones(length(x),3); % set the color of bottom to background (white)
ends up with

In the end, this doesn't seem much more effort to fix up actual temperature min/max data by the difference than would be to compute the error values for the errorbar solution. It's a little more abstract in needing to set the color for the one bar so with Steven's observation of the new property for the error bar ends lengths being able to be set, that's probably the better solution.
BTW, the idea of simply
delete(hB(1))
to clear the first bar instead of rewriting the 'CData' doesn't work-- bar then turns the plot into a standard bar plot with zero baseline; doesn't keep the 'stacked' property any longer.
4 Kommentare
Thomas Burbey
am 22 Aug. 2018
dpb
am 22 Aug. 2018
Just the RGB 3-vector of [1 1 1] for 'w' for each element of the CData array for the first bar object which is the bottom bar of the two stacked bars...there are two bar object handles, not 30; the two objects are the bottom and top pieces, not a two-segmented bar for each day if that makes sense?
If you have changed the graph background color from white, then you would retrieve it and use its RGB triplet instead.
OH!!! Just had idea -- wonder if one couldn't just delete the one set of handles instead...
I did also figure out how to do the scaling correctly; I'll amend the above ANSWER to correct that earlier oversight when get back home -- just looked in again after cleaning up to head to town but have got to get gone now...the idea is to subtract the low from the high so the second bar is the difference; then the sum is the total and the top bar will range over the min-max, not max-total as is by default.
[Thomas Answer moved to comment...dpb]
I still get an error with the line: hB(1).CData =ones(length(x),3) as it doesn't know what CData is. I'm assuming this is trying to access the first column in the hB bar workspace. Is this a version issue? I'm running R2016b? Otherwise I get what you're doing. It seems to me that the bar function is simply too limited. I'd think this would be a fairly common practice to want to do what I'm asking here.
As noted before, hB(1) is the bottom bar; hB(2) is the top; the bar objects aren't by column but by level for 'stacked'
On 'CData', indeed the bar object was redefined sometime after R2016b; I am on R2017b here. For R2016b, modify the above to
hB=bar([y(1,:); diff(y)].','stacked','EdgeColor','w');
hB(1).FaceColor='w'; % set the color of bottom to background (white)
But, it seems to me that while interesting to show what can manage to be done with enough creativity, that Star's simple plot solution is the best way to go, isn't it?
And, yes, I fully agree that bar is terribly limited in both what it can do "out of the box" easily and in subsequently trying to mung on it to do obviously needed/wanted things. I've complained for 20+ years there should be something like 'baseline' on a column basis.
Yuvaraj Venkataswamy
am 22 Aug. 2018
0 Stimmen
1 Kommentar
Thomas Burbey
am 22 Aug. 2018
Yuvaraj Venkataswamy
am 22 Aug. 2018
For example,
if true
x = 1:1:12;
y = [34 23 47 28 41 35 21 18 38 20 30 32];
bar(x,y)
end
2 Kommentare
Thomas Burbey
am 22 Aug. 2018
Yuvaraj Venkataswamy
am 22 Aug. 2018
Bearbeitet: Yuvaraj Venkataswamy
am 22 Aug. 2018
You mean,
if true
ylim([min_value max_value])
end
For example, ylim([0 40]);
Steven Lord
am 22 Aug. 2018
0 Stimmen
3 Kommentare
dpb
am 22 Aug. 2018
But afaik, Steven, there's no way to get rid of the end bars on the error bars with errorbar and they're also magnified when 'linewidth' is increased to draw the bar more like a bar or boxplot.
If OP is satisfied with that or the default then it's pretty simple, yes.
Steven Lord
am 22 Aug. 2018
For at least the first part of your comment, if you're using release R2016b or later you can use the CapSize property introduced in that release. I just checked in release R2018a and setting CapSize to 0 is allowed.
dpb
am 22 Aug. 2018
Ah, in that case, probably simpler than the bar...wasn't aware of that modification/new property.
Kategorien
Mehr zu Errorbars finden Sie in Hilfe-Center und File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!