Post-processing method and system for simulation calculation result of CAE (Computer Aided Engineering) software

By splitting the simulation dataset and establishing mapping relationships, combined with a visual editor and preset rules, the problem of inflexible interface configuration in the post-processing of CAE software simulation calculation results was solved, realizing fast and flexible interface editing and efficient data scanning, and reducing system coupling.

CN121834937APending Publication Date: 2026-04-10CHINA COMPUTER DIGITAL (BEIJING) INFORMATION TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-12-30
Publication Date
2026-04-10

AI Technical Summary

Technical Problem

Existing technologies for post-processing CAE software simulation results suffer from inflexible interface configuration, require multiple steps, and rely on experience and manual scanning, making it difficult to quickly meet the visualization needs of different business operations.

Method used

By splitting simulation data into independent datasets and establishing mapping relationships with visualization components, the interface can be built by dragging and dropping components using a visualization editor. Combined with preset rules, it automatically scans and reports suspicious issues, providing flexible component combinations and custom interface editing.

Benefits of technology

It enables fast and flexible interface configuration, reduces the workload of engineers, ensures full coverage scanning, supports multi-window linkage operation, reduces system coupling, and improves development and maintenance efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121834937A_ABST
    Figure CN121834937A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of scientific calculation visualization, and discloses a post-processing method and system for a CAE software simulation calculation result, and the method mainly comprises the following steps: (1) reading the CAE software simulation calculation result, and verifying parameters in the CAE software simulation calculation result; (2) analyzing simulation data calculated by the CAE software, and splitting the data into data sets; (3) establishing a mapping relation between the data set and the post-processing visual component; (4) configuring data filters possibly existing in the mapping relation; and (5) the visual interface is edited by utilizing a visual editor according to requirements, so that the assemblies with different functions are combined more flexibly, and the effect of meeting different business requirement interfaces can be quickly formed.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of scientific computing visualization, in particular to a post-processing method for CAE software simulation calculation results. BACKGROUND

[0002] In the face of different post-processing visualization business needs of different types of CAE process solver integration, the mainstream method in the prior art is to convert the calculation result files of different solvers into a unified format according to the mature experience of previous projects, establish the mapping relationship of physical field data variables, and thus convert different simulation calculation results to one data format, and uniformly visualize the post-processing results. Another method is to analyze the variables for a data format, and provide general visualization tools such as contour lines and isosurfaces when displaying on the interface. Users can select tools according to their needs each time they view simulation result data. If a new data format is added, the corresponding data format analysis work needs to be added.

[0003] However, the above two methods still have the following defects:

[0004] 1. The post-processing visualization effect display based on the conversion of a unified data format mostly depends on the accumulation of previous project products. If new variable display requirements are encountered, code development needs to be redeveloped.

[0005] 2. The simulation data result visualization mostly depends on existing research and development accumulation. In fact, some cloud maps only change some physical field variable names, and the underlying rendering logic is consistent. There is a lack of encapsulation of this part of the visualization interface type.

[0006] 3. The simulation interface configuration is not flexible enough. Each time the result is extracted, multiple steps need to be performed, such as viewing the contour lines of the temperature field, taking the temperature field physical variable first, and then performing the contour line tool operation. If some point curve graphs also need to be displayed on one side, the point tracking function needs to be added.

[0007] Therefore, a post-processing visualization method and system that is more flexible in combination and can quickly form an interface that meets different business needs is needed. SUMMARY

[0008] The purpose of the present application is to provide a post-processing method for CAE software simulation calculation results, which has different functional components that are more flexible in combination and can quickly form an interface that meets different business needs.

[0009] The above technical purpose of the present application is achieved by the following technical scheme:

[0010] A post-processing method for CAE software simulation results includes the following steps:

[0011] Step 1: Read the simulation calculation results from the CAE software and verify the parameters therein;

[0012] Step 2: Analyze the simulation data calculated by the CAE software and split the data into datasets;

[0013] Step 3: Establish the mapping relationship between the dataset and the post-processing visualization components;

