PITCH CALL INTENT

Description

RELATED APPLICATION

This disclosure claims priority to US provisional patent application number 63/694,295 filed on Sep. 13, 2024, the disclosure of which is hereby incorporated by reference.

TECHNICAL FIELD

Embodiments disclosed herein include devices, systems, and methods directed to tracking a pitch call prior to that corresponding pitch and then, once the pitch has been thrown, deriving pitch outcome data relative to that pitch call as well as distribution of derived pitch outcome data to one or more wearable coach and/or player electronic devices, such as to display derived pitch outcome data at one or more such wearable player electronic device.

BACKGROUND

Sporting activity games, such as baseball, continue to increase in popularity and sophistication. With the advance of data analytics, opportunities for extracting intelligence from gathered data relating to the sporting activity game have become more widely available and increased the sophistication of sporting activity games at various levels. This includes not just the professional level of the sporting activity, but also the amateur levels, including collegiate and high school levels.

However, to-date, the application of data analytics to various sporting activity games has tended to be generally static and, as such, inadequate in accounting for rapidly changing circumstances of certain types of sporting activity games, particularly those sporting activity games that involve a significant number of variables. Moreover, the current application of data analytics to various sporting activity games makes it difficult to distribute substantially real-time intelligence extracted from this data to one or more players in a timely manner. Because certain, relevant sporting activity game circumstances can change in a matter of seconds, the inability to distribute, to a player, an action discerned from the data in a timely manner can render such distributed action stale and less relevant to the newly changed circumstances of the sporting activity game. This, in turn, tends to decrease the value of data analytics for such sporting activity games and limits the number of applications for data analytics.

SUMMARY

In general, this disclosure relates to using pitch call intent data, logged prior to a pitch, in conjunction with game circumstance data relating to the subsequent outcome of that pitch to enable substantially real-time pitch outcome analytics after that pitch and prior to a subsequent pitch. Accordingly, embodiments disclosed herein can be configured to track and log a pitch call for a first pitch prior to that first pitch being thrown, then use data relating to the outcome of that first pitch along with the pitch call itself to derive first pitch outcome data from the first pitch, where the derived first pitch outcome data is relative to the pitch call. Such embodiments disclosed herein can be configured to log such pitch call data and to derive such first pitch outcome data relative to the pitch call prior to a next, second pitch being thrown. Embodiments disclosed herein include devices, systems, and methods directed to tracking a pitch call prior to that corresponding pitch and then, once the pitch has been thrown, deriving pitch outcome data relative to that pitch call as well as distribution of derived pitch outcome data to one or more wearable coach and/or player electronic devices, such as to display derived pitch outcome data at one or more such wearable player electronic device.

Such embodiments disclosed herein can facilitate dynamic use of data analytics as applied to a pre-pitch intent for that pitch relative to a post-pitch actual outcome of that pitch. This can allow for applying such data analytics in a manner that can account for substantially real-time data and related trends discerned from such substantially real-time data so that a subsequent pitch call can be made by a coach using substantially real-time pitch outcome data that is relative to the pre-pitch call for that pitch. In this way, embodiments disclosed herein can provide data analytics insights for a coach that have typically not been previously available at a time when such insights could be used for a subsequent pitch call. As such, embodiments disclosed herein can allow for subsequent pitch call(s) to be made by a coach based on the substantially real-time pitch outcome data that is relative to the pre-pitch call/intent for that pitch. And, such embodiments can allow for distribution of a play calls and/or adjusted play call, generated using the substantially real-time pitch outcome data that is relative to the pre-pitch call/intent for that pitch, to one or more wearable player devices in a timely manner that allows the player wearing the wearable player device to execute the received play call and/or adjusted play call routinely and quickly and in a manner that accounts for prior pitch's pitch outcome data that is relative to the pre-pitch call/intent for that pitch. This, in turn, can provide a useful application of data analytics in a way that can provide novel data insights in the context of a pre-pitch call/intent for a pitch and can increase the value of pitch outcome data analytics for a baseball game where the game circumstances can change relatively rapidly on a pitch-by-pitch basis.

