Multi-dimensional arrays indexing for an embedded matlab function in simulink
4 vues (au cours des 30 derniers jours)
Afficher commentaires plus anciens
Quick Baground: This is an embedded MATLAB function for simulink in which it takes the elements Base Image(An image containing 3 objects), Count(Number of Objects), BBox(Coordinates of Box surrounding each object). Then uses this to create 3 different images in which in each one one of the 3 different objects is blacked out by the Bbox.(NOTE: This algorithim needs to be somewhat versatile so the number of images regardless of the count needs to be stored in one final image) So here is the base code:
function images = fcn(boxes,c,baseimage)
%#codegen
persistent h;
if isempty(h)
h = vision.ShapeInserter('Fill',true,'Opacity',1.0);%Systems object to black out objects
end;
count = c(:,1);
image = baseimage(:,:,1);
dim = size(baseimage);
x = dim(1,1);
y = dim(1,2);
images = zeros(x , y);
for g = 1:count
Pts = rot90(boxes(:,g));%Rotate by 90 to meet input parameters for step function%
images(:,:,g) = step(h, image, Pts);%This is the step I have problem with described below in which the seperate images are blacked out and stored%
end
The Problem: That everytime I run the following code it goes into a debugging mode. No matter what I try I can't find away to take the 3 separate images and index them into one. The issue most likely resides with Simulink because the algorithm runs fine in just MATLAB. The solution doesn't have to be limited to just multi-dimensional arrays but anything that allows me to store my images and import them.
3 commentaires
Réponse acceptée
Denis Gurchenkov
le 26 Juil 2011
Please try replacing
> images = zeros(x,y);
with
> images = zeros(x,y,count);
Embedded MATLAB function block does not support growing arrays on assignment. Basically, if you want to have a 3-D array of x-by-y-by-count elements in the end, you have to allocate it as such at the beginning.
Let me know if the above fix does not work for you.
Cheers,
Denis.
2 commentaires
Fangjun Jiang
le 27 Juil 2011
That error message indicates something else. Right click the signal labeled as 'images', select 'signal properties', uncheck the option 'signal must resolved to workspace object'.
Plus de réponses (1)
Denis Gurchenkov
le 27 Juil 2011
Hi David-Linus,
As Fangjun said, these look like two different issues. Can you show me your model so I can see the problem?
Voir également
Catégories
En savoir plus sur Computer Vision with Simulink dans Help Center et File Exchange
Produits
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!