Iterative testing methods, devices, equipment and media for industrial CFD software

Abstract

The present application discloses an iterative testing method, device, equipment and medium for industrial CFD software, which relates to the field of aerospace, including: if there are new functions for industrial CFD software, determine the target test case based on the simulation scenario and the fluid characteristic information of the new function; determine whether there are original functions associated with the new function in the software, and when so, obtain the historical test input combination of the last test that passed the associated original function; determine the interface test input combination and the solver test input combination based on the target test case, and obtain the test result by using the interface component, the interface test input combination, the solver test input combination and the historical test input combination; verify the test result based on the preset verification rules and post-processing tools, and determine whether the test is passed according to the verification result to complete the test operation corresponding to the new function. The coverage and accuracy of software testing are improved.

Description

Technical Field

[0001] The present invention relates to the field of aerospace, and in particular to an iterative testing method, device, equipment and medium for industrial CFD software. Background Art

[0002] In recent years, driven by demand, the development of industrial CFD (Computational Fluid Dynamics) software has accelerated. As an important part of the development process, software testing is an important means of supporting software quality.

[0003] However, unlike traditional software testing, CFD software is computationally intensive and the simulation process is time-consuming, making it difficult to fully cover the test in iterative testing. In addition, the existing testing solutions for industrial CFD software only test new functions, without considering that the addition of new functions usually causes changes in the calculation results of the original functions. In addition, since the coupling relationship between the algorithm and the program is ignored, the solver is not tested separately, resulting in the inability to accurately locate the source of the defect during the iterative testing process, whether it is the interface component or the solver. Summary of the invention

[0004] In view of this, the purpose of the present invention is to provide an iterative testing method, device, equipment and medium for industrial CFD software, which can effectively implement the new function testing and correctness evaluation in the iterative process of industrial CFD software, and can accurately locate the defect source, effectively improving the coverage and accuracy of software testing. The specific scheme is as follows:

[0005] In a first aspect, the present application provides an iterative testing method for industrial CFD software, comprising:

[0006] If there are new functions in the industrial CFD software, typical examples are selected based on the simulation scenario and the fluid characteristic information of the new functions to determine the target test examples of the new functions; the industrial CFD software includes an interface component and a solver;

[0007] Determine whether there is an existing function associated with the newly added function in the industrial CFD software, and when the association determination result is yes, obtain a historical test example and a historical test input combination that passed the last test corresponding to the associated existing function;

[0008] Determine an interface test input combination and a solver test input combination based on the target test example, and perform a test using the interface component, the interface test input combination, the solver test input combination, the historical test example, and the historical test input combination to obtain a test result;

[0009] The test results are checked based on preset checking rules and post-processing tools, and whether the test is passed is determined based on the obtained checking results, so as to complete the test operation corresponding to the newly added function.

[0010] Optionally, the selecting of typical examples based on the simulation scenario and the fluid characteristic information of the new function to determine a target test example for the new function includes:

[0011] Analyze the simulation scenario and the fluid characteristic information of the newly added function to select corresponding typical examples according to the obtained analysis results; the fluid characteristic information includes aerodynamic thermal characteristic information, high temperature gas effect information, rarefied slip effect information, aerodynamic optical characteristic information, and electromagnetic characteristic information;

[0012] A case design is performed through the typical case to determine a target test case for the new function.

[0013] Optionally, determining an interface test input combination based on the target test example includes:

[0014] Based on the target test example, determining whether the newly added function causes the interface component to be added or modified, so as to obtain a corresponding interface component determination result;

[0015] If the interface component judgment result has caused the interface component to be added or modified, a corresponding interface test input combination is generated; the interface test input combination includes input boundary test information, input type test information and error prompt test information corresponding to the interface component.

[0016] Optionally, determining a solver test input combination based on the target test case includes:

[0017] The test input parameters corresponding to the target test case are combined through the test expectation information to obtain the corresponding solver test input combination; the test input parameters include incoming flow conditions, boundary conditions, global settings, spatial discretization, and time discretization.

[0018] Optionally, the performing of testing using the interface component, the interface test input combination, the solver test input combination, the historical test example and the historical test input combination to obtain a test result includes:

[0019] Starting the interface component, and respectively setting the interface test input combination and the historical interface test input combination in the historical test input combination through the interface component to perform component verification;

