Methods, apparatus, equipment and media for generating and running aircraft simulation test schemes for CFD software

By splitting the aircraft simulations of CFD software into model and parameter files and storing them in a distributed manner, and combining the gRPC protocol and semantic tags to build a test scheme, the problems of CFD software testing relying on manual configuration and chaotic version management are solved, realizing automated execution and result traceability, and improving testing efficiency and reproducibility.

CN122884863BActive Publication Date: 2026-11-10CALCULATION AERODYNAMICS INST CHINA AERODYNAMICS RES & DEV CENT
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202611381541.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2026-09-08
Publication Date
2026-11-10
Estimated Expiration
2046-09-08

AI Technical Summary

Technical Problem

Existing CFD software testing solutions rely on manual configuration, resulting in chaotic version management, low test execution efficiency, and difficulty in efficient scheduling within distributed computing clusters.

Method used

The CFD software splits the aircraft CFD cases into model files and parameter files, which are distributed and stored on storage nodes. The historical call frequency of the model files is cached in the cache space. A communication link is established based on the gRPC protocol. The version management level of the parameter files is divided into project-level and process-level cases. A virtual node tree is constructed through semantic tags and a preset mapping rule base. The test plan is constructed by traversing from top to bottom and is run automatically on the execution node.

Benefits of technology

It realizes the automated execution and full-link traceability of CFD test cases, improves test efficiency, reproducibility and scalability, reduces the storage pressure and network bandwidth pressure of execution nodes, and supports accurate recording and synchronization of parameter versions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122884863B_ABST
    Figure CN122884863B_ABST
Patent Text Reader

Abstract

This application discloses a method, apparatus, equipment, and medium for generating and running test schemes for aircraft computational fluid dynamics (CFD) software, involving the field of computational fluid dynamics technology. The method includes: splitting aircraft CFD cases into model files and parameter files and distributing them to storage nodes; classifying aircraft CFD cases into project-level cases and process-level cases based on the version management level corresponding to the parameter files; determining target process-level cases and target parameter files; determining target matching rules based on the file structure of the target process-level cases and the key-value pairs of the target parameter files; traversing the virtual node tree layer by layer in a top-down order to construct the target test scheme; and running the test scheme on the execution node if the configured test scheme meets the preset trigger conditions. This avoids the problems of manual configuration, chaotic version management, and low test execution efficiency associated with generating test schemes based on CFD cases.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of computational fluid dynamics, and in particular to a method, apparatus, equipment, and medium for generating and running aircraft simulation test schemes for CFD software. Background Technology

[0002] Computational Fluid Dynamics (CFD) software is a core simulation tool in aerospace, automotive engineering, energy and power industries. It involves a large number of simulation examples, complex parameter configurations, and frequent iterations. However, to ensure the accuracy and reliability of the simulation results, it is essential to construct test plans based on these examples to conduct large-scale, systematic testing of the CFD software. Traditionally, CFD software testing relies on engineers manually writing shell scripts, Python scripts, or using batch processing interfaces of commercial simulation platforms, triggering execution manually and recording logs. With the expansion of simulation scale and the increasing demand for automation, the concepts of Continuous Integration (CI) / Continuous Delivery (CD) have been gradually introduced, attempting to incorporate CFD software testing into an automated pipeline.

[0003] Currently, the closest technical solutions to this invention are mainly reflected in the following two types of systems: First, there are CFD software testing automation systems based on script templates. These systems use predefined Shell / Python script templates to solidify typical test processes into scripts. Users need to manually copy the template, replace the parameter file path, configure the execution command, and trigger execution through Jenkins or GitLabCI. In these systems, the test logic is strongly bound to the test case type; adding a new test case requires rewriting the script, resulting in long test preparation times and non-universal test scripts. During test execution, the system only reads parameter data from the current workspace, without parameter version management, making it impossible to optimize parameter versions for other test processes. Furthermore, the test case's model file and parameter file are stored together, requiring synchronization of the entire test case directory for each push or update, resulting in significant network and storage overhead. Second, there are systems that provide built-in test modules / test case managers. These allow users to create test sequences and bind parameters, but they are essentially manual configuration tools, unable to automatically identify the meaning of parameters in user-uploaded CFD test cases, still requiring manual selection of test items. Moreover, these built-in modules / managers do not achieve separate storage and caching acceleration of model files and parameter files, making efficient scheduling in distributed computing clusters impossible.

[0004] As can be seen from the above, how to avoid the problems of relying on manual configuration, chaotic version management, and low test execution efficiency in the generation of test schemes based on CFD cases is an urgent issue to be solved. Summary of the Invention

[0005] In view of this, the purpose of this invention is to provide a method, apparatus, device, and medium for generating and running test schemes for aircraft computational simulations based on CFD software, which can avoid the problems of manual configuration, chaotic version management, and low test execution efficiency in the generation of test schemes based on CFD simulations. The specific solution is as follows: Firstly, this application provides a method for generating and running aircraft simulation test schemes for CFD software, including: The CFD software splits the CFD case files corresponding to the aircraft CFD cases into model files and parameter files, and based on the differences in the change frequency and storage volume of the aircraft CFD cases, the model files and parameter files are distributed and stored to storage nodes. The target model file is determined by utilizing the historical call frequency of the model file, and the target model file is cached in the cache space. A communication link between the storage node, the cache space, and the execution node is established based on the gRPC protocol. Based on the version management level corresponding to the parameter file, the aircraft CFD case is divided into project-level case and process-level case. The corresponding target process-level case and target parameter file are determined using the communication link and the target aircraft CFD case to be tested. Semantic tags are determined based on the file structure of the target process-level case and the key-value pairs of the target parameter file. The semantic tags are matched with each rule in the preset mapping rule library, and the target matching rule is determined using the matching results. A virtual node tree is constructed based on the target matching rule and the target parameter file. The virtual node tree is traversed layer by layer in a top-down order, and the target test plan is constructed using the traversal results. The target test plan is configured to obtain a configured test plan. If the configured test plan meets the preset triggering conditions, the configured test plan is run on the execution node to obtain the test results of the target aircraft CFD case. The configured test plan is bound to the parameter version identifier of the target process-level case. If the test results meet the preset test evaluation conditions, the parameter version of the target process-level example will be submitted to the project-level example to update the parameter version library of the project-level example.