One embodiment includes a computing device having non-transitory computer-executable instructions that, when executed by programmable processing circuitry of the computing device, cause the programmable processing circuitry of the computing device to: receive a first pitch call, from a coach device, for a first pitch to be thrown prior to the first pitch being thrown; create a pitch call intent data file corresponding to the received first pitch call; receive post first pitch game circumstance data corresponding to one or more results of the first pitch having been thrown; and compare the pitch call intent data file to the received post first pitch game circumstance data to generate first pitch outcome data, wherein the first pitch outcome data is generated relative to the pitch call intent data file and prior to a second pitch that is subsequent to the first pitch having been thrown.

In a further embodiment of this device, the generated first pitch outcome data comprises a magnitude of a margin of error between the pitch call intent data file and the post first pitch game circumstance data. The non-transitory computer-executable instructions, when executed by programmable processing circuitry of the computing device, can further cause the programmable processing circuitry of the computing device to transmit the magnitude of the margin of error to the coach device. The non-transitory computer-executable instructions, when executed by programmable processing circuitry of the computing device, can cause the programmable processing circuitry of the computing device to transmit the magnitude of the margin of error to the coach device prior to the second pitch being thrown. For instance, the pitch call intent data file can comprise a type of pitch and an intended location, relative to a batter, for that type of pitch, and the post first pitch game circumstance data can comprise an actual location, relative to the batter, where the first pitch was thrown. This can include the magnitude of a margin of error comprising data indicative of a deviation between the intended location and the actual location.

In a further embodiment of this device, the non-transitory computer-executable instructions, when executed by programmable processing circuitry of the computing device, can further cause the programmable processing circuitry of the computing device to transmit the generated first pitch outcome data to at least one player wearable player electronic device.

In a further embodiment of this device, the non-transitory computer-executable instructions, when executed by programmable processing circuitry of the computing device, can further cause the programmable processing circuitry of the computing device to transmit, to at least one player wearable player electronic device, a player instruction that comprises a direction relative to the field of play for a player wearing the at least one player wearable player electronic device to move prior to the second pitch being thrown. For example, the non-transitory computer-executable instructions, when executed by programmable processing circuitry of the computing device, can cause the programmable processing circuitry of the computing device to generate the player instruction at least based on the generated first pitch outcome data.

In a further embodiment of this device, the non-transitory computer-executable instructions, when executed by programmable processing circuitry of the computing device, can cause the programmable processing circuitry of the computing device to automatically create the pitch call intent data file upon receiving the first pitch call.

In a further embodiment of this device, the device can further include a transceiver in communication with the programmable processing circuitry and non-transitory storage medium storing the non-transitory computer-executable instructions and in communication with the programmable processing circuitry.

As one such example, such non-transitory computer-executable instructions, when executed by programmable processing circuitry of the computing device, can cause the programmable processing circuitry of the computing device to: receive a first pitch call that includes fastball high and outside, from a coach device, for a first pitch to be thrown prior to that first pitch being thrown; create a pitch call intent data file corresponding to the received first pitch call, such as creating a fastball high and outside pitch call intent data file; receive post first pitch game circumstance data corresponding to one or more results of the first pitch being thrown, such as the first pitch having been thrown as a fastball low and outside; compare the pitch call intent data file to the received post first pitch game circumstance data to generate first pitch outcome data, where the first pitch outcome data is generated relative to the pitch call intent data file and prior to a second pitch that is subsequent to the first pitch being throw, such as comparing the fastball high and outside pitch call intent data file to the received result of the first pitch having been fastball low and outside to generate first pitch outcome data that includes a difference between the fastball high and outside pitch call intent data file to the received result of the first pitch having been fastball low and outside. For instance, the generated first pitch outcome data can include a magnitude of a margin of error between the fastball high and outside pitch call intent data file to the received result of the first pitch having been fastball low and outside (e.g., the outcome of the first pitch being thrown deviated from the first pitch call intent by six inches low). Then, this magnitude of a margin of error between the fastball high and outside pitch call intent data file to the received result of the first pitch having been fastball low and outside can be used by the coach in assessing a pitch call intent for a second, subsequent pitch prior to the second, subsequent pitch being thrown.

