Comments on Others:
Summary
This paper proposed an interactive system for graphical input in which the user openly participate in training the machine and massaging the data at all levels of interpretation. This includes 3 experiments, HUNCH: which tries to answer the question of existence of a syntax for sketching, architectural knowledge in recognizing a sketch and user involvement in the input process.
HUNCH is a set of FORTRAN programs with different level of interpretation to process freehand sketches drawn with a data tablet or a light pen. The HUNCH used a program called a STRAIT as a corner finder, which actually based on the function of speed of the pen. Another program called CURVIT was used to finder the curves instead of corners. Even with the sketch recognition capabilities of the CURVIT and STRAIT, authors found that there is a difference when different people using the system which based on the human sketching behavior. Due to the latching problems the STRAIT was re-written without it called STRAIN. Overtracing was another interpretation problem that authors faced during the HUNCH development. The newest approach was using a much more interactive system to get user involvement to make decisions on machine selection which consisted of a database to and programs to manipulate data. The program is based on inference making procedures which is different from HUNCH and STRAIN and LATCH.
Discussion
The paper is about a GUI to input and recognizer freehand sketches, but overall picture of the system is too hazy to understand. Author starts with a legacy system they used before the new system and the difficulties with the old system and how they overcome those in the new system. Without some performance measures and an overall picture of the system, it is hard to imagine how this new system works towards sketch recognition. I’m lost somewhere in the middle of the paper……………..!!!
Find the paper here.
1 comment:
(Actually, this is to answer your question in my blog).For multi-stroke, their templates are still stored as uni-stroke, so they have to change to uni-stroke then compare to templates.
Post a Comment