Raif Olson

Hi @abelBEDOYA, I think I know what your problem is. It looks like you are printing the bounding box stored in the tracked object in this line ```python print('bbox from...

If you use the detections returned from `tracker.update_with_detections(detections)` and the `Detections` object has segmentation masks, then the segmentation masks from the model will be retained and have a tracker_id assigned...

Hi @ddrisco11! This could be caused by several things, could you upload a test video and the model weights to google drive and share the link so we can reproduce...

Thanks for the code, model weights, and video. I have done a few tests and it looks like there is a few things going on. First off, it looks like...

@LinasKo, I think I know the reason the tracker is skipping ID's. I will try to make a fix and see if it works.

I don't think so. It seems like MASA is built on the trackers in the MMDet library, which are set up slightly different than the trackers in MMTracking. The trackers...

As for the MASA performance, I also noticed it was pretty bad at handling occlusion and creating new track IDs. I looked a bit into the code and it seems...

Maybe we should wait on the MASA integration because the library isn't quite there yet, and the tracking output will probably change. If we wanted to integrate a strong tracking...

Yes. They output a dict containing `track_results` and `det_results` which are each dicts containing `bbox_results` and `mask_results` which in turn are lists of 2d numpy arrays where each array corresponds...

Ya it would be pretty easy. I can work on it right now.