In a further embodiment, such non-transitory computer-executable instructions, when executed by programmable processing circuitry of the computing device, can send the generated first pitch outcome data to at least one player wearable player electronic device. In some such examples, the non-transitory computer-executable instructions, when executed by programmable processing circuitry of the computing device, can send the generated first pitch outcome data to at least one player wearable player electronic device along with a player instruction that includes a direction (e.g., relative to the baseball field) for that player to move prior to the second, subsequent pitch being thrown.

Another embodiment includes a method. This method embodiment includes the steps of: receiving a first pitch call, from a coach device, for a first pitch to be thrown prior to that first pitch being thrown; creating a pitch call intent data file corresponding to the received first pitch call; receiving post first pitch game circumstance data corresponding to one or more results of the first pitch being thrown; and comparing the pitch call intent data file to the received post first pitch game circumstance data to generate first pitch outcome data, where the first pitch outcome data is generated relative to the pitch call intent data file and prior to a second pitch that is subsequent to the first pitch being thrown.

The details of one or more examples of the disclosure are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the disclosure will be apparent from the description and drawings, and from the claims.

BRIEF DESCRIPTION OF DRAWINGS

The following drawings are illustrative of particular examples of the present invention and therefore do not limit the scope of the invention. The drawings are not necessarily to scale, though embodiments can include the scale illustrated, and are intended for use in conjunction with the explanations in the following detailed description wherein like reference characters denote like elements. Examples of the present invention will hereinafter be described in conjunction with the appended drawings.

FIG. 1 is a schematic block diagram of an embodiment of a system for receiving pitch call intent data and generating pitch outcome data that is relative to the pitch call intent data.

FIG. 2 is a block diagram of an embodiment of a computing device having non-transitory computer-executable instructions that, when executed by programmable processing circuitry of the computing device, cause the programmable processing circuitry of the computing device to compare first pitch call intent data to received post first pitch game circumstance data to generate first pitch outcome data that is relative to the first pitch call intent data.

FIG. 3 is a flow diagram of an embodiment of a method for using first pitch call intent data and post first pitch game circumstance data to generate first pitch outcome data that is relative to the first pitch call intent data.

DETAILED DESCRIPTION

The following detailed description is exemplary in nature and is not intended to limit the scope, applicability, or configuration of the invention in any way. Rather, the following description provides some practical illustrations for implementing examples of the present invention. Those skilled in the art will recognize that many of the noted examples have a variety of suitable alternatives.

Embodiments are disclosed herein, and illustrated in the accompanying drawings, using baseball as a non-limiting example of a sporting activity game. However, the embodiments disclosed herein can be applied to other types of sporting activity games, such as softball, football, basketball, hockey, volleyball, as other non-limiting examples. For instance, the teachings disclosed herein as to pitch call data and pitch outcomes can be applied to other, non-baseball sporting activity games where the pitch call data is data relating to an intent for a play prior to executing the play and the pitch outcome data is data relating to the result of that play after the play has been executed.

FIG. 1 is a schematic block diagram of an embodiment of a system 100 for using first pitch call intent data and post first pitch game circumstance data to generate first pitch outcome data that is relative to the first pitch call intent data. For some embodiments within the scope of the present disclosure, post first pitch game circumstance data can additionally or alternatively be received from a third party data provider who itself has procured and created the post first pitch game circumstance data using any number of various data acquisition means.

The system 100 can include a coach device 102, a central computing device, such as a remote server, 104, and one or more wearable player devices 106. Each of the coach device 102 and the one or more wearable player devices 106 can include programmable processing circuity and a user interface. The coach device 102 can be configured to receive input at the user interface and transmit the received input to the remote server 104, and the coach device 102 can be configured to display received data at the user interface. Each of the one or more wearable player devices 106 can be configured to receive data from the remote server and to display such received data at the user interface.

