Access to memory store via global in matlab function
Ältere Kommentare anzeigen
Don't know how I managed this

Note how the second error report one simulation time step later exactly contradicts the first one from t=0.
I'm just using a matlab function to access a Simulink data store.
Here are the settings for it

Here is the code that raises the errors
% t is input from a clock block
% size(Screen)=[5 8]
function DOIT(t, Screen)
global CurrentSEPScreen;
if t==0 % Initialise - Shouldn't be necessary, but errors are raised
% Can't get rid of that error, trying different initialisation approaches.
Y=[32 32 32 32 32 32 32 32];
% CurrentSEPScreen(1,:)=Y;
% CurrentSEPScreen(2,:)=Y;
% CurrentSEPScreen(3,:)=Y;
% CurrentSEPScreen(4,:)=Y;
% CurrentSEPScreen(5,:)=Y;
CurrentSEPScreen=[Y;Y;Y;Y;Y];
else
for RowN=1:5
if any(Screen(RowN,:)~=CurrentSEPScreen(RowN,:))
CurrentSEPScreen(RowN,:)=Screen(RowN,:);
end
end
end
end
Antworten (1)
Fangjun Jiang
am 24 Okt. 2018
0 Stimmen
I think the warning message is clear. If you want to ignore this, go to Simulation, Model Configuration Parameters, Diagnostics, Data Validity, Data Store Memory block, and change the setting.
6 Kommentare
John Carter
am 24 Okt. 2018
Bearbeitet: John Carter
am 24 Okt. 2018
Fangjun Jiang
am 24 Okt. 2018
They are not contradicting. These write-after-write and read-before-write could all happen during the same simulation step. You can change the setting to ignore them.
John Carter
am 25 Okt. 2018
Bearbeitet: John Carter
am 25 Okt. 2018
Fangjun Jiang
am 25 Okt. 2018
The setting regarding how to report these data store memory access abnormally, either "use local settings", "disable all", "enable all as warnings" or "enable all as errors".
John Carter
am 1 Nov. 2018
Bearbeitet: John Carter
am 1 Nov. 2018
John Carter
am 1 Nov. 2018
Bearbeitet: John Carter
am 1 Nov. 2018
Kategorien
Mehr zu Sources finden Sie in Hilfe-Center und File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!
