US 6,421,048 B1Grant
Systems and methods for interacting with virtual objects in a haptic virtual reality environment
Issue Date:2002-07-16
•44 Claims
•25 Drawing Sheets
Abstract
A user of a modeling application uses a haptic interface device in the real world to manipulate a virtual tool in a virtual environment to interact with a virtual object. The user can use the tool to evaluate the shape of the virtual object and navigate its virtual surface, based on an interactive force feedback approach. When the user attempts to penetrate the virtual object with the virtual tool, a modeling application limits the movement of the virtual tool depending on the geometry of the surface, the position of the virtual tool, and a haptic interface location in the virtual environment, which represents the physical location of the haptic interface device in the real world. The user can evaluate different geometries of the virtual surface, including an edge geometry, such as occurs when the virtual tool is touching or moving along an edge of the virtual object.
Metadata
Assignee
- SensAble Technologies, Inc.
Inventors
- Loren Shih
- Walter A. Aviles
- Thomas H. Massie
- Christopher M. Tarr
Application Information
Application Number:US 09/340,875
Filing Date:1999-06-28
Priority Date:1998-07-17
Art Unit:7
Classifications
IPC:
G06T 1500
Field of Search:
345419345420345440345441345156345157
Patent Drawings (25 sheets)
Description
CROSS-REFERENCE TO RELATED APPLICATION
[0002] This application is based on and claims priority to U.S. Provisional Patent Application Ser. No. 60/093,304, filed Jul. 17, 1998, entitled “Method and Apparatus for Sculpting Virtual Objects in a Haptic Virtual Reality Environment,” the entire contents of which are incorporated herein by reference.
FIELD OF INVENTION
[0003] The invention relates generally to a method and apparatus for interacting with virtual objects in a haptic virtual reality environment, and more specifically to a method and apparatus for using virtual tools to interact with virtual objects in a haptic virtual reality environment.
BACKGROUND OF INVENTION
[0004] Computers have been long used to display objects in a computerized environment. Examples are CAD (computer-aided design) systems that are used in the design of mechanical parts, such as parts used in an assembly process. For example, a designer may use a CAD system to design parts for an automobile, which are then produced and used in an automobile assembly line. Such CAD systems require significant training and understanding in using the computerized design system. CAD systems are typically difficult to use and lack the freedom and expressiveness of traditional noncomputerized drawing, sketching, and model-making procedures.
[0005] A more modern approach uses a virtual reality technique to model objects in a computerized virtual environment. Virtual Reality (VR) is an artificial environment constructed by a computer which permits the user to interact with that environment as if the user were actually immersed in the environment. Early VR devices permitted the user to see three-dimensional (3-D) depictions of an artificial environment and to move within that environment. The reality of the VR environment is enhanced by the ability of a user to manipulate virtual objects within the virtual environment using hand motions and gestures. A designer may use a virtual tool to manipulate and/or modify a computerized model or virtual object in the virtual environment. However, a designer must be able to accurately evaluate the virtual object. One way the designer can evaluate the virtual object is by touching and feeling the surface of the object by using a virtual tool which the designer controls through a haptic interface device, such as a joystick, glove, stylus or other physical device.
[0006] Many existing virtual reality techniques do not provide for a realistic feeling of interaction by the designer. The designer cannot feel when virtual tools touch the virtual object. Moreover, in some cases, the virtual tool may pass through the virtual object without any impediment, thereby severely degrading the realism of the experience and the designer's ability to feel all parts of the virtual object accurately.
SUMMARY OF INVENTION
[0007] Thus, there is a need for a 3-D computerized modeling system that overcomes the problems of CAD techniques and traditional noncomputerized modeling techniques. One object of the invention is to provide a haptic feedback approach that aids the user of the system in evaluating the whole object including special features by giving the user useful interactive force feedback. This feedback is particularly useful when the user skirts the surface of a virtual object and encounters a special case such as an edge, a “hole,” or other feature in the virtual object, or attempts to penetrate it.
[0008] Being able to feel the virtual object allows the user to resolve visual ambiguities, such as a shape that may appear either concave or convex as perceived by an observer. The user may rely on haptic feedback when modifying the object such as scratching a slight groove in the object, which the user then deepens or expands while receiving feedback through the tool on the shape and current depth of the groove. Feedback also allows the designer to monitor and modulate the cutting rate or amount of change induced by the virtual tool. Haptic feedback also helps the user navigate around and on the surface of the object; that is, using the feel of the object to know where the virtual tool is on the object.
[0009] The system of the invention may be used for different purposes such as in a medical teaching system, in other educational systems, for seismic data analysis and interpretation, in a computer game, and other purposes.
[0010] The invention relates to a method for interfacing with a virtual object in a haptic virtual environment, including the steps of generating a virtual object including a virtual surface in the haptic virtual environment; sensing a location of a user in real space; determining a virtual tool having discrete points for use by the user in the haptic virtual environment; determining a haptic interface location in the haptic virtual environment in response to the location of the user in real space; determining locations for the points of the virtual tool in the haptic virtual environment in comparison to the haptic interface location and the location of the virtual surface; determining a geometry for the virtual surface at an area of penetration of the virtual tool if one or more of the points penetrates the virtual surface; and limiting movement of the virtual tool based on (i) the geometry of the virtual surface, (ii) the location of one or more points, and (iii) the haptic interface location.
[0011] In another embodiment of the invention, the method includes limiting movement of the virtual tool by moving the position of the virtual tool toward the haptic interface location. In a further embodiment, the method includes determining a surface direction vector in response to the location of one or more points of the virtual tool and determining if one or more of the points penetrates the virtual surface. In another embodiment, the method includes determining the geometry of the virtual surface to be an edge geometry. In another embodiment, the method includes calculating an interaction force between the virtual object and virtual tool in response to determining the locations of the points of the virtual tool.
[0012] The invention also relates to a system for interfacing with a virtual object in a haptic virtual environment. The virtual object includes a virtual surface. The system also includes a haptic interface device, a virtual tool, and a modeling application. The haptic interface device senses a location of a user in real space. The virtual tool includes a plurality of discrete points for use by the user in the haptic virtual environment. The modeling application is in communication with the haptic interface device, the virtual object, and the virtual tool, and the modeling application (a) determines a haptic interface location in the haptic virtual environment in response to the location of the user in real space; (b) determines locations for the points of the virtual tool in the haptic virtual environment in comparison to the haptic interface location and the location of the virtual surface; (c) determines a geometry for the virtual surface at an area where one or more points of the virtual tool penetrates the virtual surface; and (d) limits movement of the virtual tool based on (i) the geometry of the virtual surface, (ii) the location of one or more points of the virtual tool, and (iii) the haptic interface location.
[0013] In one embodiment, the modeling application limits the movement of the virtual tool by moving the virtual tool toward the haptic interface location. In another embodiment, the system includes a surface direction vector that the modeling application determines based on the locations of one or more points of the virtual tool that have penetrated the virtual surface. In another embodiment, the geometry of the virtual surface is an edge geometry. In a further embodiment, the modeling application calculates an interaction force between the virtual object and the virtual tool based on the locations of the points of the virtual tool.
[0014] In another embodiment, the invention relates to a method for interfacing with a virtual surface in a haptic virtual environment, including the steps of generating a virtual surface in the haptic virtual environment; sensing a location of a user in real space; determining a virtual representation of the user in real space, the virtual representation comprising a plurality of discrete points; determining a haptic interface location in the haptic virtual environment in response to the location of the user in real space; determining a virtual representation location in the haptic virtual environment; moving the virtual representation location toward the haptic interface location in the haptic virtual environment; and limiting movement of the virtual representation based on a geometry of the surface and on preventing any one of the plurality of discrete points of the virtual representation from substantially penetrating the virtual surface.
BRIEF DESCRIPTIONS OF THE DRAWINGS
[0015] The invention is pointed out with particularity in the appended claims. The above and further advantages of this invention may be better understood by referring to the following description taken in conjunction with the accompanying drawings, in which:
[0016] FIG. 1 depicts a functional block diagram of a system for one embodiment of the invention, including a haptic interface device, modeling application, and graphics display;
[0017] FIG. 2A provides a pictorial view of a virtual environment including a virtual object and a virtual tool, for one embodiment of the invention;
[0018] FIG. 2B provides a pictorial view of a virtual tool contacting the virtual surface of a virtual object in connection with a haptic interface location within the virtual object, for the embodiment of the invention shown in FIG. 2A;
[0019] FIG. 3 illustrates a high-level flowchart of the haptic rendering process between a virtual tool and virtual object, for one embodiment of the invention;
[0020] FIG. 4 is a high-level flowchart of the haptic rendering process between a virtual tool and a virtual object for another embodiment of the invention;
[0021] FIG. 5A illustrates a pictorial view of a virtual tool approaching the virtual surface of a virtual object;
[0022] FIG. 5B illustrates a pictorial view of a proposed location for a virtual tool with one point of the virtual tool penetrating the virtual surface of the virtual object, for the embodiment shown in FIG. 5A;
[0023] FIG. 5C illustrates a pictorial view of a proposed location for the virtual tool with two points of the virtual tool penetrating the virtual surface of the virtual object, for the embodiment shown in FIG. 5A;
[0024] FIG. 5D illustrates a pictorial view of a virtual tool moving along the virtual surface of a virtual object, for the embodiment shown in FIG. 5A;
[0025] FIG. 5E illustrates a two dimensional pictorial view of a virtual tool moving along a concave edge in the virtual surface of a virtual object for the embodiment shown in FIG. 5A;
[0026] FIG. 5F illustrates a three dimensional pictorial view of a virtual object moving along a concave edge, for the embodiment shown in FIG. 5E;
[0027] FIG. 6 illustrates a virtual tool with points located throughout the interior of the tool;
[0028] FIGS. 7A-7C depict flowcharts of the haptic rendering process between a virtual object and virtual tool for one embodiment of the invention;
[0029] FIG. 8A illustrates a pictorial view of a virtual tool encountering the convex edge of a virtual object for one embodiment of the invention;
[0030] FIG. 8B illustrates a pictorial view of a surface direction vector calculated for one proposed tool position for the embodiment of the invention shown in FIG. 8A;
[0031] FIG. 8C illustrates a pictorial view of a surface direction vector calculated for a second proposed tool position for the embodiment shown in FIG. 8A;
[0032] FIG. 8D illustrates a pictorial view of virtual tool constrained to the edge of a virtual object for the embodiment of the invention shown in FIG. 8A;
[0033] FIG. 9 depicts a set of voxels with different density values and an isosurface;
[0034] FIG. 10 illustrates a two dimensional representation of a rectangular solid with voxels and an isosurface, for the embodiment shown in FIG. 9;
[0035] FIG. 11 illustrates a ramp length diagram comparing voxel values to penetration distances for one embodiment of the invention;
[0036] FIG. 12 illustrates a pictorial view of the surface direction vector of a point and surrounding density evaluation points for one embodiment;
[0037] FIG. 13 illustrates a schematic view of a gradient for a virtual object, including a last SCP, a current SCP, an initial point, and a midpoint for one embodiment;
[0038] FIGS. 14A, 14B, and 14C illustrates pictorial views of a virtual surface and the endpoints of a segment that intersects the a virtual surface of a virtual object for one embodiment of the invention;
[0039] FIG. 15 illustrates a pictorial view of previous surface contact points, tangency planes, and resulting surface contact point for one embodiment of the invention;
[0040] FIGS. 16A and 16B show a pictorial view of a spherical virtual tool in a channel formed between two virtual objects and;
[0041] FIGS. 17A-17E show pictorial views of a virtual tool encountering a surface and moving along the surface constrained by a constraint plane.
DETAILED DESCRIPTION OF THE INVENTION
[0042] The description includes headings and subheadings that aid in organizing the text, but are not meant to be limiting in any way. Topics discussed under a heading or subheading may also be described elsewhere throughout the specification.
[0043] FIG. 1 shows a system for one embodiment of the invention, including a haptic interface device 10, modeling application 12, and graphics display 14 in electrical communication with each other. The modeling application 12 includes a haptic rendering process 16, a virtual tool and object interaction process 18, a virtual object modification process 20, and a graphics process 22 all in electrical communication with each other.
[0044] Generally, a user of the system uses the haptic interface device 10 to interact with the virtual object 26 (see FIG. 2) receiving force feedback produced by the haptic rendering process 16 and viewing graphics rendered by the graphics process 22 on a graphic display 14.
[0045] Software Process
[0046] In one embodiment, a “process”, as referred to in FIG. 1, is a software process executing on a hardware microprocessor. All the processes may execute on one microprocessor, or in other embodiments, one or more processes may execute on different microprocessors, which are linked by buses, cables, local networks, wide area networks, or global computer networks, such as the Internet.
[0047] The modeling application 12 is viewed in FIG. 1 as a software application executing on one computer system. In another embodiment, the modeling application 12 executes on one or more computer systems connected by a communications device, such as a bus, cable, or network connection. In an alternate embodiment, the modeling application is a hardware device, such as an ASIC (application specific integrated circuit), and one or more processes of the application are implemented on one or more ASIC devices. In a further embodiment, the modeling application 12 is implemented as one or more objects, which may execute on one or more computer systems. In one embodiment, the modeling application 12 runs on a dual 300 MHz Intel® Pentium® 2 computer running Microsoft® Windows NT™ 4.0 using an Open GL accelerated graphics card.
[0048] The modeling application 12 is not required to include a haptic rendering process 16, an interaction process 18, a modification process 20, and a graphics process 22. In one embodiment, the functions of the modeling application 12 are implemented by a different number of processes. In one embodiment, the modeling application 12 includes the haptic rendering process 16 and the graphics process 22.
[0049] In one embodiment, the invention is implemented using an object-oriented approach. The haptic rendering process 16 and other processes are implemented as software objects. In another embodiment, the virtual object 26 and the virtual tool 28 are implemented as software objects and perform one or more of the functions of the haptic rendering process 16. In one embodiment, the virtual tool 28 is a software object that performs such functions as determining if contact has occurred with a virtual object 26 and determining the surface direction vector 101, as will be discussed later.
[0050] In one embodiment, the virtual object 26 and the virtual tool 28 are implemented as software objects in the C++ programming language. In other embodiments, the virtual object 26 and virtual tool 28 are implemented using an object-oriented programming language other than C++.
[0051] In one embodiment, the modeling application is a computer program stored on a computer readable storage media, such as a CD disc, diskette, tape, or other media. In another embodiment, the modeling application is a computer program distributed over a computer-readable propagated signal, such as a program distributed over the Internet.
[0052] Haptic Interface Device
[0053] In one embodiment, the system includes a haptic interface system, as shown in FIG. 1, including the haptic interface device 10 and the haptic rendering process 16 which generates a virtual object of the virtual environment to be “touched” and determines the results of the interaction (discussed in more detail below). The haptic interface device 10 is a tactile or force-feedback device which provides the touch sensations of interacting with virtual objects 26 to a user of the system. Some haptic interface devices 10 consist of an electromechanical linkage which can exert a controllable force on a user's hand. See, for example, U.S. Pat. No. 5,625,576 issued to Thomas H. Massie and J. Kenneth Salisbury, Jr., the disclosure of which is herein incorporated by reference in its entirety. As used herein, “haptic rendering” refers to the creation of a virtual environment with which a user can interact through the sense of touch. The term “haptic rendering process” 16 refers to the computer program which generates the haptic aspects of the virtual environment and determines the forces to be applied to a user through a haptic interface. The haptic rendering process 16 generates haptic representations of virtual objects in the virtual environment.
[0054] Overview of Device, Virtual Object and User Interaction
[0055] FIG. 2A shows a haptic virtual environment including a virtual object 26 and a virtual tool 28. The virtual object 26 of the embodiment shown in FIG. 1 is depicted as a 3-D (three dimensional) block of material typically “floating” in the virtual space of the virtual environment. The virtual object 26 has a virtual surface 25 that represents the “skin” of the virtual object 26. The virtual tool 28 is represented in FIG. 2A as a sphere 34 with a rod or “handle” 32 connected to it.
[0056] In one embodiment, the user uses a haptic interface device 10 in real space to grasp or manipulate the handle 32 of the virtual tool 28 in virtual space. In one embodiment, the location of this handle with respect to the virtual tool 28 can be changed interactively by the user. As used herein, a “haptic virtual environment” refers to a computer-generated virtual environment that can be explored by a user through the sense of touch. In one embodiment, the haptic virtual environment contains a virtual object 26 that is model of a real world object that a user is creating in the virtual environment. In another embodiment, the haptic virtual environment incorporates two or more virtual objects 26 that are linked to each other, such as in a hierarchical arrangement. It should be understood that the interaction and/or modification methods described herein may be readily extended to apply to two or more virtual objects 26 linked or associated in a haptic virtual environment.
[0057] FIG. 2B illustrates a virtual tool 28 contacting the virtual surface 25 of a virtual object 26. The user guides the virtual tool 28 using the haptic interface device 10, represented, in this embodiment, by a stylus 33 in FIG. 2B. The position and orientation of the tip of the stylus 33 indicate the haptic interface location 98. Note that, although the user may be manipulating a literal stylus in some embodiments, the haptic interface location 98 could be controlled by a user interacting with any number of differently shaped elements such as a thimble, a yoke, or a ball. The tip of the virtual stylus 33 is indicated by the haptic interface location 98. In one embodiment, the haptic rendering process 16 tracks the haptic interface location 98, but does not otherwise track the shape or location of the entire haptic interface device 10.
[0058] The haptic rendering process 16 attempts to move the virtual tool 28 so that the origin 27 of the virtual tool 28 matches the haptic interface location 98. However, unless the haptic rendering process 16 is using the virtual tool 28 to remove material from the virtual object 26, then the haptic rendering process 16 typically does not allow the virtual tool 28 to penetrate the virtual object 26. Thus, as shown in FIG. 2B, the user has attempted to move the virtual tool 28 into the virtual object 26, which is indicated by the haptic interface location 98 within the virtual object 26. The haptic rendering process 16 calculates a resistance to the movement of the virtual tool 28 into the virtual object 26. This calculation is based on a connection 29 between the tool origin 27 and the haptic interface location 98, as will be discussed in more detail later. In one embodiment, the connection 29 includes a virtual spring 31. In one embodiment, the connection 29 includes a virtual dash-pot. Thus, if the user attempts to move the virtual tool 28 further into the virtual object 26, the haptic rendering process 16 calculates an increasing resistance force that is fed back to the user through the haptic interface device 10 based on the virtual spring 31.
[0059] In one embodiment, the user is allowed to move the virtual tool 28 through the virtual object 26 without resistance while removing material. In this case, the user selects a transparent or translucent mode, and the virtual tool 28 appears translucent. The haptic rendering process 16 allows the user to move the virtual tool 28 through the virtual object 26 without constraint or resistance.
[0060] Description of Virtual Tool and Modification Options
[0061] As already described, the user interacts with the virtual object 26 in the virtual environment through a virtual tool 28. The user may select any shape for the tool 28. The shape of the tool 28, along with other characteristics, such as interaction mode, determine the interaction with the virtual object 26. In one embodiment, the tool 28 may be represented as a series of discrete points in virtual space which outline a three-dimensional shape of the tool 28. The virtual tool 28 is modeled as a set of discrete points for the purposes of haptic interaction and collision detection with the virtual object 26. In another embodiment, the points of the virtual tool 28 are created by an algebraic equation or any other continuous or piecewise mathematical method suitable for determining a 3-D shape in a virtual environment. In another embodiment, the tool 28 can be represented directly by continuous or piecewise mathematical equations, rather than by discrete points. The virtual tool 28 may take on any of a number of shapes that may be useful for a user when using a virtual tool 28 to create a virtual object 26 in the virtual environment. Typical shapes may include a sphere or cylinder. In another embodiment, the user selects one or more interaction modes for the virtual tool 28, such as a sandpaper mode, which causes the tool 28 to remove material gradually from the virtual object 26, much like using real sandpaper to smooth the shape of a block of wood in the real world.
[0062] Creating and Manipulating the Virtual Object
[0063] FIG. 3 illustrates a flowchart of the haptic rendering process between a virtual tool 28 and virtual object 26. First, a virtual object 26 is generated (step 40). Typically, this occurs when the user requests that an initial virtual object 26 be created, for example, by directing that the virtual object 26 assume a 3-D cube or “block” shape. In one embodiment, the initial virtual object can be defined as a shape generated from a saved file, scanner, or 3D digitizer. In one embodiment, the user selects an interaction mode that selects the characteristic of the virtual object 26. The shape and material, and surface properties of the virtual object 26 can be specified, for example, the hardness or softness of the object 26. For example, if the user selects a sculpting mode, then the virtual object 26 assumes characteristics generally representative of a block of clay. If the user selects a 3-D sketch mode, then the virtual object 26 is overlaid with a stack of planes or slices, and the user sketches a template on the surface of one of the planes. However, the virtual object 26 is not required to assume a cube or block shape and may assume any 3-D shape that the user finds useful when starting to design a model from the virtual object 26. In one embodiment, the object properties permit only manipulation or movement of the virtual object 26 without any sculpting or other modification thereof. The modification mode is not limited to what is described here, but, in other embodiments, is based on other modes of interaction or modification that a user finds useful. For example, other modes may include smoothing the surface of the virtual object 26, shifting material, or mirroring all or parts of the object 26.
[0064] In one embodiment, the virtual object 26 is created by the modification process 20 under the directions of the user, and then the graphics process 22 displays a corresponding representation of the virtual object 26 to the user.
[0065] If the user selects a 3-D sketch mode, then the virtual object 26 is overlaid with a stack of planes or slices, and the user sketches a template on the surface of one of the planes.
[0066] Generating the Virtual Tool
[0067] In the next step, a virtual tool 28 is generated (step 42). In one embodiment, the user selects a shape and characteristics for the virtual tool 28, which the haptic rendering process 16 generates in the virtual environment. The graphic process 22 then displays a corresponding version of the virtual tool 28 to the user on a graphics display 14. For example, the virtual tool 28 can assume different shapes and interaction or modification characteristics. The tool 28 can assume any 3-D shape, such as a sphere 34 or a cube, or a substantially 2-D shape, such as a spatula or knife. In general, modes include a material removal, material addition, or other material modification mode such as smoothing. In one embodiment, removal modes include Boolean removal, sand paper removal, and removal using the concept of a function which falls off gradually. Additional modes include Boolean addition, Boolean pull, and pull using a fall-off function. An additional form of interaction and modification includes a sketch mode for sketching a template on the surface of a virtual object 26. Used here, Boolean refers to adding or subtracting two geometries to arrive at a third geometry.
[0068] Sensing User Location
[0069] In the next step, sensors determine the location of a user in real space (step 44). In one embodiment, the sensors are any type of sensors useful in determining the location of a user, such as the location of a hand in real space. Such sensors could be based on measurements of location based on mechanical, electrical, magnetic, optical, or other sensing devices. In one embodiment, the haptic interface device 10 senses the location of the user in real space. For example, the user physically manipulates the haptic interface device 10, such as a handgrip or stylus, in real space and the location of this device is determined in real space. In one embodiment, one such haptic interface device 10 is the PHANToM® device from SensAble Technologies, Inc., Cambridge, Mass. Generally, the PHANToM® device can sense six degrees of freedom—x, y, z, pitch, roll, yaw, while providing for force feedback in three degrees of freedom—x, y, z. One embodiment of this invention includes a haptic interface that can provide more than three degrees of force feedback.
[0070] As used herein, “real world space” is defined as the real world environment. The haptic rendering process 16 utilizes the information obtained by the sensors to determine the haptic interface location 98 in the virtual environment. As used herein, “haptic virtual environment” refers to the region in the computer generated virtual environment with which the user can interact through the sense of touch. The location of the haptic interface describes the location of the user in the haptic virtual environment.
[0071] Correlating User Location and Virtual Tool Position
[0072] In one embodiment, the haptic rendering process 16 then translates the location of the haptic interface device 10 in real space into a corresponding location in the haptic virtual environment, which is the haptic interface location 98 (step 46). Then the haptic rendering process 16 uses a method to limit the movement of the tool 28 based on the virtual surface 25, the position of the tool 28, and the haptic interface location 98 (step 54). The objective of the method is to move the tool 28 as close as possible to the haptic interface location 98, without crossing the virtual surface 25 and using a path for the tool 28 that yields progressively better locations for the tool 28, which typically means locations closer to the haptic interface location 98. This method is discussed in detail later.
[0073] Typically, the haptic rendering process 16 analyzes the interaction and calculates results based on the potential position of the virtual tool 28 relative to the virtual object 26 (step 56). Then the results are applied to the virtual tool 28 and/or the user (step 58).
[0074] Calculation of Force
[0075] For example, if the movement of the virtual tool 28 is constrained such that the virtual tool origin 27 is not coincident with the haptic interface, the haptic rendering process 16 may calculate an interaction force to be applied to the haptic interface device 10, so that the user feels a resistance to trying to move the virtual tool 28 into the virtual object 26. In this case, the results are a feedback force applied to the user via the haptic interface device 10 and corresponding constraints or limits on the movement of the virtual tool 28 (step 56). The force feedback provides the user important non-visual information about the shape of the virtual object, whether the interaction mode is object modification or simply evaluating the shape of the object.
[0076] Interaction and Modification
[0077] In one embodiment, if the user is using the virtual tool 28 in an interaction mode, such as sandpaper, then the modification process 20 calculates changes in the virtual object 26, such as material being removed, which in turn changes the graphical representation of the virtual object 26. The results, in this case, are a modification to the virtual object 26 (step 58). Interaction modes need not result in modification of the virtual surface. For example, in another case, the user may be trying to use the virtual tool 28 to evaluate the shape of the virtual object 26 without trying to modify the object 26. In this case, the results are limits on the movement of the virtual tool 28 without any penetration or modification of the virtual object 26. Another example is if the user presses the virtual tool 28 into a virtual object 26 in an erase or removal mode, but does not press with enough force, then the virtual tool 28 remains at the surface or may skirt along the surface of the virtual object 26 without removing any material. The results, in this case, are constraints on the movement of the virtual tool 28 (step 58). The calculation and application of results (steps 56 and 58) are not confined to what is described here but involve other effects depending on many factors, such as the shape of the virtual tool 28, the characteristics of the tool 28, the characteristics of the virtual object 26, the nature of the movement of the virtual tool 28 relative to the virtual object 26, and other factors. Another factor may be a construction constraint that aids in the construction of a virtual object 26. In one embodiment, the constraint can be a line, an arbitrary curve, or a surface that constrains the movement of the virtual tool 28.
[0078] Ongoing Interaction between User and System
[0079] Finally, after the results have been applied (step 58), the user engages in additional movement of the haptic interface device 10, in which case a new location must be sensed (step 44) and steps 46-58 are repeated. Alternatively, the user changes the nature of the virtual object 26 and/or the interaction mode. The user may also change the shape or characteristics of the virtual tool 28 (not shown in FIG. 3). These changes by the user in turn would affect the calculations, constraints, and results determined by steps 46, 54, 56, and 58.
Virtual Object and Tool Interaction
[0080] Haptic Rendering Process
[0081] FIG. 4 is a flowchart of the haptic rendering process 16 for the interaction between a virtual object 26 and a virtual tool 28 for one embodiment of the invention. In the first steps, the haptic rendering process 16 generates a virtual object 26 (step 60). The haptic rendering process 16 determines or generates a virtual tool 28 represented using a plurality of discrete points for use by the user (step 62). Sensors sense the location of the user in space (step 64) in a manner similar to that described for FIG. 3 above. The haptic rendering process 16 then determines a haptic interface location 98 (see FIG. 5A) for the haptic interface (step 66) in the haptic virtual environment corresponding to the location of the haptic interface device 10, which the user is manipulating in real space. The haptic rendering process 16 determines potential locations for the points of the virtual tool 28 in the haptic virtual environment in comparison to the haptic interface location 98 and the virtual surface of the virtual object 26 (step 68).
[0082] The haptic rendering process 16 determines the amount of penetration into the virtual object 26 for all the points of the virtual tool 28 if it were to be moved to the potential location (step 70). The haptic rendering process 16 may determine that there would be no penetration, that only one point of the virtual tool 28 would penetrate the virtual object 26, or that several points of the virtual tool 28 would penetrate the virtual object 26.
[0083] If at least one of the points of the virtual tool 28 has penetrated the virtual object 26, then the haptic rendering process 16 determines a geometry for the virtual surface at the area of penetration of the virtual tool 28 (step 72). For example, the haptic rendering process 16 determines if the virtual object 26 has an edge, trough, valley, vertex, or hole in the vicinity of the virtual tool 28, to be discussed in more detail later with respect to FIGS. 7A-7C. This determination is then used in the next step (step 74), which determines limits or constraints for the movement of the virtual tool 28 based on the geometry of the virtual object 26 (as determined in step 72), the locations of the points of the virtual tool 28 that would have penetrated the virtual object 26 (as determined in steps 68 and 70), and the haptic interface location 98 (as determined in step 66). The haptic rendering process 16 then uses the previously determined constraints to constrain or limit the movement of the virtual tool 28 (step 76). For example, if the virtual tool 28 has encountered an edge or trough on the surface of the virtual object 26, then the virtual tool 28 may be constrained to slide along the edge or trough (see FIG. 5E) until the user makes a definitive movement, such as moving away from the virtual object 26. In one embodiment, the movement of the virtual tool 28 is limited without the user feeling any force feedback. In another embodiment, the movement of the tool 28 is limited and the user feels an interactive force feedback corresponding to the limits on movement of the tool 28.
[0084] Relationship of Virtual Tool Location to Haptic Interface Location
[0085] FIG. 5A illustrates a virtual tool 28 approaching the virtual surface 25 of a virtual object 26. The surface of the virtual tool 28 is defined by a series of points, S1, S2, S3, S4, S5, S6 in a simplified view of a virtual tool 28 in one embodiment.
[0086] In another embodiment of the invention, the points that define the volume of the virtual tool 28 extend throughout the space of the virtual tool 28 (shown as additional interior points 112 within the tool 28 in FIG. 6). In one embodiment, the additional points 112 are spaced evenly throughout the interior 3-D volume of the tool 28. In another embodiment, there is no requirement that the additional points 112 be spaced evenly within the tool 28.
[0087] In the example shown in FIG. 5A, the user is moving the haptic interface device 10 so that the virtual tool 28 is moving toward the virtual surface 25 of the virtual object 26. The haptic rendering process 16 attempts to move the origin 27 of the virtual tool 28 to match the haptic interface location 98. In the embodiment shown in FIG. 5A, the location of the virtual tool origin 27 lags behind the haptic interface location 98 as the user moves the virtual tool 28 through the virtual space.
[0088] Haptic Rendering and Graphics Rendering
[0089] It should be understood that the haptic rendering process 16 is operating at a high rate of speed, such as updating the location of the haptic interface location 98 and virtual tool 28 many times per second, as the user attempts to move the virtual tool 28 through the virtual environment. In one embodiment, the haptic rendering process 16 is updating the locations at about 1000 times per second. In one embodiment, some calculations of the haptic rendering process, such as force reaction calculations, are occurring at about 1000 times per second, while less time critical calculations of the haptic rendering process, such as geometry calculations, are occurring at slower rates, such as 100 times per second. The graphics process 22 updates the image seen by the user on the graphics display 14, but typically at a lower refresh rate than the haptic rendering process 16. In one embodiment, the graphics process 22 updates the graphics display 14 at a rate of about 60 times per second.
[0090] Example of Tool Points Penetrating Virtual Object
[0091] FIG. 5B illustrates one point S4 of a virtual tool 28 encountering the virtual surface 25 of the virtual object 26, for the embodiment shown in FIG. 5A. The haptic rendering process 16 attempts to move the virtual tool origin 27 to match the location of the haptic interface 98, but determines that a point, S4, of the virtual tool 28 would cross the virtual surface 25. The haptic rendering process 16 then determines the approximate minimum distance vector 101 in a direction toward the virtual surface for a point S4. This vector 101, later referred to as the surface direction vector 101, also has the property that it is the approximate normal vector to the virtual surface 25 where it crosses the surface 25. As described in more detail later, the haptic rendering process 16 uses this vector 101 to calculate movement constraints for the virtual tool 28, as the virtual tool origin 27 is progressively moved toward the haptic interface location 98. In general, the haptic rendering process 16 attempts to keep the points of the tool 28 outside of the virtual surface 25 of the virtual object 26; that is, the object 26 is treated as a solid.
[0092] Example of More than One Point Encountering the Virtual Object
[0093] FIG. 5C illustrates two points, S3 and S4, of the virtual tool 28 encountering the virtual surface 25 of a virtual object 26, for the embodiment shown in FIG. 5A. In this case, the virtual tool 28 encounters the virtual surface 25 at a different orientation than the one shown in FIG. 5B. For example, the user has rotated the virtual tool 28 slightly or is moving the virtual tool 28 at a slightly different angle, so that two points, S3 and S4, are encountering the virtual surface 25 rather than the one point, S4, as shown in FIG. 5B. The surface direction vector 101 shown in FIG. 5B is based on point S4. In FIG. 5C, the surface direction vector 101 is based on point S4 as it has penetrated the virtual surface 25 more than point S3. In the embodiment shown, if multiple points penetrate the virtual surface 25, the surface direction vector 101 is calculated for the point of deepest penetration. Other embodiments may use a combination of all points which are penetrating to calculate a resulting minimum surface direction vector 101.
[0094] Local Geometry Constrains Motion
[0095] FIG. 5D illustrates a virtual tool 28 skirting along the virtual surface 25 of a virtual object 26, for the embodiment shown in FIG. 5A. A plane of tangency or constraint plane 104 is formed that is orthogonal to the surface direction vector 101 that was previously calculated. In FIG. 5D, the plane of tangency 104 is shown aligned with the origin 27 of the virtual tool 28. In other embodiments, the plane of tangency 104 may be aligned differently, such as at or near the virtual surface 25 of the virtual object 26, as long as the plane of tangency 104 constrains the movement of the virtual tool 28 substantially parallel to the virtual surface 25. In FIG. 5D, the plane of tangency extends out of the plane of the diagram. The virtual tool 28 is allowed to move along the plane of tangency 104. The movement is shown by the direction of movement or motion vector 106a.
[0096] FIG. 5E provides a two dimensional view of a virtual tool 28 constrained to move along an inside or concave edge 108. FIG. 5F illustrates a 1 three dimensional view of the virtual tool 28 constrained to move along an edge 108 of a trough or valley 110 for the embodiment of the invention shown in FIG. 5E. The virtual tool 28 is constrained to move in the direction of a vector 106bthat constrains the tool 28 to move in a direction approximately parallel to the concave edge 108 toward a haptic interface location 98. FIG. 5F provides another pictorial view of a the tool 28 moving along a vector 106bapproximately parallel to the concave edge 108 of the virtual object 26.
[0097] Modification of the Virtual Object
[0098] If the virtual tool 28 is in a removal mode, the modification process 20 may also determine material to be removed from the virtual object 26 in response to the shape of the virtual tool 28. In one embodiment, this removal mode is termed a carving mode. In one embodiment, the user feels a resistive force when attempting to move the virtual tool 28 into the virtual object 26 because forward motion of the virtual tool 28 into the object 26 is not allowed. Forward motion of the tool 28 is only achieved as a result of the modification process 20 changing or deforming the geometry of the virtual object 26 in a manner that simulates carving of the virtual object 26. The haptic rendering process 16 continues to treat the virtual object 26 as a solid object as material is removed or added. For example, the user feels added material as solid, since movement of the virtual tool 28 into the material is not permitted.
[0099] Case 1 of Tool in Empty Space
[0100] FIGS. 7A-7C depicts flowcharts of the haptic rendering process 16 which calculates interactions between the virtual object 26 and the virtual tool 28 for one embodiment of the invention. These flowcharts represent movement of the virtual tool 28 in steps relative to the virtual surface 25 of a virtual object 26. First, the aptic rendering process 16 proposes to move the virtual tool origin 27 toward the haptic interface location 98 (step 120). Then the haptic rendering process 16 determines if any of the tool 28 points would penetrate the virtual surface 25 (step 122). If none of the tool 28 points would penetrate the virtual surface 25, this represents “Case 1.” The virtual tool 28 would encounter only empty space by moving to the proposed new location, so the incremental movement of the virtual tool origin 27 is allowed (step 121) and the haptic rendering process 16 returns to step 120.
[0101] Case 2 of Tool Penetrating the Virtual Surface
[0102] If at the proposed tool position, some points of the virtual tool 28 would penetrate the virtual surface 25 (step 122), then the haptic rendering process 16 finds the direction of shortest distance to the virtual surface as indicated by surface direction vector 101 for the point of the greatest potential penetration into the virtual object 26 by the virtual tool 28 (step 126, see also FIGS. 5B and 5C). The haptic rendering process 16 then calculates a constraint plane or plane of tangency 104 (see FIG. 5D) based on the surface direction vector 101 (step 127 of FIG. 7A). The plane of tangency 104 is a plane orthogonal to the surface direction vector 101. The haptic rendering process 16 then attempts to move the virtual tool origin 27 toward the haptic interface location 98 but constrains the movement to the plane of tangency 104 (step 130) to arrive at a second proposed virtual tool 28 location.
[0103] If none of the tool 28 points would penetrate the virtual surface 25 at this second proposed virtual tool position (step 132), then the haptic rendering process 16 moves the virtual tool origin 27 to the second proposed location (step 121) and returns to step 120. This situation represents “Case 2” and the haptic rendering process 16 has assumed that the virtual tool 28 is intended to be touching the surface 25 of the virtual object 26.
[0104] Case 3 of Tool Encountering Edge Condition
[0105] If at the second proposed tool position, some points of the virtual tool 28 would penetrate the virtual surface 25 (step 132), then the haptic rendering process 16 finds the two surface direction vectors 181aand 181bof the virtual object 26 at the tool's 28 two points of greatest penetration at each of the previous two proposed tool positions (step 136). FIG. 8A illustrates a virtual tool 28 encountering the outside or convex edge 177 of a virtual object 26 in one embodiment of the invention. The virtual object 26 extends out of the plane of the diagram, and has an edge 177 that likewise extends out of the plane of the diagram. In FIG. 8B the proposed tool position penetrates the virtual object 26 at point S41and the haptic rendering process 16 calculates a surface direction vector 181arelative to virtual surface 25a.In FIG. 8C, the haptic rendering process 16 proposes a second proposed tool location based on the surface direction vector 181arelative to virtual surface 25a,as shown in FIG. 8C. In this proposed tool location, point S32has penetrated the virtual object 26, and the haptic rendering process 16 calculates the surface direction vector 181brelative to virtual surface 25b.
[0106] The haptic rendering process 16 uses the vectors 181aand 181band the desired direction of movement to determine constraints to the tool motion, as follows. The haptic rendering process 16 calculates the cross product of the vectors 181a,181bfound in step 136 to generate an edge line and a direction of movement 182 (step 138 in FIG. 7B), as shown in FIG. 8D. The haptic rendering process 16 then determines the dot product of each minimum distance vector 181a,181bwith the direction of movement 182, as indicated by the user (step 140). The haptic rendering process 16 then determines if either dot product is greater than zero (step 140). If one of the dot products is greater than zero, then the haptic rendering process 16 takes the average of both surface direction vectors 181a,181b(step 142). The haptic rendering process 16 then proposes to move the tool 28 in the direction indicated by the average vector (step 144) and then proceeds to Case 2 (step 146). The haptic rendering process 16 then proceeds to step 127 in FIG. 7A to determine a plane of tangency 104 using the average normal.
[0107] If neither dot product is greater than zero (step 140), then the haptic rendering process 16 constrains movement to the previously determined edge line (step 148). See FIG. 8D, which shows the virtual tool 28 at the edge 177 of the virtual object 26. In one embodiment, the virtual tool 28 is constrained based on one point of the tool 28, such as the origin 27 of the tool 28. The haptic rendering process 16 then attempts to move the virtual tool origin 27 toward the haptic interface location 98 but constrains the movement to the direction of the edge 108 or 177 (step 148). If none of the tool points would penetrate the virtual surface 25 at this third proposed virtual tool position (checked in step 149), then the haptic rendering process 16 moves the virtual tool origin 27 to this proposed location (step 121) and returns to step 120.
[0108] This situation represents “Case 3,” and the haptic rendering process 16 assumes that the virtual tool 28 is on an edge 108 or 177 of the virtual object 26. Generally, in Case 3, the haptic rendering process 16 attempts to properly identify an edge 108 or 177 of the virtual object 26 and allow movement of the virtual tool 28 along the edge 108 or 177.
[0109] In one embodiment the haptic rendering process 16 identifies an edge 108 or boundary between two portions of the virtual surface 25 of a virtual object 26. The two portions are not required to be planar. For example, the two portions may have curved surfaces. The two portions are not required to be in contact but may represent portions of virtual surfaces 25 of two separate virtual objects 26 located in contact with or near each other.
[0110] Case 4 of Tool Encountering a Hole
[0111] If one or more points of the virtual tool penetrate the virtual surface 25 (step 149), the haptic rendering process 16 finds the surface direction vector 101 at the point of greatest potential penetration of the virtual object 26 by the virtual tool 28 (step 154). The haptic rendering process 16 then determines the penetration value at the point of greatest potential penetration and saves this value for subsequent use (step 156). The haptic rendering process 16 then attempts to move the virtual tool 28 in the direction of the surface direction vector 101 just determined (step 158). The haptic rendering process 16 then checks to see if no points of the virtual tool 28 at the proposed location penetrate the virtual surface 25 (step 160). If no points penetrate the virtual surface 2586, then the haptic rendering process 16 moves the tool 28 to the proposed location (step 121) and proceeds to step 120. This situation represents “Case 4,” which occurs if the virtual tool 28 is in a corner, recess, or “hole” in the virtual object 26.
[0112] If one or more points of the virtual tool 28 penetrate the virtual surface 25, then the haptic rendering process 16 proceeds to step 162 and determines if the penetration values at all the tool points would be less than the previously determined penetration value at the deepest potential penetration, as calculated in step 156. If all the tool points would be less than the previously determined penetration value, then the haptic rendering process 16 returns to step 154.
[0113] If all the tool points would not be less than the previously determined penetration value, then the haptic rendering process 16 proposes moving the virtual tool 28 in a random direction (step 166) from its previous potential position and goes to step 149.
[0114] Description of a Voxel-Based Approach
[0115] In one embodiment of the invention, the virtual object 26 is implemented as a volume using concepts of voxels 78, density, and an isosurface 86. FIG. 9 shows several voxels 78 having different density values 0, 51, 102, 153, 204, and 255, a gradient 80 established by these voxel values, and an isosurface 86. As used herein, density is not a physical property of the virtual object 26, but rather an abstract construct used for determining the shape of the virtual object 26. FIG. 10 illustrates a pictorial view in two dimensions of the voxels 78 of a three dimensional rectangular solid 82 with an isosurface 86 at value 128 indicating the solid surface of the rectangular solid 82. As shown in FIG. 10, the volume of the virtual object 26 is modeled using a 3-D array of evenly spaced elements or voxels 78 located at discrete points in the virtual environment 26. In another embodiment, the elements are not required to be arranged with regular spacing. Each voxel 78 stores a density value. Density values for points that lie between the discrete voxel points can also be evaluated using interpolation. The volume also stores a density threshold value. Points having a density value greater than the density threshold are considered to be inside the object. Points having a density value less than the density threshold are considered to be outside the object. As used herein, an “isosurface” 86 refers to a locus of points all having an identical density value. In one embodiment, the isosurface 86 whose density value equals the density threshold represents the virtual surface 25 of the virtual object 26. In one embodiment, as shown in FIG. 10 this density threshold is 128 and the voxel density values can range from 0 to 255. Thus a voxel representation facilitates an easy method for determining whether points on a virtual tool 28 lie inside or outside of a virtual surface 25 of a virtual object 26. All of the voxels 78 shown in FIG. 10 are associated with the rectangular solid 82, but a user moving a virtual tool 28 toward the rectangular solid 82 would not encounter a solid feeling surface until the virtual tool 28 contacts the isosurface 86. The user would not feel any resistance to moving the tool 28 when moving through the voxels 78 with density values, such 0, 51, and 102, which are less than 128.
Implementation of the Haptic Rendering Process
[0116] The haptic rendering process 16 between a virtual object 26 and virtual tool 28 is described in more detail below for one embodiment of the invention as implemented by the assignee, SensAble Technologies, Inc. of Cambridge, Mass.
[0117] The chosen volumetric representation is integrated with the GHOST® SDK (Software Developer's Kit) haptic interaction software developed by SensAble Technologies, which provides much of the necessary haptics functionality and reduces haptic virtual objects into a set of basic methods that are then handled correctly by GHOST® SDK. The GHOST® SDK uses the c++ programming language. The developer can create a high-level object which needs only to handle basic interactions such as determining vectors, without being required to address low-level processes such as generating forces on the haptics device, resolving multiple collisions, and other more complex issues addressed by the GHOST software.
[0118] Volume Implementation Using Voxels
[0119] Haptic virtual objects are handled by a volume class. One embodiment of the invention is the gstVolume class. The gstVolume class follows the specifications of the generally provided gstShape GHOST class and follows the behavior of general geometric classes.
[0120] As described previously, the volume is represented using a voxel grid, the density values of which define an implicit virtual surface or isosurface 86 for the virtual object 26 as described for FIGS. 9 and 10. A valid volume for this representation is created containing an established gradient 80.
[0121] The specific voxel values defining the gradient 80 depend on the shape of virtual object 26 being presented. In one embodiment, the voxel values may vary between 0 and 255, with the value 128 representing the virtual surface. Any modifications to the volume must also preserve the gradient 80 to avoid incorrect calculation of surface direction vectors 101 or penetration distances.
[0122] The voxel value at any point gives an indication of the penetration depth and the shortest distance between that voxel 78 and the surface 86 of the volume. The ramp length is the number of voxels 78 over which density values go from their minimum (0) to their maximum (255). Voxel values increase with the penetration depth until the values reach a maximum. All voxels 78 beyond that penetration depth are also set to that maximum value. Likewise, when moving farther from the virtual surface in a direction away from the volume, voxel values decrease until they reach the minimum value. All values in that direction beyond that distance are set to the minimum value.
[0123] The volume class is used to determine approximate surface direction vectors 101 to the surface 86 from any internal point or point along the surface 86 of the volume using the density gradient 80 as explained below. FIG. 11 illustrates a ramp length diagram comparing voxel values to penetration distances for one embodiment of the invention. FIG. 11 depicts a vertical axis 198 for voxel values, a horizontal axis 202 for the penetration distance, an isosurface line 205 representing a density threshold value of 128, a ramp length 206, a maximum voxel value 208 with a value of 255, and a penetration line 210 at the isosurface 86 corresponding to the density threshold value 128. The penetration line 210 indicates that any penetration to the right of the line is into the solid body of the virtual object 26.
[0124] Ramp Length
[0125] The maximum penetration depth where a gradient 80 exists is defined by the ramp length 206, the density range, and the density threshold value. For example, for a ramp length 206 with a value of 4, a density range of 0 to 255 and a density threshold of 128, any penetration beyond 1.99 voxels [4/255*(255−128)] from the isosurface 86 will not lie within the portion of the volume where the voxel values exhibit a gradient. As such, the amount of penetration beyond this distance cannot be reliably calculated. Beyond that, the voxel values will all be at the maximum value. In one embodiment, the maximum value is 255.
[0126] In one embodiment, the direction of the surface direction vector 101 is calculated to be the direction of largest voxel density value gradient at that point. For any point that lies within the portion of the volume which exhibits a density gradient 80 a surface direction vector 101 can be calculated which points to the virtual surface and whose magnitude is the distance to the surface 86. In other words, in this region of space, the volume class can return a surface direction vector 101 which, when added to the current location, returns a location that is near the surface 86 of the volume. The vector calculations contain the same limitations as the penetration distance calculations; that is, the surface direction vector 101 can only be calculated reliably within the portion of the volume which exhibits a density gradient 80.
[0127] Interpolating Values for Intermediate Points
[0128] Although the volume is characterized by a discrete array of voxels 78, it must be able to return a valid value at any point along the continuous range of its space, since the object it represents is continuous. For example, a line is characterized by two discrete points, but itself is continuous and can be evaluated at any point. If a value is requested at a point where a voxel 78 is present, then that particular voxel density value is returned. For spaces between voxels 78, the value may be resolved through tri-linear interpolation, a method of converting a discrete set of points into a continuous field. In another embodiment, the interpolation can be based on other methods, such as a quadric interpolation.
[0129] In one embodiment, the evaluation is accomplished in a single step via a mathematical formula that weights the contribution of each voxel 78 by its distance to the point being evaluated.
[0130] In one embodiment, voxels 78 are spaced one millimeter (that is, one world coordinate in a coordinate system based on millimeter spacing) apart. In other embodiments, the voxels 78 are spaced other distances apart. In general, there is constant spacing between each of the voxels 78, but there need not be for some embodiments. In further embodiments, memory management techniques may be utilized. A larger number of voxels 78 can be represented, and thus either the resolution or size of the object 26 can be increased.
[0131] Calculating Vectors
[0132] As stated previously, the required surface direction vector 101 at any point is determined using the direction of maximum density gradient at that point. This maximum density gradient is determined using central differences: the density value at a set distance from the point in the direction of each Cartesian coordinate in turn is determined, and the differences between those values determines the vector direction.
[0133] FIG. 12 illustrates a method of calculating the surface direction vector 101 of a point based on the density values of surrounding evaluation points. FIG. 12 shows a point 230 for which a direction vector 101 is being calculated. The surrounding evaluation points include a first evaluation point 232 with a value of 40, a second evaluation point 234 with a value of 100, a third evaluation point 236 with a value of 80, and a fourth evaluation point 238 with a value of 40. In one embodiment, each evaluation point is a voxel 78 and the values represent density values.
[0134] The vector and density computations are used to project any point within the virtual object 26 to the virtual surface 25 of the virtual object 26. Typically, this projection is used for the purposes of calculating the potential tool surface contact point 226. If a tool point 230 is penetrating deeper than the region in which a gradient exists 206, then no projection can be made directly from that point 230. Instead, the point must be first brought closer to the surface 25 (that is, to a region where a gradient 80 exists).
[0135] FIG. 13 illustrates a region of a volume where a gradient 80 for a virtual object 26 exists, including a last tool point 224, a final tool surface contact point 226, an initial proposed point 242, and a second proposed point 244 for one embodiment of the invention. In FIG. 13, the haptic rendering process 16 proposes to move the tool location such that a point 224 on the tool 28 would move to the point represented by 242. However, point 242 is not located within the region where a valid gradient can be computed. Because the maximum surface direction vector 101 cannot be calculated for this point, the haptic rendering process 16 calculates a second proposed tool position that would result in the tool point 242 moving to the second proposed point 244. Point 244 is the approximate midpoint of a line 246 between point 242 and the last tool point 224. If the voxel density value at that point 244 is still the maximum value (255 in one embodiment), the haptic rendering process 16 can continue to average the point 244 with the last tool point 224, by using a binary algorithm to bring it progressively closer to the last tool point 224, until the midpoint 244 lies within the gradient 80. Once within the region where a gradient exists, the surface direction vector 101 to the virtual surface from the latest midpoint 244 can be computed for the purposes previously described.
[0136] In one embodiment, a binary search method is used to determine the intersection point between the endpoints of the segment. The process is repeated until either the points are within a tolerable error of the desired value, or a maximum number of iterations has been reached.
[0137] FIGS. 14A, 14B, and 14C illustrate an example of a binary search for locating the virtual surface 25 for a segment 249 that intersects the virtual surface 25 for one embodiment of the invention. In FIG. 14A, the haptic rendering process determines a midpoint 254 by averaging the locations of the endpoints 248 and 252. In FIG. 14B the haptic rendering process 16 treats the point 254 as an endpoint of a modified segment 253 extending from point 254 to endpoint 248. The haptic rendering process 16 determines a midpoint 256 between points 248 and 254 and how far points 248 and 254 are from the virtual surface 25. The haptic rendering process 16 determines that point 248 is farther from the virtual surface 25 than point 254, and thus sets the upper endpoint 248 to be at a new point 256. The endpoints of the additionally modified segment 257 are thus points 256 and 254. This process is repeated until a point is found that is regarded as the intersection point 258 (within a predetermined distance from the virtual surface 25) of the original segment 249 and the virtual surface 25, as shown in FIG. 14C.
Other Interaction Techniques
[0138] The following sections describe in more detail an implementation of virtual object 26 and virtual tool 28 interaction according to an embodiment of the invention implemented by the assignee, SensAble Technologies, Inc. of Cambridge, Mass.
[0139] Single Point Methods
[0140] In some contexts a single point virtual tool 28 may interact with the virtual object 26. This may be handled as the simplest case of multipoint interaction using the methods previously described and described in more detail later. In another embodiment, specialized methods may be used for single point interaction, as described herein.
[0141] Collision Detection for Single Point Interaction
[0142] The haptic rendering algorithm determines when a collision between a virtual tool 28 and a virtual object 26 has occurred. A collision is detected when the haptic rendering process 16 attempts to move a tool 28 to penetrate a surface. In one embodiment, a collision occurs whenever the haptic interface location crosses through the virtual surface 25. In one embodiment, the virtual surface 25 may be a NURBS surface. In one embodiment, the virtual surface 25 may be the “skin” of a volumetric solid.
[0143] A stateless haptic rendering algorithm would consider only the haptic interface location 98 in determining the resulting forces from a collision. It would not consider any history or previous collisions. The resulting forces in a stateless algorithm would use only the current haptic interface location 98 to determine the 1) depth of penetration and 2) direction to the nearest surface 25. The resulting force vector would be a vector toward the nearest surface whose magnitude is proportional to the penetration depth. In the case of a voxel embodiment, the penetration depth of the haptic interface device point is generally proportional to the voxel density at that point.
[0144] The direction of the force vector would be a vector that points from the haptic interface location 98 to the closet point on the surface. In the case of the voxel embodiment, this vector is simply the maximum voxel gradient (i.e. direction of greatest voxel density change) at the haptic interface location 98. In conclusion, a stateless haptic rendering algorithm would consider the location of the haptic interface device at each iteration, determine if it has crossed a virtual surface 25 or is embedded in a virtual object 26, then return a force vector whose direction is from the haptic interface device location 98 to the nearest point on the surface, and whose magnitude is proportional to the penetration distance.
[0145] A stateless algorithm handles only basic cases of tool 28 interaction and falls short of accurately representing some cases. The most notable case for which the stateless algorithm fails is for the case of thin objects. If a user begins pressing through a thin surface, at some point the nearest surface point to the haptic interface device location 98 will be on the other side of the thin object (i.e. after the user has pressed more than halfway through), and thus the force vector will incorrectly push the user out the other side.
[0146] An improved algorithm keeps track of a virtual tool position at each iteration. Maintaining this virtual tool position is an efficient way to contain state information about the history of the user's path or trajectory. If the haptic interface device location 98 moves across a surface, the algorithm will attempt to move the virtual tool 28 toward the haptic interface device location 98, but never through the surface, as if the two points were connected by a spring. The resulting force sent to the haptic interface device 10 is proportional to the distance between the tool 28 and the haptic interface device location. In some embodiments, the force is also proportional to the difference in velocity or acceleration between the virtual tool 28 position and the haptic interface device location 98. The tool position on the virtual surface 25 is referred to herein as the surface contact point or SCP 226.
[0147] In one embodiment, the haptic rendering process 16 attempts to minimize the distance between the SCP 226 and the current haptic interface location 98, given that a path of decreasing distance exists between the last SCP 224 and the desired one. The connection between the SCP 226 and the haptic interface location 98 can be viewed as a spring. The haptic rendering process 16 processes the locations of the SCP 226 and haptic interface location 98 in iterative steps. At each iteration, the haptic rendering process 16 attempts to minimize the distance from the SCP 226 to the haptic interface location 98 if possible.
[0148] In one embodiment, the haptic rendering process 16 uses an algorithm for determining the SCP 226 based on a stepping method. For a given number of iterations, the algorithm determines a valid direction to move the SCP 226 which would yield a better solution (that is, decrease the distance between the SCP 226 and the current haptic interface location 98) and moves the point from the previous SCP 224 to a current SCP 226 in that direction. In one embodiment, valid directions are those which move along the virtual surface 25 of the virtual object 26. The haptic rendering algorithm should not allow the SCP 226 to penetrate the virtual surface 25 as it steps toward the haptic interface location 98.
[0149] FIG. 15 shows one method of determining a final SCP 226 used in one embodiment. FIG. 15 illustrates changing SCP positions 264a,264b,264c,tangency planes 260a,260b,260c,and resulting SCP 226. The resulting SCP 226 is a stationary position until the user makes a further movement of the virtual tool 28. In one embodiment, the changing SCP 264 is similar to the last or previous SCP 224. In one embodiment, the tangency planes 260a,260b,260care similar to the tangency plane 104 described earlier. Using this process, the haptic rendering process 16 creates a tangency plane 260afor an existing SCP 264ausing the surface direction vector 101afor the SCP 264a.The haptic rendering process 16 then moves the SCP 264aa fixed step (predetermined distance) on the virtual surface 25 to new SCP 264b,constraining the movement of the changing SCP 264bto the tangency plane 260b.The haptic rendering process 16 then determines a new tangency plane 262band repeats the stepping process to move the SCP 264bto a changed SCP 264c.The haptic rendering process 16 then creates a new tangency plane 262cand repeats the process until the SCP 264creaches a final position at SCP 226 above, or at the shortest distance from, the haptic interface location 98, as shown in FIG. 15. This method of movement is also termed a march by the SCP 264 across the virtual surface 25.
[0150] In one embodiment, the SCP 264 is constrained to move in the plane 260, which passes through the current SCP 264 and whose vector is the approximate direction of the normal to the virtual surface 25 at that point. In other words, the SCP 264 is allowed to move in any direction perpendicular to the surface direction vector 101 at that point. In one embodiment, the haptic rendering process 16 determines which direction along that plane 260 which would yield the optimum solution (that is, the solution that decreases the distance between the SCP 264 and the haptic interface location 98 by the largest amount) and moves the SCP 264 in that direction. Since the shape of the surface 25 at the SCP 264 position may be curved, moving linearly in some direction may either cause the SCP 264 to penetrate the virtual surface 25 (if convex) or leave the virtual surface 25 (if concave) causing an error in the SCP 264 position. Therefore, the SCP 264 may be projected onto the surface at each step. In one embodiment, this error is minimal if the step size is small, so the haptic rendering process 16 only needs to project the SCP 264 onto the virtual surface 25 after the final position (final surface contact point 226) has been determined from the march. Another potential problem involves local minimums and maximums. Because the SCP 264 only moves in directions which draw it progressively closer to the haptic interface location 98, the SCP 264 may not be able to traverse local maximums (that is, small humps in the virtual surface 25) and may settle in local minimums (small dips in the virtual surface 25). In one embodiment, the solution is to allow the spring (a spring calculation connecting the SCP 264 and haptic interface location 98) to stretch a small and finite distance so that the SCP 264 march can overcome these local discrepancies. In one embodiment this problem of local maximums and minimums rarely becomes a serious problem, so the spring stretching approach need not be implemented.
[0151] In another embodiment, the haptic rendering process 16 implements an iterative stepping algorithm as follows: The haptic rendering algorithm creates a plane 260 passing through the current or changing SCP 264, whose surface direction vector 101 is the calculated approximate normal to the virtual surface at the SCP 264. The haptic rendering algorithm projects the current haptic interface location 98 onto the nearest point on that plane 260a,260b,260cand creates a vector 262a,262b,262cfrom the SCP 264a,264b,264cto that point. This vector then becomes the desired direction for the march. The haptic rendering algorithm moves the SCP 264a,264b,264ca fixed step in the direction indicated by the vector 262a,262b,262c.The haptic rendering algorithm repeats these steps. Finally, the haptic rendering algorithm projects the SCP 264a,264b,264conto the virtual surface 25 using the intersection technique described above. In an alternate embodiment, the haptic rendering algorithm uses the faster but less robust technique of projecting based on the surface direction vector 101 and density value at that point. For example, see FIGS. 17A-17E.
Collision Detection with Three-Dimensional Tools
[0152] Collision with a point interface is sufficient for many interactions, but in one embodiment a more complete method of three-dimensional tool interaction is used. The virtual tool 28 is represented by a series of points along its surface, as discussed previously. At each iteration, the haptic rendering process 16 tests each of these points on the surface of the tool 28 to test for penetration of the tool 28 into the virtual surface 25 of the virtual object 26.
[0153] Improved Stepping Method
[0154] One embodiment of the haptic rendering process 16 maintains a tool position and iteratively moves it toward the current haptic interface location 98. The haptic rendering process 16 operates in a repeated loop of iterative processing steps. For each loop, the haptic rendering algorithm attempts to minimize its distance to the haptic interface location 98 without violating the virtual surface 25. In other words, at each iteration, the spring connection between the tool 28 and the haptic interface location 98 attempts to contract, but stops if that action would cause any of points of the virtual tool 28 to penetrate the virtual surface 25.
[0155] During each iteration, the haptic rendering process 16 attempts to march the tool 28 toward the haptic interface location 98, checks for violations against the virtual object 26, and repeats this process a number of times. Since the haptic rendering process 16 evaluates for collision at a potential tool location which is a distance equivalent to the step size away from the previous tool location at each step, the step size is bound to a relatively small value so that the haptic rendering process 16 does not jump the tool 28 over any features such as a concave “hole” in the surface 25 of the virtual object 26. The step size should also be large enough so that the movement of the tool 28 can reasonably keep up with the movement of the haptic interface location 98 as the user moves the haptic interface device 10. If the haptic interface device 10 moves a considerable distance but the step size of the tool 28 is small, the user feels a drag as the haptic rendering process 16 attempts to move the tool 28 to the haptic interface location 98. In one embodiment, the step size for each iteration should be less than the minimum feature size that the user will want to feel. In one voxel embodiment, the step size is one half of the voxel grid spacing.
[0156] Moving Along a Face of a Surface
[0157] If the movement method is to always move directly toward the haptic interface location 98, the tool 28 would get “stuck” on the virtual surface 25 once it touched the virtual surface 25. Therefore, the haptic rendering process 16 attempts to move the tool 28 along the surface 25 in a manner that minimizes its spring distance (between the tool 28 and the haptic interface location 98) instead of simply backing up to the previous position whenever the tool 28 violates the surface 25. The methods for achieving this are similar to those for determining the SCP 226 for a single point.
[0158] FIGS. 17A-17E show a virtual tool 28 encountering a virtual surface 25 and moving along the virtual surface 25 constrained by a plane 300. In FIGS. 17A and 17B, the tool 28 is not penetrating the virtual surface 25, so the haptic rendering process moves the tool 28 to follow the location of the haptic interface location 98. In FIG. 17C the potential tool position would result in penetration of the virtual surface 25 and thus violate the interaction constraints. The haptic rendering process 16 determines the surface direction vector 101 at the point of greatest potential penetration 304. In FIG. 17D the haptic rendering process 16 determines a plane 300 perpendicular to the surface direction vector 101 and passing through the last legitimate tool position in FIG. 17B. The haptic rendering process 16 constrains the virtual tool 28 to move only within the plane 300. The desired direction of motion 306 is determined by taking a vector 308 from a tool origin 27 to the haptic interface location 98 and projecting that vector 308 onto the plane 300. In FIG. 17E, the tool 28 moves a fixed distance in the direction determined in FIG. 17D. This manner of movement effectively allows the tool 28 to move along the virtual surface 25 without getting “stuck.” Once the haptic rendering process 16 determines that the tool 28 is near the virtual surface 25 (that is, after finding a potential penetration), this method may be used for all further calculations until the tool 28 leaves the virtual surface 25 (that is, the potential tool points cease to penetrate the virtual surface 25, causing the tool 28 to no longer be in a touching state).
[0159] Thus, the haptic rendering process 16 can detect when the tool 28 is on a face of a virtual surface 25, and attempts to move it along the surface 25 instead of directly toward the haptic interface location 98 when this condition is detected.
[0160] Moving Along or Across an Edge
[0161] More complicated situations may occur where the haptic rendering process 16 is moving the virtual tool 28 along an edge 108 or 177 instead of a face of a virtual object 26. In this situation, the haptic rendering process 16 constrains the tool 28 to a line (the edge) instead of a plane (the face). When multiple potential penetration points on the surface of the tool 28 have differing surface direction vectors 101, then the haptic rendering process 16 assumes that the tool 28 is at an intersection of the two faces with differing surface direction vectors 101, and constrains the tool 28 to that virtual edge 108 accordingly. The virtual edge 108 is the cross product of the surface direction vectors 101; the haptic rendering process 16 then constrains the tool 28 to moving only in that direction or its negative. (See the discussion of edge constraints associated with FIGS. 7A-7C.)
[0162] In one embodiment, it is not always the case that the haptic rendering process 16 constrains a virtual tool 28 to moving along an edge 108 or 177 when one is detected. Otherwise, when attempting to slide across edges 177 that are convex (that is, mountains or “sharp” edges 177 in the virtual surface 25 of the virtual object 26), the tool 28 may get stuck. Thus, the haptic rendering process 16 should distinguish between when the tool 28 is attempting to slide along a concave edge 108 versus when it is attempting to cross a convex edge 177. This is determined by taking the dot product of the desired direction (that is, a vector from the tool origin 27 to the haptic interface location 98) with the surface direction vectors 101 of each face that forms the virtual edge 108 or 177. See FIG. 7B. A positive dot product indicates that the tool 28 is attempting to move away from one of the virtual surfaces 25 instead of sliding along the edge 108 or 177. If either dot product is positive, the haptic rendering process 16 assumes that the tool 28 is moving across a convex edge 177 and does not constrain itself to the convex edge 177. When this case is detected, the haptic rendering process 16 “pushes the tool 28 away” slightly, moving in the direction of the vector which is the average of the two surface direction vectors 101.
[0163] The methods described above are sufficient in most cases; however, scenarios exist where the movement of the tool 28 may get “stuck” and the haptic rendering process 16 is unable to move the tool 28 along the virtual surface 25 effectively. To compensate for this, the haptic rendering process 16 tries moving the tool 28 tries away from the surface 25 (that is, in the direction of the surface direction vector 101) at small increments if it has been stuck for a considerable time (that is, the haptic rendering process 16 has unsuccessfully attempted to move the tool 28 for the past several iterations).
[0164] Progressive Extraction
[0165] Finally, there are situations in which the tool 28 somehow becomes stuck inside the virtual surface 25. In other words, the current tool position is penetrating the surface 25. For example, if the user touches a surface 25 with the flat face of a cube, then rotates the cube such that one of the edges is now penetrating the surface 25. Unless the haptic device limits this rotation via a torque feedback, the haptic rendering process 16 can put the virtual tool 28 in a position of penetration, which violates the desired behavior. In one embodiment, the haptic interface device 10 would have six degrees of freedom of force feedback and thus not allow invalid rotations. In other embodiments, the haptic interface device 10 has more than six degrees of freedom. An embedded tool position may also occur if the user uses a modification mode to add material on top of the tool 28, or the virtual object 26 is rotated such that the tool 28 suddenly becomes embedded.
[0166] If the tool 28 is forced to an invalid position, the haptic rendering process 16 needs some way of extracting the tool 28 to a valid position. In these cases, the haptic rendering process 16 should attempt to move the tool 28 in a direction away from the virtual surface 25 to escape the surface 25. Therefore, if the tool 28 is stuck such that moving directly toward the haptic interface location 98, moving along the constraint plane 300, moving to its previous position, and moving in the direction in the normal of that plane 300 all would result in penetration of the virtual object 26, then the haptic rendering process 16 attempts to “jump” the tool 28 a significant distance in the direction of the surface direction vector 101. (See FIG. 7C.) If this jump still does not free the tool 28 (that is, one of its points would remain embedded in the surface 25), but the proposed position results in lesser penetration of the virtual object 26, then it is considered a superior position (that is, if the point of greatest penetration yields a lower density evaluation value than the previous evaluation for the previous point of greatest penetration). This condition allows the haptic rendering process 16 to have a notion of “progress;” that is, even though moving in some direction does not fully release the tool 28 from the surface 25, the movement is still an improvement over the previous position if moving in this direction causes the penetration distance to decrease.
[0167] Random Extraction
[0168] The above methods handle most cases. However, some scenarios exist where the tool 28 is “stuck” but moving in the direction of the normal to the plane does not yield any improvement. This is a rare condition since the surface direction vector 101 points toward the surface 25 of the virtual object 26, moving in that direction should decrease the penetration distance. But although moving in that direction decreases the penetration distance of that point which is used to determine the surface direction vector 101, this movement may increase the penetration of another point (usually one of the opposite side) such that the tool's 28 overall penetration distance increases. In circumstances where none of the above techniques yields acceptable results, the haptic rendering process 16 may conclude that the tool 28 is truly stuck and should not legally move (for example, as in FIGS. 16A and 16B).
[0169] For example, suppose a spherical tool 28 ends up in a situation where it is in a gap or channel 270 between two virtual objects 272 and 274, whose width is less than that of the tool 28. A similar situation occurs if the tool 28 is in a tunnel or conduit in a virtual object 26. FIGS. 16A and 16B show a spherical virtual tool 28 in a channel 270 formed between two virtual objects 272 and 274. The diameter of the channel 270 is less than the diameter of the virtual tool 28. FIG. 16A shows a point of greatest penetration 276 and a vector 278 to the surface 280 of virtual object 274. FIG. 16B shows a new point with greatest penetration 282 and its computed vector 284. The point 288 represents the tool surface contact point for the previous penetration of virtual object 274. The haptic rendering process 16 may determine that the point 276 with the greatest X value has the greatest penetration (based on a horizontal X axis for FIGS. 16A and 16B). It will then push the sphere 28 toward the minus X direction by some distance. During the next iteration, the point of greatest penetration will probably be the point 282 with the least X value. This will then cause the sphere 28 to move back in the X direction by some distance, etc. In this example, the haptic rendering process 16 could cause the tool 28 to oscillate indefinitely between the positions depicted in FIGS. 16A and 16B.
[0170] Thus, as a final method, the haptic rendering process 16 may attempt to move the tool 28 in a random direction as a way of arriving at a better solution (that is, one that decreases the greatest penetration distance). (See FIG. 7C.) However, in one embodiment, instead of moving in a purely random direction, the haptic rendering process 16 determines which of the points of the tool 28 have computed surface direction vectors 101 (that is are either embedded in the surface 25 or within the field of decreasing non-zero values surrounding the surface 25) and chooses one of those surface direction vectors 101 randomly as the direction to move in. The movement of the tool 28 obeys the same rules as described for other cases in FIGS. 7A-7C. If the maximum penetration distance does not decrease as a result of the attempted move, then the haptic rendering process 16 does not move the tool 28 but instead tries a different direction.
[0171] Note that this final method is fairly expensive computationally. Thus, when the tool 28 reaches this state, the haptic rendering process 16 may determine all the current tool penetration points only once, by creating a list of indices of points whose penetration values are within the virtual surface 25. In one embodiment using voxels 78, the points include those points with densities greater than the density of the threshold value (isosurface 86). For all successive iterations, the haptic rendering process 16 randomly chooses one of the points and moves the tool 28 in the direction of that point's surface direction vector 101.
[0172] Variable Step Size and Other Optimizations
[0173] Adaptive Step Size
[0174] In one embodiment, the user may feel a drag force if the haptic rendering process 16 is not able to maintain the movement of the tool 28 with the movement of the haptic interface device 10. For example, if the step size or number of iterations is small, then the haptic rendering process 16 may take a considerable amount of time to move the tool 28 to its final position if the haptic interface device 10 has moved a significant distance. Thus, it is desirable to have an adaptive algorithm that interactively sets the step size depending on the movement of the haptic interface device 10. If the haptic interface device 10 is moving quickly, then the step size increases to compensate. If the haptic interface device 10 is not moving quickly, the step size is decreased so that the tool 28 can be placed with greater accuracy. A smaller step size also helps prevent undesired buzzing or vibration of the haptic interface device 10. Buzzing can occur when the haptic rendering process 16 cycles the tool 28 between multiple positions, attempting to settle but never finding rest. See FIGS. 16A and 16B. However, if the step size is decreased, these oscillations become very small and barely noticeable or do not occur at all. On the other hand, if the user is moving a large distance, then oscillations and “buzzing” do not occur because the haptic rendering process 16 is attempting to maintain the position of the tool 28 with the haptic interface location 98 of the haptic interface device 10 instead of having the tool 28 stay in one position. Thus, if during a given loop, the haptic interface device 10 is not moving rapidly, the step size of the tool 28 is decreased.
[0175] Adaptive Number of Iterations
[0176] If the computer processor is not performing any other process-consuming tasks, then the number of iterations per second can be increased safely. The most intensive operations occur if the user is not only interacting with the virtual object 26 but is modifying it in some manner. For example, if the haptic rendering process 16 is using the tool 28 to remove or add material, the calculations can consume much of the processing time. If the virtual object 26 is not being modified, the haptic rendering process 16 assumes it can use a greater portion of the processing time and thus increases its number of iterations. In one embodiment, the number of iterations is increased by a factor of two. In other embodiments, other factors are used to determine the number of iterations.
[0177] Tool Point Collision Detection Optimization
[0178] The processing requirement per step can also be decreased if not all points along the tool 28 are evaluated at each loop. Evaluating a large number of points to check for penetration of the virtual surface 25 by the virtual tool 28 consumes a large amount of processing time. In one embodiment, a faster method attempts to optimize this by choosing only a set number of points to evaluate during each iteration, depending on which points are closest to the surface 25. In a voxel embodiment, during the first step in each loop, the haptic rendering process 16 evaluates the density values for the voxels 78 at all tool points and remembers the five points that evaluated to the greatest densities. For subsequent steps during that loop, it characterizes the tool 28 by those five points and thus does not perform any collision detection with any of the other tool points. This gives a significant performance increase. In one embodiment, the average tool 28 may have around 80 tool points, so evaluating the only 5 of 80 provides a large advantage. When this optimization is used; the number of iterations per loop is doubled to four, so that the haptic rendering process 16 only performs collision detection against every tool point every fourth step.
[0179] This can lead to situations where one of the tool points would violate the virtual surface 26, if that point was not one of the original five chosen during the first step. The haptic rendering process 16 however, does not usually place the tool 28 in situations where a valid position cannot be found following an evaluation of a potentially illegal series of steps.
[0180] Adaptive Stepping Behavior
[0181] In one embodiment if the haptic rendering process 16 has been moving the tool 28 toward the haptic interface location 98 without encountering intersections with virtual objects 26) for several iterations, then the haptic rendering process 16 assumes that the tool 28 is in empty space. For future iterations, instead of stepping toward the haptic interface location 98, the tool origin 27 is set to be coincident with the haptic interface location 98 at each step. Thus, the user does not feel any unwanted force effects. This continues until the tool 28 intersects with a virtual object 26, in which case the haptic rendering process 16 uses the previously discussed stepping algorithms to increment the tool position to a valid location. The number of legal steps needed before the tool 28 is set to the haptic interface location 98 may be defined to be one hundred iterations. In other embodiments, the number of legal steps may be less than or greater than one hundred iterations.
[0182] Optimize Transform Computations
[0183] For each collision detection evaluation between a tool point and the virtual surface 25, the point is transformed from the local coordinates of the tool 28 to the local coordinates of the virtual object 26. The greatest process consumption involves multiplying the point by the appropriate transformation matrix to account for the rotation of the tool 28 and virtual object 26. In one embodiment, instead of calculating this transformation for each loop, the points are only updated to the current orientation every one hundred iterations. When the points are updated, they are stored in a separate point array of local points, which is used to represent the tool 28 until it is again updated. Note that only the rotation of the points is updated every one hundred iterations; the translation of the points is accurately updated every loop to accurately reflect the potential position of the tool 28.
[0184] Additional Conditions Handling
[0185] Normally, the haptic rendering process 16 places the tool 28 to remain on the outside of any virtual object 26 with which it is interacting. If some small portion of the tool 28 becomes buried in the virtual object 26, the tool 28 can usually be extracted to the surface 86 using one or more of the techniques described above. However, situations exist where the tool 28 may instantaneously become completely buried inside a virtual object 26. For example, if the user adds a large amount of material over the current tool position, or the user begins the program with the tool position inside a virtual object 26, then the tool 28 is buried. If the tool 28 is ever inside a virtual object 26, the desired behavior is for the haptic rendering process 16 to gradually push the tool 28 away from the virtual object 26 in the direction of the nearest surface 86. In another embodiment, the tool 28 reaches a state where it is completely or nearly buried in a virtual object 26, then no forces are generated until the haptic rendering process 16 moves the tool 28 to exit completely the virtual object 26. It sets its position to the haptic interface location 98 for subsequent iterations and generates no collisions until the tool 28 reaches a position where every tool point is outside of the virtual object 26. In a voxel embodiment, the tool 28 is considered buried if its center evaluates to a density value approximate to the maximum density value (which is a value of 255 in one embodiment).
[0186] Tool Behavior Under Object Transformations
[0187] The tool position is stored in the local coordinates of the virtual object 26. Thus, if the virtual object 26 instantaneously changes scale, translation, or rotation, the tool position may jump, and the user feels a sudden “kick back” in the haptic interface device 10. To prevent this in one embodiment, a check is made during the first potential step of the tool 28 to determine if the transform of the object 26 has changed significantly since the previous loop. If this is true, then the tool position is set to the haptic interface location 98, and therefore no force generated. For example, if an object 28 were scaled upward, the haptic rendering process 16 would bury the tool 28 in the virtual object 26 instead of kicking the tool 28 to the surface 86.
[0188] Tool Position Error
[0189] The tool 28 is most often not directly on the virtual surface 25. As discussed previously, the haptic rendering process 16 only moves the tool 28 in discrete steps and its movement is constrained from violating the surface 25. Thus, the tool 28 rarely settles directly on the surface 25. This difference in position is not particularly noticeable when the user is feeling the surface 25 with the virtual tool 28. Realistic feel does not depend on having the tool 28 always directly on the virtual surface 25 In one voxel embodiment, step sizes are generally around 0.1 grid space unit; thus, the user at most experiences an error of 0.1 grid space units from the surface 86. This is below the threshold where it would make a difference in the force felt by the user. In other embodiments, the step size may have other values than the 0.1 grid space unit.
GLOSSARY
[0190] Constraint
[0191] An imposed limitation on the motion of the virtual tool 28.
[0192] Density
[0193] A scalar property of each single voxel 78, used for defining the shape of a virtual object 26 in one embodiment.
[0194] Density Threshold Value
[0195] In one embodiment, the density value which defines the isosurface 86 which represents the virtual surface 25. Voxels 78 with densities above this value represent interior points on the virtual object 26. Voxels 78 with densities below this value represent points outside the virtual object 26.
[0196] Edge
[0197] A temporary geometric construct representing a potentially viable move direction when the virtual tool 28 is contacting the virtual object 26 in more than one place.
[0198] Gradient
[0199] The rate of change of the density values of the voxels 78 along a given vector in one embodiment.
[0200] Haptic Interface Location
[0201] The location in the virtual environment which corresponds to the key position of the haptic interface device 10 in the real-world space.
[0202] Haptic Rendering Process
[0203] The process responsible for generating objects 26 in the haptic virtual environment and producing high-fidelity force-feedback to the user in real world space.
[0204] Haptic Virtual Environment
[0205] A computer representation of a space where a user can interact with virtual objects 26 through the sense of touch.
[0206] Interaction Modes
[0207] Settings which alter the interaction between the virtual tool 28 and the virtual object 26.
[0208] Isosurface
[0209] A theoretical surface 86 defined by the locus of identical voxel density values.
[0210] Panic Escape
[0211] A method of extracting the virtual tool 28 from a trapped condition.
[0212] Ramp Length
[0213] In one embodiment, the number of voxels 78 over which density values go from their minimum (0) to their maximum (255).
[0214] Real World Space
[0215] The true three-dimensional physical world in which people live and interact.
[0216] Surface Direction Vector
[0217] A vector 101 evaluated at a point in relation to a virtual surface 25. If the point is at the virtual surface 25, this vector 101 is the normal to the surface 25 at that point. If the point is not on the surface 25, the vector 101 represents the approximate shortest distance to the surface 25 and is also the approximate surface normal at the point where the vector 101 would intersect the surface 25.
[0218] Tool Surface Contact Point
[0219] A location on the virtual surface 25 where the virtual tool 28 is in contact with the virtual surface 25.
[0220] Trilinear Interpolation
[0221] In one embodiment, a technique for interpolating the densities of nearby voxels 78 to derive the density at a location that lies between the discrete voxel locations.
[0222] Virtual Object Modification Process
[0223] The process responsible for making changes to the virtual object 26.
[0224] Virtual Object
[0225] A computer representation of an object.
[0226] Virtual Surface
[0227] A computer representation of the “skin” of a virtual object 26.
[0228] Virtual Tool
[0229] A computer representation of a tool which the user uses to interact with the virtual environment.
[0230] Virtual Tool Origin
[0231] The location on the virtual tool 28 which strives to be coincident with the haptic interface location 98.
[0232] Voxels
[0233] A set of locations in the virtual environment, each storing information used in defining the shape of a virtual object 26 in one embodiment.
[0234] Having described the preferred embodiments of the invention, it will now become apparent to one of skill in the art that other embodiments incorporating the concepts may be used. It is felt, therefore, that the invention should not be limited to disclosed embodiments, but rather should be limited only by the spirit and scope of the following claims.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
What is claimed is:
1. A method for interfacing with a virtual object in a haptic virtual environment, comprising:
generating a virtual object comprising a virtual surface in the haptic virtual environment;
sensing a location of a user in real space;
determining a virtual tool comprising a plurality of discrete points for use by the user in the haptic virtual environment;
determining a haptic interface location in the haptic virtual environment in response to the location of the user in real space;
determining locations for the plurality of discrete points of the virtual tool in the haptic virtual environment in comparison to the haptic interface location and a location of the virtual surface;
determining if at least one of the plurality of discrete points of the virtual tool penetrates the virtual surface;
if at least one of the plurality of discrete points penetrates the virtual surface, determining a geometry for the virtual surface at an area of penetration of the virtual tool; and
limiting movement of the virtual tool based on (i) the geometry of the virtual surface, (ii) at least one location of at least one of the plurality of discrete points, and (iii) the haptic interface location.
2. The method of claim 1, wherein the step of limiting movement of the virtual tool further comprises moving a position of the virtual tool toward the haptic interface location.
3. The method of claim 2, further comprising the step of determining a surface contact point based on (i) the geometry of the virtual surface, (ii) at least one location of at least one of the plurality of the discrete points of the virtual tool, and (iii) the haptic interface location.
4. The method of claim 1, further comprising the step of determining a surface direction vector in response to the steps of determining the locations for the plurality of discrete points of the virtual tool in the haptic virtual environment and determining if at least one of the plurality of discrete points of the virtual tool penetrates the virtual surface.
5. The method of claim 4, further comprising the step of determining a constraint plane in response to the step of determining a surface direction vector, and wherein the step of limiting the movement of the virtual tool further comprises limiting the movement based on the constraint plane.
6. The method of claim 1, wherein the step of determining the geometry of the virtual surface comprises determining an edge geometry.
7. The method of claim 6, wherein the step of determining the edge geometry comprises determining if the virtual tool has penetrated two portions of the virtual surface; and determining two edge surface direction vectors in response to (i) the two portions and (ii) at least one location of at least one of the plurality of discrete points of the virtual tool.
8. The method of claim 7, wherein the step of determining the geometry for the virtual surface comprises determining an edge line by calculating the cross product of the two edge surface direction vectors; and the step of limiting the movement of the virtual tool comprises limiting the movement of the virtual tool based on the edge line.
9. The method of claim 1, further comprising calculating an interaction force between the virtual object and the virtual tool in response to the step of determining the locations of the plurality of discrete points of the virtual tool.
10. A system for interfacing with a virtual object in a haptic virtual environment, comprising:
the virtual object comprising a virtual surface;
a haptic interface device, wherein the haptic interface device senses a location of a user in real space;
a virtual tool comprising a plurality of discrete points for use by the user in the haptic virtual environment; and
a modeling application in communication with the haptic interface device, the virtual object, and the virtual tool, wherein the modeling application (a) determines a haptic interface location in the haptic virtual environment in response to the location of the user in real space; (b) determines locations for the plurality of discrete points of the virtual tool in the haptic virtual environment in comparison to the haptic interface location and a location of the virtual surface; (c) determines a geometry for the virtual surface at an area where at least one of the plurality of discrete points of the virtual tool penetrates the virtual surface; and (d) limits movement of the virtual tool based on (i) the geometry of the virtual surface, (ii) at least one location of at least one of the plurality of discrete points, and (iii) the haptic interface location.
11. The system of claim 10, wherein the modeling application limits the movement of the virtual tool by moving a position of the virtual tool toward the haptic interface location.
12. The system of claim 11, further comprising a surface contact point, wherein the modeling application determines the surface contact point based on (i) the geometry of the virtual surface, (ii) at least one location of at least one of the plurality of the discrete points of the virtual tool, and (iii) the haptic interface location.
13. The system of claim 10, further comprising a surface direction vector, wherein at least one of the plurality of discrete points of the virtual tool penetrates the virtual surface and the modeling application determines the surface direction vector based on the locations for the plurality of discrete points of the virtual tool in the haptic virtual environment.
14. The system of claim 13, further comprising a constraint plane, wherein the modeling application determines the constraint plane based on the surface direction vector and limits the movement of the virtual tool based on the constraint plane.
15. The system of claim 10, wherein the geometry of the virtual surface is an edge geometry.
16. The system of claim 15, further comprising two edge surface direction vectors; and the virtual surface comprising two portions, wherein the virtual tool has penetrated the two portions of the virtual surface and the modeling application determines the two edge surface direction vectors based on (i) the two portions and (ii) at least one location of at least one of the plurality of discrete points of the virtual tool.
17. The system of claim 16, wherein the edge geometry comprises an edge line, wherein the modeling application determines the edge line by calculating the cross product of the two edge surface direction vectors, and limits the movement of the virtual tool based on the edge line.
18. The system of claim 10, further comprising an interaction force between the virtual object and the virtual tool, wherein the modeling application calculates the interaction force based on the locations of the plurality of discrete points of the virtual tool in comparison to the haptic interface location and the location of the virtual surface.
19. A method for interfacing with a virtual surface in a haptic virtual environment, comprising:
generating a virtual surface in the haptic virtual environment;
sensing a location of a user in real space;
determining a virtual representation of the user in real space, the virtual representation comprising a plurality of discrete points;
determining a haptic interface location in the haptic virtual environment in response to the location of the user in real space;
determining a virtual representation location in the haptic virtual environment;
moving the virtual representation location toward the haptic interface location in the haptic virtual environment; and
limiting movement of the virtual representation based on a geometry of the surface and on preventing any one of the plurality of discrete points of the virtual representation from substantially penetrating the virtual surface.
20. The method of claim 19 wherein the virtual surface is derived from a set of scalar values arranged at spatial locations.
21. The method of claim 20 wherein the set of scalar values is arranged in a regularly spaced three dimensional grid.
22. The method of claim 19 wherein the virtual surface is an isosurface of a set of voxels.
23. The method of claim 19 further comprising a step of determining a force feedback vector and a step of sending the force feedback vector to the user through a haptic interface.
24. The method of claim 23 wherein the step of determining the force feedback vector comprises determining the force feedback vector derived from a difference in position of the haptic interface location and the virtual representation location.
25. The method of claim 24 wherein the step of determining the force feedback vector comprises determining the force feedback vector derived from a difference in velocity of the haptic interface location and the virtual representation location.
26. The method of claim 19 wherein the step of determining the virtual representation comprises determining a virtual tool.
27. The method of claim 26 wherein the step of determining the virtual tool comprises arranging the plurality of discrete points of the virtual tool to approximate a sphere.
28. The method of claim 19 wherein the step of generating a virtual surface comprises generating a virtual object from a closed surface.
29. The method of claim 28 further comprises steps of reading the virtual object from a file, modifying the virtual object in shape, and saving the virtual object to the file.
30. The method of claim 19 wherein the step of moving the virtual representation comprises moving the virtual representation iteratively.
31. The method of claim 19 wherein the step of limiting movement is achieved by determining a constraint plane based on the geometry of the virtual surface.
32. The method of claim 19 wherein the step of limiting movement is achieved by determining a constraint edge based on the geometry of the virtual surface.
33. The method of claim 19 wherein the step of determining the haptic interface location comprises determining a position and an orientation of a haptic interface.
34. The method of claim 33 further comprising a step of determining a force feedback vector; a step of sending the force feedback to the user through the haptic interface, wherein the haptic interface is adapted for measuring six degrees of freedom.
35. The method of claim 34 further comprising the step of applying the force feedback vector through the haptic interface device with less than six degrees of freedom of force feedback.
36. The method of claim 34 wherein the step of determining the force feedback comprises a step of determining a force in at least one of three principal directions and a torque in at least one of three principal rotations.
37. A method for interfacing with a virtual surface in a haptic virtual environment, comprising:
generating a virtual surface in the haptic virtual environment;
sensing a location of a user in real space;
determining a virtual representation of the user in real space, the virtual representation comprising a plurality of discrete points;
determining a haptic interface location in the haptic virtual environment in response to the location of the user in real space;
determining a virtual representation location in the haptic virtual environment;
proposing to move the virtual representation to a first proposed location in the direction of the haptic interface location;
evaluating at least one of the plurality of discrete points of the virtual representation to detect interference of the virtual representation with the virtual surface for the first proposed location of the virtual representation;
moving the virtual representation to the first proposed location if no interference of the virtual representation with the virtual surface is detected; and
proposing a second location of the virtual representation if interference of the virtual representation with the virtual surface is detected at the first proposed location.
38. The method of claim 37 wherein the step of evaluating at least one of the plurality of discrete point comprises determining an interference point from the plurality of discrete points, the interference point interfering with the virtual surface at the first proposed location, and wherein the step of proposing the second proposed location comprises calculating the second proposed location based on local geometry information of the virtual surface near the interference point.
39. The method of claim 38 further comprising a step of determining a vector formed by projecting the haptic interface location onto a plane passing through a current location of the virtual representation, the plane being tangent to the virtual surface near the interference point for the first proposed position and wherein the step of proposing the second proposed location comprises proposing the second proposed location in the direction of the vector.
40. The method of claim 39 further comprising the steps of
evaluating at least one of the discrete set of points to check for interference of the virtual representation with the virtual surface for the second proposed location of the virtual representation;
moving the virtual representation to the second proposed location if no interference of the virtual representation with the virtual surface is detected; and
proposing a third location of the virtual representation if interference of the virtual representation with the virtual surface is detected at the second proposed location.
41. The method of claim 40 further comprising a step of determining a line formed by the intersection of two planes, the two planes derived from local geometry information in a region near the first proposed location and the second proposed location, and wherein the step of proposing the third proposed location comprises determining the third proposed location in the direction of the line.
42. The method of claim 40 further comprising a step of determining a resultant vector from the cross product of two vectors derived from local geometry information in a region near the first proposed location and second proposed location, and wherein the step of proposing the third proposed location comprises determining the third proposed location in the direction of the proposed resultant vector.
43. The method of claim 37 further comprising the steps of
evaluating at least one of the discrete set of points to detect interference of the virtual representation with the virtual surface for the second proposed location of the virtual representation;
moving the virtual representation to the second proposed location if no interference of the virtual representation with the virtual surface is detected; and
proposing a third location of the virtual representation if interference of the virtual representation with the virtual surface is detected at the second proposed location.
44. A method for interfacing with a virtual surface in a haptic virtual environment, comprising:
generating a virtual surface in the haptic environment based on a set of scalar values arranged in a three dimensional grid;
sensing a location of a user in real space;
determining a virtual representation of the user in real space;
determining a haptic interface location in the haptic virtual environment in response to the location of the user in real space;
determining a virtual representation location in the haptic virtual environment;
moving the virtual representation location in the haptic virtual environment based on the previous virtual representation location, the haptic interface location in the virtual environment, and the geometry of the virtual surface.
Patent Citations (159)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US2475484(A) | 1949-07-01 | DeNise | Applicant |
| US3168203(A) | 1965-02-01 | Gallistel | Applicant |
| US3263824(A) | 1966-08-01 | Jones et al. | Applicant |
| US3449008(A) | 1969-06-01 | Colechia | Applicant |
| US3531868(A) | 1970-10-01 | Stevenson | Applicant |
| US3618786(A) | 1971-11-01 | Fick | Applicant |
| US3637092(A) | 1972-01-01 | George et al. | Applicant |
| US3920972(A) | 1975-11-01 | Corwin et al. | Applicant |
| US3944798(A) | 1976-03-01 | Eaton | Applicant |
| US4062455(A) | 1977-12-01 | Flatau | Applicant |
| US4150803(A) | 1979-04-01 | Fernandez | Applicant |
| US4216467(A) | 1980-08-01 | Colston | Applicant |
| US4302138(A) | 1981-11-01 | Zarudiansky | Applicant |
| US4367532(A) | 1983-01-01 | Crum et al. | Applicant |
| US4420808(A) | 1983-12-01 | Diamond et al. | Applicant |
| US4521685(A) | 1985-06-01 | Rebman | Applicant |
| US4604016(A) | 1986-08-01 | Joyce | Applicant |
| US4632341(A) | 1986-12-01 | Repperger et al. | Applicant |
| US4638798(A) | 1987-01-01 | Shelden et al. | Applicant |
| US4653011(A) | 1987-03-01 | Iwano | Applicant |
| US4654648(A) | 1987-03-01 | Herrington et a l. | Applicant |
| US4655673(A) | 1987-04-01 | Hawkes | Applicant |
| US4661032(A) | 1987-04-01 | Arai | Applicant |
| US4670851(A) | 1987-06-01 | Murakami et al. | Applicant |
| US4676002(A) | 1987-06-01 | Slocum | Applicant |
| US4680519(A) | 1987-07-01 | Chand et al. | Applicant |
| US4703443(A) | 1987-10-01 | Moriyasu | Applicant |
| US4729098(A) | 1988-03-01 | Cline et al. | Applicant |
| US4769763(A) | 1988-09-01 | Trieb et al. | Applicant |
| US4791934(A) | 1988-12-01 | Brunnett | Applicant |
| US4795296(A) | 1989-01-01 | Jau | Applicant |
| US4800721(A) | 1989-01-01 | Cemenska et al. | Applicant |
| US4819195(A) | 1989-04-01 | Bell et al. | Applicant |
| US4823634(A) | 1989-04-01 | Culver | Applicant |
| US4837734(A) | 1989-06-01 | Ichikawa et al. | Applicant |
| US4839838(A) | 1989-06-01 | LaBiche et al. | Applicant |
| US4853874(A) | 1989-08-01 | Iwamoto et al. | Applicant |
| US4888538(A) | 1989-12-01 | Dimitrov et al. | Applicant |
| US4893981(A) | 1990-01-01 | Yoshinada et al. | Applicant |
| US4907970(A) | 1990-03-01 | Meenen, Jr. | Applicant |
| US4907973(A) | 1990-03-01 | Hon | Applicant |
| US4942538(A) | 1990-07-01 | Yuan et al. | Applicant |
| US4945305(A) | 1990-07-01 | Blood | Applicant |
| US4945501(A) | 1990-07-01 | Bell et al. | Applicant |
| US4961138(A) | 1990-10-01 | Gorniak | Applicant |
| US4973215(A) | 1990-11-01 | Karlen et al. | Applicant |
| US4982504(A) | 1991-01-01 | Söderberg et al. | Applicant |
| US4988981(A) | 1991-01-01 | Zimmerman et al. | Applicant |
| US5004391(A) | 1991-04-01 | Burdea | Applicant |
| US5007300(A) | 1991-04-01 | Siva | Applicant |
| US5018922(A) | 1991-05-01 | Yoshinada et al. | Applicant |
| US5019761(A) | 1991-05-01 | Kraft | Applicant |
| US5038089(A) | 1991-08-01 | Szakaly | Applicant |
| US5040306(A) | 1991-08-01 | McMurtry et al. | Applicant |
| US5044956(A) | 1991-09-01 | Behensky et al. | Applicant |
| US5053975(A) | 1991-10-01 | Tsuchihashi et al. | Applicant |
| US5072361(A) | 1991-12-01 | Davis et al. | Applicant |
| US5088046(A) | 1992-02-01 | McMurtry | Applicant |
| US5088055(A) | 1992-02-01 | Oyama | Applicant |
| US5103404(A) | 1992-04-01 | McIntosh | Applicant |
| US5105367(A) | 1992-04-01 | Tsuchihashi et al. | Applicant |
| US5116051(A) | 1992-05-01 | Moncrief et al. | Applicant |
| US5116180(A) | 1992-05-01 | Fung et al. | Applicant |
| US5130632(A) | 1992-07-01 | Ezawa et al. | Applicant |
| US5131844(A) | 1992-07-01 | Marinaccio et al. | Applicant |
| US5142931(A) | 1992-09-01 | Menahem | Applicant |
| US5143505(A) | 1992-09-01 | Burdea et al. | Applicant |
| US5184319(A) | 1993-02-01 | Kramer | Applicant |
| US5185561(A) | 1993-02-01 | Good et al. | Applicant |
| US5189806(A) | 1993-03-01 | McMurtry et al. | Applicant |
| US5193963(A) | 1993-03-01 | McAffee et al. | Applicant |
| US5204824(A) | 1993-04-01 | Fujimaki | Applicant |
| US5220260(A) | 1993-06-01 | Schuler | Applicant |
| US5223776(A) | 1993-06-01 | Radke et al. | Applicant |
| US5239246(A) | 1993-08-01 | Kim | Applicant |
| US5255211(A) | 1993-10-01 | Redmond | Applicant |
| US5264768(A) | 1993-11-01 | Gregory et al. | Applicant |
| US5266875(A) | 1993-11-01 | Slotine et al. | Applicant |
| US5354162(A) | 1994-10-01 | Burdea et al. | Applicant |
| US5382885(A) | 1995-01-01 | Salcudean et al. | Applicant |
| US5389865(A) | 1995-02-01 | Jacobus et al. | Applicant |
| US5396265(A) | 1995-03-01 | Ulrich et al. | Applicant |
| US5414337(A) | 1995-05-01 | Schuler | Applicant |
| US5429140(A) | 1995-07-01 | Burdea et al. | Applicant |
| US5438529(A) | 1995-08-01 | Rosenberg et al. | Applicant |
| US5459382(A) | 1995-10-01 | Jacobus et al. | Applicant |
| US5482051(A) | 1996-01-01 | Reddy et al. | Applicant |
| US5489830(A) | 1996-02-01 | Fernandez | Applicant |
| US5497452(A) | 1996-03-01 | Shimizu et al. | Applicant |
| US5515078(A) | 1996-05-01 | Greschler et al. | Applicant |
| US5555894(A) | 1996-09-01 | Doyama et al. | Applicant |
| US5559412(A) | 1996-09-01 | Schuler | Applicant |
| US5576727(A) | 1996-11-01 | Rosenberg et al. | Applicant |
| US5587937(A) | 1996-12-01 | Massie et al. | Applicant |
| US5589854(A) | 1996-12-01 | Tsai | Applicant |
| USD377932(S) | 1997-02-01 | Schena et al. | Applicant |
| US5623582(A) | 1997-04-01 | Rosenberg | Applicant |
| US5623642(A) | 1997-04-01 | Katz et al. | Applicant |
| US5625576(A) | 1997-04-01 | Massie et al. | Applicant |
| US5629594(A) | 1997-05-01 | Jacobus et al. | Applicant |
| US5642469(A) | 1997-06-01 | Hannaford et al. | Applicant |
| US5666138(A) | 1997-09-01 | Culver | Applicant |
| US5691898(A) | 1997-11-01 | Rosenberg et al. | Applicant |
| US5694013(A) | 1997-12-01 | Stewart et al. | Applicant |
| US5701140(A) | 1997-12-01 | Rosenberg et al. | Applicant |
| US5721566(A) | 1998-02-01 | Rosenberg et al. | Applicant |
| US5724264(A) | 1998-03-01 | Rosenberg et al. | Applicant |
| US5731804(A) | 1998-03-01 | Rosenberg | Applicant |
| US5734373(A) | 1998-03-01 | Rosenberg et al. | Applicant |
| US5737505(A) | 1998-04-01 | Shaw et al. | Applicant |
| US5739811(A) | 1998-04-01 | Rosenberg et al. | Applicant |
| US5742278(A) | 1998-04-01 | Chen et al. | Applicant |
| US5751289(A) | 1998-05-01 | Myers | Applicant |
| US5754023(A) | 1998-05-01 | Roston et al. | Applicant |
| US5767839(A) | 1998-06-01 | Rosenberg | Applicant |
| US5769640(A) | 1998-06-01 | Jacobus et al. | Applicant |
| US5784542(A) | 1998-07-01 | Ohm et al. | Applicant |
| US5790108(A) | 1998-08-01 | Salcudean et al. | Applicant |
| US5798752(A) | 1998-08-01 | Buxton et al. | Applicant |
| US5800177(A) | 1998-09-01 | Gillio | Applicant |
| US5800178(A) | 1998-09-01 | Gillio | Applicant |
| US5800179(A) | 1998-09-01 | Bailey | Applicant |
| US5802353(A) | 1998-09-01 | Avila et al. | Applicant |
| US5803738(A) | 1998-09-01 | Latham | Applicant |
| US5805140(A) | 1998-09-01 | Rosenberg et al. | Applicant |
| US5821920(A) | 1998-10-01 | Rosenberg et al. | Applicant |
| US5825308(A) | 1998-10-01 | Rosenberg | Applicant |
| US5828197(A) | 1998-10-01 | Martin et al. | Applicant |
| US5831408(A) | 1998-11-01 | Jacobus et al. | Applicant |
| US5844392(A) | 1998-12-01 | Peurach et al. | Applicant |
| US5859934(A) | 1999-01-01 | Green | Applicant |
| US5880714(A) | 1999-03-01 | Rosenberg et al. | Applicant |
| US5889670(A) | 1999-03-01 | Schuler et al. | Applicant |
| US5907487(A) | 1999-05-01 | Rosenberg et al. | Applicant |
| US5913727(A) | 1999-06-01 | Ahdoot | Applicant |
| US5929607(A) | 1999-07-01 | Rosenberg et al. | Applicant |
| US5929846(A) | 1999-07-01 | Rosenberg et al. | Applicant |
| US5956484(A) | 1999-09-01 | Rosenberg et al. | Applicant |
| US6084587(A) | 2000-07-01 | Tarr et al. | Applicant |
| US6191796(B1) | 2001-02-01 | Tarr | Applicant |
| US6337678(B1) | 2002-01-01 | Fish | Examiner |
| US6342880(B2) | 2002-01-01 | Rosenberg et al. | Examiner |
| EP915434(A2) | 1999-05-01 | Applicant | |
| WO95/02801 | 1995-01-01 | Applicant | |
| WO96/16397 | 1996-05-01 | Applicant | |
| WO96/22591 | 1996-07-01 | Applicant | |
| WO96/42078 | 1996-12-01 | Applicant | |
| WO97/06410 | 1997-02-01 | Applicant | |
| WO97/12337 | 1997-04-01 | Applicant | |
| WO97/12357 | 1997-04-01 | Applicant | |
| WO97/19440 | 1997-05-01 | Applicant | |
| WO97/21160 | 1997-06-01 | Applicant | |
| WO97/44775 | 1997-11-01 | Applicant | |
| WO98/06024 | 1998-02-01 | Applicant | |
| WO98/26342 | 1998-06-01 | Applicant | |
| WO98/30951 | 1998-07-01 | Applicant | |
| WO98/58308 | 1998-12-01 | Applicant | |
| WO98/58323 | 1998-12-01 | Applicant | |
| WO99/10872 | 1999-03-01 | Applicant |
Non-Patent Literature (60)
- US 5,903, 456, 05/1999, Schena et al. (withdrawn)Applicant
- Adachi, “Touch and Trace on the Free-Form Surface of Virtual Object,” Proceedings of IEEE Virtual Reality Annual International Symposium, Sep. 18-22, 1993, Seattle WA, pp. 162-168.Applicant
- Agrawal et al., “3D Painting on Scanned Surfaces”, Stanford University, 1995, pp. 145-150.Applicant
- Atkinson et al., “Computing with Feeling” COMPUT. & GRAPHICS, vol. 2, 1977, pp. 97-103.Applicant
- Avila et al., “A Haptic Interaction Method for Volume Visualization,” GE Corporate Research & Development, Schenectady, NY, pp. 1-9 (1996).Applicant
- Barr, “Global and Local Deformations of Solid Primitives”; COMPUTER GRAPHICS; vol. 18, No. 3, pp. 21-30 (Jul., 1984).Applicant
- Bergamasco, “Design of Hand Force Feedback Systems for Glove-like Advanced Interfaces”, IEEE, Sep. 1992, pp. 286-293.Applicant
- Blinn, “Simulation of Wrinkled Surfaces,” COMPUTER GRAPHICS, vol. 12-3, Aug. 1978, pp. 286-292.Applicant
- Brooks et al., “Project GROPE-13 Haptic Displays for Scientific Visualization,” COMPUTER GRAPHICS, vol. 24, No. 4, Aug. 1990, pp. 177-185.Applicant
- Burdea, “Force And Touch Feedback For Virtual Reality,” John Wiley and Sons, Inc., New York, New York, pp. 190-193 (1996).Applicant
- Colgate et al., “Factors Affecting the Z-Width of a Haptic Display,” Published by IEEE Computer Society Press, Los Alamitos, California, in Proceedings: 1994 IEEE International Conference On Robotics and Automation, held May 8-13, 1994 in San Diego, California, vol. 4, 1994, pp. 3205-3210.Applicant
- Colgate et al., “Implementation of Stiff Virtual Walls in Force Reflecting Interfaces,” IEEE Virtual Reality Annual International Symposium (Seattle, WA), pp. 202-208 (Sep. 18-22, 1993).Applicant
- Colgate et al., “Issues in the Haptic Display of Tool Use,” published by IEEE Computer Society Press, Los Alamitos, California, in Proceedings: 1995 IEEE/RSJ International Conference on Intelligent Robots and Systems—Huyman Robot Interaction and Cooperative Robots, held Aug. 5-9, 1995 in Pittsburgh, Pennsylvania, 1995, pp. 140-145.Applicant
- Decaudin, “Geometric Deformation by Merging a 3D-Object with a Simple Shape,” Graphics Interface '96 Proceedings (Toronto, Canada), 6 pgs. (May 21-24, 1996).Applicant
- Dworkin et al., “A New Model for Efficient Dynamic,” Fourth Eurographics Animation and Simulatiion Workshop Proceedings Eurographics Technical Report Series, ISSN 1017-4656, Sep. 4-5, 1993, pp. 135-147.Applicant
- Galyean, “Sculpting: An Interactive Volumetric Modeling technique,” Computer Graphics (SIGGRAPH '91Las Vegas), vol. 25, No. 4, pp. 267-274 (Jul. 1991).Applicant
- Hashimoto et al., “Dynamic Force Simulator for Force Feedback Human-Machine Interaction”, IEEE, Sep. 1993, pp. 209-215.Applicant
- Hirata et al., “3-Diminsional Interface Device for Virtual Work Space,” Proceedings of the 1992 IEEE, Jul. 7-10, 1992, pp. 889-896.Applicant
- Hirota et al., “Providing Force Feedback in Virtual Environments”, IEEE, Sep. 1995, pp. 22-30.Applicant
- Hirota et al., “Development of Surface Display,” Proceedings of the Virtual Reality Annual International Symposium (Seattle), pp. 256-262 (Sep. 18-23, 1993).Applicant
- Howe et al., “Task Performance with a Dextrous Teleoperated Hand System,” Telemanipulator Technology, Nov. 1992, Proceedings of SPIE, vol. 1833, pp. 1-9.Applicant
- Immersion Corporation, “Impulse Engine 2000,” http:.//www.immerse.com/WWWpages/IE2000pg.htm, 2 pages (1997).Applicant
- Immersion Corporartion, “Laparoscopic IMPULSE ENGINE ≃: A New FORCE FEEDBACK Surgical Simulation Tool”, Immersion Corporation, 1995.Applicant
- Immersion Corporation, “Medical Simulation,” 1 page, (1996).Applicant
- Immersion Corporation, “The IMPULSE ENGINE ≃”, 1 page, Immersion Corporation, 1996.Applicant
- Immersion Corporation, “Virtual Laparoscopic Interface”, Immersion Corporation, 1995, 1pg.Applicant
- Inoue et al., “Parallel Manipulator,” Proceedings of 3rd Robotics Research: The Third International Symposium, Faugeras & Giralt, eds., MIT Press 1986.Applicant
- Ishii et al., “A 3D Interface Device with Force Feedback: A Virtual Work Space for Pick-and-Place Tasks”, IEEE, Sep. 1993, pp. 331-335.Applicant
- Iwata, “Pen-based Haptic Virtual Environment,” Proceedings of IEEE Virtual Reality Annual International Symposium, (Sep. 18-22, 1993, Seattle, WA), pp. 287-292.Applicant
- Iwata, “Artificial Reality with Force-feedback: Development of Desktop Virtual Space with Compact Master Manipulator,” Computer Graphics (SIGGRAPH '90 Dallas), vol. 24, No. 4, pp. 165-170 (Aug. 1990).Applicant
- Kelly et al. “MagicMouse: tactile and Kinesthetic Feedback in the Human-Computer Interface Using an Electromagnetically Actuated Input/Output Device,” Department of Electrical Engineering, University of British Columbia, Vancouver, BC, V6T 1Z4, Canada, Oct. 19, 1993, pp. 1-27.Applicant
- Kotoku et al., “A Force Display Algorithm for Virtual Environments,” SICE, pp. 347-355, 1992.Applicant
- Kraft Ocean Systems, “Grips Underwater Manipulator System”. (1988).Applicant
- Kraft Telerobotics, Inc., “GRIPS Force Feedback Manipulator System,” (1988).Applicant
- Kraft Telerobotics, Inc., “GRIPS Master/Slave Manipulator System,” 1988.Applicant
- Lewis, “Electronic Pen With Its Own Eraser”, Personal Computers, Jul., 1995, p. C8.Applicant
- Marcus et al., “EXOS Research on Master Controllers for Robotic Devices,” Fifth Annual Workshop on Space Operatons Applications and Research (SOAR '91) pp. 238-245, Jul. 1991.Applicant
- Massie, “Design of a Three Degree of Freedom Force-Reflecting Haptic Interface”, Massachusetts Institute of technology; Bachelor of Science in Electric Science and Engineering Thesis, May, 1993, pp. 1-38.Applicant
- Massie, “Initial Haptic Explorations with the Phantom: Virtual Touch Through Point Interaction”, Massachusetts Institute of technology Master of Science Thesis, Feb., 1996, pp 1-49. (not admitted as prior art).Applicant
- McAffee et al, “Teleoperator Subsystem/Telerobot Demonstrator,” Force Reflecting Hand Controller Equipment Manual, Jet Propulsion Laboratory, Jan. 1988.Applicant
- Millman et al., “A System for the Implementation and Kinesthetic Display of Virtual Environments,” Telemanipulator Technology, Proceedings of 1992 SPIE, vol. 1833, pp. 49-56.Applicant
- Minsky et al., “Feeling and Seeing: Issues in Force Display,” COMPUTER GRAPHICS, vol. 24, No. 2, Mar. 1990, pp. 235-270.Applicant
- Minsky, “Cpmputational Haptics: The Sandpaper System for Synthesizing Texture for a Force-Feedback Display,” Massachusetts Institute of Technology Ph.D. Thesis, Jun., 1995, pp. 1-217.Applicant
- Morgenbesser, “Force Shading for Shape Perception in Haptic Virtual Environments”, Massachusetts Institute of technology Master of Engineering Thesis, Sep., 1995, pp. 1-77.Applicant
- MPB Technologies, Inc., “Freedom 3/6,” 6 pages, 1996.Applicant
- Payne et al., “Distance Field Manipulation of Surface Models,” IEEE Computer Graphics & Applications, pp. 65-71 (Jan. 1992).Applicant
- Salcudean et al., “On the Emulation of Stiff Walls and Static Friction with a Magnetically Levitated Input/Output Device,” DYNAMIC SYSTEMS AND CONTROL: vol. 1, DSC-vol. 55-1, 1994, pp. 303-309.Applicant
- Salisbury et al., “Haptic Rendering: Programming Touch Interaction with Virtual Objects,” Presented and disseminated at the 1995 Symposium on Interactive 3D Graphics held Apr. 9-12, 1995 in Monterey, CA, sponsored by the Association for Computing Machinery (ACM) and published by the ACM in Proceedings: 1995 Symposium on Interactive 3D Graphics, Monterey, California, Apr. 9-12, 1995, pp. 123-130.Applicant
- SensAble Devices, Inc., “GHOST Brochure,” 1995, Cambridge, MA (2 pgs.).Applicant
- SensAble Technologies, Inc., “Phantom Haptic Interface,” 1996, Cambridge, MA (6 pgs).Applicant
- Shimoga, “A Survey of Perceptual Feedback Issues in Dextrous Telemanipulation: Part I. Finger Force Feedback” published by IEEE Neural Networks Council in IEEE Virtual Reality Annual International Symposium, held Sep. 18-22, 1993 in Seattle, Washington, 1993, pp. 263-270.Applicant
- Snow et al., “Compact Force-Reflecting Hand Controller,” NASA Tech Brief, vol. 15, No. 4 from Jet Propulsion Laboratory Report NPO-17851-7348, Apr. 1991, pp. i, 1-3, 1a-11a, 14a,15a.Applicant
- Sutter et al., “Response to Reflected-Force Feefback to Fingers in Teleoperations,” Proc. of the NASA Conference On Space Telerobotics, pp. 65-74, NASA JPL, Jan. 1989.Applicant
- Swarup, “Haptic Interaction with Deformable Objects Using Real-Time Dynamic Simulation”, Massachusetts Institute of Technology, Sep. 1995, pp. 1-83.Applicant
- Tanie et al., “Force Display Algorithms” 1993 IEEE International Conference on Robotics and Automation, May 2-7, 1993, Atlanta Georgia, USA, 1993, pp. 60-78.Applicant
- Terzopoulos et al.; “Elastically Deformable Models”; COMPUTER GRAPHICS, vol. 21, No. 4, pp. 205-214 (Jul. 1987).Applicant
- Wang et al., “Volume Sculpting”, 1995 Symposium on Interactive 3D Graphics, Monterey, California, pp. 151-156. (1995).Applicant
- Yoshikawa et al., “Construction of Virtual World Using Dynamics Modules and Interaction Modules,” Proceedings of the 1996 IEEE International Conference on Robotics and Automation (Minneapolis, MN), pp. 2358-2364 (Apr. 1996).Applicant
- Zilles et al., “A Constraint-Based God-object Method for Haptic Display,” published by IEEE Computer Society Press, Los Alamitos, California, in Proceedings of the 1995 IEEE/RSJ International Conference on Intelligent Robots and Systems—Human Robot Interaction and Cooperative Robots, held Aug. 5-9, 1995 in Pittsburgh, Pennsylvania, 1995, pp. 146-151.Applicant
- Zilles, “Haptic Rendering with the Toolhandle Haptic Interface,” Massachusetts Institute of Technology Master of Science Thesis, May 1995, pp. 1-46.Applicant