[0006] Optionally, the step of splitting the CFD case file corresponding to the aircraft CFD case in the CFD software into a model file and a parameter file, and distributing the model file and the parameter file to storage nodes based on the differences in the change frequency and storage volume of the aircraft CFD case, includes: Obtain the aircraft CFD case from the CFD software, and split the case file corresponding to the aircraft CFD case into model file and parameter file based on the storage information and purpose of the aircraft CFD case; Based on the differences in the change frequency and storage volume of the CFD case of the aircraft, the model file and the parameter file are distributed and stored to storage nodes.

[0007] Optionally, the step of determining the corresponding target process-level calculation case and target parameter file using the communication link and the CFD calculation case of the target aircraft under test includes: Obtain the CFD case of the target aircraft to be tested, and determine whether the CFD case of the target aircraft already has a test plan; If the target aircraft CFD case already has a test plan, and the target parameter file corresponding to the target aircraft CFD case has been updated, then the test plan corresponding to the target aircraft CFD case is obtained from the database, and the test plan is updated using the updated target parameter file to obtain the target test plan. If the target aircraft CFD case does not have a test scheme, then the step of determining the corresponding target process-level case and target parameter file using the communication link and the target aircraft CFD case to be tested is triggered.

[0008] Optionally, the step of determining the corresponding target process-level calculation case and target parameter file using the communication link and the CFD calculation case of the target aircraft under test, and determining semantic tags based on the file structure of the target process-level calculation case and the key-value pairs of the target parameter file, includes: The target aircraft CFD case to be tested is identified as a target process-level case, and the target parameter file corresponding to the target aircraft CFD case is determined. The file structure of the target process-level example is parsed to obtain the corresponding metadata, and the target parameter file is semantically identified to obtain key-value pairs; Test guidance parameters are extracted from the key-value pairs, and semantic tags are constructed based on the test guidance parameters and the metadata.

[0009] Optionally, the step of matching the semantic tags with each rule in a preset mapping rule base, determining the target matching rule using the matching results, and constructing a virtual node tree based on the target matching rule and the target parameter file includes: The semantic tags are matched with each rule in the preset mapping rule base, and the target matching rule is constructed using the successfully matched rules; A virtual node tree is constructed based on a preset rule nesting structure, and the configuration item information of the target parameter file and the target matching rule are written into the corresponding virtual nodes in the virtual node tree; the structure of the virtual node tree corresponds one-to-one with the configuration item structure of the target parameter file; the preset rule nesting structure corresponds to the nested key-value pair structure of the target parameter file.

[0010] Optionally, the step of traversing the virtual node tree layer by layer in a top-down order and constructing the target test plan using the traversal results includes: The virtual node tree is traversed layer by layer in a top-down order. The currently traversed virtual node is determined as the current virtual node, and it is determined whether the current virtual node is a leaf node of the virtual node tree. If it is a leaf node of the virtual node tree, then the corresponding test configuration item is constructed based on the configuration information in the current virtual node; If it is not a leaf node of the virtual node tree, then the corresponding test configuration item is constructed based on the configuration information in the current virtual node and using a preset composite construction strategy, and the configuration information in the current virtual node is distributed to the child node corresponding to the current virtual node. Jump to the step of determining whether the current virtual node is a leaf node of the virtual node tree, until all virtual nodes in the virtual node tree have been traversed to obtain the corresponding test configuration items. Summarize the test configuration items to obtain the target test plan.

[0011] Optionally, the configured test plan is obtained by configuring the target test plan. If the configured test plan meets the preset triggering conditions, the configured test plan is run on the execution node to obtain the test results of the target aircraft CFD example, including: The timeout time and runtime record export location of the target test plan are adjusted based on the configuration instructions triggered by the visual interface to obtain the configured test plan; Determine the target triggering method for the configured test plan; the target triggering method is any one of manual execution, code submission triggering, and scheduled execution. Based on the target triggering method, determine whether the configured test scheme meets the preset triggering conditions; If the configured test scheme meets the preset triggering conditions, the test task corresponding to the configured test scheme is scheduled to the execution node using the communication link, so as to run the configured test scheme based on the execution node, and obtain the test results, process log and comparison curve of the target aircraft CFD case; the comparison curve is a comparison curve between the CFD result corresponding to the current test and the preset reference CFD result.

[0012] Secondly, this application provides a device for generating and running aircraft simulation test schemes for CFD software, comprising: The case splitting module is used to split the case files corresponding to the aircraft CFD cases in the CFD software into model files and parameter files, and based on the differences in the change frequency and storage volume of the aircraft CFD cases, distribute the model files and parameter files to storage nodes. The communication link establishment module is used to determine the target model file by utilizing the historical call frequency of the model file, cache the target model file in the cache space, and establish a communication link between the storage node, the cache space and the execution node based on the gRPC protocol; The semantic tag determination module is used to divide the aircraft CFD case into project-level cases and process-level cases based on the version management level corresponding to the parameter file, determine the corresponding target process-level case and target parameter file using the communication link and the target aircraft CFD case to be tested, and determine semantic tags based on the file structure of the target process-level case and the key-value pairs of the target parameter file. The test scheme construction module is used to match the semantic tags with each rule in the preset mapping rule library, determine the target matching rule using the matching results, construct a virtual node tree based on the target matching rule and the target parameter file, traverse the virtual node tree layer by layer in a top-down order, and construct the target test scheme using the traversal results. The test plan execution module is used to configure the target test plan to obtain the configured test plan. If the configured test plan meets the preset triggering conditions, the configured test plan is run on the execution node to obtain the test results of the target aircraft CFD example. The configured test plan is bound to the parameter version identifier of the target process-level example. The parameter version submission module is used to submit the parameter version of the target process-level example to the project-level example if the test result meets the preset test evaluation conditions, so as to update the parameter version library of the project-level example.

[0013] Thirdly, this application provides an electronic device, comprising: Memory, used to store computer programs; A processor is used to execute the computer program to implement the aforementioned method for generating and running aircraft simulation test schemes for CFD software.

[0014] Fourthly, this application provides a computer-readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the aforementioned method for generating and running aircraft simulation test schemes for CFD software.