As one example application of the system 100, a coach can provide input data at the coach device 102, and this input data can be transmitted via a network 108 (e.g., a wide area network, such as a cellular network or the Internet; a local area network) from the coach device 102 to the remote server 104 and/or to the one or more wearable player devices 106.

As one specific such example, a coach can input, at the coach device, first pitch call intent data, and this first pitch call intent data can be transmitted from the coach device 102 to the remote server 104 prior to the corresponding first pitch being thrown. For instance, the coach can input, at the coach device, first pitch call intent data that includes a pitch call intent for a fastball high and outside. Prior to this pitch actually being thrown in the baseball game. Then, a pitch call intent data file corresponding to that received first pitch call can be created, for instance at the remote server 104. For instance, a pitch call intent data file can be created corresponding to the pitch call intent for a fastball high and outside. After this first pitch has been actually thrown, then the remote server 104 can receive post first pitch game circumstance data corresponding to one or more results of the first pitch being thrown. For instance, the remote server 104 can receive post first pitch game circumstance data corresponding to one or more results of the first pitch being thrown, such as the outcome of the first pitch being thrown being a fastball low and inside. This received post first pitch game circumstance data corresponding to one or more results of the first pitch being thrown can be compared, such as at the remote server 104, to the pitch call intent data file to generate first pitch outcome data, where the first pitch outcome data is generated relative to the pitch call intent data file and prior to a second pitch that is subsequent to the first pitch being thrown. For instance, the remote server 104 can compare the outcome of the first pitch being thrown being a fastball low and inside to the pitch call intent data file having the pitch call intent for a fastball high and outside to generate first pitch outcome data that is relative to the pitch call intent data file having the pitch call intent for a fastball high and outside. For instance, such generated first pitch outcome data can include a magnitude of a margin of error between the pitch call intent (e.g., fastball high and outside) and the received result of the first pitch (e.g., fastball low and inside), such as in the example here the outcome of the first pitch being thrown deviated from the first pitch call intent by six inches low and four inches inside. Then, this magnitude of a margin of error—between the intent pitch call prior to the first pitch being thrown and the result of that first pitch—can be used by the coach in assessing a pitch call intent for a second, subsequent pitch prior to the second, subsequent pitch being thrown and/or for the coach to input a player adjustment instruction to a player in the field to move to a new location relative to the baseball field (e.g., to transmit from the coach device 102 an instruction for a center fielder to shift left prior to the second pitch being thrown).

The example diagram illustrated here for the system 100 at FIG. 1 can execute various functions at the remote server 104 to help carry out the generation of first pitch outcome data that is relative to the first pitch call intent data. For the illustrated example, the remote server 104 can include one or more modules that can be executed by programmable processing circuitry at the remote server 104.

For instance, one or more application programming interfaces can be implemented at the remote server 104 to provide functionality via the remote server 104 for a charting application 110 that can both: (i) automatically record an intent pitch call (e.g., for a first pitch yet to be thrown) and input at the coach device 102 upon the intent pitch call being transmitted from the coach device 102 to the remote server 104, and (ii) record the first pitch game circumstance data corresponding to one or more results of the first pitch being thrown, such as the outcome of the first pitch being thrown. And, one or more application programming interfaces can be implemented at the remote server 104 to provide functionality via the remote server 104 for a data tracking tool 111 that can compare post first pitch game circumstance data corresponding to one or more results of the first pitch being thrown to the pitch call intent data to generate first pitch outcome data, where the first pitch outcome data is generated relative to the pitch call intent data file and prior to a second pitch that is subsequent to the first pitch being thrown. In some examples, the data tracking tool 111 can be configured, when executed, to generate one or more substantially real-time predictions relating to a subsequent pitch to be thrown. As one such example, it can be executed to generate a substantially real-time prediction of a magnitude of a margin of error between the pitch call intent received from the coach device 102 and an outcome of a subsequent pitch yet-to-be-thrown. As another additional or alternative example, it can be executed to generate a substantially real-time prediction of a location where the baseball is likely to be hit for the subsequent pitch yet-to-be-thrown and generate a baseball player movement instruction to re-position a specified player in the field of play using the prediction of the magnitude of a margin of error between the pitch call intent received from the coach device 102 and an outcome of a subsequent pitch yet-to-be-thrown.

