memory phenomenon
5 Ansichten (letzte 30 Tage)
Ältere Kommentare anzeigen
Hi. I made a m-code for image processing, but I detect some strange effect. For example I use the following code:
vid = videoinput('winvideo', 1,'YUY2_320x240');
set(vid,'ReturnedColorSpace','rgb','TriggerRepeat',1000,'FramesPerTrigger',1);
vid_src=getselectedsource(vid);
set(vid_src,'BacklightCompensation','off','ExposureMode','manual','WhiteBalanceMode','manual','WhiteBalance',6500);
triggerconfig(vid,'manual');
start(vid);
for step=1:1:inf
tic
trigger(vid);
A=getdata(vid,1);
B=rgb2hsv(A);
.
.
. %some code
.
.
figure(4);imshow(A);hold on;
plot(q,p,'Marker','*','Color','r');
flushdata(vid,'triggers');
toc
end
I observe the result for the time of execution and I saw that every cycle the time is increasing and become bigger and bigger. So algorithm is working slower and slower. I can't understand why this is happening. I use a flushdata to clear the memory, but it dosen't matter whether I use it or not. When the data are logged in the memory GETDATA function clear it when I take the data into the workspace. Can somebody tell me what is the reason and how I can fix the problem?
0 Kommentare
Akzeptierte Antwort
Walter Roberson
am 7 Dez. 2011
You do not show figure 4 as having its contents cleared, so the "hold on" would result in another graph being added to the figure for each loop iteration.
4 Kommentare
Weitere Antworten (0)
Siehe auch
Kategorien
Mehr zu Image Preview and Device Configuration finden Sie in Help Center und File Exchange
Produkte
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!