Closed Mountchicken closed 8 months ago
This error does not relate to image_feature_store
but rather that some of the inputs are non-contiguous. I tested the automatic SAM demo on this SORA video and it worked fine past 100+ frames (SAM failed to detect a lot of them but no errors were thrown). There might be some problem with your demo_with_trex2
implementation. Notably, after 50 frames, we start to "remove" objects from the scene which might lead to non-contiguous output on your end if you are referring to the object indices in any way. The easiest way might just be to slap .contiguous()
on suspicious tensors.
Feel free to re-open if there are follow-up questions.
Hi @hkchengrex Thanks for the great work. I am trying to track dense objects in an image, e.g. more than 100 objects per image. I can successfully run the code for 50 frames. However, at the 51 frames, an error occurs:
I am not familiar with the function
image_feature_store.py
. Can you share some insight about this bug? BTW, here are some visualization results from the model's out/. It just worked for the first 50 frames😂