JP2015526779A - Results-based tool selection, diagnostics, and help system for feature-based modeling environments - Google Patents

Abstract

In a modeling environment, a user typically interacts with a feature-based model by manipulating the model's features using tools that can achieve a number of different results on the features. An interface may be displayed that allows operations to be performed based on the results to be achieved, rather than by providing a generalized tool to achieve the results. Thus, the number of options presented on the interface can be reduced by eliminating irrelevant options that are associated with the tool but are not directly applicable to the desired result. A dynamic help system can be provided that provides targeted and dynamically generated information related to the results to be achieved. In addition, alerts can be displayed on the interface in real time during the model design process.

Description

(background)
This application claims priority from US application Ser. No. 61 / 654,349, filed Jun. 1, 2012. The above references are incorporated herein by reference in their entirety.

  A feature-based modeling environment is a modeling environment that can be used to build a model using one or more features. A feature may be defined by a geometric shape and may be defined in terms of a two-dimensional space, a three-dimensional space, or both. The features may be combined, stretched, extruded, or otherwise manipulated as desired by the user to achieve a shape or series of shapes. Examples of feature-based modeling environments include computer-aided design (CAD) and computer-aided manufacturing (CAM) environments. Feature-based modeling can be used to design, model, test, and / or visualize a product.

  In existing feature-based modeling environments, a user may use one or more tools to manipulate model features. Tools are generalized methods for interacting with features and manipulating feature geometries in a well-defined manner.

  One common example of a tool is an “extrusion” tool. The extrusion tool can be used to select a feature surface or a portion of a surface and move the surface in 2D or 3D space. This movement may involve “pulling” the surface away from the rest of the feature to form a new surface. Alternatively, the surface may be “pushed” into the feature and create a recess in the feature (eg, create a “cut” in the feature).

  Another example of a tool is a “stretch” tool. The stretching tool can be used to modify the outer edge of the feature surface. When one or more edges are moved away from the center of the feature, the stretched edge can enlarge the feature. In contrast, when one or more edges are moved toward the center of the feature, the stretched edge can shrink the feature.

  As can be seen from the above, a single tool can be used to achieve more than one result. For example, an extrusion tool can be used to extend a surface or create a recess in the surface. The stretching tool can be used to enlarge the surface or reduce the surface.

  A tool can be associated with a number of options that describe how the tool interacts with a feature. Typically, when a tool is selected, each of the options associated with the tool is displayed.

  For example, when a new surface is pulled from an existing surface using an extrusion tool, several new surfaces can be created as shown in FIGS. 1A-1B. In FIG. 1A, the surface 110 is on a feature in the model. Surface 110 includes a portion 120 designated for extrusion by an extrusion tool. As mentioned above, an extrusion tool can be used to “pull” a surface or a portion of a surface. As shown in FIGS. 1B and 1C, the portion 120 may be pulled away from the surface 110. By doing so, several new surfaces can be created, including surface 130 and surface 140. As a result of the extrusion of the portion 120, a new cube 150 is created.

  When creating a new cube 150, it may be important for the user to define whether the new cube is hollow or solid. That is, is the interior of the new cube filled with material, or is the interior of the new cube empty so that the cube is defined only by the walls of the cube? Thus, the extrusion tool may include an option to create a “solid” cube or only a “surface” cube.

  However, depending on the results to be achieved, some options associated with a particular tool may have little or no importance to the particular modification envisaged. For example, as in FIGS. 1A-1C, in addition to “pulling” the surface to create a new surface, the extrusion tool also “cuts” the surface, creating a dimple, as shown in FIG. 1C. (I.e., rather than pulling the portion 120, the portion 120 is pushed into the surface 110 of FIG. 1A).

  If the user uses an extrusion tool consistently to make incisions in the feature, the user will be able to define whether the geometry being created is solid or hollow Most likely you are not interested in the options. These options are meaningless in the context of a cut as compared to a protrusion because a depression is created rather than a protrusion. The option of making a solid or hollow cut is therefore irrelevant.

  Note that the specific tools described above (eg, “extrusion” and “extension”) may be given different names in different feature-based modeling environments. Throughout this specification, specific examples may be given with reference to the Creo® product family from PTC® (Needham, Massachusetts). One skilled in the art will recognize that the exemplary embodiments described herein are not limited to a particular product group and can be applied to any feature-based modeling environment.