[0015] This application splits the CFD case files corresponding to aircraft CFD cases in CFD software into model files and parameter files. Based on the differences in the change frequency and storage volume of the aircraft CFD cases, the model files and parameter files are distributed and stored on storage nodes. The target model file is determined using the historical call frequency of the model file, and the target model file is cached in the cache space. A communication link is established between the storage nodes, the cache space, and the execution nodes based on the gRPC protocol. Based on the version management level corresponding to the parameter file, the aircraft CFD cases are divided into project-level cases and process-level cases. The corresponding target process-level cases and target parameter files are determined using the communication link and the target aircraft CFD cases to be tested. The file structure of the target process-level cases and the key-value pairs of the target parameter files are used to determine the... Semantic tags are used to match the semantic tags with rules in a preset mapping rule base. The matching results are used to determine the target matching rule. A virtual node tree is constructed based on the target matching rule and the target parameter file. The virtual node tree is traversed layer by layer in a top-down order, and the traversal results are used to construct a target test plan. The target test plan is configured to obtain a configured test plan. If the configured test plan meets preset triggering conditions, it is run on the execution node to obtain the test results of the target aircraft CFD example. The configured test plan is bound to the parameter version identifier of the target process-level example. If the test results meet preset test evaluation conditions, the parameter version of the target process-level example is submitted to the project-level example to update the parameter version base of the project-level example.

[0016] As can be seen from the above, this application splits the aircraft CFD test case into model files and parameter files and distributes them to storage nodes. The target model file is determined by the historical call frequency of the model file and cached in the cache space. A communication link is established between the storage node, cache space, and execution node based on the gRPC protocol. Large but rarely modified model files no longer reside permanently on the execution node; the execution node only retrieves them on demand through the communication link, thereby reducing the storage and network bandwidth pressure on the execution node. Based on the version management hierarchy corresponding to the parameter file, the aircraft CFD test case is divided into project-level test cases and process-level test cases, ensuring that the parameter versions selected during testing are accurately recorded and supporting parameter file synchronization between process-level test cases and project-level test cases, as well as between process-level test cases of different processes. Semantic recognition is performed on the target parameter file to extract test guidance parameters and construct semantic tags. These semantic tags are then matched with rules in a preset mapping rule base. A virtual node tree is constructed based on the matched target matching rules and the target parameter file, and the target test scheme is constructed by traversing the virtual node tree layer by layer from top to bottom. In this way, after configuring the target test plan, the test plan can be automatically executed and the test results can be traced throughout the entire chain, which improves the testing efficiency, reproducibility and scalability of test plans built based on CFD cases. Attached Figure Description

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

[0018] Figure 1 This application discloses a flowchart of a method for generating and running a test scheme for aircraft computational simulations using CFD software. Figure 2 This is a schematic diagram illustrating the construction of a test scheme disclosed in this application; Figure 3 This is a schematic diagram of the architecture of a method for generating and running aircraft simulation test schemes for CFD software disclosed in this application; Figure 4 This application discloses a flowchart of a specific method for generating and running a test scheme for aircraft computational simulations using CFD software. Figure 5 This is a schematic diagram of the structure of a device for generating and running aircraft simulation test schemes for CFD software disclosed in this application; Figure 6 This is a structural diagram of an electronic device disclosed in this application. Detailed Implementation

[0019] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0020] Currently, the testing process based on aircraft CFD simulations generally suffers from problems such as reliance on manual configuration for test plan generation, chaotic version management, and low test execution efficiency, which severely restricts the automation and large-scale application of CFD simulation workflows. To address this, this application provides a method for generating and running test plans for aircraft simulations using CFD software. After configuring the target test plan, it achieves automated execution of the test plan and full-chain traceability of test results, improving the testing efficiency, reproducibility, and scalability of test plans built based on CFD simulations.

[0021] See Figure 1 As shown, this embodiment of the invention discloses a method for generating and running aircraft simulation test schemes for CFD software, including: Step S11: Split the CFD case file corresponding to the aircraft CFD case in the CFD software into a model file and a parameter file, and based on the differences in the change frequency and storage volume of the aircraft CFD case, distribute the model file and the parameter file to the storage node.

[0022] In this embodiment, an aircraft CFD case is obtained from CFD software. Based on the storage information and function of the aircraft CFD case, the case file corresponding to the aircraft CFD case is split into a model file and a parameter file. Based on the differences in the change frequency and storage volume of the aircraft CFD case, the model file and the parameter file are distributed and stored on storage nodes. The change frequency can be the number of times the corresponding case file is modified per unit time, which can be specifically counted by reading the commit records of the case file in the version control system or reading the modification timestamp sequence of the case file in the file system. The storage volume is the disk space occupied by the corresponding case file. Then, the model file and the parameter file are distributed and stored on storage nodes.

[0023] Specifically, the step of splitting the case file corresponding to the aircraft CFD case in the CFD software into model files and parameter files, and distributing the model files and parameter files to storage nodes based on the differences in the change frequency and storage volume of the aircraft CFD case, includes: obtaining the aircraft CFD case in the CFD software; splitting the case file corresponding to the aircraft CFD case into model files and parameter files based on the storage information and purpose of the aircraft CFD case; and distributing the model files and parameter files to storage nodes based on the differences in the change frequency and storage volume of the aircraft CFD case.

[0024] Step S12: Determine the target model file using the historical call frequency of the model file, cache the target model file in the cache space, and establish a communication link between the storage node, the cache space and the execution node based on the gRPC protocol.

[0025] In this embodiment, the historical call frequency can be the cumulative number of times the model file is called by the test task within a preset sliding statistics window. Model files with a historical call frequency greater than a preset frequency threshold are identified as target model files; alternatively, the model files are sorted from highest to lowest historical call frequency, and the model file with the highest ranking in the sorting result is identified as the target model file.

[0026] Understandably, by caching the target model file to the cache space, when the execution node needs to use the target model file, it can directly read it from the cache space without having to remotely retrieve it from the storage node, thereby improving the synchronization efficiency of the example files. The cache space can be a high-speed storage space deployed on the execution node cluster side, built on solid-state drives or memory. Furthermore, when the remaining capacity of the cache space is lower than a preset capacity threshold, model files in the cache space can be evicted in order of historical call frequency from low to high, ensuring that the cache space always stores the most frequently used model files.

[0027] Furthermore, while establishing a communication link between the storage node, the cache space, and the execution node is based on the gRPC protocol, other communication protocols that support streaming can also be used to replace the gRPC protocol in establishing the above communication link, as long as efficient synchronization of example files between the storage node, the cache space, and the execution node can be achieved.

[0028] Step S13: Based on the version management level corresponding to the parameter file, divide the aircraft CFD case into project-level cases and process-level cases. Use the communication link and the target aircraft CFD case to be tested to determine the corresponding target process-level case and target parameter file. Determine semantic tags based on the file structure of the target process-level case and the key-value pairs of the target parameter file.

