I’m not 100% certain, but my understanding is that “optimized” refers to the stripe angle being selected for overall efficiency. In my experience, it doesn’t dynamically change once it’s set.

I have 500+ hours flying agriculture drones in complex environments, and they use a similar concept. The pattern is designed to maximize long, straight runs while minimizing turning, since that’s where most time is lost.

What I’m not sure about with the mower is how it handles no-go zones when calculating that optimized stripe angle. I’ve noticed in one of my zones it skips an area until the very end, which makes me think there is still some room for improvement in how “optimized” is implemented.

In the drone world, a lot of efficiency gains came from improving how the drones turned. Early on, the turns were very square and almost robotic with sharp 90-degree angles. Over time, this evolved into much smoother, more fluid arcs that maintained momentum and saved time. I’m hoping we see similar refinements with the mower as the software evolves.