Flexible Modeling Using Weak Type Definitions
The introduction of a data structure with delegation objects and operators in historyless CAD systems addresses the limitation of lacking design intent reuse, enhancing flexibility and maintainability by allowing topology-based modifications and type retention.
Patent Information
- Application Number
- JP2019233118
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2018-12-30
- Filing Date
- 2019-12-24
- Publication Date
- 2024-12-04
- Estimated Expiration
- 2039-12-24
AI Technical Summary
Current historyless methods in CAD systems are unable to capture and automatically apply design modifications across different 3D models, limiting the reuse of design intent and flexibility in iterative design processes.
A data structure is introduced that includes a delegation data object with specific input parameters and operators to generate output topology, allowing for the replacement or maintenance of delegated data objects based on topology changes during design operations.
This approach enhances the flexibility and maintainability of 3D models in historyless CAD systems by enabling the retention of design intent and seamless application of modifications across different models, while maintaining the underlying type information.
Smart Images

Figure 0007594360000001 
Figure 0007594360000002 
Figure 0007594360000003
Abstract
Description
[Technical field]
[0001] The present invention relates to the field of computer programs and computer systems, and more particularly to a data structure, a method, a system and a program for designing 3D models. [Background technology]
[0002] Many systems and programs are offered on the market for designing, engineering, and manufacturing objects. CAD is an acronym for Computer-Aided Design, which relates, for example, to software solutions for designing objects. CAE is an acronym for Computer-Aided Engineering, which relates, for example, to software solutions for simulating the physical behavior of future products. CAM is an acronym for Computer-Aided Manufacturing, which relates, for example, to software solutions for defining manufacturing processes and operations. In such computer-aided design systems, the graphical user interface plays a key role with regard to the efficiency of the technology. Product Lifecycle Management (PLM) systems can incorporate these technologies. PLM refers to a business strategy that helps companies share product data, apply common processes, and leverage corporate knowledge for product development, from conception to the end of the product life, across the concept of the extended enterprise. Dassault Systèmes' PLM solutions (product names CATIA, ENOVIA, and DELMIA) provide an Engineering Hub that aggregates product engineering knowledge, a Manufacturing Hub that manages manufacturing engineering knowledge, and an Enterprise Hub that enables business integration and connectivity for both the Engineering and Manufacturing Hubs. Together, the systems provide an open object model that connects products, processes and resources, enabling dynamic knowledge-based product creation and decision support that drives optimized product definition, manufacturing preparation, production and service.
[0003] CAD software proposes a method for creating a three-dimensional (3D) model, called a part, by using a set of tools that can be divided into two categories: history-based approaches (also known as parametric modeling) and history-free approaches (also known as explicit modeling).
[0004] History-based techniques are designed to record the design intent by remembering each step of the creation process with geometric features, constraints, etc. It is in effect like a recipe for a part, where each step of the creation presents a set of parameters that the user can modify. When the user changes one parameter, the whole "recipe" is played back in the same exact order to regenerate the new part. This technique is typically represented using a tree that allows the user to quickly understand the sequence of operations.
[0005] History-free approaches do not rely on replaying a series of operations for each modification. Each modification is made to the current 3D model; that is, there are no intermediate steps or "recipe" and as the user modifies their design, the modifications are absorbed into the features and the parameters that lead to the modifications are not maintained. This approach allows the user to create 3D models faster and with more freedom, since the order in which operations are performed is not maintained. The user can focus on the geometry they are creating, rather than worrying about the order in which features are created. Additionally, the user does not need to worry about the impact of their modifications.
[0006] The advantages of the history-based approach are also its disadvantages. Parametric approaches are very convenient in that the parameters can be changed almost at any time, but they take away flexibility from the design process. Once a "recipe" is created and each feature is strongly typed, you can only use those parameters. Making other changes can be very cumbersome, because to make the change you want, you need to think about how the change will affect the outcome when the part is regenerated. This is a big disadvantage when the user wants to try different types of shapes and iterate on them quickly. In the concept modeling or A-stage, the history-based approach is mainly used to create mechanical parts that represent the real-world objects that are going to be manufactured, while the history-free approach is mainly dedicated to the organic shapes of the product.
[0007] The objects used in the history-based approach are strongly typed. To change the type of an object, it is necessary to create a completely new object and replace the original object with the new one in the tree that represents the sequence of operations. The new object, which has no relation to the object it is replacing, may not fit well into the current "recipe" due to the change in topology. This happens when an object that an operation depends on has changed so that the elements needed to compute the transformation can no longer be found. In this case, the user has to explicitly tell the system how to do it. This is a tedious task, and the more complex the history, the more tedious and time-consuming it becomes.
[0008] With the history-free approach, the user can iterate quickly on geometry because the geometric features he or she works with are not typed in any way. The user does not need to be concerned with the impact of the current modification on the history of the object being designed. Furthermore, because no history is stored in the generic geometric features, the user works on the current state of the object (being designed). Thus, when the user iterates quickly on geometry, he or she can only modify the current state of the 3D shape. The user does not have access to any parameters of any operations he or she has performed previously.
[0009] The history-based and history-free approaches are not mutually exclusive, since objects generated from a history-free context can be integrated into a history-based context. Rather, a user can create a history-free model and apply operations to it that generate a new 3D model from it.
[0010] However, the data structures of these two approaches are not interoperable. In fact, the data structures of objects generated by the history-based and history-free approaches are somewhat different, especially because the data structures of objects in the history-based approach are strongly typed, whereas the data structures of objects in the history-free approach are untyped (the designer targets generic shape features, also called "data", that have no entries). The type of a 3D model in a history-based context refers to its characteristics and is defined by a set of parameters and at least one operation that takes as input the set of parameters and returns as output the topology of the object. For example, referring to FIG. 1, a 3D sphere is a typed 3D model, and the type of this "sphere" comes with a set of parameters, such as its center, radius, and opening angle. It comes with an operation that can take all of these parameters as input and return the topology of the sphere. In contrast, in a history-free context, the created shape is by definition typeless, since objects have no parameters. Each operation applied to an object is applied to the current definition of this object. In the example of Figure 3, the user only has access to the topology of the sphere, i.e., a wireframe of all the vertices and edges, and from that information can form a surface.
[0011] In summary, the data structure of the history-based approach contains type-specific input parameters, at least one type-specific operation, and the output topology generated by a previous operation, while the data structure of the history-free approach contains the current topology generated by the last external operation applied to the object. Summary of the Invention [Problem to be solved by the invention]
[0012] Due to the fundamental differences between these two approaches, the current history-free approach cannot capture the "recipe" of modifications that a user makes to a 3D model (or even to a mesh). In particular, it cannot automatically capture and apply to a new mesh the same or similar design operations that were made to the first 3D model. For example, a designer who modifies the design of a door for a first model of a car cannot automatically apply the same modifications to the door for a second model of a car. This means that design intent is largely unavailable in history-free CAD approaches; designers must intuitively apply modifications to the mesh for the second model of the car, hoping that their original design intent will be reproduced.
[0013] Against this background, there is still a need to improve the data structures defining 3D models for history-free approaches. [Means for solving the problem]
[0014] To this end, a data structure for defining a three-dimensional (3D) model is provided, said data structure including a delegated data object including input parameters specific to the type of said delegated data object and at least one operator specific to the type of said delegated data object for generating an output topology, said data structure also including an output topology generated by said operator.
[0015] The data structure may further include an interface for adding or removing at least one operator.
[0016] A computer-implemented method for designing a three-dimensional (3D) model is also provided, the method comprising: providing a first data structure defining a first 3D model including a first delegated data object and a first output topology, modifying the first delegated data object upon a user action, calculating a second output topology as a result of the modification of the first data structure, determining whether a change in topology has occurred by comparing the first output topology with the second output topology, and replacing the first delegated data object with the second delegated data object if a change in topology between the first output topology and the second output topology is identified, or keeping the first delegated data object if no change in topology is identified.
[0017] The method may include one or more of the following.
[0018] Replacing the delegation data object with the second delegation data object includes comparing the second output topology with a list of output topologies, each of which is associated with one delegation data object, and automatically selecting a third delegation data object, which is a delegation data object in the list that has the same associated output topology as the second output topology as a result of the comparison.
[0019] If the comparison results in no delegation data object being selected from the list, one or more delegation data objects from the list having associated output topologies closest to the second output topology, including one generic delegation data object, are provided to the user, and the user selects one of the provided delegation data objects.
[0020] Upon a user operation, modifying the first delegation data object includes modifying one or more input parameters of the first delegation data object, verifying that there is no topological change as a result of the comparison, and overwriting the input parameters of the first delegation data object with the modified one or more input parameters.
[0021] After the first data structure is provided, drawing the first output topology to form a mesh, and modifying the mesh upon user manipulation.
[0022] Modifying the mesh includes performing at least one operation selected from among scaling, translating, and maintaining the first delegated data object further includes generating the first output topology by an operator of the first delegated data object.
[0023] The first delegation data object and the first output topology form a base mesh.
[0024] Replacing the first delegation data object with the second delegation data object further comprises storing the second delegation data object as a new type.
[0025] A computer program comprising instructions for performing the method is further provided.
[0026] Further provided is a computer readable storage medium having the computer program and / or the data structures recorded thereon.
[0027] There is further provided a system including a processor coupled to a memory having the computer program and / or the data structure stored therein.The system may further include a graphical user interface.
[0028] Embodiments of the invention will now be described, by way of non-limiting example, with reference to the accompanying drawings, in which: [Brief description of the drawings]
[0029] [Figure 1] Here is an example of a strongly typed object: [Diagram 2] 1 shows an example of a data structure of the present invention. [Diagram 3] 1 shows an example of a data structure of the present invention. [Figure 4] 1 shows an example of a data structure of the present invention. [Diagram 5] Here is an example of a build phase: [Figure 6] Here is an example of a build phase: [Figure 7] We show how to use data structures to design 3D models. [Figure 8] An example is shown in Figure 7. [Figure 9] An example is shown in Figure 7. [Figure 10a] 4 shows the base mesh of the output data structure. [Figure 10b] 4 shows the base mesh of the output data structure. [Figure 11a] 4 shows the base mesh of the output data structure. [Figure 11b] 4 shows the base mesh of the output data structure. [Figure 12a] 4 shows the base mesh of the output data structure. [Figure 12b] 4 shows the base mesh of the output data structure. [Figure 13] An example of a system is shown. [Figure 14a] 1 illustrates an example of a base mesh defined by a data structure. [Figure 14b] 1 illustrates an example of a base mesh defined by a data structure. [Figure 14c] 1 illustrates an example of a base mesh defined by a data structure. [Figure 14d] 1 illustrates an example of a base mesh defined by a data structure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0030] With reference to Fig. 4, a data structure for defining a three-dimensional (3D) model is proposed. The data structure includes one delegated data object and an output topology generator. The delegated data object includes input parameters specific to the type of the delegated data object and at least one operator specific to the type of the delegated data object for generating an output topology.
[0031] Such a data structure improves the design of 3D models in history-free computer-aided design systems.
[0032] In particular, the data structure removes the limitations of the history-free approach by introducing the concepts of "weak typing" and "flexible modeling". As in the history-free approach, the data structure defining the 3D model is generic. Instead of taking a type-defining object as input data, the generic object delegates its type to another object. Such other types of objects are also called "weak types". Thanks to such delegated data objects, as in the history-based approach, the 3D model can be designed using a data structure that is a generic feature, and the generic feature has a type. However, this type is not strongly bound to the feature, since it is delegated to the delegated data object. Thus, the feature can change its type during its life depending on the context and operation. Thus, since the data structure is generic enough, it can be maintained during the design operation and can be changed if necessary or requested by the designer. Furthermore, the data structure offers new possibilities to the designer regarding the creation of the features. In fact, delegated data objects do not necessarily have to be tied to common geometric features (e.g., plane, cylinder, sphere, torus, etc.), and any shape (e.g., user-designed) may be used to derive new delegated data object types.
[0033] With reference to Fig. 7, a method for designing a 3D model using a data structure is proposed. The proposed method includes providing a first data structure according to the invention. The first data structure defines a first 3D model including a first delegated data object and a first output topology. The method then includes modifying the first delegated data object of the first data structure upon a user action. The method includes calculating a second output topology as a result of the modification of the first data structure. The method also includes determining whether a change in topology has occurred by comparing the first output topology and the second output topology. The method further includes replacing the first delegated data object with the second delegated data object if a change in topology between the first output topology and the second output topology is identified, or maintaining the first delegated data object if no change in topology is identified.
[0034] Such a method improves the design of 3D models in history-free computer-aided design systems. In particular, the method uses a data structure that can remove the limitations of history-free approaches by introducing the concepts of "weak" and "flexible modeling". The method thus allows the maintenance or replacement of delegated data objects depending on whether a change in topology occurred while designing the first 3D model. Due to the history-free approach, successive operations performed on the 3D model are not stored, but each operation targets the final state of the geometric features. This means that some operations may modify the delegated data objects or generic geometric features of the data structure. If this occurs, the delegated data objects are replaced by more appropriate ones. However, in some cases, the delegated objects can be kept as they are, since not all operations (e.g. design operations) are too destructive and in fact the operations modify one of the delegated object parameters. Furthermore, the method ensures that the objects seen in the geometric feature tree never change, but rather the delegated data objects on which they are based change. As a result, when the delegation data object changes, the system continues to store the type of the previous 3D model and the type of the new 3D model. Even if the delegation data object is replaced by a new one, the information of the replaced object can be maintained. In this way, the flexibility of the history-free approach is improved.
[0035] The method is computer-implemented. This means that the steps of the method (or substantially all steps) are performed by at least one computer, or any similar system. The steps of the method are thus performed by a computer, possibly fully automatically or semi-automatically. In an embodiment, at least some of the steps of the method may be initiated by an interaction between a user and a computer. The level of interaction between the user and the computer required may depend on the level of automation expected and may be balanced against the need to realize the user's wishes. In an embodiment, this level may be user-defined and / or pre-defined.
[0036] For example, the step of modifying the first delegation data object is performed upon a user action, such as during a design operation.
[0037] A typical example of a computer implementation of a method is the execution of the method on a system suitable for the purpose. The system may include a processor and a graphical user interface (GUI) coupled to a memory, the memory having a computer program recorded thereon, the computer program including instructions for executing the method. The memory may store a database. The memory is hardware suitable for such storage, and may include several physically distinct parts (e.g., one for the program and possibly one for the database).
[0038] The data structure defines the 3D model, and the method typically involves editing the data structure and thereby editing the 3D model. The 3D model is also referred to as a modeled object. A modeled object is an object defined by data stored in a database or the like. The expression "modeled object" thus refers to the data itself. Depending on the type of system, the modeled object may be defined by different kinds of data. The system may in fact be a combination of a CAD system, a CAE system, a CAM system, a PDM system, and / or a PLM system. In such different systems, the modeled object is defined by the corresponding data. It may be called accordingly a CAD object, a PLM object, a PDM object, a CAE object, a CAM object, CAD data, PLM data, PDM data, CAM data, CAE data. However, these systems are not mutually exclusive, since the modeled object may be defined by data corresponding to a combination of these systems. Thus, as is clear from the definition of such a system given below, a system may be considered to consist of both a CAD system and a PLM system.
[0039] A CAD system further refers to a system, such as CATIA, adapted to design a modeled object based on at least a representation of the modeled object. In this case, the data defining the modeled object includes data enabling the representation of the modeled object. For example, the CAD system may represent the CAD modeled object using edges or lines, possibly together with faces or surfaces. The lines, edges, or surfaces may be represented in various manners, such as non-uniform rational B-splines (NURBS). In particular, a CAD file includes specifications from which a geometry may be generated, thus enabling the generation of a representation. The specifications of the modeled object may be stored in a single CAD file or in multiple CAD files. A typical size of a file representing a modeled object in a CAD system is in the range of 1 megabyte per part. A modeled object may typically be a collection of several thousand parts.
[0040] In the case of CAD, the modeled object may typically be a 3D modeled object, e.g., a product, such as a part or a collection of parts, or possibly a collection of products. By "3D modeled object" is meant an object modeled by data that allows for a 3D representation. The 3D representation allows the part to be viewed from all angles. For example, when represented in 3D, the 3D modeled object may be manipulated and rotated about any axis of the object or about any axis in the screen on which the representation is displayed. Notably, this excludes 2D icons that are not 3D modeled. Displaying a 3D representation makes design easier (i.e., increases the speed at which designers statistically complete their tasks). Since product design is part of the manufacturing process, this speeds up the manufacturing process in industry.
[0041] A 3D modeled object may depict the geometry of a product, such as a part (e.g., a machine part) or an assembly of parts (which in other words can be said to be a collection of parts since an assembly of parts itself can be considered as a part from the point of view of the method or the method can be applied to each part of the assembly individually), or more generally, a rigid assembly (e.g., a moving mechanism), that is manufactured in the real world after virtual design has been completed using, for example, a CAD software solution or CAD system. CAD software solutions enable product design in various industrial sectors, such as, but not limited to, aerospace, architecture, construction, consumer goods, high tech equipment, industrial equipment, transportation, marine, and / or offshore oil / gas production or transportation. Thus, the 3D modeled objects designed by the method may be ground vehicle parts (e.g., automotive and light truck equipment, racing cars, motorcycles, truck and motor equipment, trucks, buses, and trains, etc.), aircraft parts (e.g., airframe equipment, aerospace equipment, propulsion equipment, defense products, aviation equipment, space equipment, etc.), marine parts (e.g., marine equipment, commercial ships, offshore equipment, yachts, work boats, and marine equipment, etc.), general purpose machine parts (e.g., industrial manufacturing machines, mobile large or heavy machines, installation equipment, industrial The industrial products may be depicted as any mechanical part, such as an equipment product, a fabricated metal product, a tire manufacturing product, etc.), an electromechanical or electronic component (e.g., home appliances, security and / or control and / or measurement products, computing and communication devices, semiconductors, medical devices and equipment, etc.), a consumer product (e.g., furniture, home and garden products, leisure products, fashion products, durable retailer products, non-durable retailer products, etc.), packaging (e.g., food and beverage, tobacco, beauty product, personal care product, household product packaging, etc.), etc.
[0042] A PLM system further means a system adapted to the management of modeled objects that represent manufactured physical products (or manufactured products). In a PLM system, the modeled objects are therefore defined by data suitable for the manufacture of physical objects. These data are typically dimensional and / or tolerance values. For an accurate manufacture of the objects, it is in fact better to have such values.
[0043] A CAM solution means a solution, hardware and / or software, adapted to manage the manufacturing data of a product. The manufacturing data usually includes data about the product to be manufactured, the manufacturing process and the resources required. With the CAM solution, the entire manufacturing process of the product is planned and optimized. For example, a CAM solution can provide the CAM user with information about the feasibility and duration of the manufacturing process or the number of resources, such as specific robots, that may be used in a particular step of the manufacturing process. This allows decisions about management or necessary investments. CAM is a post-process that takes place after the CAD process and potentially the CAE process. Such a CAM solution is offered by Dassault Systèmes under the product name DELMIA®.
[0044] CAE solutions further mean solutions, hardware and software, adapted to the analysis of the physical behavior of modeled objects. Among CAE techniques, the Finite Element Method (FEM) is well known and widely used, which typically involves dividing the modeled object into elements whose physical behavior can be calculated and simulated using equations. Such CAE solutions are offered by Dassault Systèmes under the product name SIMULIA®. Another growing CAE technique involves the modeling and analysis of complex systems made up of elements from different fields of physics that do not have CAD geometry data. CAE solutions allow the simulation of the products to be manufactured, thus allowing their optimization, improvement and validation. Such CAE solutions are offered by Dassault Systèmes under the product name DYMOLA®.
[0045] PDM stands for Product Data Management. A PDM solution is a solution, hardware and / or software, adapted to manage any kind of data related to a particular product. PDM solutions can be used by other stakeholders involved in the product life cycle, mainly engineers, but also project managers, finance personnel, sales personnel, and purchasing personnel. PDM solutions are generally based on a product-oriented database. This allows stakeholders to share consistent data about the product, thus preventing them from using different data. Such PDM solutions are offered by Dassault Systèmes under the product name ENOVIA®.
[0046] FIG. 13 illustrates an example of a system, which is a client computer system, such as a user's workstation.
[0047] The client computer in this example comprises a central processing unit (CPU) connected to an internal communications bus 1000, and a random-access memory (RAM) 1070 also connected to the bus. The client computer further comprises a graphical processing unit (GPU) 1110 with associated video random access memory 1100 connected to the bus. The video RAM 1100 is also known in the art as a frame buffer. A mass storage device controller 1020 manages access to mass memory devices such as a hard drive 1030. Mass memory devices suitable for embodying computer program instructions and data include any form of non-volatile memory, such as semiconductor memory devices such as EPROMs, EEPROMs, flash memory devices, magnetic disks such as internal hard disks or removable disks, magneto-optical disks, and CD-ROM disks 1040. Any of the foregoing may be supplemented by or incorporated in specially designed application-specific integrated circuits (ASICs). A network adapter 1050 manages access to a network 1060. The client computer may also include a tactile device 1090, such as a cursor control device and a keyboard. In a client computer, the cursor control device is used to allow a user to selectively place a cursor at a desired location on the display 1080. Furthermore, the cursor control device allows a user to select various commands and input control signals. The cursor control device includes a number of signal generating devices for inputting control signals into the system. Typically, the cursor control device may be a mouse, where the buttons of the mouse are used to generate signals.Alternatively, or in addition, the client computer system may be equipped with a sensitive pad and / or a sensitive screen.
[0048] A computer program may include instructions executable by a computer, which may include means for causing the system to carry out the method. The program may be recordable on any data storage medium, including the memory of the system. The program may be implemented, for example, in digital electronic circuitry, computer hardware, firmware, software, or a combination thereof. The program may be implemented as an apparatus, such as an article of manufacture tangibly embodied in a machine-readable storage device for execution by a programmable processor. The method steps may be performed by a programmable processor executing a program of instructions to operate on input data and generate output to perform the functions of the method. Thus, the processor may be programmable and connected to receive data and instructions from, and transmit data and instructions to, the data storage system, at least one input device, and at least one output device. The application program may be implemented in a high level procedural or object-oriented programming language, or in assembly or machine language, as appropriate. In either case, the language may be a compiled or interpreted language. The program may be a full installation program or an update program. In either case, the program is applied to a system to provide instructions for carrying out the method.
[0049] The data structure is functional data that serves to control and store the operation of a CAD system (or the like). Thus, the data structure serves to control the operation for designing a 3D model, for example in a history-less CAD system. In particular, the data structure improves the design operation in creating shapes with types and parameters that are not strongly typed but are instead weakly typed generic shape features. Here, the data structure is functional data of technical features for designing a 3D model that depicts, for example, a real-world object.
[0050] By "designing a 3D modeled object" is meant any operation or sequence of operations that is at least part of a process of elaborating a 3D modeled object. Thus, the method may include creating a 3D modeled object from scratch. Alternatively, the method may include providing a previously created 3D modeled object and modifying the 3D modeled object. The method may be included in a manufacturing process that may include creating a physical object corresponding to the modeled object after performing the method. In either case, the modeled object designed by the method may represent an object for manufacturing. Thus, the modeled object may be a modeled solid (i.e., a modeled object that represents a solid). The object for manufacturing may be a product, such as a part or an assembly of parts. Because the method improves the design of the modeled object, the method also improves the manufacturing of the product, thereby increasing the productivity of the manufacturing process.
[0051] Figure 1 shows an example of a strongly typed data structure commonly used in known history-based CAD systems. In this example, the data structure defines a 3D sphere feature, where the 3D sphere is the typed 3D model. The 3D sphere feature defines a 3D sphere type with a set of parameters such as the sphere's center, radius, and opening angle. The data structure involves a single operation, the sphere operation. The output data of the typed feature results in the topology of the sphere, as shown on the right of Figure 1.
[0052] Then, from the perspective of the history-free approach, only the mesh that describes the sphere is used in the system. The history-free paradigm means that the shape features are generic. This means that if the CAD system only had access to the mesh (a wireframe with all the vertices, edges, from which faces can be formed), the CAD system would not know that the mesh describes a sphere. Thus, even though the designer can quickly iterate on the shape, he can only modify the current state of the mesh. Thus, it is not possible to modify only one parameter of the sphere, for example, the designer cannot modify the radius of a mesh that has the 3D shape of a 3D sphere.
[0053] FIG. 2 shows an example of a data structure of the present invention. The data structure (or shape feature) is generic. This means that the data structure is not typed and therefore is not associated with one specific type of object, such as the basic shape of a sphere. Shape features are building blocks that can be given a shape. Shape features are typically used in 3D modeling to build 3D modeled objects. As non-limiting examples, cuboids (e.g., cubes), cylinders, spheres, pyramids, cones, quadric surfaces, ruled surfaces, tori, etc. can be cited as "typical" shape features. More generally, shape features can describe any shape, even very complex shapes such as cars or airplanes, but they have a set of parameters that are sufficient for a specific operator to generate the shape. A set of shape features makes it possible to represent industrial products, such as industrial products described by meshes in a history-free CAD system.
[0054] If a data structure is generic, it can be used in a history-free CAD system. A generic feature is independent of the feature type. However, it can receive data, execute it, and obtain results similar to those obtained from a typed feature. The data structure takes as input data a delegate data object that defines the feature type. The delegate data object contributes to "weakly typing" the generic feature. This means that the data structure is generic and its genericity is constrained by the delegate data object. If a data structure is generic, it is not associated with a specific operation. The operation involves the delegate data object. Thus, the (generic) data structure inherits the type and the operators specific to the type of the delegate data object. This inheritance is done by providing the generic feature with the delegate data object (including the type and the specific operator) as input data. The output data is the topology calculated from the input data by the generic feature. Thus, the topology is specific to the type of the input data.
[0055] Figure 3 shows that when a (generic) data structure receives as input a delegated data object of type sphere, the topology it creates is a sphere. The creation of the sphere is controlled by the operator of that type, which is executed by the data structure. Thus, the operator of the delegated data object is retrieved and executed by the data structure.
[0056] A delegate data object includes input parameters that are specific to the type of the delegate data object. A delegate data object also includes one or more operators that are specific to the type of the delegate data object.
[0057] FIG. 4 shows an example of a delegation data object specific to the type "sphere". When the delegation object is executed by the generic shape feature, i.e., when the system requests the "sphere" shape feature to perform self-construction, the generic shape feature assigns it as a specific type to the delegation data object. In such an example above, the delegation data object remembers that a sphere should be constructed using "center", "radius" and "opening angle" as parameters. Thus, the delegation object generates an operation using its input parameters. This operation is then used by the generic shape feature to generate the topology. Thus, if the delegation object is replaced by another object for some reason, it is transparent from the point of view of the generic shape feature, since the other object still obtains and implements the operation given by the delegation object.
[0058] The parameters of the delegation data object allow for the creation of an instance of an operator that produces an output topology. For example, the following are known in the art:
[0059] · The input parameters specific to the "Sphere" type are center, radius, and opening angle.
[0060] The input parameters specific to the "Cylinder" type are axis direction, cylinder height, circle center, and circle radius.
[0061] · The input parameters specific to the "Cone" type are axis direction, cone height, center of cone base, and radius of cone base.
[0062] · The input parameters specific to the "Torus" type are the direction vector, the center, the radius of the major circle, and the radius of the minor circle.
[0063] The data structure further includes the output topology produced by the operator, where the topology depends on the type of the delegated data object.
[0064] In an embodiment, the operation may be performed by an operator specific to the type of the delegated data object. In such a situation, the operation is also referred to as an internal operation. The topology of the output topology is not modified. Internal operations are typically operations that are performed as a result of modifying input parameters of the delegated data object, such as the scale or movement of the output topology. A list of these operations is associated with the delegated data object, so that the generic shape feature remembers that modifications may be performed by operations already "loaded" into the generic shape feature.
[0065] In an embodiment, the operation may be performed by an operator that is not specific to the delegated data object. In such a situation, the operation is also referred to as an external operation. The output topology is altered. External operations are operations that typically cannot be performed by the operators of the delegated data object, since the topology of the output data is altered, for example, cutting is performed on the 3D representation of the 3D model defined by the data structure. To perform the operation, the data structure may have an interface adapted to add or remove at least one operator. The operator may be "loaded" into the data structure and executed. The operator of the delegated data object may be kept loaded into the generic shape feature or simply removed. The data structure always contains at least one operator.
[0066] In an embodiment, the output topology may be rendered, making a representation of the 3D model defined by the data structure accessible, for example to be presented to a user. The output topology may be rendered using a mesh, as known in the art. A mesh may be a subdivision surface, which is a method of depicting a smooth surface through the specification of a coarser, piecewise rectilinear polygon mesh. A mesh is a collection of vertices, edges, and faces that define the shape of a 3D model. Thus, a mesh defines a geometry for which a representation of the output topology of a 3D model can be generated. A mesh may be a subdivision surface, which is commonly used to model free-form surfaces of arbitrary topology. A subdivision surface is defined as a range of a refinement process of control points starting from a polygonal base mesh. The control points of the base mesh propagate the gradual changes to the subdivision surface. Thus, the mesh of the subdivision surface is refined as a result of iterative application of the subdivision process controlled by the control points of the base mesh. Thus, the subdivision surface approximates or interpolates the base mesh. The Catmull-Clark algorithm is one example of such a subdivision scheme. Base meshes are widely used in CAD, and as a simple definition, the base mesh contains the definition of the subdivision mesh and the control points of the subdivision mesh. It will be appreciated that several dedicated algorithms may be used.
[0067] Thus, a design operation may be a modification performed on one of the control points of a base mesh upon operation by the user. Examples of design operations on a base mesh are shown in Figures 14a, 14b, 14c, and 14d. Figure 14a shows an example of a base mesh, which is a cube base mesh. The cube base mesh has 8 control points and the edges are of equal length. None of the vertices, edges, or faces are weighted. In Figure 14b, the user displaces (i.e., moves) the control points of the base mesh of Figure 14a, which controls the subdivision of the original cube, into a sphere, for example using the Catmull-Clark algorithm. Figure 14c shows the subdivision surface obtained from the base mesh of Figure 14a, which is a cube base mesh (8 control points), with edges of equal length and two opposite faces weighted (100% sharp). This results in a cylinder. Figure 14d shows the subdivision surface obtained from the base mesh of Figure 14a, which is a cubic base mesh (8 control points) with edges of equal length and weighted (100% sharp) edges. A cube is obtained. In these examples, the control points modify the subdivision process by modifying the weights of the vertices, edges or faces. The attractiveness of the mesh depends on the weighting.
[0068] The build phase of a 3D model defined by a data structure according to the present invention will now be described with reference to FIGS.
[0069] Figure 5 illustrates the build phase of a generic shape feature in a history-free system known in the art. When a user requests a shape modification, the system executes the shape build phase. In most cases, during this phase, an operator is invoked that describes the current modification, and the result of this operator is a new shape that is associated with the current shape. The build phase has one output, which is the new shape.
[0070] Figure 6 illustrates the build phase of the data structure of the present invention. The build phase of the present invention is different because it does not just compute a new shape for the current modification, but ensures that the delegated data objects remain unchanged, and if not, new delegated data objects are provided to the data structure.
[0071] The build phase will now be described more precisely with reference to FIG. 7, which is an example of a computer-implemented method for designing a 3D model using the data structure of the present invention.
[0072] At S10, a first data structure according to the present invention is provided, the first data structure defining a first 3D model and including a first delegation data object and a first output topology, the first output topology defining a current geometry which may be a representation of the current 3D model, for example a base mesh is presented.
[0073] In S20, the build phase is executed.
[0074] The build phase starts with the modification (S21) of the first delegation data object by the user. The modification of the first delegation data object may include directly modifying one or more of the input parameters of the first delegation data object. Alternatively, the modification may include modifying the 3D model (the 3D shape, i.e., the representation of the 3D model) without explicitly modifying one or more of the parameters of the delegation data object. As another possibility, the first delegation data object is replaced by another delegation data object.
[0075] It is then determined (S22) whether a change in the first output topology has occurred as a result of the user modification (S21). It will be appreciated that determining that a change in topology has occurred can be accomplished using known techniques.
[0076] For example, this determination is made by comparing the first output topology with the second output topology, where the second output topology is the resulting topology after modification by the user.
[0077] Comparing the first output topology and the second output topology may include comparing a first base mesh and a second base mesh, where the first base mesh is a base mesh corresponding to the unmodified geometry and the second base mesh is a base mesh corresponding to the modified geometry, where it is easier to calculate the topology changes from the meshes.
[0078] If the current operation (S21) maintains the delegation data object, i.e. the type of the 3D shape does not change as a result of the modification, then S23 is executed, otherwise S24 and S25 are executed.
[0079] Next, S23 will be described with reference to Fig. 8. Since no change in topology is confirmed, the first delegation data object is maintained. In other words, the type of the 3D model is not changed. This is the case when one or more of the parameters of the first delegation data object are modified, or when the modification of the 3D shape that does not explicitly change the parameters of the weak type does not affect the first topology output.
[0080] Thus, when a user modifies one or more of the input parameters of the first delegation data object, the input parameters of the first delegation data object are overwritten with the modified input parameters. Interestingly, in such a situation, the change in topology may not be verified.
[0081] Also, if a modification of the 3D shape that does not explicitly change a parameter of the weak type does not affect the first topology output, the first delegation data is maintained and the parameter is modified in response to the modification of the 3D shape. New values of the one or more parameters are calculated in response to the modification of the 3D shape. The one or more new values are calculated as known in the art.
[0082] The modification of the 3D shape may be performed by the user directly modifying the mesh. In this case, a first output topology is drawn, as known in the art, to form a base mesh. The user then performs modifications on the base mesh. For example, the user moves vertices, edges, or control points of the base mesh.
[0083] In an embodiment, modifying the (base) mesh comprises performing at least one operation selected from among scaling, translation, etc. These operations are known to be topologically neutral (i.e., they do not change the topology), so the first output topology is generated by immutable operators of the first delegated data object.
[0084] S24 and S25 will now be described with reference to Figure 9. In S24, a new delegation data object is selected to replace a current delegation data object that is no longer valid (S25).
[0085] The identification of the new delegation data object may be performed by comparing the second output topology (the new output topology resulting from the modification) with the output topologies in the list of output topologies. The output topologies in the list are each associated with one delegation data object, so that when a similarity between the new output topology and the output topologies in the list is identified, the associated delegation data object is maintained as the new delegation data object. In other words, as a result of the comparison, a third delegation data object is selected, the third delegation data object being the delegation data object in the list that has the same associated output topology as the second output topology. The selection of the third delegation data object may be performed automatically, for example without user intervention.
[0086] Alternatively, the comparison may be made between 3D shapes, in which case the list includes the 3D shapes associated with the delegation data object. However, it may be impossible to select a new delegation data object in the list. A typical reason may be that the same topology is not listed in the list. In such a situation, the user is provided with one or more delegation data objects in the list that have an associated output topology that is closest to the second output topology. The distance between the two topologies is measured as known in the art. For example, this can be done by calculating the ambiguity of the meshes that describe the output topologies. At least the positions of the vertices of the meshes are compared (with a given tolerance) and thus the edges that connect the vertices are compared. A ranking is made from the measurements, and the topologies with the highest ranking are provided to the user.
[0087] Alternatively, a comparison may be made between 3D shapes, in which case a similarity measurement is made between the current 3D shape (as modified by the user's manipulation) and the list of 3D shapes associated with the delegated data object, and the delegated data object with the 3D shape most similar to the current 3D shape is presented to the user.
[0088] The list may further include one generic delegation data object that can be used if the user is not satisfied with the proposed topology, or it may be the only delegation data object proposed to the user.
[0089] After selecting one of the provided delegation data objects, the first delegation data object is replaced with the selected delegation data object.
[0090] Interestingly, at any stage of the method, and more particularly when steps S24 and S25 are performed, the user may create new types: for example, replacing the first delegation data object with the second delegation data object may include storing the second delegation data object as a new type. Referring again to FIG. 7, at S30 the data structure contains the same weak type or new weak types after modification by the user, and the topology output.
[0091] Figure 10a shows a data structure corresponding to a sphere type, and Figure 10b shows the same data structure after scaling. In fact, scaling is an operation that does not modify the delegate data object of Figure 10a.
[0092] Figure 11a shows the data structure of Figure 10a. Figure 11b shows the same data structure after an extrusion operation. The base mesh has been modified, which changes the topology of the topology output. This causes a subdivision and identifies a new delegate data object in the list of delegate data objects, which replaces the current delegate data object.
[0093] Fig. 12a shows a generic object. Fig. 12b shows the same generic object after performing a fill operation on it. The fill operation results in a sphere. In practice, the system can extract relevant information to fill in the parameter values of the sphere. This is possible by comparing the 3D shape with a list of shapes of delegate data objects. If the system recognizes several possible delegate data objects, it will prompt the user to choose from the possible options.
Claims
1. 1. A computer-implemented method for designing a three-dimensional (3D) model, comprising: providing a first data structure defining a first 3D model including a first delegation data object and a first output topology; Modifying the first delegation data object upon a user action; Calculating a second output topology as a result of modifying the first data structure; and comparing the first output topology to the second output topology to determine whether a topology change has occurred; replacing the first delegation data object with a second delegation data object if a change in topology between the first output topology and the second output topology is identified, or maintaining the first delegation data object if no change in topology is identified; A computer-implemented method comprising:
2. Replacing the first delegation data object with the second delegation data object comprises: comparing the second output topology to a list of output topologies, each topology in the list being associated with one delegation data object; automatically selecting a third delegation data object, which is a delegation data object in the list that has the same associated output topology as the second output topology as a result of the comparison; 2. The computer-implemented method of claim 1, comprising:
3. If the comparison result is that the delegation data object in the list is not selected, providing to the user one or more of the delegation data objects in the list having associated output topologies closest to the second output topology, the associated output topologies including one generic delegation data object; A user selecting one of the provided delegation data objects; The computer-implemented method of claim 2 further comprising:
4. Modifying the first delegation data object upon a user operation includes: modifying one or more input parameters of the first delegation data object; determining that there is no topological change as a result of comparing the second output topology with the list; and overwriting input parameters of the first delegation data object with the modified one or more input parameters; 4. The computer-implemented method of claim 2 or 3, comprising:
5. After the first data structure is provided, forming a mesh by rendering the first output topology; modifying said mesh upon user manipulation; The computer-implemented method of any one of claims 1 to 4, further comprising:
6. Modifying the mesh includes performing at least one operation selected from the group consisting of scaling, translation; maintaining the first delegation data object further comprises generating the first output topology by an operator of the first delegation data object.
6. The computer-implemented method of claim 5.
7. the first delegation data object and the first output topology form a base mesh. A computer-implemented method according to any one of claims 1 to 6.
8. replacing the first delegation data object with the second delegation data object further comprises storing the second delegation data object as a new type. A computer-implemented method according to any one of claims 1 to 7.
9. A computer program comprising instructions for carrying out the method according to any one of claims 1 to 8.
Citation Information
Patent Citations
Drawing support program of civil engineering structure
JP2006209233A
Method for validating features in a direct modeling paradigm
US20110025688A1
Modifying a parametrically defined model with an explicit modeler
US20120084060A1
Methods and systems for converting select features of a computer-aided design (CAD) model to direct-edit features
US9117308B1
Representation of sheet metal part models
WO2006038733A2