[0014] Step 4: Configure data filters that may exist in the mapping relationship;

[0015] Step 5: Edit the visual interface using a visual editor according to your needs.

[0016] By adopting the above technical solution, Step 2 encapsulates each component, and each component is independent of each other and has no coupling relationship, so it can be used alone. The visual interface in Step 5 is editable. The visual interface can be fully customized by relying on each encapsulated component. The required functional components can be put into the visual interface for use. Adaptive adjustments can be made for different needs to build a visual interface that is highly adapted to user needs.

[0017] The independent components can be combined more flexibly. When the function of a corresponding component is needed, simply put the corresponding component into the visual interface. There is no need to attach other components or rely on other components to implement the function of the component itself. The visual editor makes it more convenient and efficient to build visual interfaces that meet different business needs. You can simply use the visual editor to edit the visual interface.

[0018] A further provision of the present invention is that step Step 1 also includes issuing a warning for situations where the preset conditions are not met.

[0019] By adopting the above technical solution, compared with the traditional method that requires engineers to rely on experience and eyesight to find potential problems in massive cloud maps, charts and data, the present invention automatically scans all results based on preset rules during the post-processing process and feeds back suspicious problems to engineers. Engineers only need to verify and adjudicate the warnings, which greatly reduces the workload of engineers.

[0020] Furthermore, in complex models and dazzling cloud maps, minor deviations in local areas are easily overlooked by engineers relying solely on their visual perception. However, the warning system of this invention ensures 100% scanning of all areas without omission. Moreover, different engineers may have different focuses based on their experience, and the preset warnings of this invention provide objective and standardized quality thresholds that do not depend on fluctuations in personal experience. For designs with industry standards or corporate specifications, warnings can enforce checks on these hard indicators to ensure that simulation results meet the submission requirements.

[0021] A further configuration of the present invention is as follows: the simulation dataset includes grid cells, physical field values ​​and cell attributes. Step 2, as mentioned above, classifies and splits the entire simulation data into datasets, and each dataset will have a time series-like label for a calculation step.

[0022] By adopting the above technical solution, the simulation data is structured and serialized, separating the mesh, physical field and properties in the simulation data, allowing independent updates and version control. In subsequent analysis, if only a specific physical field (such as temperature field) needs to be studied, the dataset can be directly loaded, avoiding reading the entire huge result file and significantly reducing I / O time. In optimization or parametric analysis, if only part of the data changes, only the affected dataset can be updated, without having to regenerate the entire result file.

[0023] Time series labels make animation generation straightforward. Players can load datasets from different time steps in the order of the labels to create smooth animations. It is easy to extract datasets of the same physical field at different time steps for comparison, or to compare the interaction of different physical fields at the same time step. Furthermore, each dataset clearly indicates the computation step it belongs to through time step labels, which makes it easy to track the evolution of physical fields over time and ensures that the mesh, properties, and results strictly correspond at the same computation step.

[0024] A further feature of the present invention is that the post-processing visualization component in Step 3 includes a 3D visualization component, a chart component, an animation component, a calculation report component, and a control component. The data mapping relationship is established through a dataset list and the open interfaces of each component.

[0025] By adopting the above technical solutions, the transformation from a single-function platform to a flexible analysis workbench has been achieved. All connections can be defined through interfaces, reducing system coupling and facilitating development and maintenance. The development team can independently optimize the "3D rendering engine" without affecting the "chart drawing library." As long as the interface conventions remain unchanged, the components can be freely upgraded. To add a new chart type, it is only necessary to develop a new "chart component" and implement the standard interface, which can be seamlessly integrated into the existing system without modifying other parts. The same "3D visualization component" can be used in different CAE product lines, reducing development costs.

[0026] A further feature of the present invention is that the visual editor described in step 5 has the components described in step 3 built-in, and the post-processing page can be implemented by dragging and dropping components according to specific business needs.

