When I, as a human, mow, I use the perimeter cut as a “free to overwrite” zone, where it’s fine if I cut right through it to make a nice, straight cut. Sure I’m cutting twice, but who cares?
But for Yarbo, the perimeter is a sacred ground.
Can we tweak this algorithm to be more dedicated to straight, long cuts, even if you’re going through a perimeter cut?
Thanks for your suggestion! I’ll be sure to share your thoughts with our product team for their consideration. We appreciate your input and will keep it in mind as we continue to improve Yarbo.
I almost exclusively have these sorts of sections. It’s brutal. Yarbo M1 does not seem to understand where it already was. In the video on the other topic, that’s also what can be seen.
There are a few problems:
Yarbo M1 has no cost calculation for making turns
Yarbo M1 has poor understanding of connected patches
Yarbo M1 planning does not know which sections are for mowing and which are for driving to the next mowing section
Yarbo M1 does not know how large it is and whoch section of the mower is doing thr mowing.
Yarbo M1 does not know what it has already mowed
I think both planning and exectution should be revised based on a model wich draws ideal lines and a model which runs on the fly, tries to get there, and colors out the sections which were mowed whilst moving or mowing. This would alloe for much smoother operation!
I’d rather plug in an algorithm myself rather than wait for Yarbo because I don’t think they’ll make it happen.
We have several posts discussing path optimization and routing. The link above is an example. I even opened a ticket and sent them a lot of examples of such problems and all. “They understand my concerns and escalated the issue bla-bla-bla”….
This being said, in your case, try spiral. It might do better.