[0029] In this embodiment, aircraft CFD cases are divided into project-level cases and process-level cases according to the version management level of the parameter files. Project-level cases are uniformly maintained within the project scope. Operations such as adding versions, switching versions, and viewing version logs can be performed on the parameter files of project-level cases; that is, the parameter files of project-level cases constitute the parameter version library of the project. Process-level cases are cases selected during testing and are used to generate test plans. Process-level cases can synchronize parameter files from project-level cases or from process-level cases of other processes. Furthermore, after the test corresponding to a process-level case passes, the parameter file of that process-level case can be submitted and updated to the project-level cases. This satisfies the need for rapid and accurate recording of case parameter versions during testing and facilitates efficient synchronization and backtracking of case parameter versions between processes and between processes and projects.

[0030] It is understandable that when a parameter file is modified and saved, a unique parameter version identifier is generated for the parameter file. The parameter version identifier can be composed of a version number, a generation timestamp, a submitting user identifier, and a summary of the parameter file content. The parameter version identifier and the parameter file content are recorded together in the version log so that a complete snapshot of the version can be viewed later.

[0031] Furthermore, the system obtains the target aircraft CFD case selected by the user. If the parameter file of the target aircraft CFD case has only updated values ​​and its configuration item structure has not changed, data is automatically injected based on the original test plan. The values ​​of the corresponding configuration items in the test plan are replaced with the values ​​of the current parameter version to improve the test plan update efficiency in scenarios with high-frequency parameter iteration. Specifically, it can be determined whether the parameter file has only updated values ​​by comparing whether the key path set of the parameter file before and after the update is consistent. If the key path set is consistent, it is determined that only values ​​have been updated, and the above injection update process is executed; if the key path set has been added or deleted, it is determined that the configuration item structure has changed, triggering the step of determining the corresponding target process-level case and target parameter file using the communication link and the target aircraft CFD case to be tested.

[0032] Specifically, the step of determining the corresponding target process-level calculation case and target parameter file using the communication link and the target aircraft CFD calculation case to be tested includes: obtaining the target aircraft CFD calculation case to be tested and determining whether the target aircraft CFD calculation case already has a test plan; if the target aircraft CFD calculation case already has a test plan and the target parameter file corresponding to the target aircraft CFD calculation case has been updated, then the test plan corresponding to the target aircraft CFD calculation case is obtained from the database, and the test plan is updated using the updated target parameter file to obtain the target test plan; if the target aircraft CFD calculation case does not have a test plan, then the step of determining the corresponding target process-level calculation case and target parameter file using the communication link and the target aircraft CFD calculation case to be tested is triggered.

[0033] In this embodiment, a target aircraft CFD case is acquired and identified as a target process-level case. The parameter file corresponding to the parameter file version selected by the user is identified as the target parameter file. The file structure of the target process-level case and the content of the target parameter file are read from the storage node through the communication link. The file structure of the target process-level case is parsed to obtain the corresponding metadata. The metadata may include the hierarchical relationship of the case directory, the file name and extension of each case file, the case type identifier, the reference relationship between the model file and the parameter file, and the solver type corresponding to the case. Semantic recognition is performed on the target parameter file to parse it into several key-value pairs consisting of keys and values. Test guidance parameters are extracted from the key-value pairs, and semantic tags are constructed based on the test guidance parameters and the metadata. The test guidance parameters are parameters in the key-value pairs that have test guidance significance, such as turbulence model type, boundary condition type, time progression method, result output path, etc.

[0034] Specifically, the step of determining the corresponding target process-level computational instance and target parameter file using the communication link and the target aircraft CFD computational instance to be tested, and determining semantic tags based on the file structure of the target process-level computational instance and the key-value pairs of the target parameter file, includes: determining the target aircraft CFD computational instance to be tested as a target process-level computational instance, and determining the target parameter file corresponding to the target aircraft CFD computational instance; parsing the file structure of the target process-level computational instance to obtain the corresponding metadata, and performing semantic recognition on the target parameter file to obtain key-value pairs; extracting test guidance parameters from the key-value pairs, and constructing semantic tags based on the test guidance parameters and the metadata.

[0035] Step S14: Match the semantic tags with each rule in the preset mapping rule library, and use the matching results to determine the target matching rule. Construct a virtual node tree based on the target matching rule and the target parameter file. Traverse the virtual node tree layer by layer in a top-down order, and use the traversal results to construct the target test plan.

[0036] In this embodiment, each rule in the preset mapping rule library is stored in the form of a JSON file. Each rule in the preset mapping rule library may include a matching condition field and a test construction field. The matching condition field is used to describe the semantic tags to which the rule applies. The test construction field may include a steps field, a command field, a log_path field, a compare field, and a timeout field, which are used to describe the test steps, execution commands, log paths, result comparison items, and timeout duration corresponding to the rule, respectively.

[0037] Understandably, the test scheme generation engine traverses the preset mapping rule base, matching the semantic tags of the target aircraft CFD instance with each rule in the preset mapping rule base. If the semantic tag described by the matching condition field of a rule is consistent with or covered by the semantic tag of the current instance, the rule is considered to have matched successfully and is activated. Then, the target matching rule is constructed using the successfully matched rules. When there are multiple successfully matched rules, the test construction fields corresponding to each rule can be merged according to their preset priority from high to low. In cases where the same field conflicts, the value of the rule with higher priority is used, thus obtaining the target matching rule.

[0038] It should be noted that since the preset mapping rule library is stored in a separate JSON file, when adding a new type of aircraft CFD case or a new test configuration item, it is only necessary to add the corresponding rule entry to the JSON file, without modifying the system source code or redeploying the system. The rules can be applied by hot-loading after being added.

[0039] In this embodiment, a virtual node tree is constructed based on a preset rule nesting structure, and the configuration item information of the target parameter file and the target matching rule are written into the corresponding virtual node in the virtual node tree; wherein, the structure of the virtual node tree corresponds one-to-one with the configuration item structure of the target parameter file, and the preset rule nesting structure corresponds to the nested key-value pair structure of the target parameter file, that is, each configuration item in the target parameter file corresponds to a virtual node in the virtual node tree.

