Borrar filtros
Borrar filtros

Units of CostOfNonAssignment in assignDetectionsToTracks

1 visualización (últimos 30 días)
Jacob Mevorach
Jacob Mevorach el 26 de Jun. de 2017
Comentada: Horst Steuer el 16 de Mayo de 2018
I'm having a little trouble understanding what units CostOfNonAssignment is in when employed in the built in function CostOfNonAssignment. My specific situation is I am using a cost matrix based on distance values (lets call their units "distance units") showing how far new detections are from current tracks and I have a CostOfNonAssignment of "n" where n is a positive integer. My assumption was that if a new detection appeared and no pre-existing track was within n distance units of said detection that this would result in a new track being created and if there was a preexisting track within n distance units from the new detection the new detection would be assigned to said track.
Specifically I've been using a value of 20. But strangely enough when I drop the value below 20 suddenly almost nothing is tracked anymore. I have to imagine that this number (CostOfNonAssignment) is not working at all the way I expected it to. If anyone had any insight into how the number works or how I could properly manipulate it I would be eternally grateful.
  1 comentario
Horst Steuer
Horst Steuer el 16 de Mayo de 2018
Perhaps this answer helps in this case: https://uk.mathworks.com/matlabcentral/answers/308185-assigndetectionstotracks-with-parameter-of-costofnonassignment#comment_568644

Iniciar sesión para comentar.

Respuestas (0)

Categorías

Más información sobre Computer Vision Toolbox en Help Center y File Exchange.

Community Treasure Hunt

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

Start Hunting!

Translated by