MATLAB: Does evalin(…, assignin(…)) not work in MATLAB R2015b and more recent versions

15bassigninbasecallerchainevalinMATLAB

From my function workspace, I want to get a variable from my base workspace and assign it to my current function workspace. In previous versions of MATLAB, I was able to do this using the command:

>> evalin('base','assignin(''caller'',''varName'',varName)');

However, in MATLAB R2015b and more recent versions, this command no longer works. It does not give any errors, but 'varName' is not created in the function workspace.

Why does "evalin" no longer work for this use case?

Best Answer

This is actually the expected behavior, as "evalin" and "assignin" cannot be used recursively to reach more than one level deep in the function call stack.

For more information, see the 'Limitation' section of the "evalin" documentation page:

https://www.mathworks.com/help/matlab/ref/evalin.html

This change was made in MATLAB R2015b (so R2015a and earlier versions have the old behavior you observed in R2014b) to standardize the behavior of "evalin".

As a workaround for MATALB R2015b and more recent versions, you can change the line

>> evalin('base','assignin(''caller'',''varName'',varName)');

>> varName = evalin('base', 'varName');

which will create a new variable, 'varName', in your function workspace with the same value as 'varName' in the base workspace.

Related Solutions

MATLAB: Does “setVariable” in Simulink Test not update variables

In R2019b, the behavior of "setVariable" is modified such that it overrides only model variables (as opposed to MATLAB variables).

I attached a simpler model ("SimpleVars_R2019b.slx") to help illustrate this. This model has two "From Workspace" blocks, one set to "a" and one set to "evalin('base', 'b')".

If you call "findVars" on this model, only "a" is considered to be a model variable, even though both output their timeseries when run:

>> vars = Simulink.findVars('SimpleVars_R2019b')
vars = 
    VariableUsage with properties:
            Name: 'a'
          Source: 'base workspace'
      SourceType: 'base workspace'
           Users: {'SimpleVars_R2019b/From↵Workspace'}

The R2019b behavior provides stricter control of overrides and achieves parity with other Simulink tools. You will need to update the model to use variables which are recognized by Simulink.

Please update the "From Workspace" block variable parameter from "evalin('base', 'y_coordinate')" to just "y_coordinate". Then save the model and run the test file again.

You should observe that "setVariable" updates all of the variables now.

MATLAB: How can the “State name” parameter of discrete blocks be set using a variable

1. Add the following code in the callback function Discrete Block -> Block Properties -> Callbacks tab -> InitFcn

set_param(gcb,'StateName',eval(['myVariable']))

2. Initialize myVariable with char type data in the workspace with the name you wish to have in your generated code. For example:

>> myVariable = 'myStateName';

Best Answer

Related Solutions

MATLAB: Does “setVariable” in Simulink Test not update variables

MATLAB: How can the “State name” parameter of discrete blocks be set using a variable

Related Question