[0040] Specifically, the step of matching the semantic tags with each rule in the preset mapping rule library, determining the target matching rule using the matching results, and constructing a virtual node tree based on the target matching rule and the target parameter file includes: matching the semantic tags with each rule in the preset mapping rule library, and constructing the target matching rule using the successfully matched rule; constructing a virtual node tree based on a preset rule nesting structure, and writing the configuration item information of the target parameter file and the target matching rule into the corresponding virtual nodes in the virtual node tree; the structure of the virtual node tree corresponds one-to-one with the configuration item structure of the target parameter file; the preset rule nesting structure corresponds to the nested key-value pair structure of the target parameter file.

[0041] Understandable, Figure 2 This diagram illustrates a test scheme construction. The virtual node tree is traversed layer by layer in a top-down order. The currently traversed virtual node is identified as the current virtual node. It is then determined whether the current virtual node is a leaf node of the virtual node tree. If it is a leaf node, it indicates that the configuration item corresponding to this virtual node no longer contains lower-level configuration items. A corresponding test configuration item is constructed based on the configuration information in the current virtual node. If it is not a leaf node, it indicates that the configuration item corresponding to this virtual node is a nested configuration item. In this case, a corresponding test configuration item is constructed based on the configuration information in the current virtual node and using a preset composite construction strategy. The preset composite construction strategy is a construction strategy corresponding to nested configuration items, used to construct the configuration information of the virtual node itself into a composite configuration segment in the test scheme. The configuration information in the current virtual node is distributed to its corresponding child nodes, allowing child nodes to directly inherit the configuration information when constructing their test configuration items. This distribution of configuration information only occurs in non-leaf nodes; it does not occur in leaf nodes. Then, the process jumps to the step of determining whether the current virtual node is a leaf node of the virtual node tree. This determination and construction process is repeated for the next virtual node until all virtual nodes in the virtual node tree have been traversed, thus obtaining the corresponding test configuration items. All the test configuration items are then summarized to obtain the target test plan.

[0042] Specifically, the step of traversing the virtual node tree layer by layer in a top-down order and constructing a target test plan using the traversal results includes: traversing the virtual node tree layer by layer in a top-down order, determining the currently traversed virtual node as the current virtual node, and determining whether the current virtual node is a leaf node of the virtual node tree; if it is a leaf node, constructing a corresponding test configuration item based on the configuration information in the current virtual node; if it is not a leaf node, constructing a corresponding test configuration item based on the configuration information in the current virtual node and using a preset composite construction strategy, and distributing the configuration information in the current virtual node to the child nodes corresponding to the current virtual node; jumping to the step of determining whether the current virtual node is a leaf node of the virtual node tree, until all virtual nodes in the virtual node tree have been traversed to obtain the corresponding test configuration items, and summarizing each test configuration item to obtain the target test plan.

[0043] Step S15: Configure the target test plan to obtain the configured test plan. If the configured test plan meets the preset triggering conditions, run the configured test plan on the execution node to obtain the test results of the target aircraft CFD example. The configured test plan is bound to the parameter version identifier of the target process-level example.

[0044] In this embodiment, the user client can directly perform secondary configuration of the target test plan through a visual interface; this step is optional. Specifically, based on the configuration instructions triggered by the visual interface, the timeout time and the location for exporting execution records of the target test plan are adjusted to obtain the configured test plan. The timeout time is used to limit the maximum duration a single test task is allowed to occupy an execution node, and the location for exporting execution records specifies the export directory for process logs and result files. Additionally, the user client can also adjust the number of parallel cores, the number of failure retries, the result comparison threshold, and the notification method after test completion in the visual interface. This application does not limit the specific content of the secondary configuration and can adjust it according to actual circumstances.

[0045] It is understood that the target triggering method of the configured test plan is determined, and based on the target triggering method, it is determined whether the configured test plan meets the preset triggering conditions. When the target triggering method is manual execution, if an execution command triggered by the user on the visual interface is received, it is determined that the preset triggering conditions are met. When the target triggering method is code submission triggering, if a submission event of CFD software code in the code repository is detected, it is determined that the preset triggering conditions are met. When the target triggering method is scheduled execution, if the current time reaches the scheduled execution time of the user, it is determined that the preset triggering conditions are met. If the configured test scheme meets the preset triggering conditions, the test task corresponding to the configured test scheme is scheduled to the execution node using the communication link. After receiving the test task, the execution node pulls the CFD software code from the code repository and completes the compilation. It then obtains the model file corresponding to the target aircraft CFD example from the cache space through the communication link and obtains the target parameter file from the storage node. Based on the test steps in the configured test scheme, the test is executed to obtain the test results, process logs, and comparison curves of the target aircraft CFD example. The comparison curve is a comparison curve between the CFD result corresponding to the current test and the preset reference CFD result.

[0046] Furthermore, during test execution, the parameter version identifier of the target process-level instance is embedded into the configured test plan, thereby binding the configured test plan with the parameter version identifier of the target process-level instance; and after the test is completed, the parameter version identifier is linked to the configured test plan, the test results, the process log, and the comparison curve. Figure 1 The results are then stored in the database. When users view historical test results, they can directly click on the process-level case used in the current test to view a complete snapshot of the parameter versions used, thereby enabling backtracking of the test process.

[0047] Specifically, configuring the target test plan to obtain a configured test plan, if the configured test plan meets preset triggering conditions, then running the configured test plan on the execution node to obtain the test results of the target aircraft CFD instance, includes: adjusting the timeout time and run record export position of the target test plan based on configuration instructions triggered by the visual interface to obtain the configured test plan; determining the target triggering method of the configured test plan; the target triggering method is any one of manual execution, code submission triggering, and scheduled execution; judging whether the configured test plan meets the preset triggering conditions based on the target triggering method; if the configured test plan meets the preset triggering conditions, then using the communication link to schedule the test task corresponding to the configured test plan to the execution node, so as to run the configured test plan on the execution node to obtain the test results, process logs, and comparison curves of the target aircraft CFD instance; the comparison curve is a comparison curve between the CFD result corresponding to the current test and the preset reference CFD result.

[0048] Step S16: If the test result meets the preset test evaluation conditions, the parameter version of the target process-level example is submitted to the project-level example to update the parameter version library of the project-level example.

[0049] In this embodiment, if the test results of this test are outstanding, for example, if the deviation between the CFD result corresponding to the current test and the preset reference CFD result is less than the preset deviation threshold, or the number of iteration steps required to reach convergence is less than the preset step threshold, then the parameter version of the process-level test can be submitted as a sample to the project-level test, making it a reusable parameter version sample for other test processes to use synchronously.