FIG. 2 is a block diagram of an embodiment of a computing device 210 having non-transitory computer-executable instructions that, when executed by programmable processing circuitry 200 of the computing device 210, cause the programmable processing circuitry 200 of the computing device 210 to compare first pitch call intent data to received post first pitch game circumstance data to generate first pitch outcome data that is relative to the first pitch call intent data. In some examples, as applied to the exemplary system 100 illustrated at FIG. 1, the computing device 210 can be the remote server 104. Though other embodiments of the computing device 210 can be implemented at other components in the system 100 and/or at other components in different systems.

The computing device 210 can include the programmable processing circuitry 200 and associated non-transitory storage medium 201 that can store in memory non-transitory computer-executable instructions that can be executed by programmable processing circuitry 200. In addition, the computing device 210 can include transceiver 202 that can be configured to transmit data from the computing device 210 over one or more networks and/or to receive data at the computing device 210 over one or more networks. And, the computing device 210 can include pitch call intent and outcome comparison module 203 that can be configured to generate first pitch outcome data, which relates to an outcome of a first pitch after the first pitch has been thrown, where this first pitch outcome data is relative to first pitch call intent data, which can be automatically logged upon receiving the first pitch call intent data at the transceiver 202 from the coach device.

Thus, the pitch call intent and outcome comparison module 203 can include non-transitory computer-executable instructions that, when executed by programmable processing circuitry 200, can cause the programmable processing circuitry 200 to receive pitch call intent data from coach device corresponding to an intended pitch type and/or intended pitch location for a first pitch that has not yet be thrown. And, the pitch call intent and outcome comparison module 203 can include non-transitory computer-executable instructions that, when executed by programmable processing circuitry 200, can cause the programmable processing circuitry 200 to, after the first pitch has been thrown, compare the received pitch call intent data from coach device corresponding to an intended pitch type and/or intended pitch location for a first pitch that has not yet be thrown to first pitch game circumstance data that corresponds to one or more results of the first pitch being thrown.

In some additional embodiments, the pitch call intent and outcome comparison module 203 can include non-transitory computer-executable instructions that, when executed by programmable processing circuitry 200, can cause the programmable processing circuitry 200 to use the comparison between the received pitch call intent data to the post first pitch game circumstance data to generate one or more substantially real-time predictions relating to a subsequent, second pitch to be thrown in the future. As one such example, it can be executed to generate a substantially real-time prediction of a magnitude of a margin of error between the pitch call intent received from the coach device 102 and an outcome of a subsequent, second pitch yet-to-be-thrown. As another additional or alternative example, it can be executed to generate a substantially real-time prediction of a location where the baseball is likely to be hit by a batter for the subsequent pitch yet-to-be-thrown and generate a baseball player movement instruction to re-position a specified player in the field of play using the prediction of the magnitude of a margin of error between the pitch call intent received from the coach device and an outcome of a subsequent pitch yet-to-be-thrown.

FIG. 3 is a flow diagram of an embodiment of a method 300 for using first pitch call intent data and post first pitch game circumstance data to generate first pitch outcome data that is relative to the first pitch call intent data. For example, the method 300 can be executed, in some instances, using any one or more of the computing devices and/or systems disclosed previously herein with respect to FIGS. 1 and/or 2.

At step 301, the method 300 includes receiving a first pitch intent call, from a coach device, for a first pitch to be thrown prior to that first pitch being thrown. For example, a coach can input at coach device 102 a first pitch intent call for a first pitch to be thrown and this first pitch intent call can be transmitted over a network from the coach device to remote server 104 prior to that first pitch being thrown. The first pitch intent call can include one or both of a pitch type for the first pitch to be thrown and a pitch location for the first pitch to be thrown. As one such example, the first pitch intent call can include a fastball pitch type and a location high and outside for a pitch location for the first pitch to be thrown.

