u/Charming_Health_2483

This is not a complaint but just a general question about robotics.

Why is the mower so slow when it's making decisions? For example, just now it was mowing a zone and I paused it (instant obedience), then I canceled the rest of that mow and told it to go mow a different zone. It had to sit and think for a couple minutes.

It seems to me that by 2026, this cannot be due to lack of memory or bandwidth or computing ability. What is it thinking about? As the algorithms get better and so on will this latency go away?

Imagine if I told my teenager: "stop mowing that zone and mow the other zone!" He would say OK, and roll the mower over to the new zone. But the computer needs to think for a couple minutes. Similarly, when it runs into apparently blocks, or edges, it seems like it could get a lot more done if it made decisions faster.

What is it about robotics that causes this latency in decision making? Is there some server farm in Asia that is plotting out a course and so on?

I saw this play in a HS tournament game yesterday.

R1, sacrifice bunt. Batter runner stays in the running lane. Pitcher fields the ball, flips to F4 who is covering the bag, the ball arrived and passed through the fielder and on into right field. The ball was not thrown into the path of the runner; rather the pitcher was too close and threw it too hard. A split second later there was a collision where the batter runner tripped over F4. He picked himself up and was tagged out on a close play at 2nd base. Runner from 1st scored.

Now Consider this Case Play:

>F6 fields a ground ball and and throws to F3 in attempt to retire B1 at first. The ball is thrown wide. As F3 lunges towards the ball, F3 collides with B1 knocking B1 to the ground prior to possessing the ball (a) while B1 is short of first base or (b) after B1 has contacted first base. Ruling (a) Obstruction; (b) legal. (8.3.2. Situation K)

So my question is:

When you see a collision, what rulebook criteria do you use to justify that the collision is a "nothing?" Do you go by instinct, severity of impact, intent, etc.?

It seems to me that the case play suggests that the only time we have a "nothing" is when the fielder possesses a ball in which the throw took him into the basepath at the last moment. So in any case where the ball is not possessed, even briefly, we have to have either OBS or INT?

Also, do you just think the HS case play is dumb and no one enforces it that way?

I'm struggling with my new Lymow One Plus. Customer service is not very responsive right now and probably won't have the time to talk to me. I thought I would ask my question here, which isn't just a question but also an invitation for someone to help me understand how to diagnose. If there is a better place to get an answer, let me know.

I have a large 1 acre plot that I'm testing. Here are some things I'm noticing that seem to me like they're related. I believe they are all related to RTK misfunctions.

1. Fully charged mower mows 15-20 stripes and returns to recharge. After charging the mower starts putting down stripes that are 10 degrees or so different, and overlapping the earlier stripes.

2. Same Idea, but the mower's actual location on the ground seems 10-20 feet displaced from where it thinks it is, both based on map on the app, but also the way it is turning corners.

3. On the perimeter pass, the mower is 3-4 feet away from the edge, sometimes out on my street other times leaving 2-3 feet of grass unmowed on the edge.

4. weird one: after mowing 10 stripes perfectly, in the middle of hte 11th stripe, it inexplicably performs a 180 and mows a kind of repeat half strip.

5. After mowing, there are odd-shaped wedges of unmowed grass.

My RTK reading varies. AT the moment is it at .01. I've seen it as high as 0.16. I feel like this statistic is more volatile than it should be.