(wrap up)
The display of irrelevant information is particularly problematic in feature-based modeling environments where the model designer's primary focus is likely to be on the model being designed, rather than the design environment itself. Providing extraneous options reduces the “occupied area” on the screen that can be used by the designer to design the model.

  Traditionally, because the design environment does not distinguish between a tool and the results that a user may desire to achieve using that tool, each option associated with the tool is displayed in response to the activation of the tool.

  The exemplary embodiments described herein are feature-based models in terms of desired results that are to be achieved through interaction, as opposed to the tools that are to be used to achieve the results. Redefine user interaction with. Referring to the previous example, a user may interact with the model by instructing the design environment to create a solid protrusion, create a hollow protrusion, or create a cut. This is in contrast to using a tool to extrude or pull the surface while selecting a general extrusion tool and defining options for making the resulting shape solid, hollow, or cut. is there.

  An irrelevant option associated with the tool by focusing on the desired result instead of the tool (but otherwise unrelated or less important to the result to be achieved) Can be hidden and provide an improved and more efficient modeling environment. Furthermore, the use of a results-driven paradigm rather than a tool-driven paradigm allows other modifications to streamline the design environment. For example, help information corresponding to a dynamic situation can be presented based on the result that the user is trying to achieve. Further, potential errors can be identified during the model design process in real time or near real time when an attribute value or values are defined for one or more options associated with the result. .

  One such error is a violation of design intent that can be identified based on the results that the user intends to achieve. For example, if the user wants to create a hollow protrusion, but instead the user moves the surface in a manner that results in a cut or indent, the environment will prompt the user to Can be immediately notified that will be violated by the proposed modifications.

  According to one exemplary embodiment, a feature-based modeling environment may be provided and the computing device may interact with the feature-based modeling environment. A feature-based modeling environment may include a model having at least one feature described by a feature geometry. The feature-based modeling environment may support at least one tool that defines the manipulation of feature geometry. Operations can be applied to achieve a number of different results, each individual result affecting the feature in a different way. A selection of results to be achieved by the tool may be received and the feature geometry may be manipulated according to the selected results.

  In some embodiments, at least two of the plurality of different results may be displayed on the interface of the feature-based modeling environment. At least two of the plurality of different results may be a subset of the plurality of different results, the subset being selected based on previous history of result selection. For example, the subset may be selected based on previous user selections of results and / or options associated with the results. In some embodiments, the interface may be displayed in response to receiving a selection of results to be achieved by the tool, and the interface is associated with a tool that is applicable to the selected result. You will be given a choice.

  In some embodiments, another interface may be displayed depending on the selection of results to be achieved by the tool. The interface may be populated with options related to the result. The choices entered into the interface may be user selected or may be selected programmatically based on, for example, previous user interactions. The options entered into the interface may be a subset of the options associated with the tool. Further, one or more options associated with the tool but not in the subset may be presented in the interface. The subset may be a user-defined subset or may be defined programmatically. In some embodiments, the subset may be dynamically generated when the user selects a result to be achieved by the tool.

  In order to display an interface associated with options associated with a result, a template may be defined to define which options are associated with the result. In one embodiment, a selection of tools for use with a feature-based modeling environment may be received. A tool may interact with one or more surfaces, edges, or vertices of a feature in a feature-based modeling environment and may be capable of modifying one or more surfaces, edges, or vertices. Multiple configurable options for the tool may be displayed. The configurable option may be capable of accepting attribute values, and the set of attribute values for the configurable option defines the result of using the tool. One or more of the configurable options may be flagged as associated with the result or unrelated to the result.

  Subsequently, the result may be displayed as a possible choice. In response to receiving the selection of results, an interface associated with the results may be displayed. The interface may only display options that are marked as associated with the result. Alternatively or additionally, the interface may hide any option marked as unrelated to the result.

  In some embodiments, the interface may be associated with a particular user or group of users. Thus, the identity of the user or user group may be determined, and when the user or user group subsequently reenters the modeling environment, the interface associated with the user or user group is read and displayed. Also good.

  In another embodiment, the interface may be associated with features defined using the interface. For example, features originally manipulated by a user or group of users using an interface may be identified. An interface may be associated with a feature, for example by storing the identification of the interface with the feature (or vice versa). The instructions for interacting with the feature associated with the interface may be received from a second user or a second group of users, which may be different from the original user or group of users who manipulated the feature using the interface. . As a result of the instructions for interacting with the feature, the interface originally used to manipulate the feature may be displayed to the second user or the second group of users. In this way, a consistent interface may be associated with a particular feature on a user base, allowing subsequent users to manipulate the feature in the same way that the feature was originally created.

  In some embodiments, if the feature is displayed on a display device, the interface may be displayed on the display device at a location that is defined based on the location of the feature on the display device. Thus, an interface may be provided in close proximity to features associated with or manipulated by the interface. Thus, the user does not need to search through the menu or take the attention away from the feature in order to manipulate the feature.

  In some embodiments, evaluation and alert features may be provided that operate in real-time or near real-time to determine the validity of inputs to model choices. Thus, during the model design process, in response to receiving a selection of results to be achieved by the tool, an interface may be displayed in response to receiving the selection of results. The interface may be populated with options associated with the tools that are applicable to the selected result. An attribute value for one of the options may be received and the feature may be represented using the attribute value. The attribute value may be provided by the user using the interface. The feature may be evaluated during the model design process in response to receiving one or more attribute values for one or more result options. Problems with attribute values may be identified and warnings with attribute values may be displayed.

  In some embodiments, when an interface that includes options is displayed on a display, a warning may be displayed at a location that is determined based on the location of the options within the interface. In this way, the alert may be displayed in close proximity to the option to assist the user in identifying the alert source.

  Features may be evaluated for different error conditions. For example, in one embodiment, the alert may be related to a violation of a geometric shape rule. In another embodiment, the warning may relate to a violation of design intent. In yet another embodiment, the warning may indicate a missing or null value.

  In some embodiments, a help page depending on the dynamic situation may be displayed after receiving a selection of results to be achieved by the tool during the model design process. In these embodiments, the interface may be displayed in response to receiving a selection of results. The interface may be populated with options associated with the tools that are applicable to the selected result.

  The interface may provide an entry point to the help system. For example, the interface itself may be an entry point. Alternatively, one of the aforementioned options in the interface may serve as an entry point. The entry point may be an explicit entry point, such as a “?” Button provided on the interface. Alternatively, the entry point may be implicit, for example, a user interacting with the interface may press the “F1” key, and the interface is the user's interface when that help is requested. As a result of the interaction with, it may be recognized as an entry point. In these and other similar methods, a request to enter the help system from an entry point may be received.

  In response to receiving a request to enter the help system from an entry point, the help page may be dynamically generated with content selected based on the entry point. For example, when the entry point is an interface, the help page may include specific information related only to the interface. If the entry point is an option in the interface, the help page may be dedicated to the option. The option may be the option that the user is currently interacting with (such as by typing an attribute value into the option field), and the content is the option that the user is currently interacting with when a request to enter the help system May be generated dynamically when received based on The content may further be dynamically generated based on one or more user selections or user-supplied attribute values associated with the options with which the user is currently interacting.

  A help system may be provided to generate content for the help page. The help system may include help information. The content selected for display to the user may be a subset of the help information in the help system and may be selected dynamically based on entry points.

  Thus, the target help content may be dynamically generated so as to be most applicable to the user's area of interest.

  The invention may be embodied as instructions stored on a non-transitory computer readable medium. The instructions may be executed by one or more processors to cause one or more processors to implement an exemplary embodiment of the invention. The present invention may also be embodied as a computer-executable method. Furthermore, the present invention may be embodied as a system such as a server or computing device that includes a memory and a processor for executing instructions for implementing the exemplary embodiments.

FIG. 1A depicts a featured conventional surface 110 with a portion 120 of the surface 110 marked for extrusion. FIG. 1B depicts the surface 110 of FIG. 1A after the portion 120 has been extruded. FIG. 1C depicts the surface 110 of FIG. 1A after the portion 120 has been extruded in the opposite direction to FIG. 1B. FIG. 2 depicts an exemplary feature-based model design environment. FIG. 3 depicts an example interface showing a template 350 for results achieved by the example extrusion tool 300. FIG. 4 depicts exemplary options 402 within the interface 400. FIG. 5 illustrates how options 510, 520 can be rearranged within the exemplary interface. FIG. 6 depicts options 610 that are carried over from the first interface to the second interface. FIG. 7 illustrates the persistence of exemplary option values 720 within the interface 710. FIG. 8 depicts an example interface 800 employing a diagnostic tool, according to an example embodiment. FIG. 9 is a flow diagram depicting an exemplary method for manipulating features, according to an exemplary embodiment described herein. FIG. 10 is a flow diagram depicting an exemplary method for associating an interface with a user and / or feature and invoking the interface when the user creates a new user session or is accessed by a user whose feature is different. FIG. 11 depicts an example dynamically generated help tool 1110 in response to a situation. FIG. 12 is a flow diagram depicting an exemplary method for displaying a dynamically generated context-sensitive help tool, according to an exemplary embodiment described herein. FIG. 13 depicts an exemplary computing device 800 suitable for use with the exemplary embodiments described herein. FIG. 14 depicts an exemplary network implementation suitable for use with the exemplary embodiments described herein.

