I have a code which is definitely correct, but the loglog graph wont work properly.

Question

Rayhaan Bhikha 2016-3-8

2
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/272199-i-have-a-code-which-is-definitely-correct-but-the-loglog-graph-wont-work-properly

移动：DGM 2024-2-11

clear all
x=linspace(-1,1,40);
t=linspace(0,1,20);
n=[5,10,20];
hold on
for i=1:3
    U=(exp(-(pi.^2)*t(n(1,i)))+sin(t(n(1,i))))*sin(pi*x);
    v=CN(n(1,i));
    En(i)=max(abs(U-v));
end
loglog(n,En,'--')
hold on
loglog(n,n)

this is the graph I get

this is the graph i should get

2 个评论
显示无隐藏无

Star Strider 2016-3-8

What’s ‘CN’?

John D'Errico 2024-2-10

编辑：John D'Errico 2024-2-10

It is definitely perfectly, absolutely correct, BUT, it does not work. Why does that seem to put the lie to your claim of correctness?

The point being, a simple definition of correctness of code, is that it works as designed, and it does what it is supposed to do.

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Steven Lord 2016-3-8

8
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/272199-i-have-a-code-which-is-definitely-correct-but-the-loglog-graph-wont-work-properly#answer_212861

在 MATLAB Online 中打开

You told MATLAB to " hold on ". That means MATLAB is allowed to change a few properties of the axes (from that documentation page: "MATLAB® adjusts axes limits, tick marks, and tick labels to display the full range of data.") but keeps most properties (including XScale and YScale, the properties that control whether the axes are in linear or log scale) unchanged.

You can explicitly tell MATLAB to change the scale at the end of your code and it will do it, but HOLD prevents it from changing the scale automatically.

set(gca, 'XScale', 'log', 'YScale', 'log');

If you had a handle to the axes in a variable, like ax, you could instead using the dot notation to change the scales.

ax.XScale = 'log';
ax.YScale = 'log';

4 个评论
显示 2更早的评论隐藏 2更早的评论

Hank Lin 2020-5-24

20200524

Thank you very much. :)

Jürgen 2024-2-10

移动：DGM 2024-2-11

I can understand the arguments of Steven Lords answer.

However the arguemtns are kind of artificial and the behaviour of two loglog in succession guarded wiht hold on is simply unexpected and irritating. It should be regarded as an error and be corrected in the next release.

I stumpled several times on that obstacle, look up the topic, apply the workaround, forget it again and stumble again into the same trap after a while.

请先登录，再进行评论。