MATLAB: Odd behavior with a Simulink reserved name in a function

bugfunctionsimulink

Not sure what to make of this. Running R2017a. I have a numeric double precision variable named f14n. I save it to a .mat file. I call a function that loads the mat file with variable f14n in it, and it becomes a Simulink model. This of course crashes the function because I'm treating f14n as a numeric variable. Threw together some ugly code (below) to reproduce what I'm describing. Variable f14n is fine in the calling script, but it launches a Simulink window in the function. Is this a bug or am I breaking a bunch of scripting rules here? Thanks.

f14n=1:10; 
save junk.mat f14n
x=10;
dum=junk_func(x);
%%%%%%%%%%
function dum = junk_func(dum2)
load junk.mat
f14n
dum=0

Best Answer

Don't "poof" variables into the workspace like that. When MATLAB parsed junk_func it needed to know to what f14n referred. Since there was no indication in the code that it was a variable, and there is a Simulink® model available by that name, it treated that reference as opening that model.

Related Solutions

MATLAB: Best way to rename a loaded variable

Say you have the name of your variable:

VAR = 'S';

Now you want to load that variable, but with the name T. This method follows the general rule of thumb to avoid 'poofing' variables into the workspace.

T = load('myfile',VAR);  % Function output form of LOAD
T = T.(VAR)

MATLAB: What is the best way to get the name of a variable in a script

No, there is no built-in function and your way is actually clever.

And yes, the fact that load and save require variable names instead of the variable themselves feels awkward and prevent easy refactorisation.

Of course, if you go your way, you have to make sure that the code that reads the mat file can cope with changing variable names

Best Answer

Related Solutions

MATLAB: Best way to rename a loaded variable

MATLAB: What is the best way to get the name of a variable in a script

Related Question