Pen-enabled devices such as tablet pc's and personal digital assistants often use one or more types of handwriting recognizers to allow users to enter data using the pen. Handwriting recognizers analyze the user's handwriting according to a series of rules to determine the most likely match. Typically, the ink segments are compared to ink samples in a database to determine a list of probabilities of the most likely results. Most recognizers also use language models and/or dictionaries to further improve recognition results.
One way to assure that words that do not follow the rules of the language model or are not in the dictionary can still be recognizer is to use two different modules—in-dictionary module and out-of-dictionary module—each producing their own list of best matching results. The merging of these lists into one list of alternates presents a significant difficulty.
Various technologies and techniques are disclosed that improve handwriting recognition operations. During training mode, a balancing factor is calculated that can later be used in recognition mode to compare out-of-dictionary recognition scores with in-dictionary recognition scores. A training set of correct ink samples of words is provided, with some in-dictionary words and some out-of-dictionary words. One or more tuning sets are generated from the correct ink samples, and the tuning set(s) have a percentage of out-of-dictionary words based upon what is expected for a typical user. A handwriting recognizer is run against the tuning set(s) to determine a set of statistics. The statistics are based upon the recognized answer for each of the words compared to the correct answer. The statistics are used to calculate the balancing factor. Later, during recognition mode, a user inputs handwriting to be recognized. The balancing factor is used to compare and combine an in-dictionary alternate list with an out-of-dictionary alternate list to reach a recognition decision.
This Summary was provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
For the purposes of promoting an understanding of the principles of the invention, reference will now be made to the embodiments illustrated in the drawings and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope is thereby intended. Any alterations and further modifications in the described embodiments, and any further applications of the principles as described herein are contemplated as would normally occur to one skilled in the art.
The system may be described in the general context as an application that improves handwriting recognition, but the system also serves other purposes in addition to these. In one implementation, one or more of the techniques described herein can be implemented as features within a handwriting recognition application, or from any other type of program or service that includes a handwriting recognition feature. In one implementation, some of the techniques discussed herein are performed during a training mode before the handwriting recognition application is shipped to an end user. In another implementation, some of the techniques discussed herein are performed during a recognition mode being initiated by an end user of the handwriting recognition application. In other implementations, some, all, or additional techniques to those discussed herein are performed at various times during a training mode and/or a recognition mode of a handwriting recognition application.
Turning now to
Handwriting recognition training application 150 includes program logic 152, which is responsible for carrying out some or all of the techniques described herein. Program logic 152 includes logic for determining expected percentage of out-of-dictionary words for a typical user 154; logic for providing (creating or accessing) a large set of correct ink samples of words, with some out-of-dictionary and some in-dictionary 156; logic for generating one or more tuning sets of samples from the set of correct samples, with the percentage of out-of-dictionary words in the tuning set(s) matching the percentage expected for the typical user 158; logic for running the handwriting recognizer on the tuning set(s), recording certain statistics for each word based upon the recognized answer compared to the correct answer 160; logic for calculating a balancing factor based on the statistics (actual correctness of the in-dictionary and out-of-dictionary top choices), the balancing factor being useful to compare in-dictionary and out-of-dictionary scores together in recognition operations 162; and other logic for operating the application 168. In one implementation, program logic 152 is operable to be called programmatically from another program, such as using a single call to a procedure in program logic 152.
Handwriting recognition application 170 includes program logic 172, which is responsible for carrying out some or all of the techniques described herein. Program logic 172 includes logic for receiving handwritten input from a user 174; logic for breaking the image/ink into segments 176; logic for determining the probability of matching each segment of ink with a character/character segment in the database 178; logic for using an in-dictionary module to generate and in-dictionary list of alternates with corresponding probability 180; logic for using an out-of-dictionary module to generate an out-of-dictionary list of alternates with corresponding probability 182; logic for combining the in-dictionary alternate list with the out-of-dictionary alternate list using a balancing factor 184; logic for making a final recognition decision by picking the top choices from the combined alternate list 186; logic for displaying the recognized character(s) to the user 188; logic for allowing a user to adjust how the balancing factor is used in recognition operations 190; and other logic for operating the application 192. In one implementation, program logic 172 is operable to be called programmatically from another program, such as using a single call to a procedure in program logic 172.
Turning now to
The in-dictionary alternate list is combined with the out-of-dictionary alternate list using a balancing factor (stage 212). The balancing factor can be system generated and/or user-influenced by a customization setting. In one implementation, the out-of-dictionary probability of each item in alternate list is multiplied by the balancing factor and then compared to the in-dictionary alternate list (stage 212). The system makes a final recognition decision by picking the top choice from the combined alternate list (stage 214) and then displays the recognized character(s) to the user (stage 216). The process then ends at end point 218.
In one implementation, just one balancing factor is used, and thus just one tuning set is needed. In another implementation, a user is able to adjust the balancing factor later based on a desired preference weight to be given to out-of-dictionary words versus in-dictionary words. In such a scenario, multiple tuning sets are used to generate different balancing factors for the different percentages that might be specified by the user for out-of-dictionary versus in-dictionary emphasis. This scenario is described in further detail in
The handwriting recognizer is run on the tuning set(s), and certain statistics are recorded for each word based upon the recognized answer compared to the correct answer (stage 248). Based on the statistics (actual correctness of the in-dictionary and out-of-dictionary top choices), a balancing factor is calculated that can be used to compare in-dictionary and out-of-dictionary scores together in recognition operations (e.g. balancing factor with the smallest error) (stage 250). The balancing factor is used by handwriting recognition application 170 to improve handwriting recognition of handwriting input received from a user (e.g. by being able to compare in-dictionary and out-of-dictionary scores together in a meaningful way) (stage 252). The process ends at end point 254.
If enough samples have not been collected for both out-of-dictionary and in-dictionary (decision point 272), then a large, representative language corpus is used to generate ink samples for the words in the corpus using the small amount of data already collected (stage 276). All the samples are then divided into two sets based on whether they are in-dictionary or out-of-dictionary (stage 278). The process ends at end point 280.
In one implementation, the probability coming from the in-dictionary module is the probability of Ink match times the probability of the word as given by the in-dictionary model. Similarly, the probability coming from the out-of-dictionary module is the probability of Ink match times the probability of the word as given by the out-of-dictionary language model (sometimes called the weak language model). Other variations for calculating the probabilities from the in-dictionary module and/or the out-of-dictionary module are also possible, and could be used with the techniques discussed herein. The stages are repeated if there are more words in the tuning set (decision point 292). The process ends at end point 304.
If the top choice of out-of-dictionary modules is correct and the top choice of in-dictionary modules is incorrect (i.e. only the out-of-dictionary top result matches the prompt), large values of the balancing factor will result in a correct answer and small values in an incorrect answer (stage 318). The answer in this scenario is correct when the balancing factor is larger than the Probability (In-Dictionary Word)/Probability (Out-Of-Dictionary Word) and incorrect when it is smaller than the Probability (In-Dictionary Word)/Probability (Out-Of-Dictionary Word) (stage 318).
For each tuning set, the system chooses the value of the balancing factor for which the total error across all samples is minimal (stage 320). The process ends at end point 322.
As shown in
Additionally, device 600 may also have additional features/functionality. For example, device 600 may also include additional storage (removable and/or non-removable) including, but not limited to, magnetic or optical disks or tape. Such additional storage is illustrated in
Computing device 600 includes one or more communication connections 614 that allow computing device 600 to communicate with other computers/applications 615. Device 600 may also have input device(s) 612 such as keyboard, mouse, pen, voice input device, touch input device, etc. Output device(s) 611 such as a display, speakers, printer, etc. may also be included. These devices are well known in the art and need not be discussed at length here. In one implementation, computing device 600 includes either handwriting recognition training application 150 or handwriting recognition application 170. In another implementation, computing device 600 includes both handwriting recognition training application 150 and handwriting recognition application 170. Other variations are also possible.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims. All equivalents, changes, and modifications that come within the spirit of the implementations as described herein and/or by the following claims are desired to be protected.
For example, a person of ordinary skill in the computer software art will recognize that the client and/or server arrangements, user interface screen layouts, and/or data layouts as described in the examples discussed herein could be organized differently on one or more computers to include fewer or additional options or features than as portrayed in the examples.
Number | Name | Date | Kind |
---|---|---|---|
3651459 | Hahn | Mar 1972 | A |
5644648 | Bose et al. | Jul 1997 | A |
5680511 | Baker et al. | Oct 1997 | A |
5710866 | Alleva et al. | Jan 1998 | A |
5812697 | Sakai et al. | Sep 1998 | A |
5812698 | Platt et al. | Sep 1998 | A |
5903668 | Beernink | May 1999 | A |
5999902 | Scahill et al. | Dec 1999 | A |
6055333 | Guzik et al. | Apr 2000 | A |
6223155 | Bayya | Apr 2001 | B1 |
6393395 | Guha et al. | May 2002 | B1 |
6453070 | Seni et al. | Sep 2002 | B1 |
6633672 | Guzik et al. | Oct 2003 | B1 |
6677932 | Westerman | Jan 2004 | B1 |
6718060 | Yokota et al. | Apr 2004 | B1 |
6724936 | Riemer | Apr 2004 | B1 |
6735562 | Zhang et al. | May 2004 | B1 |
6850885 | Raddino et al. | Feb 2005 | B2 |
6970877 | Rowley et al. | Nov 2005 | B2 |
7158678 | Nagel et al. | Jan 2007 | B2 |
7228275 | Endo et al. | Jun 2007 | B1 |
7293231 | Gunn et al. | Nov 2007 | B1 |
7336827 | Geiger et al. | Feb 2008 | B2 |
7421417 | Mangasarian et al. | Sep 2008 | B2 |
20010018654 | Hon et al. | Aug 2001 | A1 |
20030007018 | Seni et al. | Jan 2003 | A1 |
20030086612 | Hullender | May 2003 | A1 |
20030110038 | Sharma et al. | Jun 2003 | A1 |
20040002940 | Meek et al. | Jan 2004 | A1 |
20040002986 | Rowley et al. | Jan 2004 | A1 |
20040006468 | Gupta et al. | Jan 2004 | A1 |
20040140956 | Kushler et al. | Jul 2004 | A1 |
20050049985 | Mangasarian et al. | Mar 2005 | A1 |
20050074169 | Filatov et al. | Apr 2005 | A1 |
20050129313 | Hullender | Jun 2005 | A1 |
20050256712 | Yamada et al. | Nov 2005 | A1 |
20050289140 | Ford et al. | Dec 2005 | A1 |
20060020461 | Ogawa | Jan 2006 | A1 |
20060190259 | Jeong et al. | Aug 2006 | A1 |
20070005356 | Perronnin | Jan 2007 | A1 |
20070005537 | Abdulkader et al. | Jan 2007 | A1 |
20070050191 | Weider et al. | Mar 2007 | A1 |
20080215301 | Eyal et al. | Sep 2008 | A1 |
20090276705 | Ozdemir et al. | Nov 2009 | A1 |
Number | Date | Country | |
---|---|---|---|
20070280537 A1 | Dec 2007 | US |