[0020] If the verification is successful, determining a target interface test input combination corresponding to the newly added function based on the interface test input combination and a historical interface test input combination in the historical test input combination;

[0021] Setting the target interface test input combination through the interface component to perform simulation test to obtain corresponding interface test results;

[0022] On a high-performance computing cluster, a target solver test input combination is determined based on the solver test input combination and the historical solver test input combination in the historical test input combination, and after the setting of the target solver test input combination is completed in a parameter file matching the solver, a job is submitted through the cluster scheduling system to obtain a corresponding solver test result.

[0023] Optionally, the checking the test result based on a preset checking rule and a post-processing tool, and determining whether the test is passed according to the obtained checking result, includes:

[0024] Performing data processing on the interface test result and the solver test result in the test result by using a visualization tool, and judging whether the interface test result and the solver test result are consistent with each other through the obtained first processing result, so as to determine a first verification result;

[0025] Performing data processing on the solver test result and the previous version solver test result using a visualization tool, and judging whether the interface test result is consistent with the previous version solver test result through the obtained second processing result, so as to determine a second verification result;

[0026] If both the first verification result and the second verification result are yes, it is determined that the test has passed.

[0027] Optionally, before determining that the test is passed, the process further includes:

[0028] Obtaining a test result corresponding to the historical solver test input combination in the solver test results to determine a first solver test result;

[0029] Obtaining a solver test result in the historical test results corresponding to the historical test example to determine a second solver test result;

[0030] By comparing the test result of the first solver and the test result of the second solver, it is determined whether the newly added function causes a change in the function of the solver, and a third verification result is obtained;

[0031] If the third verification result is yes, it is determined that the test has passed.

[0032] In a second aspect, the present application provides an iterative testing device for industrial CFD software, comprising:

[0033] A calculation example selection module, for selecting typical calculation examples based on simulation scenarios and fluid characteristic information of new functions if there are new functions in the industrial CFD software, so as to determine target test examples of the new functions; the industrial CFD software includes an interface component and a solver;

[0034] An association judgment module is used to judge whether there is an original function associated with the new function in the industrial CFD software, and when the association judgment result is yes, obtain the historical test examples and historical test input combinations that have passed the last test corresponding to the associated original function;

[0035] A test result acquisition module, used to determine an interface test input combination and a solver test input combination based on the target test example, and perform a test using the interface component, the interface test input combination, the solver test input combination, the historical test example and the historical test input combination to obtain a test result;

[0036] The result verification module is used to verify the test results based on preset verification rules and post-processing tools, and determine whether the test is passed based on the obtained verification results, so as to complete the test operation corresponding to the newly added function.

[0037] In a third aspect, the present application provides an electronic device, including:

[0038] Memory, used to store computer programs;

[0039] The processor is used to execute the computer program to implement the steps of the aforementioned iterative testing method for industrial CFD software.

[0040] In a fourth aspect, the present application provides a computer-readable storage medium for storing a computer program, which, when executed by a processor, implements the steps of the aforementioned iterative testing method for industrial CFD software.

[0041] It can be seen that in the present application, if there are new functions in the industrial CFD software, typical examples are selected based on the simulation scenario and the fluid characteristic information of the new function to determine the target test example of the new function; the industrial CFD software includes an interface component and a solver; it is determined whether there are original functions associated with the new function in the industrial CFD software, and when the obtained association judgment result is yes, the historical test examples and historical test input combinations that passed the last test corresponding to the associated original function are obtained; based on the target test example, the interface test input combination and the solver test input combination are determined, and the interface component, the interface test input combination, the solver test input combination, the historical test examples and the historical test input combination are used to perform testing to obtain test results; the test results are verified based on preset verification rules and post-processing tools, and it is determined whether the test passes according to the obtained verification results to complete the test operation corresponding to the new function. That is, when testing the new functions of the industrial CFD software, the present application conducts a correlation analysis on the new functions, and carries out iterative testing and result verification of the new functions, the original functions associated with the new functions, the interface components and the solvers. In this way, the new function testing and correctness evaluation in the iteration process of the industrial CFD software can be effectively realized, and the defect source can be accurately located, effectively improving the coverage and accuracy of software testing. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0043] Figure 1 A flow chart of an iterative testing method for industrial CFD software provided in this application;

[0044] Figure 2 A specific flow chart of an iterative testing method for industrial CFD software provided in this application;