[0050] As can be seen from the above, this application splits the CFD case files corresponding to the aircraft CFD cases in the CFD software into model files and parameter files. Based on the differences in the change frequency and storage volume of the aircraft CFD cases, the model files and parameter files are distributed and stored on storage nodes. The target model file is determined by the historical call frequency of the model file and cached in the cache space. A communication link is established between the storage nodes, cache space, and execution nodes based on the gRPC protocol. Large model files with few modifications no longer reside permanently on the execution nodes. The execution nodes only obtain them on demand through the communication link when needed, thereby reducing the storage pressure on the execution nodes. This approach addresses force and network bandwidth pressure. Based on the version management hierarchy corresponding to the parameter files, aircraft CFD cases are divided into project-level and process-level cases. This ensures accurate recording of the selected parameter versions during testing and supports parameter file synchronization between process-level and project-level cases, as well as between process-level cases of different processes. Semantic recognition is performed on the target parameter files to extract test guidance parameters and construct semantic tags. These semantic tags are then matched with rules in a pre-defined mapping rule base. A virtual node tree is constructed based on the matched target rules and the target parameter files, and the target test plan is built by traversing the virtual node tree layer by layer from top to bottom. This configuration of the target test plan enables automated execution and end-to-end traceability of test results, improving the testing efficiency, reproducibility, and scalability of test plans built based on CFD cases.

[0051] As can be seen from the above embodiments, this application achieves a rapid improvement in testing efficiency based on the dynamic construction of the test plan. Therefore, the process of dynamic construction based on the test plan is described.

[0052] Combination Figure 3 and Figure 4 As shown in the figure, this invention discloses a specific method for generating and running aircraft simulation test schemes for CFD software, including: In this embodiment, the CFD software to be tested is selected to initiate the test process, the target aircraft CFD case to be tested is determined, and it is determined whether the target aircraft CFD case already has a test plan. If the target aircraft CFD case already has a test plan and the target parameter file corresponding to the target aircraft CFD case has been updated, the test plan corresponding to the target aircraft CFD case is obtained from the database, and the test plan is updated using the updated target parameter file to obtain the target test plan.

[0053] It is understood that if the target aircraft CFD case does not have the test plan, the corresponding target process-level case and target parameter file are determined using the communication link and the target aircraft CFD case to be tested. The file structure of the target process-level case is parsed to obtain the corresponding metadata. Semantic recognition is performed on the target parameter file to obtain key-value pairs. Test guidance parameters are extracted from the key-value pairs, and semantic tags are constructed based on the test guidance parameters and the metadata. The semantic tags are matched with each rule in the preset mapping rule base, and the target matching rule is determined using the matching results. A virtual node tree is constructed based on the preset rule nesting structure, and the configuration item information of the target parameter file and the target matching rule are written into the corresponding virtual nodes in the virtual node tree. The virtual node tree is traversed layer by layer in a top-down order, and the target test plan is constructed using the traversal results.

[0054] Furthermore, the target test plan is reconfigured based on the visual interface. If the configured test plan meets the preset triggering conditions, the test task corresponding to the configured test plan is scheduled to the execution node using the communication link. After receiving the test task, the execution node first pulls the CFD software code from the code repository and completes the compilation, and then runs the configured test plan to obtain the test results, process logs, and comparison curves of the target aircraft CFD case. If the test results of this test are outstanding, the parameter version of this process-level case can be submitted as a sample to the project-level case, making it a reusable parameter version sample for other test processes to use synchronously.

[0055] As can be seen from the above, this application automatically generates test plans adapted to various types of test cases by allowing users to select test cases and parameter versions on the client side, which greatly shortens the test preparation time. When only the values ​​in the parameter files of the same test case are updated, the test plan is automatically updated without the need to regenerate the virtual node tree or reconfigure manually, thus improving iteration efficiency and solving the problem of test configuration lag caused by test case parameter changes. The hierarchical management of test cases and the binding of test plans with the parameter versions of process-level test cases enable frequently updated parameter versions to execute tests quickly and analyze test results by combining test records. Parameter versions with outstanding test results can be synchronized to the project level for management, thereby providing samples for other test processes.

[0056] Accordingly, see Figure 5 As shown, this application also provides a device for generating and running aircraft simulation test schemes for CFD software, including: The calculation case splitting module 11 is used to split the calculation case file corresponding to the aircraft CFD calculation case in the CFD software into model file and parameter file, and based on the difference in the change frequency and storage volume of the aircraft CFD calculation case, distribute the model file and the parameter file to the storage node. The communication link establishment module 12 is used to determine the target model file by utilizing the historical call frequency of the model file, cache the target model file in the cache space, and establish a communication link between the storage node, the cache space and the execution node based on the gRPC protocol; The semantic tag determination module 13 is used to divide the aircraft CFD case into project-level cases and process-level cases based on the version management level corresponding to the parameter file, determine the corresponding target process-level case and target parameter file using the communication link and the target aircraft CFD case to be tested, and determine semantic tags based on the file structure of the target process-level case and the key-value pairs of the target parameter file. The test scheme construction module 14 is used to match the semantic tags with each rule in the preset mapping rule library, determine the target matching rule using the matching results, construct a virtual node tree based on the target matching rule and the target parameter file, traverse the virtual node tree layer by layer in a top-down order, and construct the target test scheme using the traversal results. The test plan execution module 15 is used to configure the target test plan to obtain the configured test plan. If the configured test plan meets the preset triggering conditions, the configured test plan is run on the execution node to obtain the test results of the target aircraft CFD example. The configured test plan is bound to the parameter version identifier of the target process-level example. The parameter version submission module 16 is used to submit the parameter version of the target process-level example to the project-level example if the test result meets the preset test evaluation conditions, so as to update the parameter version library of the project-level example.

[0057] In some specific embodiments, the instance splitting module 11 may specifically include: The file splitting unit is used to obtain the aircraft CFD case in the CFD software and split the case file corresponding to the aircraft CFD case into model file and parameter file based on the storage information and purpose of the aircraft CFD case. The file storage unit is used to distribute and store the model file and the parameter file to storage nodes based on the differences in the change frequency and storage volume of the CFD case of the aircraft.

