Analysis of “CRITIQUING FREEHAND SKETCHING”
Summary:
Creates a manually-defined heuristics-based engine that checks the parameters of a user’s sketch for a floor plan. The sketch recognition is not deep as it is mainly boxes or blobs (rooms) and lines (doors and windows). The application then runs through it’s heuristics to see that the certain labeled rooms meet the proper criteria based on where they are (e.g. “the Emergency Room should be closer to the Entrance Lobby”).
Heuristics are defined in a simple tuple form: (<requirement> <room> <room>) for example (SHOULD-BE-ADJACENT ER ICU). These heuristics are manually input by an expert and not automatically gleamed. This allows for text feedback when a heuristic is violated. The system takes into account the placement of doors and arrangement of rooms.
The sketch is later converted in a simple walkthrough 3D model using VRML.
Discussion:
This idea is similar to the domain-independent approach of LADDER, except the defined constraints are not used to recognition domain symbols but to verify the placement of those symbols. The user is responsible for labeling the rooms. The system only recognizes that a box or blob is a room.
How is this applicable to drawing a face? We already know certain things about the face (i.e. placement of the eyes in relation to the nose, etc.) that won’t change from face to face, but a heuristic here can be supplanted by just having the user follow a step by step methdology (e.g. draw the nose; now draw the eyes). However, it would be nice to have a more generic approach so that steps do not have to be handcrafted.