[0045] Figure 3 A schematic diagram of the structure of an iterative test device for industrial CFD software provided in this application;

[0046] Figure 4 A structural diagram of an electronic device provided for this application. DETAILED DESCRIPTION

[0047] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0048] Different from traditional software testing, CFD software is computationally intensive software, and the simulation process is time-consuming, making it difficult to fully cover the test in iterative testing. In addition, the existing testing schemes for industrial CFD software only test new functions, without considering that the addition of new functions usually causes changes in the calculation results of the original functions, and because the coupling relationship between the algorithm and the program is ignored, the solver is not tested separately, resulting in the inability to accurately locate the source of the defect during the iterative testing process, whether it is the interface component or the solver. To this end, the present application provides an iterative testing scheme for industrial CFD software, which can effectively implement new function testing and correctness evaluation in the iterative process of industrial CFD software, and can accurately locate the source of defects, effectively improving the coverage and accuracy of software testing.

[0049] See also Figure 1 As shown, the embodiment of the present invention discloses an iterative testing method for industrial CFD software, including:

[0050] Step S11: If there is a new function in the industrial CFD software, typical examples are selected based on the simulation scenario and the fluid characteristic information of the new function to determine the target test example of the new function; the industrial CFD software includes an interface component and a solver.

[0051] In this embodiment, the fluid characteristics such as aero-thermal characteristics, high-temperature gas effects, rarefied slip effects, aero-optical characteristics, and electromagnetic characteristics of the new functions for industrial CFD software are first analyzed, and typical examples are selected in combination with simulation scenarios. The selected typical examples should at least include wind tunnel test data, model flight data, literature data, or theoretical data, and then the typical examples are used as a test basis to design test examples to examine the correctness of the new functions. Among them, typical examples represent a class of simulation cases used to calibrate certain algorithms, including but not limited to one. That is, based on the simulation scenario and the fluid characteristic information of the new functions, the corresponding typical examples are selected according to the obtained analysis results; the fluid characteristic information includes aero-thermal characteristic information, high-temperature gas effect information, rarefied slip effect information, aero-optical characteristic information, and electromagnetic characteristic information; the example design is carried out through typical examples to determine the target test examples of the new functions.

[0052] Step S12, determine whether there is an original function associated with the new function in the industrial CFD software, and when the association judgment result is yes, obtain the historical test example and historical test input combination that passed the last test corresponding to the associated original function.

[0053] Combination Figure 2 As shown, this embodiment takes into account that the addition of new functions usually causes changes in the calculation results of the original functions, so a correlation analysis is performed on the new functions that need to be tested, the original functions associated with the new functions are obtained, and the test examples used to calibrate the correctness of the original functions are obtained, that is, the historical test examples and historical test input combinations that passed the last test corresponding to the associated original functions. In this way, by performing a correlation analysis on the new functions to obtain the associated functions and conducting tests and evaluations on them, the software test coverage can be effectively improved.

[0054] Step S13, determining an interface test input combination and a solver test input combination based on the target test example, and performing testing using the interface component, the interface test input combination, the solver test input combination, the historical test example and the historical test input combination to obtain a test result.

[0055] Combination Figure 2 As shown, in this embodiment, after determining the target test case, the test input will be generated. It should be understood that this embodiment divides the test into interface test corresponding to the interface component in the software and solver test corresponding to the solver in the software.

[0056] Regarding the determination of the interface test input combination, in this embodiment, first determine whether the newly added function causes the addition or modification of the interface component based on the target test case to obtain the corresponding interface component judgment result; if the interface component judgment result has caused the addition or modification of the interface component, then generate the corresponding interface test input combination; the interface test input combination includes the input boundary test information, input type test information and error prompt test information corresponding to the interface component. In other words, if the newly added function causes the addition or modification of the interface component, then generate the interface test input combination, which mainly covers the input boundary, input type, error prompt and other test types of the interface component.

[0057] At the same time, regarding the determination of the solver test input combination, in this embodiment, the test input parameters corresponding to the target test case are combined through the test expectation information to obtain the corresponding solver test input combination; the test input parameters include inflow conditions, boundary conditions, global settings, spatial discretization, and time discretization. In other words, firstly, the test case is designed based on the typical case, and the test input parameters such as inflow conditions, boundary conditions, global settings, spatial discretization, and time discretization are generated, and then combined according to the test requirements to obtain the solver test input combination.

