Replies: 1 comment
-
👋 Hello @tonyreina, thank you for your interest in Ultralytics 🚀! Your use case sounds intriguing—thanks for sharing your detailed code and explanation. An Ultralytics engineer will review this soon and provide further insights 🎯. In the meantime, here are a few suggestions and resources that may help: General Guidance
UpgradeEnsure you’re using the latest pip install -U ultralytics Explore the Docs 📚Our documentation includes a wealth of information about supported features and usage examples: In particular, the streaming and tracking section might help clarify how the Join Our Community 🧑🤝🧑Have you checked out our Ultralytics community? Here's where you can connect with other users and find additional support:
EnvironmentsIn case you want to test in different setups, YOLO works in several verified environments, including free GPU Notebooks: For deployment scenarios, see Google Cloud, AWS, or our Docker guide here. StatusAlternatively, to ensure everything is functioning smoothly with your environment setup, check the Ultralytics CI badge status below. CI tests verify functionality across various platforms, tasks, and modes every 24 hours and on each commit: Let us know if you have additional concerns—we’re here to help! 😊 |
Beta Was this translation helpful? Give feedback.
-
@tonyreina your usage of |
Beta Was this translation helpful? Give feedback.
-
This code seems to be working correctly, but I am a little unsure of my using the
for result
loop and was hoping to get some feedback.From what I can tell, the
model.track
when set as astream=True
will work on batches of images within the given directory path. However, it looks like it won't actually perform the function until the iterator is called. So I'm just running apass
in the iterator for-loop. This would then save the tracking info for each frame in a.txt
file with the frame number.Is that the correct usage? Is there a more elegant way to do this?
Thanks.
Best.
-Tony
Beta Was this translation helpful? Give feedback.
All reactions