System and method for creating application interfaces for multiphysics modeling
Abstract
A system generates a customized application data structure for modeling physical systems. The system includes a processor, an input device, optionally a display device, and a memory device. The processor is adapted to embed a multiphysics model data structure in the application data structure. The multiphysics model data structure comprises a representation of models of physical systems. Geometry data representing geometry subroutines and call data representing geometry subroutine calls are added to the embedded multiphysics model data structure. Data representing application features are added to the application data structure. Each application feature comprises one or more of (i) first data representing a form feature, or (ii) second data representing an action feature. A customized application data structure is generated providing a customized modeling of the physical systems using a modeling operation, a geometry of the one or more models of physical systems, an application feature, and a geometry subroutine. The customized application data structure is configured for distribution to end users as an application executed by an application runtime engine.
Claims
exact text as granted — not AI-modified1 - 21 . (canceled)
22 . A graphical user interface (GUI) implemented in a computer system comprising one or more processors, the GUI configured to customize components to include in an application data structure for modeling a physical system, the application data structure based on an embedded model data structure and user-selected application features, the embedded model data structure including a geometry and physical quantities represented in terms of a combined set of equations, the GUI including selectable GUI elements configured to implement the following acts:
displaying one or more first GUI elements representing one or more model data structures; receiving one or more first user inputs associated with a user selection from the one or more first GUI elements; displaying one or more second GUI elements representing one or more application features for association with the one or more model data structures; receiving one or more second user inputs associated with a user selection from the one or more second GUI elements; in response to receiving the one or more first user inputs, embedding the selected one or more model data structures in an application data structure; and in response to receiving the one or more second user inputs, adding the selected one or more application features to the application data structure, thereby generating a customized application data structure including at least the selected one or more model data structures and the selected one or more application features.
23 . The GUI of claim 22 , further comprising the GUI being configured to add application feature settings to at least one of the one or more added application features by implementing the following acts:
displaying one or more GUI elements representing one or more application feature settings; and receiving a user input associated with a user selection of the one or more application feature settings.
24 . The GUI of claim 23 , wherein at least one of the one or more application feature settings corresponds to a restriction setting or a preference setting.
25 . The GUI of claim 22 , wherein at least one of the one or more selected application features is added to the customized application data structure by implementation of the following acts:
displaying a context menu in the GUI, the context menu including several selectable application features; and receiving a user input associated with a user selection of one of the displayed selectable application features.
26 . The GUI of claim 22 , wherein at least one of the one or more model data structures is added to the customized application data structure by implementation of the following acts:
displaying a context menu in the GUI, the context menu including at least one selectable GUI element representing adding a model data structure; receiving a user input associated with a user selection of the at least one selectable GUI element; in response to receiving the user input, displaying a list including representations of available model data structures; and receiving a user input associated with a user selection of at least one of the available model data structures.
27 . The GUI of claim 22 , wherein at least one of the selected one or more application features includes input forms, output forms, form collections, and widget collections,
wherein the GUI is configured to allow interactive drawing and positioning of the input forms and output forms, and wherein the GUI is configured to allow for interactive design of form collections and widget collections.
28 . The GUI of claim 27 , wherein the GUI is configured to allow for a snapping option for positioning the forms and widgets.
29 . The GUI of claim 27 , wherein the GUI is configured to receive a user input for at least one of a default horizontal spacing setting and a default vertical spacing setting to be applied to a positioning of the input form or the output form.
30 . A graphical user interface (GUI) implemented in a computer system comprising one or more processors, the GUI configured to customize components to include in an application data structure for modeling a physical system, the application data structure based on an embedded model data structure and user-selected application features, the embedded model data structure including a geometry and physical quantities represented in terms of a combined set of equations, the GUI including selectable GUI elements configured to implement the following acts:
displaying one or more first GUI elements representing one or more model data structures; receiving one or more first user inputs associated with a user selection from the one or more first GUI elements representing the one or more model data structures; displaying one or more second GUI elements representing one or more application features for association with the one or more model data structures; receiving one or more second user inputs associated with a user selection from the one or more second GUI elements representing the one or more application features; in response to receiving the one or more first user inputs, embedding the selected one or more model data structures in an application data structure; in response to receiving the one or more second user inputs, adding the selected one or more application features to the application data structure; displaying one or more third GUI elements representing one or more selections for generating an executable standalone application for a customized application data structure that includes at least the selected one or more model data structures and the selected one or more application features; optionally displaying additional GUI elements as part of the one or more third GUI elements, the additional GUI elements representing one or more selections for packaging settings for the executable standalone application; and receiving one or more third user inputs associated with a user selection from the one or more third GUI elements representing the one or more selections for generating the executable standalone application, wherein the executable stand-alone application is generated based on the received one or more third user inputs, the stand-alone application including the customized application data structure.
31 . The GUI of claim 30 , wherein the displayed additional GUI elements include selectable settings to embed a platform compatible runtime engine with the executable standalone application.
32 . The GUI of claim 30 , wherein the displayed additional GUI elements include selectable settings for packaging a downloader for a runtime engine compatible with the executable standalone application.
33 . The GUI of claim 31 , wherein the displayed additional GUI elements further include representations of one or more platforms a packaged runtime engine is compatible with, and
in response to receiving the one or more third user inputs, generating the executable stand-alone application such that the packaged runtime engine is compatible with the platform associated with the received third user input.
34 . The GUI of claim 30 , further comprising:
displaying one or more fourth GUI element representing one or more selectable splash screens; and in response to receiving one or more fourth user inputs associated with a user selection of the one or more fourth GUI elements, packaging a file describing the splash screens associated the selected one or more fourth user inputs with the executable stand-alone application and automatically displaying the file during the launch of the executable stand-alone application.
35 . The GUI of claim 30 , wherein the additional GUI elements are displayed allowing user interaction with the additional GUI elements, and
wherein in response to a user interaction with one or more of the additional GUI elements, the executable application is generated with the packaging of the executable stand-alone application being in accordance with one or more selections of package settings associated with the user interaction with the one or more additional GUI elements.
36 . The GUI of claim 30 , wherein the one or more application features include method calls, and wherein in response to the one or more second inputs being associated with a user selection from a GUI element representing a method call, adding the selected method call to the application data structure.
37 . The GUI of claim 36 , wherein the GUI is further configured to allow modification of default values of the method call.
38 . The GUI of claim 30 , further comprising:
displaying one or more GUI elements representing a custom file arrangement; in response to receiving an input associated with a user selection of the one or more GUI elements representing the custom file arrangement, displaying a settings window, the settings window including at least one of a name input field and a list of available class identifiers; receiving a user input corresponding to a user selection of a name and/or an available class identifier; and in response to receiving the user input for the name and/or available class identifier, configuring the application data structure to include the custom file arrangement in accordance with the user inputs.Cited by (0)
No later patents cite this yet.
References (0)
No backward citations on record.