Send variable from c to matlab

Question

zohar 2011-10-30

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/19829-send-variable-from-c-to-matlab

评论： Walter Roberson 2018-6-13

采纳的回答： Walter Roberson

在 MATLAB Online 中打开

Hi all,

I have a c program that set variable into matlab, using matlab Engine.

ep = engOpen(NULL);
...
engPutVariable(ep, "var", var);

Everything is OK except that I want to send the variable,

to regular matlab workspace

and not to matlab Engine.

Any help ???

thx

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

Marisol Sierra 2018-6-13

Hey did you solve this problem?

请先登录，再进行评论。

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

Answer 1

Walter Roberson 2011-10-30

1
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/19829-send-variable-from-c-to-matlab#answer_26194

Your C program is the "MATLAB engine" in MATLAB terminology.

I have not been able to establish this as a fact so far, but as best I can tell reading between the lines, engPutVariable() writes the variable into the "base workspace" of the MATLAB process associated with the engine.

There is no mechanism provided to write a variable in to the workspace of a particular function because no functions can be running in the MATLAB process at the time engPutVariable() is executed (or so my reading suggests.)

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

Walter Roberson 2011-10-31

What does a "regular matlab workspace" look like to you?

Regular MATLAB offers:

- A "base" workspace. This is the same workspace that you get if you work entirely at the command line. The variables that exist by default in the "base" workspace are only "i" and "j", both with the value sqrt(-1) . Everything else, including "ans", is only created at need.

- A "global" workspace. This workspace is accessible on a variable-by-variable basis, by using the "global" command followed by a variable name to indicate that the global instance should be accessed. There are no variables in the global workspace by default.

- one workspace per function which is currently in the call chain (either actively running, or called another function and so was suspended itself, or was interrupted by a timer or a callback). This workspace contains all of the variables used by the function, and other than in special circumstances, the workspace will have all those variables cleared out when the workspace goes out of scope. By default, each function executing or in temporary suspension has a separate workspace.

- one workspace per function that is not currently in the execution stack, if the function is the owner of a variable that is being used as part of an active closure. This one is a bit difficult to explain. By default, closures do not exist.

None of these different types of workspaces has any obviously different appearance than any other. You would probably have to go back to MATLAB version 4 for obvious differences in the look of a workspace.

Are you perhaps talking about a desktop or inspector tool of some kind? Or are you perhaps referring to the appearance of the command prompt or command line??

Perhaps posting a screen short might help.