[0058] Further, after obtaining the interface test input combination and the solver test input combination of the new function, the present embodiment starts the test in combination with the historical test input combination. Specifically, the interface component is started, and the interface test input combination and the historical interface test input combination in the historical test input combination are set by the interface component to perform component verification; if the verification is passed, the target interface test input combination corresponding to the new function is determined based on the interface test input combination and the historical interface test input combination in the historical test input combination; the target interface test input combination is set by the interface component to perform simulation testing to obtain the corresponding interface test result; on the high-performance computing cluster (High-Performance Computing Cluster, referred to as HPCC), the target solver test input combination is determined based on the solver test input combination and the historical solver test input combination in the historical test input combination, and after completing the setting of the target solver test input combination in the parameter file matching the solver, the corresponding solver test result is obtained by submitting the job through the cluster scheduling system. In this way, by testing the interface and the solver separately, not only can defects be effectively detected, but also the defect location can be provided to developers, which is conducive to the rapid repair of software defects.

[0059] Step S14: verify the test result based on preset verification rules and post-processing tools, and determine whether the test is passed according to the obtained verification result, so as to complete the test operation corresponding to the newly added function.

[0060] Specifically, in this embodiment, after obtaining the test of the newly added function, the test results will also be checked. The result check mainly uses the post-processing tool to process the data to obtain the residual curve, aerodynamic curve, stagnation line heat flow value, pressure cloud map, density cloud map, wall friction and other results, and judge whether the results are consistent. The details are as follows:

[0061] (1) Using visualization tools to process the interface test results and solver test results in the test results, and judging whether the interface test results and solver test results are consistent with each other through the first processing results (which may be lift curve, drag curve, residual, cross-sectional heat flow, etc.), so as to determine the first verification result;

[0062] (2) Use visualization tools to process the solver test results and the previous version solver test results, and use the obtained second processing results (such as lift curve, drag curve, residual, cross-sectional heat flow, etc.) to determine whether the interface test results are consistent with the previous version solver test results to determine the second verification result;

[0063] (3) Obtain the test result corresponding to the historical solver test input combination in the solver test result to determine the first solver test result; obtain the solver test result in the historical test result corresponding to the historical test case to determine the second solver test result; by comparing the first solver test result with the second solver test result, determine whether the newly added function causes the solver function to change, and obtain a third verification result;

[0064] (4) If the verification results of the above three situations (1), (2) and (3) are all yes, that is, the result of the new function is correct, it is correctly integrated in the interactive interface, and the original function is not affected by the new function, it indicates that this iteration test has passed. The calculation example used for this round of testing will be used to calibrate the correctness of the new function and be used for the next test of this function.

[0065] (5) If any of the verification results of the above three situations (1), (2), and (3) is negative, it means that this iteration test fails, and the test defect will be fed back to the developer for modification.

[0066] In summary, considering that not every function has a corresponding example, it is difficult to accurately evaluate the correctness of the new function. This embodiment will set a test example for each new function to calibrate the correctness of the function based on high-confidence data, which can effectively improve the accuracy of the test results. In addition, the test method proposed in this embodiment also has the following beneficial effects:

[0067] 1) By testing and mutually verifying the interactive interface, new functions, original functions and related functions during the iteration process, the correctness of the new functions added during the software iteration process and the differences between the new and old versions of the solver can be effectively evaluated, thereby improving the coverage of CFD software testing.

[0068] 2) By using high-reliability data such as wind tunnel test data, model flight data, literature data or theoretical data to design test cases, the accuracy of CFD software test results can be improved and the software quality can be effectively guaranteed.

[0069] 3) By using standard examples to design test cases and calibrate functional modules, and by directly inputting parameters to perform simulation and compare the results in the next round of functional testing, efficient reuse of test cases can be achieved, thereby improving the efficiency of software iteration testing.