[0027] By adopting the above technical solution, engineers do not need to write code or repeatedly click through multiple menus. They can quickly combine components such as 3D cloud maps, line graphs, and data tables into a customized analysis page that meets the needs of the current task by simply dragging and dropping, just like building blocks. This reduces the work that used to require hours of manual configuration and screenshot comparison to just a few minutes to complete the page setup and directly enter the analysis state.

[0028] Multiple windows can be opened simultaneously, displaying different calculation results, design schemes, or results at different time steps side by side. All views are based on the same data source and support linked operations, facilitating direct observation of multiphysics coupling effects, comparison of design schemes, and quick identification of the root cause of problems, avoiding the hassle and cognitive fragmentation of repeatedly switching between multiple software windows.

[0029] A further feature of the present invention is that the visual editor can open multiple visual interfaces simultaneously, and one visual interface can combine multiple components, and components can be nested within each other to form a nested relationship.

[0030] By adopting the above technical solution, multiple basic components can be combined and packaged into a fully functional composite component. Users can directly drag and drop this composite component to quickly reuse a set of complex functions, greatly simplifying the operation. Technical experts can use this to create advanced analysis modules that are ready to use out of the box for direct use by the team.

[0031] You can save your verified and efficient analysis methods, including component layout, data mapping logic, and judgment criteria, as an analysis template for easy reuse or to share with others. Each time you use it or on different devices, you only need to open the corresponding template, eliminating the need to repeatedly build the same template, saving time and improving efficiency.

[0032] A further provision of the present invention is that a system for implementing the above method is also provided, comprising:

[0033] 1. Calculation result file input module

[0034] The input module for the results file mainly reads the calculation results file, verifies the parameters in it, and provides warnings for cases that do not meet the preset requirements.

[0035] 2. Data Model Parsing Module

[0036] The results of simulation calculations generally include the mesh elements, physical field values, and element properties from the simulation data. Mesh element types may include tetrahedrons, hexahedrons, triangular prisms, etc. Each element includes: node coordinates and node indices. Physical field values ​​typically include numerical results such as stress, strain, temperature, velocity, and displacement. Element properties may include, for example, interface fronts in casting processes or element birth / death in additive manufacturing processes.

[0037] The data model parsing module is responsible for analyzing the simulation calculation result file. Following the logic described above, it categorizes and splits the entire simulation data into datasets, such as mesh nodes, cell datasets, temperature field node datasets, and displacement datasets (which typically have X, Y, and Z components), resulting in three-dimensional datasets. Each dataset is labeled with a time-series-like tag representing a calculation step.

[0038] 3. Data Mapping Model Configuration Module

[0039] This section uses a visualization approach to establish a mapping relationship between the dataset and post-processing visualization components. These components primarily include 3D visualization components such as contour plots, vector graphics, and voxel rendering; chart components, mainly multi-dimensional line graphs; animation components, such as contour plot changes with each calculation step; and a calculation report component, which requires the visualization interface editor module from Part 5.

[0040] The data mapping model is configured by establishing data mapping relationships through a list of datasets and the interfaces exposed by different components. For example, the cloud map component renders the physical field of the result after color mapping at the node and accepts a one-dimensional dataset. Since the exposed interface is also a one-dimensional dataset, the corresponding one-dimensional dataset can be selected from the dataset list, such as temperature or equivalent stress, depending on the interface.

[0041] 4. Data Flow Engine Module

[0042] The workflow engine module primarily addresses data processing of split datasets based on data flows generated by multiple filters. These filters include, but are not limited to: data type filters, visualization filters, and sampling type filters. Data type filters handle mathematical operations and precision calculations. Visualization filters address interface cropping, contour mapping, and streamlines. Sampling type filters handle point and linear interpolation point sampling. Filters can be cascaded to form a data processing flow.

[0043] 5. Visual Interface Editor Module

[0044] A key module of this invention is the visual interface editor, which provides a visual interface with pre-packaged components described in the data mapping module. Users can easily build most post-processing pages by dragging and dropping. Based on the specific business requirements of the post-processing visualization, users can select the required component types from the component library and place them on the interface by dragging and dropping. An interface can combine multiple components, or components can be nested within each other to form a nested relationship.

