Closed sandsq closed 3 months ago
Maybe add some fixed, large penalty (larger than any feasible sequence could score) and make a note at the end of the process notifying the user that some ngrams are not typeable
Or maybe just throw an error
I think throw an error so that one can't accidentally optimize for a layout but miss keys that are needed for typing the particular dataset
If we simply pass on it, it will contribute 0 to the effort score, thus making the layout seem better even though it isn't actually able to type the ngram in question