(Detailed explanation)
The exemplary embodiments provide a result bias approach for interacting with features in a feature-based modeling environment. In a feature-based modeling environment, a user typically interacts with a feature-based model by manipulating the model's features using tools that can achieve several different results for the feature. Rather than providing a generalized tool for achieving results, an interface may be displayed that allows operations to be performed based on the results to be achieved. Thus, the number of options presented on the interface can be reduced by eliminating irrelevant options that are associated with the tool but are not directly applicable to the desired result. A dynamic help system may be provided that provides targeted and dynamically generated information related to the results to be achieved. In addition, feature validity alerts may be displayed in the interface in real time during the model feature creation process.

  These embodiments provide several advantages over traditional feature-based modeling environments. For example, irrelevant tool options are typically excluded from view because the user manipulates features based on the results that the user desires to obtain rather than based on tools that can achieve multiple different results. Or can be hidden. This saves the footprint of the display for the actual target-to-model for the modeling environment. In addition, the time that the user spends looking for tool options in the environment's tool menu may also be reduced. Because the interface associated with tools and tool choices can be focused by the choice of interest for user results, the interface is displayed in close proximity to the tool and other parts of the modeling environment (ribbons or The user's focus can be maintained on the model and / or feature without having to move the pointer to a file menu or the like. Thus, the modeling process is made cleaner and more efficient because the exemplary embodiments described herein can reduce visual scanning, marginal distractions, and mouse movement. Thus, the user's visual and intelligent focus can be maintained on the targets and tasks in front of the eyes.

  In addition, since the modeling environment is focused on results, not tools, the modeling environment can be streamlined so that help can be provided in response to dynamic situations and real-time alerts and errors can be generated . The modeling environment is also made more customizable because of the result-oriented template. For example, a user or administrator may create a template to be adapted to the user's job type or corporate style criteria, which may help improve user efficiency.

  An exemplary feature-based modeling environment 200 is depicted in FIG. In the feature-based modeling environment 200, the user may construct the model 210 by defining the model geometry. The geometry that makes up the model consists of a set of “surfaces”, such as surfaces 220, that can be bounded by “edges”, such as edges 230.

  As used herein, a “surface” is a surface defined by a particular geometric shape in a model that is bounded by one or more edges. A feature may have one or more surfaces or a set of surfaces. The surface may be flat, curved, or angular. For example, a cube has six flat surfaces. The cylindrical shape has flat circular top and bottom surfaces and a single curved side surface. The conical shape has a flat circular bottom surface and a round, tapered angular side surface with the tip at the top of the conical shape.

  As used herein, an “edge” represents the outer boundary of a surface. For example, the front surface of a cube has four edges that are equal in size and are oriented perpendicular to each other.

  As used herein, a “vertex” is a point where two or more edges meet. In a cube, vertices are located at each corner and three edges meet.

  A geometric shape may represent a “feature” of a model, such as a feature 240, ie, a component 240 that may take various shapes or sizes. A connected set of surfaces, edges, and vertices may define features in the model that can be considered as independent atomic components from which feature-based models can be built.

  Feature-based modeling environments generally provide “tools” for manipulating feature geometries. A “tool” is a utility in the environment that manipulates the feature geometry in a well-defined manner. An example of a tool is an “extrusion” tool 250 that moves a surface or part of a surface in a two-dimensional or three-dimensional space. Another tool is a “stretch” tool that moves selected edges and vertices in a defined direction to enlarge or reduce the entire surface or feature.

  The tool can provide specific “results”. The result describes what happens to the feature when the tool is applied to the feature in a particular way.

  For example, an extrusion tool has the general function of extruding or extruding a surface or part of a surface and moving the surface or part of a surface, thereby reshaping features that are part of that surface. However, different results can be achieved depending on how the surface is manipulated by the extrusion tool. According to an exemplary embodiment of the present invention, a user is presented with and interacts with a result bias tool option to manipulate features. FIG. 3 depicts an example of the results achieved using the extrusion tool 300.

  For example, a protrusion can be created by extruding a feature from a feature whose surface is a part. If the protrusion is filled (eg, the space between the original location on the surface and the new location on the surface is filled with a material such as the material that makes up the original surface), the “solid protrusion” 310 is The result is the use of an extrusion tool. On the other hand, the space between the original location of the surface and the new location of the surface is such that the projection is hollow (i.e. only the new surface defined by the projection is created without anything between them). If it is empty, a “surface protrusion” 320 results in using the extrusion tool. Still further, if the surface is pushed into a feature that is part of it, a dimple or “cut” 330 can be created. A “tapered” surface 340 can be created if the surface is increased or decreased in size relative to other surfaces such that the side surfaces are angled.

  In other words, the tool describes a method (eg, “moving the surface of the feature”) for interacting with the feature. The result describes how the feature is changed as a result of using that tool (eg, “Create a solid fill protrusion on the feature and the boundary of the protrusion is defined by the movement of the surface”) .

  In one embodiment, the tool may be configurable by changing various configurable settings. The particular combination of values for the configurable setting can define the result achieved by the tool. The combination of values that define the result can be used to build an interface when the user indicates the desire to achieve the result associated with the template by selecting the result in the model environment. It may be stored as a “template”.

  For example, the extrusion tool may have configurable options that describe the direction of movement of the surface (e.g., a positive value indicates that the surface is moved away from the feature, creating a protrusion, and a negative value Indicates that the surface is moved into the feature and creates a cut). Another configurable option may provide an option for selecting whether the protrusion created by the extrusion tool should be hollow or filled.

  The user need not provide values for possible configuration options for every possibility for the tool. As mentioned above, some configuration options may be irrelevant to a particular result. One example would be an option to define whether the protrusion is solid or hollow due to the “cut” result of the extrusion tool.

  In some cases, a particular configuration option may be related to the result, but the user may desire to leave the option blank so that the option can be configured in the future. For example, an extrusion tool can be associated with a “depth” configuration option that defines how much the surface should be moved into or out of the feature. Such options are likely to depend on the particular feature or model that the user is working on at the time, and thus may be defined when a desired result is selected. In some embodiments, the user can specify default values to be used for configuration options, which can be changed later when results are selected.

  As shown in FIG. 3, each defined result may be stored as a template 350. Template 350 describes specific results achieved by the Yule from possible results, and each tool may be associated with multiple templates 350.

  Templates 350 may be prioritized based on the user's previous history. For example, if the user frequently uses the solid template 310 (eg, the user uses the solid template at least a predetermined number of times, or at a predetermined rate or ratio compared to other templates), The solid template 310 may be stored as a favorite template 360. Alternatively, the user may manually designate a particular template 350 as one of its favorite templates 360. The favorite template 360 may be preferentially displayed in a list of results with which the user may interact.

  The template 350 may also be user-definable so that the user can create a template 350 that describes a particular result to be achieved by the tool. For this purpose, the tool may be configurable using a tool configuration, and the user may specify in the template 350 which tool configuration should be used to achieve the result. Good. The user may be presented with a wizard or interface to set a default tool configuration corresponding to a particular desired result.

  Depending on the selection of template 350, the user may be presented with an interface, such as the exemplary interfaces 400, 410 shown in FIG. For example, the interface 410 includes two configuration options 402 and a slider 404. By default, the interface 400 may display only configuration options that are relevant to a particular result. Other options may be accessed by dragging slider 404 to increase the size of interface 400 and represent additional options 402. Moving the slider 404 in the opposite direction (decreasing the size of the interface 400) may cause fewer options 402 to be displayed. Configuration options associated with a particular result may be determined programmatically (eg, options for defining solid / hollow settings may be preprogrammed to be irrelevant to break results) Or may be defined by the user when the template is created (or later by modifying the template).

  For example, configuration options may be associated with attributes such as “required / optional” attributes. Setting such an attribute to “required” means that the options associated with the attribute must be shown in the interface 410 and cannot be hidden (eg, by moving the slider 404). You can show that. In another example, the option may be associated with a “show / hide” attribute. Setting the attribute to “display” may indicate that the choice associated with the attribute is displayed by default, but may be hidden by moving the slider 404. Alternatively, setting an attribute to “hidden” may indicate that the choice associated with the attribute is not displayed by default, but may be displayed by moving the slider 404.

  In some embodiments, the options may be ranked with respect to each other to control the order in which the options appear in interface 400. For example, each option may be associated with an absolute ranking that defines its order within interface 400. Alternatively, as shown in FIG. 5, the relative ordering of options may be defined. For example, in FIG. 5, the user drags the “blocked end” option 510 to the position of the “blocked end” option 510 below the “tapered” option 520.

  In addition, the options defined in one template may be further reused in other related templates. For example, FIG. 6 uses two related tools: a “hole” tool that creates a hole in a feature around a central axis and an “axis” tool for defining that axis to achieve the results. Interfaces 600 and 602 are shown. As shown in FIG. 6, if an “offset” option 610 that defines the center of the hole / axis is defined within a template, the offset option 610 can be carried over through both interfaces 600, 602.

  In other embodiments, as shown in FIG. 7, the selected option may be made to persist even when the user selects a different result or tool to apply. For example, as shown in FIG. 7, the user has selected a result based on an extrusion tool. Thus, the interface 710 is displayed and the user has typed a value of “244.84” into the depth option 720. At this point, if the user selects a new tool (such as sweep tool 730) without applying the configured results to the feature, a new interface will be displayed, allowing the user to configure the sweep options. May be. However, the choices made at the interface 710, including the values defined for the depth choice 720, may be temporarily stored so that the user can later return to the interface 710. Thus, if the user decides to pursue a different result prior to completion of the originally assumed operation of the feature, the user need not re-enter each value.

  When a user specifies one or more values for an option in the interface, the diagnostic tool uses that value to determine whether an error results from the correction or a feature or suggested correction May be evaluated. The diagnostic tool may operate in real time or near real time during the model design process before the proposed operation is performed. For example, FIG. 8 shows such a diagnostic tool in operation.

  In interface 800, the user has defined values for “section” option 810 and “depth” option 830. No value is defined for the “axis” option 820 (or alternatively, a null value is defined for the “axis” option 820).

  The diagnostic tool may attempt to evaluate features with respect to prescriptive and non-prescriptive options. The diagnostic tool may determine whether any errors arise from, or may arise from, the correction that results from applying the option. The diagnostic tool may perform an evaluation as the value for the option is typed or after the value has been typed, and the user provides some indication that the value is complete ("line break" or " By pressing the "tab" key etc.). Alternatively, the diagnostic tool may wait until the user defines a value for each option in the interface 800 or until a value is defined for the last option in the interface 800. Further, the diagnostic tool may be manually invoked by the user, for example by pressing a designated key (eg, “F5” key), at which point the diagnostic tool is defined within the interface 800. Any optional value that would have been evaluated would be evaluated.

  For example, in an attempt to implement the proposed modification, the diagnostic tool may determine that the “Sketch 2” value defined for section option 810 is a valid value. Thus, a positive indicator 812 is displayed next to the section option 810.

  However, when attempting to evaluate whether the feature can be pivoted about a defined axis, the diagnostic tool may notice that the axis is not defined in the axis option 810. If the axis is a required field, the diagnostic tool may place a warning signal 822 next to the axis option 820. In addition, an explanation window 824 may be displayed and provide details regarding the warning signal 822. The description window may provide a recheck option 826 and allow the user to re-evaluate the feature as new values are typed for the axis option 820.

  The diagnostic tool may identify that a value (ie, “0.00”) exists for the depth option 820. Therefore, no warning is presented. However, when a diagnostic tool attempts to perform a rotation at a depth of 0.00, it may recognize that the rotation will fail because the value is outside the effective depth range. Thus, an error indicator 832 may be presented proximate to the depth option 830. The diagnostic tool is discussed in more detail with respect to FIG.

  The foregoing embodiments may operate within a feature-based modeling environment as shown in the flow diagram depicted in FIG.

  In step 910, the computing device may interact with a feature-based modeling environment. A feature-based modeling environment may include a model having at least one feature described by a geometric shape.

  In step 920, the feature-based modeling environment may display one or more results that may be used to manipulate the features of the model. For example, a feature-based modeling environment may support at least one tool that defines manipulation of feature geometries. An operation may be applied to achieve a plurality of different results, each individual result affecting a feature in a different way.

  The result may be, for example, a collection of options with or without attributes defined for the options, the options being associated with the tool. In one embodiment, a result may be defined by a template that flags one or more options as associated with the result and one or more options as unrelated to the result. The options may be pre-programmed into the modeling environment, may be customizable templates defined and / or modified by the user or users, or may be past interactions with one or more user tools. It may be determined by a program based on the history. For example, if a user uses a tool to achieve a result by specifying tool options above a predetermined threshold number of times, the template is defined programmatically for future use by the user, The result may be stored.

  In some embodiments, at least two of the plurality of different results may be displayed on the interface of the feature-based modeling environment. The at least two results may be a subset of a plurality of different results made available by the tool. The subset may be selected based on previous history of result selection. For example, the subset may be selected based on previous user selections of results and / or options associated with the results.

  In step 930, the feature-based modeling environment may receive a selection of results. For example, the user may select a desired result from a menu or ribbon within the modeling environment.

  In step 940, the feature-based modeling environment may display one or more options for the results in the options interface. In some embodiments, the options interface may be displayed in response to a selection of results to be achieved by the tool. The interface may be populated with options related to the result. The choices entered into the interface may be user selected or may be selected programmatically based on, for example, previous user interactions.

  In some embodiments, the options interface may be displayed in response to receiving a selection of results to be achieved by the tool. The interface may be populated with options associated with the tools that are applicable to the selected result.

  The choices that are entered into the interface may be all subsets of choices that are associated with or available for use with the tool. Furthermore, one or more options associated with the tool but not in the subset may not be presented in the interface. The subset may be a user-defined subset or may be defined programmatically.

  In some embodiments, the subset may be dynamically generated when the user selects a result to be achieved by the tool. For example, when the user selects a tool, the model environment may examine a list of “commonly used results” that are frequently achieved with the tool. For this purpose, the modeling environment may record the options used for use with the tool and identify the frequency with which the options are selected. The model environment may then provide a list of results corresponding to frequently used configurations of the tool (eg, used configurations that exceed a predetermined number of times or a predetermined rate).

  In some embodiments, when a feature is displayed on a display device, the interface may be displayed on the display device at a location that is defined based on the location of the feature on the display device. For example, the options interface may be displayed at a predetermined location that is calculated within a predetermined distance of the feature or based on the location of the feature on the display device. Thus, an interface may be provided in close proximity to features associated with or manipulated by the interface. Thus, the user does not need to search through the menu or take the attention away from the feature in order to manipulate the feature.

  In step 950, the feature-based modeling environment may receive an attribute value for one of the options displayed in step 940. For example, the options interface may provide a check box, text box, or other input mechanism for receiving attribute values for options. The input mechanism may be pre-filled with default values determined by the template for the results.

  In step 960, the feature-based modeling environment may evaluate the features using the attribute values received in step 950 using a diagnostic tool. The diagnostic tool may operate in real time or near real time to determine the effectiveness of input to model choices. Thus, in response to receiving an attribute value for an option, the diagnostic tool may evaluate a proposed modification of the feature that can be achieved using the feature or the result with the defined option. Evaluation may occur during the model design process prior to performing the correction using the defined values.

  For example, the evaluation may occur as the user types attribute values into the input mechanism. Alternatively, after the user completes typing the attribute value for the option, the user may signal that the input is complete, for example, by pressing a “carriage return” or “tab” key. In another embodiment, the diagnostic tool may wait until a predetermined number of values are defined for different options. Further, the diagnostic tool may wait until values are provided for all options that are visible in the interface. In another embodiment, the diagnostic tool may wait until a value is provided for the last option listed in the interface. In either case, instead of supplying a value, the user may simply skip the option without supplying a value (eg, press the “Tab” key while in the input mechanism for the option). And move to the next option without specifying a value).

  Further, the diagnostic tool need not be automatically invoked upon receipt of a value for a choice (including a null value). For example, a button or other mechanism may be provided to allow the user to manually invoke the diagnostic tool when the user is ready to evaluate the options provided. The user may specify that only certain options are evaluated, for example, using a series of check boxes or by selecting a different option for diagnosis.

  In step 970, the diagnostic tool may determine whether the attribute value received in step 960 is present, valid, and / or acceptable (ie, “OK”). The evaluation may involve comparing a known range of acceptable values for the input attribute value and the choice. The evaluation may also check to ensure that the value is defined for the option and that the value is of the appropriate type.

  Features may be evaluated for different error conditions. For example, in one embodiment, the warning may relate to violations of geometry rules, such as when the user attempts to define a surface that is not bounded by edges. Furthermore, violations of geometric shape rules may involve the user specifying a value that is outside an acceptable range for manipulation of the geometric shape defined by the feature. In another embodiment, the warning may indicate a missing or null value.

  In yet another embodiment, the warning may relate to a violation of design intent. The user's design intent may be determined by the modeling environment based on the results that the user indicates that the user is trying to achieve. For example, if the user indicates that the user is trying to create a solid protrusion using an extrusion tool, but the user defines a value that moves the surface into the feature (thus creating a dimple or cut) The modeling environment may determine that the user's design intent is violated. The modeling environment may determine that a specified value (eg, a negative value relative to the depth of the surface) is otherwise valid for the extrusion tool, but the design intent is violated. . In other words, the user's design intent is defined by the results that the user desires to achieve, and the modeling environment compares the attribute values specified for the options in the options interface and the specified values are the specified results. It may be determined whether it is consistent with. If the two are not consistent, the modeling environment determines that the design intent is violated.

  If in step 970 it is determined that the attribute value does not exist, is not valid, and / or is not acceptable (ie, “OK”), then in step 980 the diagnostic tool displays a warning message or failure indication. It may be displayed. In some embodiments, if an interface that includes options is displayed on the display, the alert may be displayed at a location that is determined based on the location of the options within the interface. For example, if an option exists at a location, an alert may be displayed next to the option, within a predetermined distance, and / or in a predetermined direction away from the option. In this way, alerts may be displayed in close proximity to options to help the user identify the alert source.

  If it is determined at step 970 that the attribute value is present, valid, and / or acceptable (ie, “OK”), the process proceeds to step 990 and the selected result. An operation defined by may be performed.

  Processing may then return to step 950 where additional attribute values may be provided and subsequently evaluated. Alternatively, if additional attribute values remain to be supplied, processing may return to step 930 and the user may select a new result to be supplied to the model.

  In another embodiment, the aforementioned interfaces (eg, results interface and options interface) may be associated with users, users, or features so that the interface is displayed consistently. Thus, the identity of the user or group of users interacting with the interface may be determined, and when the user or group of users subsequently reenters the modeling environment, the interface associated with the user or group of users is read out. And may be displayed.

  Further, the interface may be associated with features defined using the interface. For example, features originally manipulated by a user or group of users using an interface may be identified. An interface may be associated with a feature, for example by storing the identification of the interface with the feature (or vice versa). Instructions for interacting with the features associated with the interface may be received from a second user or a second group of users that may be different from the original user or group of users who manipulated the features using the interface. . As a result of the instructions for interacting with the feature, the interface originally used to manipulate the feature may be displayed to a second user or a second group of users.

  In this way, a consistent interface may be associated with a particular feature on a user base, allowing subsequent users to manipulate the feature in the same way that the feature was originally created.

  For example, FIG. 10 is a flow diagram depicting an exemplary method for associating an interface with a user and / or feature and invoking the interface when the user creates a new user session or when the feature is accessed by a different user. is there.

  In step 1010, the modeling environment may identify a user or group of users accessing the modeling environment. For example, a user or group of users may log in to the modeling environment and create a user session. The modeling environment may require evidence of identification, such as a password submitted by the user.

  In step 1020, the modeling environment may associate the user or user group with an interface (eg, the options interface and / or results interface described above) that is being used by the user or user group to manipulate features. In step 1030, the interface may also be associated with the manipulated feature.

  The association may be a logical association. For example, the interface may be identified by an identifier such as an identification number. Users, groups of users, and / or features may be associated with an identifier as well. The interface identifier may be stored with the user, user group, and / or feature identifiers in a data structure such as a table, array, or linked list.

  In step 1040, the model environment may detect the end of the user session. For example, a user or group of users may indicate that they have logged out of the model environment, closed the model environment, or have stopped working on a model in the model environment (eg, closed a file associated with the model, or By remembering it).

  In step 1050, the model environment may detect a new user session. A new user session may be initiated in step 1010, similar to the user session described above.

  In step 1060, the model environment may determine whether the user or user group associated with the new user session is the same as the user or user group identified in step 1010. In one embodiment, the model environment may check the aforementioned data structure to determine whether any interface is associated with the currently logged-in user and / or any model that the user is currently operating on. .

  If the user or group of users is not determined to be the same in step 1060, the model environment determines in step 1070 whether the user or group of users is attempting to operate on the same feature associated with the interface in step 1030. May be. This is because even if the users are different, it may still be desirable to display a consistent interface when the same model is being operated by different users. Thus, even if the user would not otherwise have the authority to use the interface stored in the data structure (eg because the user did not create the interface or the user was associated with them) The user may temporarily have the authority to use the interface to manipulate features associated with the interface. In some embodiments, the option allows the functionality to allow the user to always see the interface used to create the object, or to always see its own user-based interface. Options for prohibiting may be provided.

  If the user or user group is different and the user or user group has not attempted to modify a previously defined feature, at step 1072, the model environment is different from the interface associated with the user / user group at step 1020. An interface may be displayed. For example, the model environment may generate a new interface or retrieve the interface associated with the specific user or group of users that initiated the new user session at step 1050.

  On the other hand, if the user identified in step 1060 matches the user identified in step 1010, or if the user is attempting to manipulate the same feature associated with the interface in step 1030, then in step 1080, A request to redefine the features may be received. In this situation, the interface associated with the user and / or feature may be retrieved and displayed at step 1090. The displayed interface may be used by the user to manipulate the features.

  As previously mentioned, the interface associated with the exemplary embodiment of the present invention allows unrelated options to be removed from consideration, thereby streamlining the model design process. Similarly, because the results that the user is trying to achieve are known, context-sensitive help tools may also be provided. For example, FIG. 11 depicts an example dynamically generated help tool 1110 in response to a situation.

  The help tool 1100 may be entered from one of the options 1102 in the options interface and / or through the results interface. Help tools are created on a case-by-case basis by using “entry points”. For example, when a user requests use of the help tool 1100, the model environment remembers where the help tool 1100 was requested and / or the results or choices the user was interacting with when the help tool 100 was requested. Keep it.

  Based on the entry points for the help tool, the model environment may be able to determine the result that the user was attempting to achieve, and more than one or more already defined in the attempt for the user to achieve the result. The options may be identifiable. The help tool 1100 may be provided with this information, which may be used to determine the results the user is trying to achieve and / or the user's current specifications (or, for example, options from a diagnostic tool If it is determined that a problem exists with respect to one of the above, a help page 1110 associated with the option (as already defined) may be dynamically generated.

  The help tool 1100 of FIG. 11 may be displayed according to a method as depicted in the flowchart of FIG.

  In step 1210, the model environment may interact with the model. In step 1220, the modeling environment may display one or more results that may be applied to the features in the model to modify the features. Steps 1210 and 1220 generally correspond to steps 910 and 920 of FIG. For brevity, details of steps 1210 and 1220 are not repeated here.

  In step 1230, the modeling environment may receive a help request while displaying the potential results. The model environment may flag specific results that were interacting as “entry points” to the help system, and processing may proceed to step 1260.

  The entry point may be an explicit entry point such as a “?” Button provided in the vicinity of one of the results. Alternatively, the entry point may be implicit. For example, a user interacting with a result (eg, by hovering over one of the results) may press the “F1” key, and the result being interacted with when help is requested. May be recognized as entry points. In these and other similar methods, a request to enter the help system from an entry point may be received.

  Alternatively, if no help request is received while the results are displayed at step 1220, the model environment receives a selection of the desired results at step 1240 and relates to the results selected in the interface at step 1250. Options may be displayed. Steps 1240 and 1250 generally correspond to steps 930 and 940 of FIG. 9, respectively. For brevity, details of steps 1240 and 1250 are not repeated here.

  It should be understood that an explicit help request need not be generated to enter the help system. For example, a help page may be generated in response to user actions such as selection or activation of a particular tool.

  While the user is interacting with one of the options displayed at step 1250, a help request may be received. In this case, the model environment may flag specific options that the user has interacted with the entry point to the help system, and processing may proceed to step 1260.

  In step 1260, the model environment identifies the entry points flagged in either step 1230 or step 1250. The model environment may then dynamically generate a help page whose content depends on the entry point.

  In response to receiving a request to enter the help system from an entry point, the help page may be dynamically generated with content selected based on the entry point. For example, if the entry point is an interface, the help page may include specific information related to the interface only. If the entry point is an option in the interface, the help page may be dedicated to the option. The option may be the option that the user is currently interacting with (such as by typing an attribute value into the option field), and the content is the option that the user is currently interacting with when the request to enter the help system May be generated dynamically when received based on

  Help information may be provided to generate content for the help page. The content selected for display to the user may be a subset of the help information in the help system and may be selected dynamically based on entry points. For example, the help system may include information about tools that can achieve several different results. If it is determined that the entry point is a result applicable to the tool, only a subset of the help system that directly addresses the result may be displayed.

  The help information may include individual sections that are marked as associated with a particular entry point. For example, help sections may be marked with keywords. When a help request is received by the help system, the help system may retrieve help information for keywords associated with the entry point and return help content to the user. The keyword associated with the entry point may be based on the name of the entry point (eg, the name of a tool or option that the user enters the help system) or other words (eg, synonyms, pre- Or related words programmed in the A user may manually flag a particular piece of help information as associated with a particular template, which may be stored with the template's identifier, among other possibilities, or The keyword may be associated with the template by assigning a keyword for identifying the template in the help information.

  The content may further be dynamically generated based on one or more user selections or user-supplied attribute values associated with the options with which the user is currently interacting. For example, if the user specifies the results to be achieved and has already provided one or more attribute values for the choice, the help system may allow some portion of the help information to relate to the user's goals. Or you may determine that it is unrelated. For example, if the help system determines that an attribute value provided for an option in a particular result will violate the user's design intent, the help system may also provide help content related to the design intent. Good.

  The help system may interface with the diagnostic tool to determine whether an assigned value causes an error or warning. For example, if the help system determines that the diagnostic tool will generate an error because some value supplied to the option is outside the acceptable range of the option, the help system provides information about the acceptable range. May be.

  In this way, targeted help content may be dynamically generated such that it is most applicable to the user's area of interest or the results the user is trying to achieve.

  One or more of the foregoing acts may be embodied as computer-executable instructions that can be executed by processing logic. Computer-executable instructions may be stored on one or more non-transitory computer-readable media. One or more of the foregoing actions may be performed within a suitably programmed electronic device. FIG. 13 depicts an example of an electronic device 1300 that may be suitable for use with one or more of the actions disclosed herein.

  Electronic devices 1300 include, but are not limited to, computers, workstations, servers, network computers, quantum computers, optical computers, internet appliances, mobile devices, pagers, tablet computers, smart sensors, application specific processing devices, etc. Many forms may be taken.

  Electronic device 1300 is illustrative and may take other forms. For example, alternative implementations of electronic device 1300 may have fewer components, more components, or differently configured components than the configuration of FIG. The components of FIG. 13 and / or other diagrams described herein are logic (eg, hybrid) that is hardware-based logic, software-based logic, and / or a combination of hardware and software-based logic. Logic). Accordingly, the components illustrated in FIG. 6 and / or other figures are not limited to a specific type of logic.