[0045] The types of components can be categorized (including but not limited to) 3D visualization components, chart components, animation components, calculation report components, control components, etc.

[0046] The beneficial effects of this invention are:

[0047] 1. For CAE simulation computing scenarios, provide an interface editor that better meets the needs of business post-processing visualization, and generate post-processing visualization interfaces through dataset configuration.

[0048] 2. The drag-and-drop method generates simulation calculation reports, which is more flexible and better meets customized business needs.

[0049] 3. Through the process engine and visual interface editor, the user's post-processing operation process is better preserved and solidified into a specific interface, saving the user time from repeated operations.

[0050] 4. It effectively decouples the logical relationship between the entire simulation data result file and the post-processing visualization, making the combination of post-processing visualizations more flexible. Attached Figure Description

[0051] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0052] Figure 1 This is a flowchart of the method of the present invention.

[0053] Figure 2 This is a schematic diagram of the system of the present invention.

[0054] Figure 3 This is a schematic diagram of the user interface according to an embodiment of the present invention. Detailed Implementation

[0055] The technical solution of the present invention will now be clearly and completely described with reference to specific embodiments. Obviously, the described embodiments are merely some embodiments of the present invention, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0056] A post-processing method for CAE software simulation results includes the following steps:

[0057] Step 1: Read the simulation calculation results from the CAE software and verify the parameters therein. Issue warnings if the preset conditions are not met.

[0058] Step 2: Analyze the simulation data calculated by the CAE software and split the data into datasets;

[0059] Step 3: Establish the mapping relationship between the dataset and the post-processing visualization components. The post-processing visualization components include 3D visualization components, chart components, animation components, calculation report components, and control components. The mapping relationship between the data is established through a dataset list and the open interfaces of each component.

[0060] Step 4: Configure the data filters that may exist in the mapping relationship;

[0061] Step 5: Edit the visual interface using the visual editor according to the requirements. The visual editor has built-in components described in Step 3. According to specific business needs, the post-processing page can be implemented by dragging and dropping components. Multiple visual interfaces can be opened simultaneously using the visual editor. Multiple components can be combined in one visual interface, and components can be nested within each other to form a nested relationship.

[0062] The simulation dataset includes grid cells, physical field values, and cell properties. Step 2 above describes the classification of the entire simulation data into specific categories, and each dataset will have a time series-like label for a calculation step.

[0063] Step 2 encapsulates each component, ensuring that each component is independent and uncoupled, allowing for individual use. Step 5 introduces an editable visual interface that can be fully customized based on the encapsulated components. Simply place the required functional components into the visual interface for use. Adaptive adjustments can be made to meet different needs, creating a visual interface that is highly adapted to user requirements.

[0064] The independent components can be combined more flexibly. When the function of a corresponding component is needed, simply put the corresponding component into the visual interface. There is no need to attach other components or rely on other components to implement the function of the component itself. The visual editor makes it more convenient and efficient to build visual interfaces that meet different business needs. You can simply use the visual editor to edit the visual interface.

[0065] Compared to the traditional method where engineers need to rely on experience and eyesight to find potential problems in massive cloud maps, charts and data, this invention automatically scans all results based on preset rules during post-processing and feeds back suspicious problems to engineers. Engineers only need to verify and adjudicate the warnings, which greatly reduces the workload of engineers.

[0066] Furthermore, in complex models and dazzling cloud maps, minor deviations in local areas are easily overlooked by engineers relying solely on their visual perception. However, the warning system of this invention ensures 100% scanning of all areas without omission. Moreover, different engineers may have different focuses based on their experience, and the preset warnings of this invention provide objective and standardized quality thresholds that do not depend on fluctuations in personal experience. For designs with industry standards or corporate specifications, warnings can enforce checks on these hard indicators to ensure that simulation results meet the submission requirements.

