Robot Umps?!

[S5Dewey]

Even fair/foul calls cannot be challenged unless the ball was a home run. And they won't be, because there are no guidelines for what to do with baserunners.

 

I think baseball has done a pretty poor job overall with instant replay. It works out pretty well for safe/out calls at 1b, but far too often it is used to reverse calls on baserunners because they separated from the bag for a frantion of a second during their slide...

 

I agree with this (in bold)^^ but I'm not sure what the answer would be. The rule is quite specific now in that a runner who is not in contact with a base is in jeopardy of being tagged out. If we change the rule to include a runner's momentum carrying them beyond the bag aren't we opening the door to runners intentionally overrunning the base, which would essentially almost eliminate sliding? That's a change I wouldn't want to see.

[moonslav59]

I agree with this (in bold)^^ but I'm not sure what the answer would be. The rule is quite specific now in that a runner who is not in contact with a base is in jeopardy of being tagged out. If we change the rule to include a runner's momentum carrying them beyond the bag aren't we opening the door to runners intentionally overrunning the base, which would essentially almost eliminate sliding? That's a change I wouldn't want to see.

 

Can we trade balls and strike called by robo umps to eliminating the ability to challenge those plays?

[S5Dewey]

Well, they don't allow challenges on balls and strikes.

 

This what I referred to a few days ago. Rather than go to robo-umps let hitters/managers challenge a pitch with a limited number of challenges per game.

 

I could live with the umpire making a mistake if it didn't give the pitcher license to throw that same unhittable pitch again I tend to go back to the sequence with JDM in the playoffs when an unhittable pitch was called a strike. The problem is that once an umpire calls an unhittable pitch a strike he feels the need to be "consistent"... so when the pitcher throws the next pitch in the same place (unhittable) he calls that one a strike, too!

It's not the pitcher's fault - heck, I'd do the same thing if I were pitching. It's not the batter's fault that he was thrown an unhittable pitch and it was called a strike. Hitters have a right to expect any pitch called a strike to be a hittable pitch. SO that leaves the blame for a batter not being given an opportunity to get a hit squarely on the shoulders of the umpire. Calls like that can change a game and therefore an entire season.

 

