Axis labels - subscripts not working

Question

Wiktor Wróblewski 2021-11-29

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/1598449-axis-labels-subscripts-not-working

评论： dpb 2023-5-13

采纳的回答： dpb

Morning all,

could you please help me with subscripts in axis labels?

When I use code:

figure(1);
title('Generation change')
xlabel('Time [sec]')
ylabel('ΔP_G [pu]')
legend('ΔP_G for 1%','ΔP_G for 5% ','Location','southeast');

Everything is working.

However, when I use "plot" command, subsrcipt on y axis is not working anymore:

figure(1);
plot(PT1);
hold on;
plot(PT2);
grid on;
title('Generation change')
xlabel('Time [sec]')
ylabel('ΔP_G [pu]')
legend('ΔP_G for 1%','ΔP_G for 5% ','Location','southeast');

Data I am using is timeseries from Simulink. Subscripts in legend are working in both cases. Thanks in advance.

0 个评论
显示 -2更早的评论隐藏 -2更早的评论

请先登录，再进行评论。

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

Answer 1

dpb 2021-11-29

2
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/1598449-axis-labels-subscripts-not-working#answer_842964

编辑：dpb 2021-11-29

What does

hAx=gca;hAx.YLabel.Interpreter

return after the figure?

If you get no error message, the above symptoms indicate that the label 'Interpreter' property is somehow set to default to 'none'.

If it were 'tex', the string would be interpreted as desired, it it were 'latex' it would generate an error about invalid interpreter syntax.

ADDENDUM

Given the additional info from the series of comments below, the workaround to your problem seemingly caused by Simulink being overly aggressive in its setting of MATLAB default graphics parameters is to use the explicit named parameter when calling x/ylabel

ylabel('ΔP_G [pu]','Interpreter','tex')

etc., SHOULD do it. If, for some reason, the instantiation of ylabel that is being calls ignores the named parameter (if it does, I'd also call that a bug and report it), then you can always revert to forcing it after the fact...

hYLbl=ylabel('ΔP_G [pu]');          % write label, save handle accept default interpreter
hYLbl.Interpreter='tex';            % now brute-force it to be wanted 'tex'

Changing the interpreter property for the object itself will change the behavior of the object; setting the default property after the fact won't; the object is already in existence and the default behavior is only looked at on object creation.

That's why the set options above didn't work -- I didn't think of the behavior actually being embedded in the function calls themselves; that's just so egregious I didn't think any chance TMW would have done -- I presumed it had gotten set once by accident and fixing it once would fix it forever.

12 个评论
显示 10更早的评论隐藏 10更早的评论

dpb 2021-11-29

编辑：dpb 2021-11-29

If I were a MATLAB user with Simulink, I'd definitely regard Simulink changing my MATLAB default settings behind my back as a bug. To modify the groot value is egregious because, as you've discovered, that changes everything that happens from that point forward.

There are ways for Simulink to force that behavior on its plots only by setting the property at the figure or axes level instead of root; not having done it that way is the reason I would definitely consider the present behavior you describe as a bug. It is, at least, "rude" in the extreme, even if TMW were to claim WAD ("working as designed", one of the favorite outs of developers when they don't want to admit to/fix a nonfatal bug).

Anyways, to work around it given that it appears that the version of legend that gets invoked if you use Simulink-generated data which triggers a specific axes format automagically will be to set the 'Interpreter' property specifically when you use x/ylabel since the behavior seems to be buried inside them.

ylabel('ΔP_G [pu]','Interpreter','tex')

etc., SHOULD do it. If, for some reason, the instantiation of ylabel that is being calls ignores the named parameter (if it does, I'd also call that a bug and report it), then you can always revert to forcing it after the fact...

hYLbl=ylabel('ΔP_G [pu]');          % write label, know interpreter may be 'none'
hYLbl.Interpreter='tex';            % now brute-force it to be wanted 'tex'

Changing the interpreter property for the object itself will change the behavior of the object; setting the default property after the fact won't; the object is already in existence and the default behavior is only looked at on object creation.

That's why the set options above didn't work -- I didn't think of the behavior actually being embedded in the function calls themselves; that's just so egregious I didn't think any chance TMW would have done -- I presumed it had gotten set once by accident and fixing it once would fix it forever.

dpb 2021-11-30

编辑：dpb 2021-11-30

OBTW, even though the above will mask the symptoms, if indeed the value in groot is being reset, that's going to have ramifications all over the rest of MATLAB because the above won't reset it back to the default 'tex' value; you'll still have to execute the set code every stinkin' time you plot one of those time traces.

As noted, this behavior is "just plain rude!" and I can't believe it hasn't been observed before, unless it's a brand new behavior.

What does

whos f1

where f1 is one of these timeseries variables return? Is it a unique class or a struct or something, not just an array of double? That would also indicate Simulink has its own plot.

How about

which -all plot

return? I've never seen a Simulink installation so don't know if it produces a specific legend function that is getting called based on the object type of the time series data or if it might be somewhere else more deeply buried in the bowels.

I rarely, if ever, suggest munging on a TMW file, but this is a case I might go spelunking and see if I could find the culprit code line and neuter it.

For confirmation, try the following and post the result...

get(groot,'factoryAxesTickLabel')
figure
plot(randn(10,1))
hAx=gca;
hAx.TickLabelInterpreter
hold on
plot(f1)
hAx.TickLabelInterpreter

Andrei 2023-5-13

Hi, I am currently having the same problem, and when I try to reset it to factory settings, I get the following

set(groot,'factoryAxesTickLabelInterpreter','tex')

Error:

Error using matlab.ui.Root/set

Factory properties can only be queried, not set.

What should I do?

dpb 2023-5-13

You don't set factory settings/or the root object as noted; you instead clear temporary and/or personal settings to restore the factory default programmtically. You should also be able to reset with the Preferences menu item, the problem will be if this is still the behavior with a time series, it'll destroy it again next time you plot one.

I had never found the timeseris object to be of much, if any, help; it always seemed to have some undesired behavior or lacked the ability to do something I wanted to do so I gave it up (or, actually, never adopted it as being of value) so hadn't discovered this aberrant behavior.

I would just use a timetable instead or just treat as regular double arrays to avoid the grief.

请先登录，再进行评论。

Answer 2

Cris LaPierre 2021-12-22

2
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/1598449-axis-labels-subscripts-not-working#answer_859930

I heard back. This was an intentional setting change introduced with Timeseries. The work around for now is to manually override the axis label interpreter setting:

PT1 = timeseries(rand(5,1));

PT2 = timeseries(rand(5,1));

figure(2)

plot(PT1)

hold on

plot(PT2)

hold off

grid on

title('Generation change')

xlabel('Time [sec]')

ylabel('ΔP_G [pu]')

legend('ΔP_G for 1%','ΔP_G for 5% ','Location','southeast')

% set YLabel interpreter back to 'tex'

ax = gca;

ax.YLabel.Interpreter = 'tex';

1 个评论
显示 -1更早的评论隐藏 -1更早的评论

dpb 2023-5-13

"...This was an intentional setting change introduced with Timeseries.:"

Just saw the latest plea from the wilderness and this follow-up, @Cris LaPierre. Why on earth would anybody choose to have done this dastardly deed? I can see no justification could possibly be to have done.

请先登录，再进行评论。