[0067] It realizes the structuring and serialization of simulation data, separates the mesh, physics field and properties in the simulation data, and allows independent updates and version control. In subsequent analysis, if only a specific physics field needs to be studied, the dataset can be loaded directly to avoid reading the entire huge result file, which significantly reduces I / O time. In optimization or parametric analysis, if only part of the data changes, only the affected dataset can be updated, without having to regenerate the entire result file.

[0068] Time series labels make animation generation straightforward. Players can load datasets from different time steps in the order of the labels to create smooth animations. It is easy to extract datasets of the same physical field at different time steps for comparison, or to compare the interaction of different physical fields at the same time step. Furthermore, each dataset clearly indicates the computation step it belongs to through time step labels, which makes it easy to track the evolution of physical fields over time and ensures that the mesh, properties, and results strictly correspond at the same computation step.

[0069] It has achieved the transformation from a single-function to a flexible analysis workbench. All connections can be defined through interfaces, reducing system coupling and facilitating development and maintenance. The development team can independently optimize the "3D rendering engine" without affecting the "chart drawing library". As long as the interface convention remains unchanged, the components can be freely upgraded. To add a new chart type, simply develop a new "chart component" and implement the standard interface to seamlessly integrate it into the existing system without modifying other parts. The same "3D visualization component" can be used in different CAE product lines, reducing development costs.

[0070] Engineers no longer need to write code or repeatedly click through multiple menus. They can simply drag and drop to quickly combine components such as 3D cloud maps, line graphs, and data tables into a customized analysis page that meets the needs of the current task, just like building blocks. This reduces the work that used to take hours of manual configuration and screenshot comparison to just a few minutes to complete the page setup and directly enter the analysis state.

[0071] Multiple windows can be opened simultaneously, displaying different calculation results, design schemes, or results at different time steps side by side. All views are based on the same data source and support linked operations, facilitating direct observation of multiphysics coupling effects, comparison of design schemes, and quick identification of the root cause of problems, avoiding the hassle and cognitive fragmentation of repeatedly switching between multiple software windows.

[0072] It allows multiple basic components to be combined and encapsulated into a fully functional composite component. Users can directly drag and drop this composite component to quickly reuse a set of complex functions, greatly simplifying the operation. Technical experts can use this to create high-level analysis modules that are ready to use out of the box for the team to use directly;

[0073] You can save your verified and efficient analysis methods, including component layout, data mapping logic, and judgment criteria, as an analysis template for easy reuse or to share with others. Each time you use it or on different devices, you only need to open the corresponding template, eliminating the need to repeatedly build the same template, saving time and improving efficiency.

[0074] To implement the above method, the present invention also provides a post-processing system for CAE software simulation calculation results, specifically including:

[0075] 1. Calculation result file input module

[0076] The input module for the results file mainly reads the calculation results file, verifies the parameters in it, and provides warnings for cases that do not meet the preset requirements.

[0077] 2. Data Model Parsing Module

[0078] The results of simulation calculations generally include the mesh elements, physical field values, and element properties from the simulation data. Mesh element types may include tetrahedrons, hexahedrons, triangular prisms, etc. Each element includes: node coordinates and node indices. Physical field values ​​typically include numerical results such as stress, strain, temperature, velocity, and displacement. Element properties may include, for example, interface fronts in casting processes or element birth / death in additive manufacturing processes.

[0079] The data model parsing module is responsible for analyzing the simulation calculation result file. Following the logic described above, it categorizes and splits the entire simulation data into datasets, such as mesh nodes, cell datasets, temperature field node datasets, and displacement datasets (which typically have X, Y, and Z components), resulting in three-dimensional datasets. Each dataset is labeled with a time-series-like tag representing a calculation step.

[0080] 3. Data Mapping Model Configuration Module

[0081] This section uses a visualization approach to establish a mapping relationship between the dataset and post-processing visualization components. These components primarily include 3D visualization components such as contour plots, vector graphics, and voxel rendering; chart components, mainly multi-dimensional line graphs; animation components, such as contour plot changes with each calculation step; and a calculation report component, which requires the visualization interface editor module from Part 5.