[0070] It can be seen that in the embodiment of the present application, if there are new functions for the industrial CFD software, typical examples are selected based on the simulation scenario and the fluid characteristic information of the new functions to determine the target test examples for the new functions; the industrial CFD software includes an interface component and a solver; it is determined whether there are original functions associated with the new functions in the industrial CFD software, and when the associated judgment result is yes, the historical test examples and historical test input combinations that passed the last test corresponding to the associated original functions are obtained; based on the target test examples, the interface test input combination and the solver test input combination are determined, and the interface component, the interface test input combination, the solver test input combination, the historical test examples and the historical test input combination are used for testing to obtain test results; the test results are verified based on preset verification rules and post-processing tools, and it is determined whether the test passes according to the verification results obtained to complete the test operations corresponding to the new functions. That is, when testing the new functions of the industrial CFD software, the present application conducts a correlation analysis on the new functions, and carries out iterative testing and result verification of the new functions, the original functions associated with the new functions, the interface components and the solvers. In this way, the new function testing and correctness evaluation in the iteration process of the industrial CFD software can be effectively realized, and the defect source can be accurately located, effectively improving the coverage and accuracy of software testing.

[0071] See also Figure 3 As shown, the embodiment of the present application also discloses an iterative testing device for industrial CFD software, including:

[0072] The example selection module 11 is used for selecting typical examples based on the simulation scenario and the fluid characteristic information of the new function if there is a new function in the industrial CFD software, so as to determine the target test example of the new function; the industrial CFD software includes an interface component and a solver;

[0073] The association judgment module 12 is used to judge whether there is an original function associated with the new function in the industrial CFD software, and when the association judgment result is yes, obtain the historical test example and historical test input combination that passed the last test corresponding to the associated original function;

[0074] A test result acquisition module 13 is used to determine an interface test input combination and a solver test input combination based on the target test example, and to perform a test using the interface component, the interface test input combination, the solver test input combination, the historical test example and the historical test input combination to obtain a test result;

[0075] The result verification module 14 is used to verify the test result based on preset verification rules and post-processing tools, and determine whether the test is passed according to the obtained verification result, so as to complete the test operation corresponding to the newly added function.

[0076] Among them, for more specific working processes of the above-mentioned modules, please refer to the corresponding contents disclosed in the aforementioned embodiments, which will not be repeated here.

[0077] It can be seen that when testing the new functions of the industrial CFD software, the present application conducts a correlation analysis on the new functions, and carries out iterative testing and result verification of the new functions, the original functions associated with the new functions, the interface components and the solver. In this way, the new function testing and correctness evaluation in the iteration process of the industrial CFD software can be effectively realized, and the defect source can be accurately located, effectively improving the coverage and accuracy of software testing.

[0078] In some specific embodiments, the example selection module 11 may specifically include:

[0079] An information analysis unit, used for analyzing the fluid characteristic information of the simulation scenario and the newly added function, so as to select corresponding typical examples according to the obtained analysis results; the fluid characteristic information includes aerodynamic thermal characteristic information, high temperature gas effect information, rarefied slip effect information, aerodynamic optical characteristic information, and electromagnetic characteristic information;

[0080] The calculation example determination unit is used to perform calculation example design through the typical calculation example to determine the target test calculation example of the new function.

[0081] In some specific embodiments, the test result acquisition module 13 may specifically include:

[0082] An interface judgment unit, used to judge whether the newly added function causes the interface component to be added or modified based on the target test example, so as to obtain a corresponding interface component judgment result;

[0083] The first input acquisition unit is used to generate a corresponding interface test input combination if the interface component judgment result has caused the interface component to be added or modified; the interface test input combination includes input boundary test information, input type test information and error prompt test information corresponding to the interface component.

[0084] In some specific embodiments, the test result acquisition module 13 may specifically include:

[0085] The second input acquisition unit is used to combine the test input parameters corresponding to the target test case through the test expectation information to obtain the corresponding solver test input combination; the test input parameters include incoming flow conditions, boundary conditions, global settings, spatial discretization, and time discretization.

[0086] In some specific embodiments, the test result acquisition module 13 may specifically include:

[0087] A component verification unit, used for starting the interface component, and performing component verification by respectively setting the interface test input combination and the historical interface test input combination in the historical test input combination through the interface component;

[0088] An input determination unit, configured to determine, if the verification is passed, a target interface test input combination corresponding to the newly added function based on the interface test input combination and a historical interface test input combination in the historical test input combination;

[0089] A first result acquisition unit, used to set the target interface test input combination through the interface component to perform simulation test to obtain a corresponding interface test result;