[0058] In some specific embodiments, the semantic tag determination module 13 may specifically include: The target test case determination unit is used to obtain the target aircraft CFD test case to be tested and determine whether the target aircraft CFD test case already has a test plan. The scheme update unit is used to obtain the test scheme corresponding to the CFD case of the target aircraft from the database if the CFD case of the target aircraft already has a test scheme and the target parameter file corresponding to the CFD case of the target aircraft has been updated, and update the test scheme using the updated target parameter file to obtain the target test scheme. The target file determination unit is used to trigger the step of determining the corresponding target process-level calculation case and target parameter file using the communication link and the target aircraft CFD calculation case to be tested if there is no test plan for the target aircraft CFD calculation case.

[0059] In some specific embodiments, the semantic tag determination module 13 may specifically include: The target calculation case determination unit is used to determine the target aircraft CFD calculation case to be tested as a target process-level calculation case, and to determine the target parameter file corresponding to the target aircraft CFD calculation case; The semantic recognition unit is used to parse the file structure of the target process-level example to obtain the corresponding metadata, and to perform semantic recognition on the target parameter file to obtain key-value pairs; A semantic tag construction unit is used to extract test guidance parameters from the key-value pairs and construct semantic tags based on the test guidance parameters and the metadata.

[0060] In some specific embodiments, the test scheme construction module 14 may specifically include: The rule building unit is used to match the semantic tags with each rule in the preset mapping rule library, and to build target matching rules using the successfully matched rules; The rule writing unit is used to construct a virtual node tree based on a preset rule nesting structure, and write the configuration item information of the target parameter file and the target matching rule into the corresponding virtual node in the virtual node tree; the structure of the virtual node tree corresponds one-to-one with the configuration item structure of the target parameter file; the preset rule nesting structure corresponds to the nested key-value pair structure of the target parameter file.

[0061] In some specific embodiments, the test scheme construction module 14 may specifically include: The node determination unit is used to traverse the virtual node tree layer by layer in a top-down order, determine the currently traversed virtual node as the current virtual node, and determine whether the current virtual node is a leaf node of the virtual node tree. The first configuration item construction unit is used to construct a corresponding test configuration item based on the configuration information in the current virtual node if it is a leaf node of the virtual node tree. The second configuration item construction unit is used to construct a corresponding test configuration item based on the configuration information in the current virtual node and using a preset composite construction strategy if it is not a leaf node of the virtual node tree, and to distribute the configuration information in the current virtual node to the child node corresponding to the current virtual node. The configuration item summary unit is used to jump to the step of determining whether the current virtual node is a leaf node of the virtual node tree, until all virtual nodes in the virtual node tree have been traversed to obtain the corresponding test configuration items, and to summarize the test configuration items to obtain the target test plan.

[0062] In some specific embodiments, the test scheme execution module 15 may specifically include: The scheme adjustment unit is used to adjust the timeout time and the location of the run record export of the target test scheme based on the configuration instructions triggered by the visual interface, so as to obtain the configured test scheme. The triggering method determination unit is used to determine the target triggering method of the configured test plan; the target triggering method is any one of manual execution, code submission triggering, and scheduled execution. The scheme judgment unit is used to determine whether the configured test scheme meets the preset triggering conditions based on the target triggering method; The scheme execution unit is used to schedule the test task corresponding to the configured test scheme to the execution node through the communication link if the configured test scheme meets the preset triggering conditions, so as to run the configured test scheme based on the execution node and obtain the test results, process logs and comparison curves of the target aircraft CFD case; the comparison curve is a comparison curve between the CFD result corresponding to the current test and the preset reference CFD result.

[0063] Furthermore, embodiments of this application also disclose an electronic device, Figure 6 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content of the diagram should not be construed as limiting the scope of this application. Specifically, the electronic device 20 may include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 stores a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the method for generating and running aircraft simulation test schemes for CFD software disclosed in any of the foregoing embodiments. Furthermore, the electronic device 20 in this embodiment may specifically be an electronic computer.

[0064] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 25 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0065] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk or optical disk, etc. The resources stored thereon can include operating system 221, computer program 222, etc., and the storage method can be temporary storage or permanent storage.

[0066] The operating system 221 is used to manage and control the various hardware devices on the electronic device 20 and the computer program 222, which may be Windows Server, Netware, Unix, Linux, etc. In addition to including computer programs capable of generating and running the aircraft simulation test scheme for CFD software executed by the electronic device 20 as disclosed in any of the foregoing embodiments, the computer program 222 may further include computer programs capable of performing other specific tasks.

[0067] Furthermore, this application also discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, it implements the aforementioned method for generating and running aircraft simulation test schemes for CFD software. Specific steps of this method can be found in the corresponding content disclosed in the foregoing embodiments, and will not be repeated here.

[0068] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

[0069] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0070] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0071] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0072] The technical solutions provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A method for generating and running aircraft simulation test schemes for CFD software, characterized in that, include: The CFD software splits the CFD case files corresponding to the aircraft CFD cases into model files and parameter files, and based on the differences in the change frequency and storage volume of the aircraft CFD cases, the model files and parameter files are distributed and stored to storage nodes. The target model file is determined by utilizing the historical call frequency of the model file, and the target model file is cached in the cache space. A communication link between the storage node, the cache space, and the execution node is established based on the gRPC protocol. Based on the version management level corresponding to the parameter file, the aircraft CFD case is divided into project-level case and process-level case. The corresponding target process-level case and target parameter file are determined using the communication link and the target aircraft CFD case to be tested. Semantic tags are determined based on the file structure of the target process-level case and the key-value pairs of the target parameter file. The semantic tags are matched with each rule in the preset mapping rule library, and the target matching rule is determined using the matching results. A virtual node tree is constructed based on the target matching rule and the target parameter file. The virtual node tree is traversed layer by layer in a top-down order, and the target test plan is constructed using the traversal results. The target test scheme is configured to obtain a configured test scheme. If the configured test scheme meets the preset triggering conditions, the configured test scheme is run on the execution node to obtain the test results of the target aircraft CFD case. The configured test scheme is bound to the parameter version identifier of the target process-level test case; If the test results meet the preset test evaluation conditions, the parameter version of the target process-level example will be submitted to the project-level example to update the parameter version library of the project-level example.