[0082] The data mapping model is configured by establishing data mapping relationships through a list of datasets and the interfaces exposed by different components. For example, the cloud map component renders the physical field of the result after color mapping at the node and accepts a one-dimensional dataset. Since the exposed interface is also a one-dimensional dataset, the corresponding one-dimensional dataset can be selected from the dataset list, such as temperature or equivalent stress, depending on the interface.

[0083] 4. Data Flow Engine Module

[0084] The workflow engine module primarily addresses data processing of split datasets based on data flows generated by multiple filters. These filters include, but are not limited to: data type filters, visualization filters, and sampling type filters. Data type filters handle mathematical operations and precision calculations. Visualization filters address interface cropping, contour mapping, and streamlines. Sampling type filters handle point and linear interpolation point sampling. Filters can be cascaded to form a data processing flow.

[0085] 5. Visual Interface Editor Module

[0086] A key module of this invention is the visual interface editor, which provides a visual interface with pre-packaged components described in the data mapping module. Users can easily build most post-processing pages by dragging and dropping. Based on the specific business requirements of the post-processing visualization, users can select the required component types from the component library and place them on the interface by dragging and dropping. An interface can combine multiple components, or components can be nested within each other to form a nested relationship.

[0087] The components can be categorized (including but not limited to) 3D visualization components, chart components, animation components, calculation report components, and control components. The following is a description of each component:

[0088] (1) 3D visualization components: Visualization of 3D data simulation results is the core part of the entire post-processing. Common encapsulated components include: cloud maps, vector maps, voxel rendering, etc. Visualization components need to define the data interfaces for external communication. For example, the data dimension in the cloud map component is 1, the corresponding data dimension in the vector map component is 3, and the voxel rendering component is a raster data type.

[0089] (2) Chart components: mainly multi-dimensional curve charts, the most commonly used of which are multiple curves. The horizontal axis is the calculation step, and the vertical axis can be the maximum value of the current physical field or the physical field value of a certain node. The physical field can be temperature, stress, etc.

[0090] (3) Animation component: changes in the cloud map as the calculation step progresses, or changes in the hidden surface of the model under the unit attribute.

[0091] (4) Calculation report component: Another feature of this invention is that the content of the calculation report often has different physical field cloud map outputs. At this time, a calculation report template can be formed by dragging and dropping. After the calculation is completed, it is dynamically output as a text and image report, and the layout is relatively flexible.

[0092] The calculation report will include common front-end UI components, such as text and tables.

[0093] (5) Control components: These components are mainly used to form the layout control of a component.

[0094] For CAE simulation computing scenarios, this system provides an interface editor that better meets the needs of business post-processing visualization. It generates post-processing visualization interfaces through dataset configuration; simulation computing reports are generated by dragging and dropping, which is more flexible and can better meet customized business needs; through the process engine and visualization interface editor, this system better preserves the user's post-processing operation process and solidifies it into a specific interface, saving users time from repeated operations; it also effectively decouples the logical relationship between the entire simulation data result file and the post-processing visualization, making the combination of post-processing visualizations more flexible.

[0095] The following description, in conjunction with specific examples, provides further details.

[0096] There is a requirement for the development of a post-processing interface, which needs to generate a post-processing interface with a total displacement cloud map and a curve of the displacement of a certain point.

[0097] Based on the above requirements, the following steps can be taken:

[0098] 1. Based on the calculation file, input the calculation results into the module and verify whether the data types of the parameters in the file meet the expected requirements.

[0099] 2. Based on the obtained simulation result calculation file, the simulation results are split into a mesh dataset, a displacement field numerical dataset, and a time series of calculation steps for each field. The mesh dataset includes the tetrahedral mesh index and the coordinates of the mesh nodes, while the displacement field dataset includes data in three dimensions: X, Y, and Z.