[0090] The second result acquisition unit is used to determine a target solver test input combination on a high-performance computing cluster based on the solver test input combination and the historical solver test input combination in the historical test input combination, and after completing the setting of the target solver test input combination in a parameter file matching the solver, submit a job through the cluster scheduling system to obtain a corresponding solver test result.

[0091] In some specific embodiments, the result checking module 14 may specifically include:

[0092] A first verification unit is used to perform data processing on the interface test result and the solver test result in the test result by using a visualization tool, and judge whether the interface test result is consistent with the solver test result through the obtained first processing result, so as to determine a first verification result;

[0093] A second verification unit is used to perform data processing on the solver test result and the previous version solver test result by using a visualization tool, and judge whether the interface test result is consistent with the previous version solver test result through the obtained second processing result, so as to determine a second verification result;

[0094] The test passing unit is used to determine that the test has passed if both the first verification result and the second verification result are yes.

[0095] In some specific embodiments, the iterative testing device for industrial CFD software can also be used to obtain the test results corresponding to the historical solver test input combination in the solver test results to determine the first solver test result; obtain the solver test results in the historical test results corresponding to the historical test examples to determine the second solver test result; by comparing the first solver test result and the second solver test result, it is determined whether the new function causes the function of the solver to change, and a third verification result is obtained; if the third verification result is yes, it is determined that this test has passed.

[0096] Furthermore, the present application also discloses an electronic device. Figure 4 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content in the diagram cannot be regarded as any limitation on the scope of use of the present application.

[0097] Figure 4 A schematic diagram of the structure of an electronic device 20 provided in an embodiment of the present application. The electronic device 20 may specifically 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 is used to store a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the iterative testing method for industrial CFD software disclosed in any of the aforementioned embodiments. In addition, the electronic device 20 in this embodiment may specifically be an electronic computer.

[0098] In this embodiment, the power supply 23 is used to provide working 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 the external device, and the communication protocol it follows is any communication protocol that can be applied to the technical solution of the present application, and is not specifically limited here; the input and output interface 25 is used to obtain 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.

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

[0100] The operating system 221 is used to manage and control the hardware devices and computer program 222 on the electronic device 20, and can be Windows Server, Netware, Unix, Linux, etc. In addition to the computer program that can be used to complete the iterative testing method for industrial CFD software executed by the electronic device 20 disclosed in any of the aforementioned embodiments, the computer program 222 can further include computer programs that can be used to complete other specific tasks.

[0101] Furthermore, the present application also discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the aforementioned disclosed iterative testing method for industrial CFD software is implemented. The specific steps of the method can be referred to the corresponding contents disclosed in the aforementioned embodiments, and will not be repeated here.

[0102] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

[0103] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0104] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0105] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0106] The technical solution provided by the present application is introduced in detail above. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. At the same time, for general technical personnel in this field, according to the idea of ​​the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. An iterative testing method for industrial CFD software, characterized in that: include: If there are new functions in the industrial CFD software, typical examples are selected based on the simulation scenario and the fluid characteristic information of the new functions to determine the target test examples of the new functions; the industrial CFD software includes an interface component and a solver; Determine whether there is an existing function associated with the newly added function in the industrial CFD software, and when the association determination result is yes, obtain a historical test example and a historical test input combination that passed the last test corresponding to the associated existing function; Determine an interface test input combination and a solver test input combination based on the target test example, and perform a test using the interface component, the interface test input combination, the solver test input combination, the historical test example, and the historical test input combination to obtain a test result; Verify the test results based on preset verification rules and post-processing tools, and determine whether the test is passed based on the obtained verification results, so as to complete the test operation corresponding to the newly added function; The determining of the interface test input combination based on the target test example includes: Based on the target test example, determining whether the newly added function causes the interface component to be added or modified, so as to obtain a corresponding interface component determination result; If the interface component judgment result has caused the interface component to be added or modified, a corresponding interface test input combination is generated; the interface test input combination includes input boundary test information, input type test information and error prompt test information corresponding to the interface component; Determining a solver test input combination based on the target test case includes: The test input parameters corresponding to the target test case are combined through the test expectation information to obtain the corresponding solver test input combination; the test input parameters include incoming flow conditions, boundary conditions, global settings, spatial discretization, and time discretization.