2. The method for generating and running aircraft simulation test schemes for CFD software according to claim 1, characterized in that, The step of splitting the CFD case file corresponding to the aircraft CFD case in the CFD software into a model file and a parameter file, and distributing the model file and the parameter file to storage nodes based on the differences in the change frequency and storage volume of the aircraft CFD case, includes: Obtain the aircraft CFD case from the CFD software, and split the case file corresponding to the aircraft CFD case into model file and parameter file based on the storage information and purpose of the aircraft CFD case; Based on the differences in the change frequency and storage volume of the CFD case of the aircraft, the model file and the parameter file are distributed and stored to storage nodes.

3. The method for generating and running aircraft simulation test schemes for CFD software according to claim 1, characterized in that, The process of determining the corresponding target process-level calculation case and target parameter file using the communication link and the CFD calculation case of the target aircraft under test includes: Obtain the CFD case of the target aircraft to be tested, and determine whether the CFD case of the target aircraft already has a test plan; If the target aircraft CFD case already has a test plan, and the target parameter file corresponding to the target aircraft CFD case has been updated, then the test plan corresponding to the target aircraft CFD case is obtained from the database, and the test plan is updated using the updated target parameter file to obtain the target test plan. If the target aircraft CFD case does not have a test scheme, then the step of determining the corresponding target process-level case and target parameter file using the communication link and the target aircraft CFD case to be tested is triggered.

4. The method for generating and running aircraft simulation test schemes for CFD software according to claim 1, characterized in that, The step of determining the corresponding target process-level calculation case and target parameter file using the communication link and the target aircraft CFD calculation case under test, and determining semantic tags based on the file structure of the target process-level calculation case and the key-value pairs of the target parameter file, includes: The target aircraft CFD case to be tested is identified as a target process-level case, and the target parameter file corresponding to the target aircraft CFD case is determined. The file structure of the target process-level example is parsed to obtain the corresponding metadata, and the target parameter file is semantically identified to obtain key-value pairs; Test guidance parameters are extracted from the key-value pairs, and semantic tags are constructed based on the test guidance parameters and the metadata.

5. The method for generating and running aircraft simulation test schemes for CFD software according to claim 1, characterized in that, The step of matching the semantic tags with rules in a preset mapping rule base, determining the target matching rule using the matching results, and constructing a virtual node tree based on the target matching rule and the target parameter file includes: The semantic tags are matched with each rule in the preset mapping rule base, and the target matching rule is constructed using the successfully matched rules; A virtual node tree is constructed based on a preset rule nesting structure, and the configuration item information of the target parameter file and the target matching rule are written into the corresponding virtual nodes in the virtual node tree; the structure of the virtual node tree corresponds one-to-one with the configuration item structure of the target parameter file; the preset rule nesting structure corresponds to the nested key-value pair structure of the target parameter file.

6. The method for generating and running aircraft simulation test schemes for CFD software according to claim 1, characterized in that, The step of traversing the virtual node tree layer by layer in a top-down order and constructing the target test plan using the traversal results includes: The virtual node tree is traversed layer by layer in a top-down order. The currently traversed virtual node is determined as the current virtual node, and it is determined whether the current virtual node is a leaf node of the virtual node tree. If it is a leaf node of the virtual node tree, then the corresponding test configuration item is constructed based on the configuration information in the current virtual node; If it is not a leaf node of the virtual node tree, then the corresponding test configuration item is constructed based on the configuration information in the current virtual node and using a preset composite construction strategy, and the configuration information in the current virtual node is distributed to the child node corresponding to the current virtual node. Jump to the step of determining whether the current virtual node is a leaf node of the virtual node tree, until all virtual nodes in the virtual node tree have been traversed to obtain the corresponding test configuration items. Summarize the test configuration items to obtain the target test plan.

7. The method for generating and running aircraft simulation test schemes for CFD software according to any one of claims 1 to 6, characterized in that, The configured test plan is obtained by configuring the target test plan. If the configured test plan meets the preset triggering conditions, the configured test plan is run on the execution node to obtain the test results of the target aircraft CFD example, including: The timeout time and runtime record export location of the target test plan are adjusted based on the configuration instructions triggered by the visual interface to obtain the configured test plan; Determine the target triggering method for the configured test plan; the target triggering method is any one of manual execution, code submission triggering, and scheduled execution. Based on the target triggering method, determine whether the configured test scheme meets the preset triggering conditions; If the configured test scheme meets the preset triggering conditions, the test task corresponding to the configured test scheme is scheduled to the execution node using the communication link, so as to run the configured test scheme based on the execution node, and obtain the test results, process log and comparison curve of the target aircraft CFD case; the comparison curve is a comparison curve between the CFD result corresponding to the current test and the preset reference CFD result.

8. A device for generating and running aircraft simulation test schemes for CFD software, characterized in that, include: The case splitting module is used to split the case files corresponding to the aircraft CFD cases in the CFD software into model files and parameter files, and based on the differences in the change frequency and storage volume of the aircraft CFD cases, distribute the model files and parameter files to storage nodes. The communication link establishment module is used to determine the target model file by utilizing the historical call frequency of the model file, cache the target model file in the cache space, and establish a communication link between the storage node, the cache space and the execution node based on the gRPC protocol; The semantic tag determination module is used to divide the aircraft CFD case into project-level cases and process-level cases based on the version management level corresponding to the parameter file, determine the corresponding target process-level case and target parameter file using the communication link and the target aircraft CFD case to be tested, and determine semantic tags based on the file structure of the target process-level case and the key-value pairs of the target parameter file. The test scheme construction module is used to match the semantic tags with each rule in the preset mapping rule library, determine the target matching rule using the matching results, construct a virtual node tree based on the target matching rule and the target parameter file, traverse the virtual node tree layer by layer in a top-down order, and construct the target test scheme using the traversal results. The test plan execution module is used to configure the target test plan to obtain the configured test plan. If the configured test plan meets the preset triggering conditions, the configured test plan is run on the execution node to obtain the test results of the target aircraft CFD case. The configured test scheme is bound to the parameter version identifier of the target process-level test case; The parameter version submission module is used to submit the parameter version of the target process-level example to the project-level example if the test result meets the preset test evaluation conditions, so as to update the parameter version library of the project-level example.

9. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor is configured to execute the computer program to implement the method for generating and running aircraft simulation test schemes for CFD software as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, Used to store a computer program, wherein the computer program, when executed by a processor, implements the method for generating and running aircraft simulation test schemes for CFD software as described in any one of claims 1 to 7.

Citation Information

Patent Citations

  • CFD software automatic testing method and system

    CN117806981A

  • Iterative testing method, device and equipment for industrial CFD (computational fluid dynamics) software and medium

    CN119557234A