[0100] 3. Establish the mapping relationship between the dataset and the 3D visualization component. Since the cloud map visualization component requires one-dimensional data, the displacement field data needs to be processed, data filters configured, and data type operations used: X_total = Math.sqrt(x * x + y * y + z * z). This converts the three-dimensional data into one dimension for integration with the cloud map visualization component. The data interface for the curve chart is a set of coordinate points, a one-dimensional dataset (vertical axis), and an indicator (horizontal axis). Therefore, specify coordinate points (x1, y1) and (x2, y2), with the X_total dataset representing the chart dimension and the calculation step size representing the indicator. This completes the data mapping and data filter configuration.

[0101] 4. Configure the top-level menu parameters on the left side of the interface as an index to the current interface, such as configuring "Displacement Cloud Map and Point Tracking". In the interface, drag and drop the displacement cloud map component and the curve chart of the point set onto the page to form a visualization page of the post-processing results. Finally, publish and launch the page.

[0102] The entire post-processing result visualization process is now complete.

[0103] If the post-processing result visualization interface needs to be modified during the project's progress, the page can be modified in the visualization editor without changing the code. Project maintenance personnel can complete the entire interface modification.

[0104] This invention has been described through several embodiments. Those skilled in the art will recognize that various changes or equivalent substitutions can be made to these features and embodiments without departing from the spirit and scope of the invention. Furthermore, under the teachings of this invention, modifications can be made to these features and embodiments to adapt to specific situations and materials without departing from the spirit and scope of the invention. Therefore, this invention is not limited to the specific embodiments disclosed herein, and all embodiments falling within the scope of the claims of this application are protected by this invention.

Claims

1. A post-processing method for CAE software simulation calculation results, characterized in that: It includes the following steps: Step 1: Read the simulation calculation results from the CAE software and verify the parameters therein; Step 2: Analyze the simulation data calculated by the CAE software and split the data into datasets; Step 3: Establish the mapping relationship between the dataset and the post-processing visualization components; Step 4: Configure the data filters that may exist in the mapping relationship; Step 5: Edit the visual interface using a visual editor according to your needs.

2. The post-processing method for CAE software simulation calculation results according to claim 1, characterized in that: Step 1 also includes issuing warnings for situations where preset conditions are not met.

3. The post-processing method for CAE software simulation calculation results according to claim 2, characterized in that: The simulation dataset includes grid cells, physical field values, and cell attributes. Step 2, as mentioned above, classifies and splits the entire simulation data into datasets, with each dataset containing a time-series label for a computational step.

4. The post-processing method for CAE software simulation calculation results according to claim 3, characterized in that: The post-processing visualization components in Step 3 include 3D visualization components, chart components, animation components, calculation report components, and control components. Data mapping relationships are established through a dataset list and the open interfaces of each component.

5. A post-processing method for CAE software simulation calculation results according to claim 4, characterized in that: The visual editor described in Step 5 has the components described in Step 3 built-in. Depending on specific business needs, the post-processing page can be implemented by dragging and dropping components.

6. A post-processing method for CAE software simulation calculation results according to claim 5, characterized in that: The visual editor can open multiple visual interfaces simultaneously, and a single visual interface can combine multiple components, which can be nested within each other to form a nested relationship.

7. A system for implementing the method of any one of claims 1-6, characterized in that: It includes a calculation result file input module, a data model parsing module, a data mapping model configuration module, a data flow engine module, and a visual interface editor module, which are used to implement steps 1-5 respectively.

8. A post-processing system for CAE software simulation calculation results according to claim 7, characterized in that: The data flow engine module is based on a data flow formed by multiple filters and is used to solve the data processing function of the split dataset.

9. A post-processing system for CAE software simulation calculation results according to claim 8, characterized in that: The filters can be connected in series to form a data processing flow.

10. A post-processing system for CAE software simulation calculation results according to claim 9, characterized in that: The functionality of the visualization editing module depends on the data mapping model configuration module, which encapsulates each component. The visualization interface editor has a built-in component library containing pre-encapsulated components. Based on the specific business requirements of post-processing visualization, users can select the required component type from the component library and drag it to the visualization interface.