2. The iterative testing method for industrial CFD software according to claim 1, characterized in that: The selecting of typical examples based on the simulation scenario and the fluid characteristic information of the new function to determine the target test example of the new function includes: An analysis is performed based on the simulation scenario and the fluid characteristic information of the newly added function, so as to select corresponding typical examples according to the obtained analysis results; the fluid characteristic information includes aerodynamic thermal characteristic information, high temperature gas effect information, rarefied slip effect information, aerodynamic optical characteristic information, and electromagnetic characteristic information; A case design is performed through the typical case to determine a target test case for the new function.

3. The iterative testing method for industrial CFD software according to claim 1 or 2, characterized in that: The method of performing a test using the interface component, the interface test input combination, the solver test input combination, the historical test example and the historical test input combination to obtain a test result includes: Starting the interface component, and respectively setting the interface test input combination and the historical interface test input combination in the historical test input combination through the interface component to perform component verification; If the verification is successful, determining a target interface test input combination corresponding to the newly added function based on the interface test input combination and a historical interface test input combination in the historical test input combination; Setting the target interface test input combination through the interface component to perform an interface component design simulation test for the newly added function to obtain a corresponding interface test result; On a high-performance computing cluster, a target solver test input combination is determined based on the solver test input combination and the historical solver test input combination in the historical test input combination, and after the setting of the target solver test input combination is completed in a parameter file matching the solver, a job is submitted through the cluster scheduling system to obtain the solver test result for the new function.

4. The iterative testing method for industrial CFD software according to claim 3, characterized in that: The test result is verified based on the preset verification rules and post-processing tools, and whether the test is passed is determined according to the obtained verification results, including: Performing data processing on the interface test result and the solver test result in the test result by using a visualization tool, and judging whether the interface test result and the solver test result are consistent with each other through a first processing result obtained, so as to determine a first verification result; Performing data processing on the solver test result and the solver test result of the previous version by using a visualization tool, and judging whether the solver test result is consistent with the solver test result of the previous version by using the obtained second processing result, so as to determine a second verification result; If both the first verification result and the second verification result are yes, it is determined that the test has passed.

5. The iterative testing method for industrial CFD software according to claim 4, characterized in that: Before determining that this test has passed, the following steps are also included: Obtaining a test result corresponding to the historical solver test input combination in the solver test results to determine a first solver test result; Obtaining a solver test result in the historical test results corresponding to the historical test example to determine a second solver test result; By comparing the test result of the first solver and the test result of the second solver, it is determined whether the newly added function causes a change in the function of the solver, and a third verification result is obtained; If the third verification result is yes, it is determined that the test has passed.

6. An iterative testing device for industrial CFD software, characterized in that: include: A calculation example selection module, for selecting typical calculation examples based on simulation scenarios and fluid characteristic information of new functions if there are new functions in the industrial CFD software, so as to determine target test examples of the new functions; the industrial CFD software includes an interface component and a solver; An association judgment module is used to judge whether there is an original function associated with the new function in the industrial CFD software, and when the association judgment result is yes, obtain the historical test examples and historical test input combinations that have passed the last test corresponding to the associated original function; A test result acquisition module, used to determine an interface test input combination and a solver test input combination based on the target test example, and perform a test using the interface component, the interface test input combination, the solver test input combination, the historical test example and the historical test input combination to obtain a test result; A result verification module is used to verify the test results based on preset verification rules and post-processing tools, and determine whether the test is passed according to the obtained verification results, so as to complete the test operation corresponding to the newly added function; The test result acquisition module includes: An interface judgment unit, used to judge whether the newly added function causes the interface component to be added or modified based on the target test example, so as to obtain a corresponding interface component judgment result; A first input acquisition unit is used to generate a corresponding interface test input combination if the interface component judgment result has caused the interface component to be added or modified; the interface test input combination includes input boundary test information, input type test information and error prompt test information corresponding to the interface component; The test result acquisition module includes: The second input acquisition unit is used to combine the test input parameters corresponding to the target test case through the test expectation information to obtain the corresponding solver test input combination; the test input parameters include incoming flow conditions, boundary conditions, global settings, spatial discretization, and time discretization.

7. An electronic device, characterized in that: include: Memory, used to store computer programs; A processor, configured to execute the computer program to implement the iterative testing method for industrial CFD software as claimed in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that: Used to store a computer program, which, when executed by a processor, implements the iterative testing method for industrial CFD software as described in any one of claims 1 to 5.

Images