At step 302, the method 300 includes creating a pitch call intent data file corresponding to the received first pitch call. For example, remote server 104 can be configured to use the first pitch intent call received from the coach device to create the pitch intent data file. For instance, in the above mentioned example, his can include the remote server 104 creating a pitch call intent data file that includes the first pitch type (e.g., fastball) and the first pitch location (e.g., high and outside), corresponding to the first pitch intent call received from the coach device, prior to that first pitch being thrown. In some cases, the remote server 104 can be configured to automatically create and save the pitch intent data file as a result of receiving the first pitch intent call data from the coach device.

At step 303, the method 300 includes receiving post first pitch game circumstance data corresponding to one or more results of the first pitch being thrown. For example, as a result of the first pitch having been thrown, the remote server 104 can receive data indicating one or more outcomes of the first pitch having been thrown (e.g., from an external, third-party data source). This can include the actual pitch type thrown for the first pitch (e.g., the first pitch was thrown as a fastball type pitch) and the actual location where the first pitch was thrown (e.g., the first pitch was thrown at a low and insider location to the batter). Additionally or alternatively, as a result of the first pitch having been thrown, the remote server 104 can receive data indicating one or more outcomes of the first pitch having been thrown that includes a location in the field of play where the batter hit the first pitch.

At step 304, the method 300 includes comparing the pitch call intent data file to the received post first pitch game circumstance data to generate first pitch outcome data, where the first pitch outcome data is generated relative to the pitch call intent data file and prior to a second pitch that is subsequent to the first pitch being thrown. For example, the remote server 104 can compare (i) the pitch call intent data file, which can include the first pitch type (e.g., fastball) and the first pitch location (e.g., high and outside) corresponding to the first pitch intent call received from the coach device prior to that first pitch being thrown to (ii) the post first pitch game circumstance data corresponding to one or more results of the first pitch being thrown (e.g., the first pitch was thrown as a fastball type pitch at a low and insider location to the batter) prior to a second pitch that is subsequent to the first pitch being thrown. For some applications of step 304, the method can include executing the noted comparison to generate a difference between the intent pitch call location (e.g., high and outside) and the post first pitch game circumstance first pitch location (e.g., low and inside) prior to a second pitch that is subsequent to the first pitch being thrown. For instance, as one example, it can include generating a magnitude of a margin of error between the intent pitch call location (e.g., high and outside) and the post first pitch game circumstance first pitch location (e.g., generate a magnitude of a margin of error between the high and outside pitch intent call location and the actual post first pitch location ending up low and inside to the batter such that a magnitude of a margin of error is six inches lower and four inches inside of the intent pitch call location).

In some cases, the method 300 can include a step of using this magnitude of the margin or error between the intent pitch call location and the post first pitch game circumstance first pitch location when inputting a pitch intent call for a second, subsequent pitch at the coach device. For example, if the magnitude of the margin of error between the intent pitch call location and the post first pitch game circumstance first pitch location indicates the first pitch location deviated lower and further inside than the location indicated in the first pitch intent call, then the coach may use this magnitude of the margin of error to input an intent pitch call for the second, subsequent pitch that accounts for this magnitude of the margin of error (e.g., the coach inputs the second pitch intent call as a modified second pitch intent call that is at a location higher and more outside than the original second pitch intent call would have been but for using the magnitude of the margin of error from the prior, first pitch).

For some embodiments, the method 300 can include transmitting the generated first pitch outcome data to at least one player wearable player electronic device. In some such examples, the method 300 can include sending the generated first pitch outcome data to at least one player wearable player electronic device along with a player instruction that includes a direction (e.g., relative to the baseball field) for that player to move prior to the second, subsequent pitch being thrown. For instance, if the generated first pitch outcome data indicates the pitcher is missing the intent pitch call location consistently higher than the location called for in the intent pitch call data file, the method 300 could include sending, to at least one wearable player device, an instruction to move in a specified direction relative to the field of play—such as to a player device worn by a left fielder to move back further away from home plate—prior to the second, subsequent pitch being thrown. Alternatively, if the generated first pitch outcome data indicates the pitcher is missing the intent pitch call location consistently lower than the location called for in the intent pitch call data file, the method 300 could include sending, to at least one wearable player device, an instruction to move in a specified direction relative to the field of play—such as to a player device worn by a left fielder to move in closer toward home plate—prior to the second, subsequent pitch being thrown.

