Comment Location:
http://christalks624.blogspot.com/2010/09/reading-10-graphical-input-through.html
Summary:
This is an old paper, written in 1976. The HUNCH system was an early sketch recognizer that worked for some users and not for others; the programmer had styled his programming for a particular style of behavior; some users matched it, some did not. "Latching", the practice of joining together endpoints if certain conditions are met, failed in a number of cases and did not work perfectly in the end. The author demonstrated a "room finder" which calculated the location of room in floor plans by finding whitespace surrounded by lines; it worked well for simple plans, but it was less effective for oddly-shaped floor plans.
The author implemented "speed" and "bentness" as means of measuring and interpreting the data; I suspect "bentness" is a precusor to the term "curvature". The author observed slower speeds and high bentness usually meant a corner. In the end, the author was able to do some sketch recogntion clean-up that is rather common-place today.
Discussion:
This paper was another get-back-to-the-basics that demonstrated how the author implemented techniques already in existence today. I don't remember the "latching" from any recent papers, though. I suspect the term changed or there are not a lot of people who use it.
On a side note, where are the results & evaluation sections?
This paper seemed much more exploratory than actually producing a usable system with high recognition rates. This paper was from 1974, so the issues it discusses were relevant to the infancy of sketch input (though many of the issues are still relevant today).
ReplyDeleteI also didn't remember the term "latching" specifically. However, we have focused more on low-level recognition, while the latching problem is more of a high-level operation, such as combining multiple strokes in one shape. I dealt with the latching problem in my truss implementation (though it was a poor implementation ;).