The processor 1302 may include hardware-based logic or a combination of hardware-based logic and software and execute instructions instead of the electronic device 1300. The processor 1302 may include logic that may interpret, execute, and / or otherwise process information contained in the memory 1304, for example. The information may include computer-executable instructions and / or data that may implement one or more embodiments of the invention. The processor 1302 may comprise a variety of similar or dissimilar hardware. The hardware may be, for example, one or more processors, a microprocessor, a field programmable gate array (FPGAS), an application specific instruction set processor (ASIP), an application specific integrated circuit (ASIC), a complex programmable logic device (CPLD), It may include a graphics processing unit (GPU) or some combination of other types of processing logic that may interpret, execute, manipulate, and / or otherwise process information. The processor may include a single core or multiple cores 1303. Further, the processor 1302 may include a system on chip (SoC) or a system in package (SiP). An example of the processor 1302 is the Intel® Core ^™ processor series available from Intel Corporation (Santa Clara, California).

  The electronic device 1300 includes one or more tangible, non-transitory computer readable storage media for storing one or more computer-executable instructions or software that may implement one or more embodiments of the invention. But you can. The non-transitory computer readable storage medium may be memory 1304 or storage 1318, for example. Memory 1304 may comprise RAM, which may include a RAM device that can store information. A RAM device may be volatile or non-volatile, for example, one or more DRAM devices, flash memory devices, SRAM devices, zero capacitor RAM (ZRAM) devices, twin transistor RAM (TTRAM) devices, read only memory. (ROM) devices, ferroelectric RAM (FeRAM) devices, magnetoresistive RAM (MRAM) devices, phase change memory RAM (PRAM) devices, or other types of RAM devices.

  One or more computing devices 1300 may include a virtual machine (VM) 1305 for executing instructions loaded into memory 1304. A virtual machine 1305 may be provided to handle processes that are launched on multiple processors so that the process may appear using only one computing resource rather than multiple computing resources. Virtualization may be employed within the electronic device 1300 so that infrastructure and resources within the electronic device may be dynamically shared. Multiple VMs 1305 may reside on a single computing device 1300.

  A hardware accelerator 1306 may be implemented in an ASIC, FPGA, or some other device. Hardware accelerator 1306 may be used to reduce the general processing time of electronic device 1300.

  The electronic device 1300 includes, but is not limited to, standard telephone lines, LAN or WAN links (eg, T1, T3, 56 kb, X.25), broadband connections (eg, integrated services digital network (ISDN), frame relay, asynchronous transfer) Through various connections, including mode (ATM), wireless connection (eg, 802.11), high speed interconnection (eg, InfiniBand, gigabit Ethernet®, Myrine), or some combination of some or all of the foregoing , A local area network (LAN), a wide area network (WAN), or a network interface 1308 for interfacing with the Internet. Work adapters, network interface cards, personal computer memory card international association (PCMCIA) network cards, card bus network adapters, wireless network adapters, universal serial bus (USB) network adapters, modems, or electronic devices 1300 communicate and are described herein. Any other device suitable for interfacing with any type of network capable of performing the operations described may be included.

  The electronic device 1300 can be used, for example, to receive input from a user, keyboard, multipoint touch interface, pointing device (eg, mouse), gyroscope, accelerometer, haptic device, haptic device, neural device, One or more input devices 1310 such as a microphone or camera may be included. Note that electronic device 1300 may include other suitable I / O peripherals.

  Input device 1310 may allow a user to provide input that is registered on visual display device 1314. A graphical user interface (GUI) 1316 may be shown on the display device 1314.

  A storage device 1318 may also be associated with the computer 1300. Storage device 1318 may be accessible to processor 1302 via an I / O bus. Information may be executed, interpreted, manipulated, and / or otherwise processed by processor 1302. Storage device 1318 may include a storage device such as, for example, a magnetic disk, an optical disk (eg, CD-ROM, DVD player), a random-access memory (RAM) disk, a tape unit, and / or a flash drive. The information may be stored on one or more non-transitory tangible computer readable media contained within the storage device. The medium can be, for example, a magnetic disk, optical disk, magnetic tape, and / or memory device (eg, flash memory device, static RAM (SRAM) device, dynamic RAM (DRAM) device, or other memory device)). May be included. Information may include data and / or computer-executable instructions that may implement one or more embodiments of the invention.

  Storage device 1318 may store any modules, outputs, displays, files, information, user interfaces, etc. provided in the exemplary embodiment. Storage device 1318 may store an application for use by computing device 1300 or another electronic device. An application may include programs, modules, or software components that enable computing device 1300 to perform tasks. Examples of applications include word processing software, shells, internet browsers, productivity suites, and programming software. In one embodiment, computing device 1300 may include a feature-based modeling environment 1320 for building a model. Modeling environment 1320 may be, for example, a software component or a computer program. The modeling environment 1320 may be a CAD environment. The modeling environment 1320 may include means for building, editing, saving, and loading the model 1321, simulating the performance of the model 1321, and providing the model 1321 as an input to a high speed prototype or manufacturing unit. The modeling environment 1320 may further include a geometry kernel 1322 that calculates and represents the geometry of the features in the model.

  Further, the model environment 1320 may include or be associated with a help system 1330, a diagnostic tool 1340, a results template 1350, and / or one or more tools 1360. Each of these features of the model environment 1320 are discussed in detail above.

  Storage device 1318 may also store an operating system 1326 for operating computing device 1300. Storage device 1318 may store additional applications to provide additional functionality as well as data 1327 for use by computing device 800 or another device. Data 1327 may include files, variables, parameters, images, text, and other forms of data. Storage device 1318 may also store library 1324, such as a library for storing model 1321 used by modeling environment 1320. Library 1324 may be used, for example, to store default or custom models or model components.

  Storage device 1318 may further store an operating system (OS) 1326 for activating computing device 1300. Examples of OS 826 include: Microsoft® Windows® operating system, Unix® and Linux® operating system, MacOS® for Macintosh computers, embedded operating systems, such as , A Symbian OS, a real-time operating system, an open source operating system, a dedicated operating system, an operating system for a mobile electronic device, or other capable of booting on the electronic device and performing the operations described herein An operating system may be mentioned. The operating system may boot in native mode or emulation mode.

  One or more embodiments of the invention may be implemented using computer-executable instructions and / or data that may be embodied on one or more non-transitory tangible computer-readable media. The medium includes, but is not limited to, a hard disk, a compact disk, a digital general purpose disk, a flash memory card, a programmable read only memory (PROM), a random access memory (RAM), a read only memory (ROM), and a magnetoresistive random access memory (MRAM). ), Magnetic tape, or other computer readable medium.

  One or more embodiments of the invention may be implemented in a programming language. Some examples of languages that can be used include: Python, C, C ++, C #, SystemC, Java, Javascript, Hardware Description Language (HDL), Unified Modeling Language (UML), and Programmable Logic Controller (PLC) languages are included, but not limited to them. Furthermore, one or more embodiments of the invention may be implemented in a hardware description language or other language that may allow computations to be defined. One or more embodiments of the invention may be stored on or in one or more media as object code. Instructions that may implement one or more embodiments of the invention may be executed by one or more processors. Part of the invention may be in instructions that execute on one or more hardware components other than a processor.

  It should be understood that the present invention may be implemented in a distributed or network environment. For example, the model may be provided and manipulated on a central server while the user interacts with the model through the user terminal.

  FIG. 14 depicts a network implementation that may implement one or more embodiments of the present invention. System 1400 may include computing device 1300, network 1412, service provider 1413, target environment 1414, and cluster 1415. The embodiment of FIG. 14 is exemplary, and other embodiments can include more devices, fewer devices, or devices in a different arrangement than in the arrangement of FIG.

  The network 1412 may transfer data from the source to the destination. Embodiments of network 1412 may transfer data using network devices and connections (eg, links) such as routers, switches, firewalls, and / or servers (not shown). The data has substantially any format that can be adapted for use in one or more networks and / or with one or more devices (eg, computing device 1300, service provider 1413, etc.). It may refer to any type of machine readable information. The data may include digital information or analog information. The data may further be packetized and / or non-packetized.

  Network 1412 may be a wired network that uses wired conductors and / or optical fibers, and / or may be a wireless network that uses free space light, radio frequency (RF), and / or acoustic transmission paths. Good. In one implementation, the network 1412 may be a substantially open public network such as the Internet. In another implementation, the network 1412 may be a more restricted network such as a corporate virtual network. Network 1412 may include the Internet, an intranet, a local area network (LAN), a wide area network (WAN), a city-wide network (MAN), a wireless network (eg, using IEEE 802.11), or other types of networks. Good. The network 1412 may use middleware such as Common Object Request Broker Architecture (CORBA) or Distributed Component Object Model (DCOM). Network and / or device implementations operating on the networks described herein are not limited to any particular data type, protocol, and / or architecture / configuration, for example.

  Service provider 1413 may include a device that makes the service available to another device. For example, service provider 1413 may include entities (eg, individuals, businesses, educational facilities, government agencies, etc.) that provide one or more services to destinations using servers and / or other devices. A service may include instructions executed by a destination to perform an operation (eg, an optimization operation). Alternatively, the service may include instructions that are executed on behalf of the destination to perform actions on behalf of the destination.

  Target environment 1414 may include devices that receive information via network 1412. For example, target environment 1414 may be a device that receives user input from computer 1300.

  Cluster 1415 may include a number of execution units (UEs) 1416 and may perform processing on behalf of another device, such as computer 800 and / or service provider 1413. For example, the cluster 1415 may perform parallel processing on operations received from the computer 1300. Cluster 1415 may include UEs 1416 that reside on a single device or chip, or that reside on several devices or chips.

  An execution unit (UE) 1416 may include a processing device that performs operations on behalf of a device, such as a requesting device. The UE may be a microprocessor, a field programmable gate array (FPGA), and / or another type of processing device. UE 1416 may include code, such as code for an operating environment. For example, the UE may launch a portion of the operating environment for parallel processing activity. Service provider 1413 may operate cluster 1415 and may provide bi-directional optimization capabilities to computer 1300 on a subscription basis (eg, via a web service).

  An execution unit (UE) may provide remote / distributed processing capabilities for products such as the modeling environment 1320 of FIG. A hardware execution unit may include devices (eg, hardware resources) that may perform and / or participate in parallel programming activities. For example, a hardware execution unit may perform and / or participate in parallel programming activities in response to received requests (eg, received directly or via a proxy) and / or tasks. A hardware execution unit may use and / or participate in substantially any type of parallel programming (eg, tasks, data, stream processing, etc.) using one or more devices. For example, a hardware execution unit may include a single processing device that includes multiple cores or several processors. The hardware execution unit may also be a programmable device such as a field programmable gate array (FPGA), application specific integrated circuit (ASIC), digital signal processor (DSP), or other programmable device. Devices used within a hardware execution unit may be arranged in many different configurations (or topologies), such as grids, rings, stars, or other configurations. A hardware execution unit may support one or more threads (or processes) when performing processing operations.

  A software execution unit may include software resources (eg, a technical computing environment) that may perform and / or participate in one or more parallel programming activities. A software execution unit may perform and / or participate in one or more parallel programming activities in response to receiving a program and / or one or more portions of a program. A software execution unit may use and / or participate in different types of parallel programming using one or more hardware execution units. A software execution unit may support one or more threads and / or processes when performing processing operations.

  The term “parallel programming” may be understood to include multiple types of parallel programming, eg, task parallel programming, data parallel programming, and stream parallel programming. Parallel programming may include various types of processing that may be distributed over multiple resources (eg, software execution units, hardware execution units, processors, microprocessors, clusters, labs) and performed simultaneously.

  For example, parallel programming may include task parallel programming, where several tasks can be processed simultaneously on several software execution units. In task parallel programming, a task may be processed, for example, simultaneously and independently of other running tasks.

  Parallel programming may include data parallel programming, in which data (eg, a data set) can be analyzed into several parts that can be executed in parallel using, for example, a software execution unit. In data parallel programming, software execution units and / or data portions may communicate with each other as processing proceeds.

  Parallel programming may include stream parallel programming (sometimes referred to as pipeline parallel programming). Stream parallel programming may use several software execution units, for example arranged in series (eg, lines), where the first software execution unit assumes the first result and the second result. A first result may be generated that may be fed to a second software execution unit. Stream parallel programming may also include situations where task allocation can be represented in a directed acyclic graph (DAG) or a cyclic graph.

  Other parallel programming techniques may involve task, data, and / or stream parallel programming techniques alone or in some combination with other types of processing techniques to perform hybrid parallel programming techniques.

  The foregoing description may provide illustrations and descriptions of various embodiments of the invention, but is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Modifications and variations may be possible in light of the above teachings or may be obtained from practice of the invention. For example, although a series of actions has been described above, the order of actions may be modified in other implementations consistent with the principles of the invention. In addition, non-dependent actions may also be performed in parallel. Further, although features and access classes have been described above using a particular syntax, features and access classes may be equally defined using different methods and using different syntax.

  In addition, one or more implementations consistent with the principles of the invention may be used in one or more devices and / or configurations other than those illustrated in the drawings and described in the specification without departing from the spirit of the invention. May be implemented using: One or more devices and / or components may be added to and / or removed from the illustrated implementation depending on the specific deployment and / or application. Also, one or more disclosed implementations may not be limited to specific combinations of hardware.

  Further, certain portions of the invention may be implemented as logic that may perform one or more functions. The logic may include hardware such as wired logic, application specific integrated circuits, field programmable gate arrays, microprocessors, software, or a combination of hardware and software.

  Any element, action, or instruction used in the description of the present invention should not be construed as critical or essential to the present invention unless explicitly described as such. Also, as used herein, the article “a” is intended to include one or more items. Where only one item is intended, the term “a single” or similar language is used. Further, the phrase “based on”, as used herein, unless otherwise expressly stated, “based, at least in part, on (at least in part, Is intended to mean "based on". In addition, the term “user” as used herein is broadly construed to include, for example, an electronic device (eg, a workstation) or a user of an electronic device, unless stated otherwise. Is intended.

  The invention is not limited to the specific embodiments disclosed above, but the invention is intended to include any specific embodiments and equivalents within the scope of the following appended claims. .

Claims (27)

A non-transitory computer readable medium storing instructions, wherein when the instructions are executed by one or more processors, the one or more processors,
Accessing a modeling environment, wherein the modeling environment provides at least one feature described by a geometric shape, supports at least one tool that defines manipulation of the geometric shape of the feature, and The operations can be applied to achieve a plurality of different results, each individual result using the tool to affect the feature in a different way and corresponding to a different configuration of the tool When,
Receiving a selection of results to be achieved by the tool;
Manipulating the geometric shape of the feature according to the selected result.   The medium of claim 1, further storing instructions for displaying at least two of the plurality of different results on an interface of the modeling environment.   The medium of claim 2, wherein at least two of the plurality of different results are a subset of the plurality of different results, the subset being selected based on a previous history of result selection.   In response to receiving a selection of results to be achieved by the tool, further stores instructions for displaying an interface on a display device, the interface being applicable to the selected results. The medium of claim 1, wherein one or more options associated with a certain tool are entered.   The option entered into the interface is a subset of the options associated with the tool, and one or more options associated with the tool but not within the subset are not present in the interface. 4. The medium according to 4.   The medium of claim 5, wherein the interface is associated with a particular user or group of users in a data structure. Using the modeling environment to determine the identity of a user or group of users;
Retrieving an interface associated with the identified user or group of users in the data structure;
The medium of claim 6, further storing instructions for displaying the interface on a display device.   The medium of claim 7, wherein the read interface is displayed in response to an instruction to redefine a previously manipulated feature using the interface. Using the interface to identify features originally manipulated by the user or group of users;
Associating the interface with the feature;
Receiving a request from a second user or a second group of users to interact with a feature associated with the interface;
7. The medium of claim 6, further storing instructions for displaying to the second user or group of second users an interface originally used to manipulate the feature.   The medium of claim 4, wherein at least one of the options is pre-populated with a value based on previous user interaction with the interface.   The medium of claim 4, wherein the feature is displayed on a display device and the interface is displayed on the display device at a location defined based on the location of the feature on the display device.   The medium of claim 5, wherein the subset is a user-defined subset.   6. The medium of claim 5, wherein the subset is determined dynamically upon receipt of a selection of results to be achieved by the tool. A computer-implemented method, the method comprising:
Accessing a modeling environment, wherein the modeling environment provides at least one feature described by a geometric shape, supports at least one tool that defines manipulation of the geometric shape of the feature, and Operations can be applied to achieve a plurality of different results, each individual result affecting the feature in a different way and corresponding to a different configuration of the tool;
Receiving a selection of results to be achieved by the tool;
Manipulating the geometric shape of the feature according to the selected result. A system, the system comprising:
A memory for storing a model, the model including at least one feature described by a geometric shape;
A processor and
The processor is
Providing at least one tool defining an operation of the feature geometry, wherein the operation is applicable to achieve a plurality of different results, each individual result being said in a different way; Affecting the characteristics,
Receiving a selection of results to be achieved by the tool;
Manipulating the geometric shape of the feature according to the selected result. A non-transitory computer readable medium storing instructions, wherein when the instructions are executed by one or more processors, the one or more processors,
Receiving a selection of a tool for use with a modeling environment, wherein the tool interacts with one or more surfaces, edges, or vertices of a feature in the modeling environment, and the one or more surfaces Can modify edges, vertices, and
Displaying a plurality of configurable options for the tool, wherein the configurable option is capable of accepting an attribute value, and the set of attribute values for the configurable option is the tool Define a result that uses
Flagging one or more of the configurable options as associated with the result or as unrelated to the result;
Receiving the selection of results;
Displaying an interface associated with the result, wherein the interface only displays options that are marked as associated with the result or hides options that are marked as unrelated to the result A medium that makes things happen. A non-transitory computer readable medium storing instructions, wherein when the instructions are executed by one or more processors, the one or more processors,
Accessing a modeling environment, wherein the modeling environment provides at least one feature described by a geometric shape, supports at least one tool that defines manipulation of the geometric shape of the feature, and Operations can be applied to achieve a plurality of different results, each individual result affecting the feature in a different way and corresponding to a different configuration of the tool;
Receiving a selection of results to be achieved by the tool during the model design process;
Responsive to receiving the result selection, displaying an interface, the interface being populated with options associated with the tool that are applicable to the selected result; ,
Receiving an attribute value for one of the options;
Evaluating the feature using the attribute value prior to an operation being performed using the received attribute value during the model design process;
Identifying a problem with the attribute value;
A medium for displaying a warning regarding the attribute value.   The medium of claim 17, wherein the alert is displayed at a location determined based on the location of the option within the interface.   The medium of claim 17, wherein the warning relates to a violation of a geometric shape rule.   The medium of claim 17, wherein the warning relates to a violation of design intent.   The medium of claim 17, wherein the warning indicates a missing or null value.   The medium of claim 17, wherein the attribute value is provided by a user. A non-transitory computer readable medium storing instructions, wherein when the instructions are executed by one or more processors, the one or more processors,
Accessing a modeling environment, wherein the modeling environment provides at least one feature described by a geometric shape, supports at least one tool that defines manipulation of the geometric shape of the feature, and Operations can be applied to achieve a plurality of different results, each individual result affecting the feature in a different way and corresponding to a different configuration of the tool;
Receiving a selection of results to be achieved by the tool during the model design process;
In response to receiving the selection of results, displaying an interface on a display device, wherein the interface is populated with options associated with the tool that are applicable to the selected results. The interface provides an entry point to the help system;
Receiving a request to enter the help system from the entry point;
Dynamically generating a help page with content selected based on the entry point;
Displaying the dynamically generated help page.   24. The medium of claim 23, wherein the entry point is associated with one of the options in the interface and the help page is dedicated to one of the options.   One of the options is an option that the user is currently interacting with, and the content is received based on the option that the user is currently interacting with to request to enter the help system. The medium of claim 24, wherein the medium is dynamically generated when   26. The medium of claim 25, wherein the content is dynamically generated based on one or more user selections or user-supplied attribute values associated with options that the user is currently interacting with.   24. The medium of claim 23, wherein the help system includes help information, and the content is a subset of the help information related to the entry point.