Giving the batter/manager the right to challenge a pitch by going to the K-zone (or whatever it's called now) will level the playing field between the pitcher and the hitter without going "all robo-umps". It'll keep the pitchers more honest and it'll give the hitters potential recourse when they see an unhittable pitch called a strike.

 

In a bigger picture, with playoff spots frequently decided by a game or two it's entirely possible that situations like this throughout the season have an impact on who even makes the playoffs!

[S5Dewey]

Can we trade balls and strike called by robo umps to eliminating the ability to challenge those plays?

 

Why make a trade at all? See my above post about challenges.

[jad]

I agree with this (in bold)^^ but I'm not sure what the answer would be. The rule is quite specific now in that a runner who is not in contact with a base is in jeopardy of being tagged out. If we change the rule to include a runner's momentum carrying them beyond the bag aren't we opening the door to runners intentionally overrunning the base, which would essentially almost eliminate sliding? That's a change I wouldn't want to see.

 

A simple rule-change would fix this: "a runner in a slide, after making contact, is considered to still be in contact with the bag as long as he is over it."

The micromanaging of replay on this now is ridiculous (as Bob Costas pointed out immediately after replay was implemented).

[moonslav59]

Why make a trade at all? See my above post about challenges.

 

We need less challenges- not more.

 

I'm just saying, balls and strike calls by robo umps outweighs getting a few over-slide bases missed calls and would speed up the game.

 

I'd rather keep replays and have all balls and strikes whispered in the ears of the home plate ump via robo calls.

[mvp 78]

Coming off the bag isn't good, actually.

[Bellhorn04]

Coming off the bag isn't good, actually.

 

The idea that if the foot is still over the bag the guy is safe makes sense to me.

[mvp 78]

The idea that if the foot is still over the bag the guy is safe makes sense to me.

 

No, a runner could still make a movement towards the next base while being over the bag and get tagged, but would be safe for some reason in the weird rules you guys are writing.

 

Your ideas are off base.

[Bellhorn04]

No, a runner could still make a movement towards the next base while being over the bag and get tagged, but would be safe for some reason in the weird rules you guys are writing.

 

Your ideas are off base.

 

We wouldn't even be talking about this if it wasn't for the super-high-res-stop-action shots of guys whose shoe separates from the bag by a millimeter for a nanosecond.

[mvp 78]

We wouldn't even be talking about this if it wasn't for the super-high-res-stop-action shots of guys whose shoe separates from the bag by a millimeter for a nanosecond.

 

At least that is going by the rule book.

[jad]

No, a runner could still make a movement towards the next base while being over the bag and get tagged, but would be safe for some reason in the weird rules you guys are writing.

 

Your ideas are off base.

 

Not under my rule change: note "in a slide." You are not going to have runners "make a movement toward the next base" if a fielder is standing there next to him with the ball in his glove. The application of the rule now is silly: again, paraphrasing Costas: "That runner has been considered safe in that situation for 150 years. Replay was designed to correct egregiously bad calls, not to micromanage the way the game is played."

[mvp 78]

Not under my rule change: note "in a slide." You are not going to have runners "make a movement toward the next base" if a fielder is standing there next to him with the ball in his glove. The application of the rule now is silly: again, paraphrasing Costas: "That runner has been considered safe in that situation for 150 years. Replay was designed to correct egregiously bad calls, not to micromanage the way the game is played."

 

Runner slides into 3b. Runner heads for home as ball is bobbled. Runner changes mind and leaps back for 3b. Is tagged by 3b, but the runner's hand is hovering above the bag.

[notin]

A simple rule-change would fix this: "a runner in a slide, after making contact, is considered to still be in contact with the bag as long as he is over it."

The micromanaging of replay on this now is ridiculous (as Bob Costas pointed out immediately after replay was implemented).

 

And this is the proper solution...

[notin]

Runner slides into 3b. Runner heads for home as ball is bobbled. Runner changes mind and leaps back for 3b. Is tagged by 3b, but the runner's hand is hovering above the bag.

 

Once he is no longer above the base, he is considered to be running to the next base. The base "air space" is active once the runner makes inital contact until he moves past the base...

[Bellhorn04]

And now a question regarding the strike zone.

 

Does it actually say in the rule book that the strike zone is based on the entire surface of home plate, or is it only the front line of the plate?

 

If it's only the front of the plate, that would make robo calls of balls and strikes much simpler.

[notin]

And now a question regarding the strike zone.

 

Does it actually say in the rule book that the strike zone is based on the entire surface of home plate, or is it only the front line of the plate?

 

If it's only the front of the plate, that would make robo calls of balls and strikes much simpler.

 

Rule 2-35 The strike zone is that space over home plate, the top of which is halfway between the batter’s shoulders and the waistline, and the bottom being the knees, when he assumes his natural batting stance. The height of the strike zone is determined by the batter’s normal batting stance. If he crouches or leans over to make the shoulder line lower, the umpire determines height by what would be the batter’s normal stance.

[Bellhorn04]

Rule 2-35 The strike zone is that space over home plate, the top of which is halfway between the batter’s shoulders and the waistline, and the bottom being the knees, when he assumes his natural batting stance. The height of the strike zone is determined by the batter’s normal batting stance. If he crouches or leans over to make the shoulder line lower, the umpire determines height by what would be the batter’s normal stance.

 

Thanks.

 

This rule needs to be re-written too, methinks.

 

I mean, home plate isn't even a square, or rectangular shape - it's a rectangle and a triangle stuck together. , or an "irregular pentagon", that tapers to a point. Not ideal.

[mvp 78]

Once he is no longer above the base, he is considered to be running to the next base. The base "air space" is active once the runner makes inital contact until he moves past the base...

 

There was question on if a runner slid through the bag. Would that be considered coming off? Seems like there is too much grey area here.

[5GoldGlovesOF,75]

Thanks.

 

This rule needs to be re-written too, methinks.

 

I mean, home plate isn't even a square, or rectangular shape - it's a rectangle and a triangle stuck together. , or an "irregular pentagon", that tapers to a point. Not ideal.

 

... especially if robos use cameras from the side and call strikes in 3D...

 

A hitter who plants his back foot on the far transverse chalk line of the batter's box (like coaches instruct players to do vs. fast pitchers and umps with high zones) can be standing 12-24 inches behind the farthest point of home plate... and then the catcher catches the pitch behind the hitter.

 

https://groundskeeper.mlblogs.com/how-to-layout-homeplate-6477ddaa457b

[notin]

Thanks.

 

This rule needs to be re-written too, methinks.

 

I mean, home plate isn't even a square, or rectangular shape - it's a rectangle and a triangle stuck together. , or an "irregular pentagon", that tapers to a point. Not ideal.

 

The simpler term is "pentagon"...

[notin]

There was question on if a runner slid through the bag. Would that be considered coming off? Seems like there is too much grey area here.

 

Yes. Once you exit the bag's air space, you are in play...

[mvp 78]

Yes. Once you exit the bag's air space, you are in play...

 

Is there a specific body part that has to remain over the bag? Will there be overhead cameras to show definitively that a player has remained in the appropriate air space?

[Bellhorn04]

Is there a specific body part that has to remain over the bag? Will there be overhead cameras to show definitively that a player has remained in the appropriate air space?

 

Must be an extremity, foot or hand. Camera or sensors underneath or in the bag will be used.

[mvp 78]

Must be an extremity, foot or hand. Camera or sensors underneath or in the bag will be used.

 

Player slides head first. In getting up, he's no longer touching the bag, but his stomach is over the bag. Tagged out?

[Bellhorn04]

Player slides head first. In getting up, he's no longer touching the bag, but his stomach is over the bag. Tagged out?

 

In that case he has to call time out, I guess, the same as they do now.

[notin]

Is there a specific body part that has to remain over the bag? Will there be overhead cameras to show definitively that a player has remained in the appropriate air space?

 

There will be an umpire. And he will call it like he did before instant replay...

[mvp 78]

There will be an umpire. And he will call it like he did before instant replay...

 

Fine.

[notin]

Fine.

 

And that call can still be reviewable. It's not even remotely the same call as the runner stealing second and breaking contact for a fraction of a second...

[mvp 78]

And that call can still be reviewable. It's not even remotely the same call as the runner stealing second and breaking contact for a fraction of a second...

 

What if it's a fraction of a second at 1b?