Handling Errors

[brentwalker]

Just some questions about scoring errors.

How do you score the following:

Runner on 1st and put in play to SS who bobbles the ball and makes a late throw to 1st since runner going to second was already there.

Key sequence:
1. InPlay
2. Error
3. touch location SS, Next
4. Error on SS
5. Runner advancing from first, safe at second, [Held up, Advanced by batter, or error]?, assuming error touch SS
6. Batter/Runner, safe at first, Error, touch SS

Not sure why you prompt to select SS with the error (listed above in step 4) if you have to do this sequence for each batter.

If you said Held Up or Advanced by Batter then the scorecard would read the same, runner at 2nd listed as being moved by "AB#" and runner at 1st reads "E6"

If you said Error then the scorecard would read runner at 2nd listed as being advanced on error (E6) and 1st would read "E6" as well

In both cases only one error would be recorded. Which is more accurate. I tend to lean towards "error" on all runner advancements but wanted to ask how others would score it.

Also, has there been consideration for adding types of errors, bobbled ball, bad throw, dropped catch/throw, etc? Not needed for screen display but certainly important when reviewing stats.

[FDT92]

I view it this way, without the error, the batter would either have a FC (6-4) or would be put out (6-3). One would still be safe (can't assume DP). The error only accounts for 1 extra base runner not both. I mark the runner as advanced by batter and only the batter with "reached on error".

[FTMSupport]

We agree with FDT92 on this one. Here would be the sequence:

1. InPlay
2. Error
3. touch location SS, Next
4. Error on SS
5. Runner advancing from first, safe at second, Advanced by batter
6. Batter/Runner, safe at first, Held Up

In #6, it is asking what happened to the batter/runner after he already reached first on error. You have already said he made it to first on error with #1/#2, so just saying Held Up at that point is fine.

You COULD enter Error in all three questions (step #2, step #5, and step #6), but it would ask who made the error each time. iScore would correctly only assign one error to the shortstop even though you entered it 3 times, but this is really overkill, and probably not accurate.

If the shortstop bobbled the ball and made a late throw to second instead of first, then it would probably be scored as Safe, Fielders Choice, Runner Safe at Second due to Error. But since he threw to second, the more accurate scoring is probably Batter safe due to error, runner safe - advanced by batter, batter/runner held up at first.

We would like to capture the type of errors that occur as well, but at the same time don't want to make the scorekeeping process even more cumbersome, so will likely not do it until we start having preferences for people to turn off things they don't want to track. For example, we already have turning off hit location tracking as a preference for the next release (v2.80) as some people already feel there are too many steps. But there are others that have expressed an interest in capturing even more info, so we would like a preference for that.

As a side note to the error types, we have never seen them listed statistically as "throwing error" vs "bobbled ball" vs ??? Statistically, they are just clumped as "errors". But we would like to capture that level of detail and provide a way to report on it as well (again, as a prefernce).

[danmcc]

v2.80???? Gettin the word out early?

Any chance that the new stats such as first pitch strike % and AB with RSP will be pushed to the website stats page with this new update?

Thanks in advance for you efforts to continuously improve the app.

[FTMSupport]

Yes, we intend for the new sats to be available on the websites as part of the v2.80 release. Inevitable next question... timeframe? We don't have a timeframe on when it will be submitted for approval yet. We are still doing updates to it.

[danmcc]

The crowd goes wild!!!!!!!!!!!!