The following provides an exemplary listing of particular embodiments within the scope of the present disclosure:

One embodiment includes a computing device having non-transitory computer-executable instructions that, when executed by programmable processing circuitry of the computing device, cause the programmable processing circuitry of the computing device to: receive a first pitch call, from a coach device, for a first pitch to be thrown prior to that first pitch being thrown; create a pitch call intent data file corresponding to the received first pitch call; receive post first pitch game circumstance data corresponding to one or more results of the first pitch being thrown; and compare the pitch call intent data file to the received post first pitch game circumstance data to generate first pitch outcome data, where the first pitch outcome data is generated relative to the pitch call intent data file and prior to a second pitch that is subsequent to the first pitch being throw.

In one such more particular embodiment, the non-transitory computer-executable instructions, when executed by programmable processing circuitry of the computing device, can cause the programmable processing circuitry of the computing device to: receive a first pitch call that includes a pitch type (e.g., fastball) and an intended pitch location (e.g., high and outside), from a coach device, for a first pitch to be thrown prior to that first pitch being thrown; create a pitch call intent data file corresponding to the received first pitch call, such as creating a first pitch call intent data file (e.g., create a fastball high and outside intent data file prior to the pitch being thrown); receive post first pitch game circumstance data corresponding to one or more results of the first pitch being thrown (e.g., the first pitch having been actually thrown as a pitch type that either matches or deviates from the pitch call intent data file pitch type (e.g., fastball or not) and either matches or deviates from the pitch call intent data file pitch location (e.g., pitch was actually thrown low and outside instead of high and outside an intended for the pitch call before the pitch was thrown); compare the pitch call intent data file to the received post first pitch game circumstance data to generate first pitch outcome data, where the first pitch outcome data is generated relative to the pitch call intent data file and prior to a second pitch that is subsequent to the first pitch being thrown (e.g., comparing the fastball high and outside pitch call intent data file to the received result of the first pitch having been fastball low and outside to generate first pitch outcome data that includes a difference between the fastball high and outside pitch call intent data file to the received result of the first pitch having been fastball low and outside). For instance, the generated first pitch outcome data can include a magnitude of a margin of error between the fastball high and outside pitch call intent data file to the received result of the first pitch having been fastball low and outside (e.g., the outcome of the first pitch being thrown deviated from the first pitch call intent by six inches low). Then, this magnitude of a margin of error between the fastball high and outside pitch call intent data file to the received result of the first pitch having been fastball low and outside can be used by the coach in assessing a pitch call intent for a second, subsequent pitch prior to the second, subsequent pitch being thrown.

In another additional or alternative more particular embodiment, such non-transitory computer-executable instructions, when executed by programmable processing circuitry of the computing device, can send the generated first pitch outcome data to at least one player wearable player electronic device. In some such examples, the non-transitory computer-executable instructions, when executed by programmable processing circuitry of the computing device, can send the generated first pitch outcome data to at least one player wearable player electronic device along with a player instruction that includes a direction (e.g., relative to the baseball field) for that player to move prior to the second, subsequent pitch being thrown.

Another embodiment within the scope of the present disclosure includes a method. This method embodiment includes the steps of: receiving a first pitch call, from a coach device, for a first pitch to be thrown prior to that first pitch being thrown; creating a pitch call intent data file corresponding to the received first pitch call; receiving post first pitch game circumstance data corresponding to one or more results of the first pitch being thrown; and comparing the pitch call intent data file to the received post first pitch game circumstance data to generate first pitch outcome data, where the first pitch outcome data is generated relative to the pitch call intent data file and prior to a second pitch that is subsequent to the first pitch being thrown. In some additional method embodiments, features can be incorporated similar to, or the same as, those noted above with respect to the embodiments relating to the computing device having non-transitory computer-executable instructions that are executed by programmable processing circuitry of the computing device.