With the latest release, Yarbo renders obstacles it detects into the map as it works. In the release YouTube video, the gentleman says mower gets smarter the more you use it, suggesting this data is being stored and updated from job to job.
After running a job, I don’t see the point cloud data again, and starting another job shows no previous point cloud data on the map, until Yarbo encounters an obstacle again. It appears to start from scratch every time.
Am I missing something?
It currently only saves for the duration of the work plan. It will use what it learned during the entirety of the plan. After it’s complete, it wipes it and starts fresh for next time. Long term they may be able to retain that or allow you to make no go zones with the data more easily.
Thank you for your question! The point cloud-based obstacle bypass feature is designed to help the mower navigate around unexpected obstacles in real time, and the obstacle data is currently saved only for the duration of the work plan. This is why the point cloud data is not retained after the job is completed. However, we will consider adding the ability to retain obstacle information for future work plans if more users express similar requests. We appreciate your feedback!
Thank you @Yarbo-Forum for the clarification. The rendering of obstacles is a nice-to-have, but hopefully this feature will continue to be developed. Using that information to remember where obstacles are, allowing user to create no-go zones from these obstacles, etc., would be a huge improvement to initial setup of Yarbo. Thanks again for the continued improvement!
@Yarbo-Forum Please discuss this with co-founder Ken. He and Ryan may not be up on the status of this feature.
I agree with this. During today’s live stream, co-founder Ken referred to this feature as if Yarbo remembers and learns obstacles over time, and gives you ability to create no go zones from this data. Such features would be great, but are not in the current release.
Yes, yes, a really smart system should retain obstacle for next time!!! or better choose which of theme
I agree that it should give you the option to retain it but it currently gets a lot wrong so I’d prefer that it reset and learn it each time. I’d say that if it encounters something more than 3 times in the same location then it should consider it accurate and offer an automatic NGZ creation.
Right now, inclines, sun reflections, shadows, and overhanging branches tend to get falsely detected. If it comes at it from a different angle it will detect again that nothing is there and remove it from the map. This is a good behavior currently. So is wiping the data after. I end up with a bunch of perimeter detections as it’s doing the zig zag due to bushes along the perimeter. Thankfully it doesn’t detect this during the perimeter run because I have boundary obstacle avoidance disabled. If it remembered after each run then it would be avoiding those areas even during the perimeter cut. This would not be ideal.
I think once the vision algorithms are more refined, saving for future run will be the norm, or at least give the user the option to save some and delete others once they removed the obstacle (like a branch).
Right now vision system is pretty much unusable. Sure, it will see the obstacles, but there are too many false positives, causing a bunch of grass to be left uncut. At least they have a way to turn it off for now.
I think Bryan’s point/s is more accurate at this time. There’s too many false positives as he noted and Jeremy noted. I’d hate to see it adding NGZ’s based on the current setup because I watch it add “obstacles” all the time and there’s literally nothing there. Tells me it’s not seeing correctly what’s in front of it/around it.
yes bryan, but if you use “delicate touch” (no vision, too many fake) as i use, there is no false obstacle and they could be saved.
It would be a huge bonus to have this as a feature. My yard has a lot of no-go zones, and if you could have it remember, that would make the setup way faster. Hopefully you consider adding this feature.
(post deleted by author)
