Closed A-acuto closed 1 week ago
Hi @orosoman-dstl and @sdhiscocks : I have applied the suggested changes to the text and references. Now all tracks follows the ground-truths better and there is no more track drifting.
Regarding @sdhiscocks question about the number of tracks: I tried using the GaussianMixtureInitiator
with unknown number of tracks (e.g. using the MultiTargetGroundTruthSimulator
) but I was not able to make it work properly with the tracking loop needed for the MFA data associator. Hence my approach of fixing the number of targets and start the tracks in this way.
Happy to discuss a more general solution (if possible with the current setup).
Regarding @sdhiscocks question about the number of tracks: I tried using the
GaussianMixtureInitiator
with unknown number of tracks (e.g. using theMultiTargetGroundTruthSimulator
) but I was not able to make it work properly with the tracking loop needed for the MFA data associator. Hence my approach of fixing the number of targets and start the tracks in this way.To be honest, I wasn't sure if there was a limitation in the actual algorithm itself that means it assumes fixed number of targets, or limitation of the implementation. I've found when trying to use with varying targets, you can get an
RuntimeError
due to "Infeasible primal problem", which I suspected could be related to varying the number of tracks.
This PR adds an example of a Multi-Hypothesis tracking using the Multi-frame assignment components. This example was supposed to rely more on Stone Soup components (e.g.,
GaussianMixtureInitiator
andMultiTargetTracker
), however the current implementation of such components is not aligned with the MFA components making complex to deal with it (e.g. #896).This example shows how to set up this type of simulations in a more general way than the example present in the documentation.