Size of matrix changing when input through function

2016 11 29
0 个回答
更新时间：2016 12 1
10 次查看（30 天）

0 个投票

Something odd is occurring when I input a matrix through a function. I have the following in a script:
range = [500,2000];
increment = 100;
duty = range(1):increment:range(2);
It gets passed into the following function:
ODE_output = get_ODE(duty);
and the length of 'duty' within the get_ODE function goes from 16 to 186 columns. Instead of keeping the original matrix it creates a new one with the following size:
duty = 150:10:2000
I know at one point I had changed my conditions to the above, however I do not understand why it keeps reverting to that specific duty matrix.
I've cleared variables and restarted MATLAB numerous times. I've debugged this for a while and the duty matrix isn't called again until the get_ODE function.
Any ideas on why it's happening and how to fix this?
Thanks!

7 个评论
显示 5更早的评论 隐藏 5更早的评论

Guillaume
Guillaume 2016-11-29
Well, what is the code of get_ODE?
Note that whatever happens in the function get_ODE does not affect the values of the variables in your base workspace (except ODE_Output of course), even if they have the same name.
Domenick Avanzi
Domenick Avanzi 2016-11-29
编辑：Domenick Avanzi 2016-11-29
Duty is called two times within the ODE_output function. The following lines:
function ODE_output = get_ODE(duty)
mSize = length(duty);
for i = 1:mSize
force(i) = -g*duty(i);
end
end
Note this is an extremely abbreviated version of the code. The rest of it has no impact on duty. So the length of mSize ends up being 186, and if I print the duty at any point in get_ODE (first line, last line), I get a 1 x 186 matrix.
Daniel kiracofe
Daniel kiracofe 2016-11-29
I'd suggest you post your code. If not the entire code, at least post a large enough segment that we can run it and reproduce the problem. It's hard to debug "weird" things like this without seeing the whole code.
bio lim
bio lim 2016-11-30
When your duty is called by get_ODE, the value of duty will not be changed in your base workspace even if the size of duty changes inside your function. Are you sure, you are missing a part in your script where you mistakenly change your duty variable?
the cyclist
the cyclist 2016-11-30
I second the suggestion to post code that displays the problem. I recommend trying to distill the code down to the bare minimum that exhibits the behavior. (Often, that process itself will expose the issue.)
Domenick Avanzi
Domenick Avanzi 2016-12-1
Thank everyone. I actually figured it out. In my get_ODE function I was calling on a .mat file, however when I initially created the .mat it saved the entire workspace instead of the variables I wanted. This explains why it was reverting to previous workspace variables.
Guillaume
Guillaume 2016-12-1
and that is why you never use plain load. Instead you assign it to a variable and assign the file content as fields of that variable. That way, you never run the risk that load is going to overwrite any of your current variables.

请先登录，再进行评论。

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

回答（0 个）

类别

在 帮助中心 和 File Exchange 中查找有关 Creating and Concatenating Matrices 的更多信息

标签

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by