OpenFOAM-based user interface integrated driving framework
Through the integrated driver framework of user interface based on OpenFOAM, the user configuration and error handling of OpenFOAM are simplified, the threshold for use is lowered, the simulation computing efficiency and user operation convenience are improved, and the good scalability of modular design is achieved.
Patent Information
- Application Number
- CN202510671193.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-23
- Publication Date
- 2025-08-15
AI Technical Summary
OpenFOAM has a high threshold for use, difficult parameters adjustment, and opaque error reporting, resulting in low engineering simulation computing efficiency.
It provides an integrated driver framework for user interfaces based on OpenFOAM, including the user interface layer and the intermediate service layer. It simplifies user configuration through parameter input module and result display module. The intermediate service layer generates OpenFOAM standard input files and includes error checking modules and parameter configuration modules to improve configuration efficiency and error transparency.
It has achieved the reduction of OpenFOAM's usage threshold, simplified parameter adjustment, and clear error reporting, improved simulation computing efficiency and user operation convenience, and has good scalability and portability.
Smart Images
Figure CN120493337A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computational fluid dynamics technology, and in particular to an OpenFOAM-based user interface integrated driving framework. Background Art
[0002] Computational fluid dynamics (CFD) is a discipline that uses numerical methods and algorithms to simulate fluid flow. By solving the governing equations of fluid dynamics, fluid behavior is studied, analyzing flow, heat transfer, mass transfer, and other issues. OpenFOAM, an open-source CFD software, provides the solvers, algorithms, and modules necessary to implement CFD theory, enabling simulation and solution of numerical problems in fluid dynamics and related physical phenomena.
[0003] While OpenFOAM's modular system (physical model, meshing tools, solver) provides flexibility, it takes time for users to understand how the various modules work together. The number of case configurations required to call OpenFOAM for calculations is numerous and complex, and improper user configuration can easily lead to solution errors. OpenFOAM relies on a Linux environment, and users need to have C++ code and CFD theoretical knowledge to use and develop. Furthermore, OpenFOAM's error messages come from various sources, and diagnostic information is not intuitive. Users need to invest a significant amount of time and learning costs to use OpenFOAM as smoothly as conventional software. Summary of the Invention
[0004] In order to alleviate, mitigate or eliminate the above technical problems, this application provides an OpenFOAM-based user interface integrated driving framework to improve simulation calculation efficiency.
[0005] In a first aspect, the present application provides an OpenFOAM-based user interface integrated driving framework, characterized by including:
[0006] The user interface layer includes a parameter input module and a result display module. The parameter input module is used to display input controls on the user interface, obtain the parameters configured by the user through the input controls, and send them to the intermediate service layer. The result display module is used to call OpenFOAM to perform solution calculations and visually display the calculation results on the user interface.
[0007] The intermediate service layer includes an input file generation module, which is used to generate an OpenFOAM standard input file according to user-configured parameters.
[0008] In one possible implementation, the framework further includes:
[0009] Data layer, used to store OpenFOAM standard input files.
[0010] In a possible implementation, the intermediate service layer further includes OpenFOAM.
[0011] In a possible implementation, the input control includes a scene type configuration control, and the scene type configuration control is used for the user to configure scene type parameters;
[0012] The intermediate service layer further includes a parameter configuration module, which is used to load a corresponding parameter template according to the scenario type parameter;
[0013] The parameter input module is further configured to generate an input parameter configuration control according to the parameter template and display it on the user interface, obtain input parameters configured by the user through the input parameter configuration control and send them to the intermediate service layer;
[0014] The parameter configuration module is further used to update the data model according to the input parameters, and map and bind the data model to the corresponding input parameter configuration controls of the user interface;
[0015] And the generating of OpenFOAM standard input file according to the parameters configured by the user includes:
[0016] Map the updated data model to the OpenFOAM standard input file.
[0017] In one possible implementation, mapping the updated data model to an OpenFOAM standard input file includes:
[0018] Determine the turbulence model type based on the updated data model;
[0019] Select the target OpenFOAM standard input file according to the turbulence model type;
[0020] Complete the parameter filling of the target OpenFOAM standard input file according to the updated data model.
[0021] In one possible implementation, the result display module is also used to monitor the target parameters during the solution calculation process, and to display the changes of the target parameters during the solution calculation process on the user interface, and in response to an abnormality of the target parameters during the solution calculation process, to display an abnormality prompt on the user interface, and the abnormality prompt is used to guide the user to modify the configuration of the input parameters.
[0022] In a possible implementation, the parameter configuration module is further configured to recommend parameter values of input parameters associated with the partial input parameters configured by the user.
[0023] In one possible implementation, the intermediate service layer also includes an error checking module, which is used to verify whether the input parameters configured by the user are legal in response to the user configuring the input parameters through the input parameter configuration control; and in response to the input parameters configured by the user being illegal, display an error prompt on the user interface, and the error prompt is used to guide the user to modify the erroneous input parameters.
[0024] In a possible implementation, the parameter input module is further configured to automatically locate the input parameter configuration control corresponding to the erroneous input parameter in response to the user clicking the error prompt on the user interface, and provide modification suggestions.
[0025] In one possible implementation, verifying whether the input parameters configured by the user are legal includes one or more of the following:
[0026] Verify the integrity of user-configured input parameters;
[0027] Verify the value range of user-configured input parameters;
[0028] Verify the matching relationship between the input parameters configured by the user.
[0029] Compared with the prior art, this application has the following advantages:
[0030] The user interface integrated driving framework based on OpenFOAM provided by this application includes a user interface layer and an intermediate service layer. The user interface layer includes a parameter input module and a result display module, wherein the parameter input module is used to display input controls in the user interface, obtain the parameters configured by the user through the input controls and send them to the intermediate service layer; the result display module is used to call OpenFOAM to solve the calculation and visually display the calculation results in the user interface; the intermediate service layer includes an input file generation module, which is used to generate an OpenFOAM standard input file based on the parameters configured by the user. This application adopts a modular architecture design, with clear logic and strong decoupling between each functional module, good scalability and engineering applicability, and standardized input, controllable calculation, and intelligent feedback. It solves the key problems of OpenFOAM in engineering simulation, such as high threshold for use, difficult parameter adjustment, and opaque error reporting, and improves simulation calculation efficiency. Each module of this framework can be independently upgraded, expanded, and replaced without changing the overall logical structure, and has significant portability. Even if the module function is optimized, the algorithm is upgraded, or the underlying language is converted, it will not affect the establishment of this framework, providing a stable architecture and technical foundation for subsequent version upgrades, cross-platform deployment, and function expansion. BRIEF DESCRIPTION OF THE DRAWINGS
[0031] The accompanying drawings are included to provide a further understanding of the present application. They are incorporated into and constitute a part of this application. The accompanying drawings illustrate embodiments of the present application and, together with this specification, serve to explain the principles of the present application. In the accompanying drawings:
[0032] Figure 1 This is a structural diagram of an OpenFOAM-based user interface integrated driving framework provided in an embodiment of the present application;
[0033] Figure 2 This is a flow chart of a computational fluid dynamics calculation method based on a user interface integrated driving framework provided in an embodiment of the present application. DETAILED DESCRIPTION
[0034] To more clearly illustrate the technical solutions of the embodiments of this application, the following is a brief introduction to the drawings required for describing the embodiments. Obviously, the drawings described below are merely examples or embodiments of this application. Those skilled in the art can apply this application to other similar scenarios based on these drawings without inventive effort. Unless otherwise apparent from the context or otherwise noted, the same reference numerals in the figures represent the same structure or operation.
[0035] As used herein, unless the context clearly indicates otherwise, the terms "a," "an," "an," and / or "the" are not intended to refer to the singular but may include the plural. Generally speaking, the terms "include" and "comprise" only indicate the inclusion of the steps and elements specifically identified, and these steps and elements do not constitute an exclusive list. A method or apparatus may also include other steps or elements.
[0036] At the same time, this application uses specific terms to describe the embodiments of this application. For example, "one embodiment," "an embodiment," and / or "some embodiments" refer to a certain feature, structure, or characteristic related to at least one embodiment of this application. Therefore, it should be emphasized and noted that "one embodiment," "an embodiment," or "an alternative embodiment" mentioned twice or multiple times in different locations in this specification does not necessarily refer to the same embodiment. In addition, certain features, structures, or characteristics in one or more embodiments of this application may be appropriately combined.
[0037] Unless otherwise specified, the relative arrangement of the parts and steps, numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present application. Meanwhile, it should be understood that, for ease of description, the sizes of the various parts shown in the accompanying drawings are not drawn according to actual proportional relationships. Technology, methods and equipment known to those of ordinary skill in the relevant art may not be discussed in detail, but in appropriate cases, the technology, methods and equipment should be considered as a part of the specification. In all examples shown and discussed here, any specific value should be interpreted as being merely exemplary, rather than as a limitation. Therefore, other examples of exemplary embodiments may have different values. It should be noted that similar numbers and letters represent similar items in the following drawings, and therefore, once an item is defined in an accompanying drawing, it does not need to be further discussed in subsequent drawings.
[0038] In addition, although the terms used in this application are selected from commonly known and commonly used terms, some of the terms mentioned in this specification may be selected by the applicant at his or her discretion, and their detailed meanings are explained in the relevant parts of the description herein. In addition, it is required that this application be understood not only by the actual terms used, but also by the meaning implied by each term.
[0039] Flowcharts are used in this application to illustrate the operations performed by devices or apparatuses according to embodiments of the present application. It should be understood that the preceding or following operations are not necessarily performed in exact order. Instead, the steps may be performed in reverse order or simultaneously. Furthermore, other operations may be added to these processes, or one or more operations may be removed from these processes.
[0040] Figure 1 This is a schematic diagram of the structure of an OpenFOAM-based user interface integrated driving framework provided in the embodiment of the present application. Figure 1 As shown, the user interface integrated driving framework 100 based on OpenFOAM includes a user interface layer 101 and an intermediate service layer 102. The user interface layer 101 and the intermediate service layer 102 can interact with each other in a bidirectional manner.
[0041] The user interface layer 101 includes a parameter input module 111 and a result display module 112. The parameter input module 111 is used to display input controls in the user interface, obtain the parameters configured by the user through the input controls and send them to the intermediate service layer 102. The input controls may include drop-down menus, text input boxes, voice input boxes, selection boxes, radio buttons, charts, pop-up windows and the like. The embodiment of the present application does not limit the form of input controls. In an exemplary embodiment, the user can directly describe the simulation requirements in natural language through the input controls. For example, the user enters "simulate the flow of a straight pipe with a diameter of 0.1m, a pressure of 1.5MPa, and a temperature of 400K" in the dialog box, and uses natural language processing (NLP) technology to obtain the corresponding input parameters.
[0042] The result display module 112 is used to call OpenFOAM to solve the calculation and visualize the calculation results in the user interface. OpenFOAM can be installed locally as a separate software, or installed in other entities, or integrated in the intermediate service layer 102. Figure 1 In the exemplary embodiment shown, OpenFOAM can be installed locally as a separate piece of software. The OpenFOAM-based user interface integrated driving framework 100 can also include a data layer 103 for storing OpenFOAM standard input files. OpenFOAM reads input files from the data layer 103. Visual displays of calculation results include, but are not limited to, charts, curves, and other forms.
[0043] Intermediate service layer 102 includes an input file generation module 121. This module is used to generate an OpenFOAM standard input file based on user-configured parameters. In one exemplary embodiment, a user can enter the required parameters using a static form via input controls, and then directly convert the form parameters into an OpenFOAM standardized input file via a command line.
[0044] In some embodiments, the input file generation module 121 may send the generated OpenFOAM standard input file to the data layer 103. In other embodiments, the intermediate service layer 102 further includes OpenFOAM 122, and the OpenFOAM standard input file generated by the input file generation module 121 may be directly provided to OpenFOAM 122, which then solves the calculation and sends the calculation results to the user interface layer 101.
[0045] In some embodiments, a parameter template library can be predefined. The parameter template library can use a structured language (such as JSON, etc.), with the CFD scene type as the index unit, and define standardized solver types, initial conditions, boundary conditions, turbulence models, physical property models, meshing methods, etc. for different CFD scene types. The parameter set includes required parameter items and default values, parameter types, parameter value ranges, dependencies between parameters, etc. The input control includes a scene type configuration control for the user to configure the scene type parameters. The user can configure the CFD simulation scene that needs to be simulated through the scene type configuration control, such as the user selects the "steady state" or "single-phase flow" scene type through the scene type configuration control.
[0046] The intermediate service layer 102 may also include a parameter configuration module 123. The parameter configuration module 123 is used to load the corresponding parameter template according to the scenario type parameters. The parameter input module 111 is also used to generate an input parameter configuration control based on the parameter template and display it on the user interface, obtain the input parameters configured by the user through the input parameter configuration control and send it to the intermediate service layer 102. The parameter configuration module 123 is also used to update the data model based on the input parameters, and map and bind the data model to the corresponding input parameter configuration control of the user interface. The input file generation module 121 maps the updated data model to an OpenFOAM standard input file. For example, the input file generation module 121 maps the structured parameters input by the user through the user interface to a standard OpenFOAM input file based on the template engine, including p, turbulenceProperties, controlDict, etc., supporting dynamic filling and formatted writing or multi-file collaborative generation. In such an embodiment, by loading parameter templates of different simulation scenarios, completing parameter configuration and modification, and realizing OpenFOAM standard input file conversion, the use threshold can be significantly lowered and the use efficiency can be improved.
[0047] In some embodiments, the input file generation module 121 determines the turbulence model type based on the updated data model; selects a target OpenFOAM standard input file based on the turbulence model type; and then completes parameter filling of the target OpenFOAM standard input file based on the updated data model. The following uses the turbulence model "k-ωSST" as an example for further explanation. In this specific example, the user sets the turbulence model to "k-ωSST" through the input parameter configuration control displayed in the user interface, such as the interface field "Turbulence Model = k-ωSST", which corresponds to the data model field "Turbulence Model = k-ωSST".
[0048] The input file generation module 121 reads the file generation rules and selects the constant / turbulenceProperties and constant / RASProperties files based on "turbulence model is on" and "turbulence model = k-ωSST". Then, the parameters of the turbulenceProperties and RASProperties files are filled in according to the updated data model:
[0049] The contents of the file turbulenceProperties are:
[0050] simulationType RASModel; \\fill in data model parameters
[0051] The contents of the file RASProperties are:
[0052]
[0053]
[0054] The generation process can be implemented using a template engine combined with file generation rules to ensure that the output file complies with the OpenFOAM specification requirements and is extensible to support subsequent module expansion.
[0055] In some embodiments, the parameter configuration module 123 is also used to recommend parameter values of input parameters associated with some input parameters configured by the user, thereby assisting the user to reasonably set parameters. In an exemplary embodiment, the parameter configuration module 123 automatically recommends parameter values or selects models based on the current input parameter characteristics, according to built-in rules and experience databases, such as recommending time steps based on grid size and recommending grid division methods based on geometric features. The built-in rule library can be subsequently expanded and updated as needed. Exemplarily, a rule engine can be used for implementation, and the main process includes "input parameter change" → "trigger and extract features" → "match rules" → "output recommended values". The specific process examples are as follows:
[0056] If the number of mesh cells in a mesh file imported or generated in the user interface exceeds 5,000,000, the default value of the maximum number of iterations in the user interface is adjusted to 1,000, and the default value of the relative error of convergence is adjusted to 1×10 -6 , the default values of pressure and velocity relaxation factors are adjusted to 0.5, and the parallel calculation setting is turned on. The default number of calculation cores in the XYZ direction is 2, 2, and 2. Users can adjust it based on the default values to take into account the flexibility of the calculation settings.
[0057] In some embodiments, the intermediate service layer 102 also includes an error checking module 124. The error checking module 124 is used to check whether the input parameters configured by the user are legal in response to the user configuring the input parameters through the input parameter configuration control; and in response to the input parameters configured by the user being illegal, an error prompt is displayed on the user interface. The error prompt can be used to guide the user to modify the erroneous input parameters, such as prompting the user with the erroneous parameters in a pop-up window, and suggesting that the user modify the erroneous parameters, or directly locating the input parameter configuration control corresponding to the erroneous parameters and giving modification suggestions. Exemplarily, the parameter input module 111 is also used to automatically locate the input parameter configuration control corresponding to the erroneous input parameters in response to the user clicking the error prompt in the user interface, and giving modification suggestions. In some embodiments, the user interface layer 101 can also provide an error log function, listing common errors and repair suggestions.
[0058] In some embodiments, checking whether the input parameters configured by the user are legal may include one or more of the following: checking the integrity of the input parameters configured by the user; checking the numerical range of the input parameters configured by the user; checking the matching relationship between the input parameters configured by the user. In an exemplary embodiment, an error checking rule base may be constructed, including mandatory item checking, numerical range checking, and physical and logical consistency checking. Mandatory item checking refers to whether the mandatory parameters in the user interface are complete, that is, checking the integrity of the input parameters configured by the user, and confirming whether the current configuration can carry out calculations. Numerical range checking refers to whether any input parameter in the user interface is within the corresponding legal range, that is, checking the numerical range of the input parameters configured by the user. Physical and logical consistency checking refers to checking whether the physical parameters match and whether there are inconsistent logical relationships, that is, checking the matching relationship between the input parameters configured by the user, such as the matching relationship between the turbulence model and the Reynolds number.
[0059] In some embodiments, the result display module 112 is further configured to monitor target parameters during the solution calculation process and display changes in the target parameters during the solution calculation process on the user interface, and in response to an abnormality in the target parameters during the solution calculation process, display an abnormality prompt on the user interface. The abnormality prompt can be used to guide the user to modify the configuration of the input parameters, such as using a pop-up window to prompt the user of an error and suggesting which parameters to modify, or directly locating the input parameter configuration control corresponding to the erroneous parameter and providing modification suggestions.
[0060] For example, during the solution calculation process, the result display module 112 monitors important parameters in the simulation process, such as the residual values of different parameters and the corresponding time steps, and displays real-time monitoring data, including residual curve graphs, CPU resource usage graphs, etc. If the monitoring curve is abnormal during the calculation process, including increased residual values, memory overflow, etc., the alarm mechanism of the user interface will be triggered to feedback the problem to the user in real time. The user can see feedback information on the user interface, such as "The residual value increases during the calculation process, there is a risk of divergence, it is recommended to adjust the grid size to 0.001m." If the above phenomenon occurs, it is recommended that the user modify the configured input parameters.
[0061] It will be understood that each module can adopt a modular packaging design, support on-demand loading and dynamic replacement, and integrate other functions through plug-ins without affecting the original functions, meeting various types of CFD simulation needs. Each module can also be deployed as a standalone tool, interacting through a unified file interface (such as JSON), rather than an integrated architecture, and achieving simulation through a distributed tool chain.
[0062] This application solves the problems of complex input file structures, strong physical model coupling, and discontinuous operation processes in the OpenFOAM computing framework, achieving deep adaptation of the CFD simulation process rather than superficial interaction optimization. Modules can communicate with each other through a unified data interface, ensuring the continuity of the simulation process, optimizing the human-computer interaction experience of traditional CFD software, simplifying the CFD simulation operation process, and improving the convenience, accuracy, and scalability of user operations.
[0063] The scenario type configuration control is displayed in the user interface, and the user selects the simulation scenario through the user interface. The parameter template is loaded according to the simulation scenario selected by the user to automatically fill in the parameters. The input parameter configuration control is generated according to the parameter template and displayed in the user interface. The user adjusts the parameter settings through the input parameter configuration control. The intelligent recommended parameters provide auxiliary suggestions, and the legality of the configuration parameters is verified in real time and an alarm prompt is issued. After the input is confirmed, the standard input file required for OpenFOAM operation is generated, the solver corresponding to the case is determined, and OpenFOAM is called for calculation. Enter the simulation run, and refresh the residual curve regularly to monitor the current calculation stability. After the calculation is completed, the case status is changed and detailed calculation results are provided, including calculation time, resources, etc. Users can view the visual cloud map in the user interface, check the calculation results, and evaluate the calculation accuracy.
[0064] Figure 2 1 is a flow chart of a computational fluid dynamics calculation method based on the user interface integrated driving framework 100 provided in an embodiment of the present application. Figure 2 As shown, the computational fluid dynamics calculation method 200 includes the following:
[0065] Step S210: Determine the simulation scenario.
[0066] The parameter input module 111 displays a scenario type configuration control on the user interface, and the user selects a simulation scenario through the scenario type configuration control on the user interface.
[0067] Step S220: Load the parameter template.
[0068] The corresponding parameter template is loaded according to the simulation scenario selected by the user through the parameter configuration module 123. The input parameter configuration control is generated according to the loaded parameter template through the parameter input module 111 and displayed on the user interface.
[0069] Step S230: configure input parameters.
[0070] The user configures input parameters via input parameter configuration controls displayed on the user interface. In some embodiments, during the user configuration of input parameters, parameter values associated with the user-configured portion of the input parameters may be recommended. In some embodiments, the input parameters may also be dynamically optimized based on historical calculation data or a built-in algorithm.
[0071] Step S240: input parameter verification.
[0072] The error checking module 124 verifies the legality of the configured input parameters. If the configured input parameters are illegal, an error message is displayed on the user interface. If the user clicks on the error message, the parameter input module 111 automatically locates the incorrect input parameter and provides correction suggestions, returning to step S230. Alternatively, the input parameters are automatically optimized based on historical calculation data or a built-in algorithm. If the configured input parameters are legal, the process proceeds to step S250.
[0073] Step S250: Generate an OpenFOAM standard input file.
[0074] Based on the configured input parameters, the input file generation module 121 loads the corresponding OpenFOAM input file template and populates it to generate an OpenFOAM standard input file. In some embodiments, after completing the configuration of the input parameters, the user can click a confirmation button on the user interface. In response to the user clicking the confirmation button on the user interface, the OpenFOAM standard input file is generated.
[0075] Step S260: Simulation calculation starts.
[0076] The user can start the simulation calculation through the user interface. For example, the user can start the calculation by clicking the run button on the user interface.
[0077] Step S270: real-time monitoring and feedback.
[0078] During the calculation process, the target parameters are monitored in real time via the result display module 112. If a monitoring anomaly occurs during the calculation process, an alarm mechanism in the user interface may be triggered, providing real-time feedback to the user. Otherwise, the process proceeds to step S280. For example, in response to an anomaly in the target parameter calculation process, an anomaly prompt may be displayed on the user interface, where the anomaly prompt is used to guide the user to modify the configuration of the input parameters. For example, in response to the user clicking the anomaly prompt, the process returns to step S230 to reconfigure the input parameters. The user may modify the input parameters based on the information displayed in the anomaly prompt, or the input parameters may be automatically optimized based on historical calculation data or a built-in algorithm.
[0079] Step S280: Visual display of results.
[0080] After the calculation is completed, the calculation results are visualized through the result display module 112.
[0081] Although operations are described herein in a specific order, this should not be understood as requiring that these operations be performed in the specific order or sequence shown, or that all operations shown be performed to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are involved in the above discussion, these details should not be interpreted as limiting the scope of the application, but rather as describing features specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be combined in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented individually or in any suitable subcombination in multiple embodiments.
[0082] Although the present application has been described with reference to the current specific embodiments, those skilled in the art should recognize that the above embodiments are merely used to illustrate the present application, and that various equivalent changes or substitutions may be made without departing from the spirit of the present application. Therefore, any changes or modifications to the above embodiments that fall within the spirit of the present application will fall within the scope of the present application.
Claims
1. A user interface integrated driving framework based on OpenFOAM, characterized by: include: The user interface layer includes a parameter input module and a result display module. The parameter input module is used to display input controls on the user interface, obtain the parameters configured by the user through the input controls, and send them to the intermediate service layer. The result display module is used to call OpenFOAM to perform solution calculations and visually display the calculation results on the user interface. The intermediate service layer includes an input file generation module, which is used to generate an OpenFOAM standard input file according to user-configured parameters.
2. The user interface integrated driving framework based on OpenFOAM according to claim 1, characterized in that: Also includes: Data layer, used to store OpenFOAM standard input files.
3. The user interface integrated driving framework based on OpenFOAM according to claim 1, characterized in that: The intermediate service layer also includes OpenFOAM.
4. The user interface integrated driving framework based on OpenFOAM according to any one of claims 1 to 3, characterized in that: The input control includes a scene type configuration control, and the scene type configuration control is used for the user to configure scene type parameters; The intermediate service layer further includes a parameter configuration module, which is used to load a corresponding parameter template according to the scenario type parameter; The parameter input module is further configured to generate an input parameter configuration control according to the parameter template and display it on the user interface, obtain input parameters configured by the user through the input parameter configuration control and send them to the intermediate service layer; The parameter configuration module is further used to update the data model according to the input parameters, and map and bind the data model to the corresponding input parameter configuration controls of the user interface; And the generating of OpenFOAM standard input file according to the parameters configured by the user includes: Map the updated data model to the OpenFOAM standard input file.
5. The user interface integrated driving framework based on OpenFOAM according to claim 4, characterized in that: Mapping the updated data model to an OpenFOAM standard input file includes: Determine the turbulence model type based on the updated data model; Select the target OpenFOAM standard input file according to the turbulence model type; Complete the parameter filling of the target OpenFOAM standard input file according to the updated data model.
6. The OpenFOAM-based user interface integrated driving framework according to claim 4, characterized in that: The result display module is also used to monitor the target parameters during the solution calculation process, and to display the changes of the target parameters during the solution calculation process on the user interface, and in response to an abnormality of the target parameters during the solution calculation process, to display an abnormality prompt on the user interface, and the abnormality prompt is used to guide the user to modify the configuration of the input parameters.
7. The user interface integrated driving framework based on OpenFOAM according to claim 4, characterized in that: The parameter configuration module is further configured to recommend parameter values of input parameters associated with the partial input parameters configured by the user.
8. The OpenFOAM-based user interface integrated driving framework according to claim 4, characterized in that: The intermediate service layer further includes an error checking module, wherein the error checking module is configured to check whether the input parameters configured by the user are legal in response to the user configuring the input parameters through the input parameter configuration control; In response to the input parameters configured by the user being illegal, an error prompt is displayed on the user interface, wherein the error prompt is used to guide the user to modify the incorrect input parameters.
9. The OpenFOAM-based user interface integrated driving framework according to claim 8, characterized in that: The parameter input module is further configured to automatically locate an input parameter configuration control corresponding to an erroneous input parameter in response to a user clicking on the error prompt in the user interface, and provide modification suggestions.
10. The user interface integrated driving framework based on OpenFOAM according to claim 8, characterized in that: The verification of whether the input parameters configured by the user are legal includes one or more of the following: Verify the integrity of user-configured input parameters; Verify the value range of user-configured input parameters; Verify the matching relationship between the input parameters configured by the user.