Model data management system for wind tunnel tasks

Abstract

The present invention discloses a model data management system for wind tunnel tasks, which relates to the field of data management for wind tunnel tests, including: a data layer with an operation and maintenance history database and a real-time database; a UI layer that provides an operation and maintenance management interactive interface and is responsible for managing the operation and maintenance history database; a service layer that provides multiple data services; the data stored in the data layer includes three types of data: historical application engineering data related to wind tunnel task information, operation and maintenance twin data related to the test digital twin simulation data information generated by the model, and personnel positioning data. The present invention provides a model data management system for wind tunnel tasks, which associates and stores test operation data information, and manages it. Based on these model data, it can support the digital improvement of traditional wind tunnel test processes such as wind tunnel test plan coordination, wind tunnel test plan design, and wind tunnel test plan scheduling.

Description

Technical Field

[0001] The present invention relates to the field of data management for wind tunnel tests, and more particularly to a model data management system for wind tunnel tasks. Background Art

[0002] The traditional data storage and management system that is compatible with wind tunnel test equipment uses a relational database to store various measurement point collection data in time series. The list of measurement point data within a period of time can be queried through the unique identifier of the measurement point, such as the temperature measurement point data of a component in the past week. The measurement point data is only identified by time and cannot be associated with the wind tunnel task. For example, 30 tests have been conducted in the past year. Each test has test requirements, test inputs, test process data, test digital twin simulation data, test conclusion reports, etc. The data corresponding to each test can only be queried in the database according to the time when the test occurred and ended, and cannot be aligned with the test digital twin simulation data.

[0003] From the above, it can be seen that the measurement point collection data stored in the existing data storage and management system supporting the wind tunnel test equipment is only identified by time, and cannot be associated with the wind tunnel task. It can only be queried in the database according to the time when the test occurred and ended, and cannot be aligned with the test digital twin simulation data. Summary of the invention

[0004] An object of the present invention is to solve at least the above problems and / or disadvantages and to provide at least the advantages which will be described hereinafter.

[0005] In order to achieve these objectives and other advantages of the present invention, a model data management system for wind tunnel tasks is provided, comprising:

[0006] The data layer is equipped with operation and maintenance history database and real-time database;

[0007] Provides an operation and maintenance management interactive interface and is responsible for the UI layer that manages the operation and maintenance history database;

[0008] A service layer that provides multiple data services;

[0009] The multiple data services include: data access services, database migration and backup, data operation logs, and data hot and cold partitions;

[0010] The data services are all packaged in the form of interfaces for operation and maintenance management interactive interfaces and external program calls;

[0011] The operation and maintenance history database and the real-time database are used to store cold data and hot data respectively;

[0012] The data stored in the data layer includes three categories: historical application engineering data related to wind tunnel mission information, operation and maintenance twin data related to the experimental digital twin simulation data information generated by the model, and personnel positioning data;

[0013] Among them, the operation and maintenance twin data includes: physical equipment operation data and digital simulation model operation simulation data.

[0014] Preferably, hot data that exceeds a predetermined time is converted into cold data, and the cold data is asynchronously saved to a disk array for persistence when the program is idle, and the index path and index information of the persistent data are added to the operation and maintenance history database;

[0015] When the user client initiates a data search request, the digital operation and maintenance system kernel will determine whether to obtain data from SqlServer or redis database based on the query conditions.

[0016] Preferably, the cold data is a persistent database file, the file name of each file is a Key in the redis database, and the content in each file is the compressed binary data of the Value corresponding to the Key.

[0017] Preferably, the operation and maintenance history database includes two forms of external interfaces: C++ dynamic library and WebAP;

[0018] The data access interface in the form of a C++ dynamic library includes a series of interface functions. The input parameters of each function are input in Json format, and the output format includes a return value based on Json and a return value based on a file path name.

[0019] Preferably, during the data storage process, the operation and maintenance history database has three sub-libraries: a historical application engineering data sub-library, an operation and maintenance twin data sub-library, and a personnel location data sub-library, and each sub-library stores business data in the form of a single database and multiple tables.

[0020] Preferably, the historical application engineering data sub-database of the operation and maintenance history database manages different application data in the form of multiple tables, specifically including: a test plan coordination data table, a test plan design data table, a test plan scheduling data table, and an engineering application data table;

[0021] The test plan coordination data table, test plan scheduling data table, and engineering application data table are all stored in a structured data manner;

[0022] The experimental design data table is stored in two data storage methods: structured and unstructured.

[0023] The present invention includes at least the following beneficial effects: The present invention designs a model data management system for wind tunnel tasks, which associates and combines wind tunnel task information, digital twin simulation models, virtual simulation data information generated by the digital twin simulation model, and test operation data information collected by wind tunnel test device measuring points, and stores and manages them. Based on these model data, it can support digital improvements to traditional wind tunnel test processes such as wind tunnel test plan coordination, wind tunnel test plan design, and wind tunnel test plan scheduling.

[0024] Other advantages, objectives and features of the present invention will be embodied in part through the following description, and in part will be understood by those skilled in the art through study and practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 This is an architecture diagram of the model data management system for wind tunnel tasks according to the present invention. DETAILED DESCRIPTION

[0026] The present invention is further described in detail below in conjunction with the accompanying drawings so that those skilled in the art can implement the invention with reference to the description.

[0027] A model data management system for wind tunnel tasks stores virtual simulation data generated by a wind tunnel digital twin prototype model and test operation data measured and collected by a wind tunnel measurement and control system in a time series database, stores test task data and simulation model data in a relational database, and establishes multi-dimensional association relationships among four types of data: test task data, test operation data, simulation result data, and simulation model instance, so as to realize data playback and reuse. Specifically, the technical solution of the present invention includes: a data service layer, an application function layer, and an interactive interface layer;

[0028] The data service layer uses a database combination to store the four types of data separately and establishes a data association index. Virtual simulation data and test operation data are persistently stored in a time series database, and test task data are stored in a relational database. In particular, the present invention associates the three types of data with the wind tunnel digital prototype simulation model instance, and the association between the four is also stored in a relational database. In addition to data storage, it also provides data access operation interface services for external system calls;

[0029] The application function layer provides the background function logic for checking, retrieving, editing and managing various data such as test data, simulation data, wind tunnel test tasks, operating conditions, equipment operation process status monitoring data, alarm data, etc. It can use any information such as the test task code, simulation task code, test case code, operating condition status code, simulation model instance, etc. of the wind tunnel system task as the operation entry object, query other models and data information associated with it, and can wake up and call the digital prototype model simulation software to play back and deduce the virtual simulation data and test operation data. It can compare the virtual simulation data and test operation data under different wind tunnel test conditions, provide a variety of data comparison and analysis tools, and perform statistical analysis on batch data to obtain the correlation between the test condition parameters and the test operation data and the parameters of the virtual simulation data, and obtain the influencing factors of the test condition parameters on the error between virtual and real data;

[0030] The interactive interface layer provides a human-computer interactive interface for operation and maintenance management, and provides an interactive entry for operations such as viewing, searching, editing, and managing the operation and maintenance history database;

[0031] The time series database of the data service layer is provided with hot and cold partitions, and the data of recent simulation or experimental production is stored as hot data, and the hot data is regularly dumped as cold data, and interactive operations are supported to dump cold data as hot data. The cold data is asynchronously saved to the disk array for persistent storage when the program is idle;

[0032] The data service layer establishes the association relationship between four types of data. Each function in the application function layer can set any type of data as the operation entry object. After the user sets the operation entry object data through the interactive interface, the system identifies various types of data related to it according to the heterogeneous data relationship diagram, and can perform routine operations such as viewing, searching, editing, and managing these data. It can also carry out specific operations such as comparative analysis, trend analysis, curve data call, and data correlation traceability inspection based on these data;

[0033] Furthermore, with the test task data as the operation entry object, it is possible to carry out related data query, display and application operations based on the wind tunnel test task as the clue. The test task requirements, working condition parameters, equipment operation process status monitoring data and alarm data related to the test can be obtained by querying the relationship data table through the test task identifier. The test data index identifier and simulation data index identifier recorded in the relationship data table can be used to query the time series database to obtain the test data and simulation data. It can realize the retrieval, call, comparison and analysis of multiple test data of the same test task, the comparison and analysis of test data and simulation data under the same experimental task, and can also realize the graphical display and operation of various related data of a certain test task.

[0034] Furthermore, with the test operation data as the operation entry object, it is possible to carry out related data query, display and application operations based on status monitoring, including operating efficiency, operating power, health status, load conditions, etc., and use the system operating condition as the operation object, while retrieving related task information, equipment information, test curves, simulation data, etc., which can be applied to scenarios such as comparison of virtual and real data, comparison of operating data trends under multiple working conditions, and analysis of the correlation between working condition parameters and test data.

[0035] Furthermore, with the test operation data as the operation entry object, various application operations based on the operation status can be carried out. The test equipment specifically includes compressors, throats, semi-flexible wall nozzles, and various control valves and process auxiliary equipment. The equipment operation status includes operation efficiency, operation power, health status, load conditions, operation time, etc., and the relevant task information, equipment information, test curves, simulation data, etc. can be retrieved according to the equipment operation status, supporting the retrieval, call, comparison, analysis, display or other operations of various types of data.

[0036] Furthermore, with simulation result data as the operation entry object, various application operations can be carried out based on the changes in system operation parameters. The wind tunnel test system, the test data of various equipment parameters, and the simulation data are used as the operation entry objects to identify the relevant simulation test conditions, operating time, test system status, simulation model settings and other parameters, and support the retrieval, call, comparison and analysis of parameter time-varying data under different test conditions and different test conditions. This function also supports the interactive verification between mechanism models and measured data, and identifies abnormal inspections of digital models or test data.

[0037] Furthermore, with simulation result data as the operation entry object, it is possible to carry out time-series simulation data retrieval services based on task use cases, and define the test task or test subject data structure in combination with the virtual and real test conditions, load changes, power changes, and test object characteristics involved in the wind tunnel system simulation test use cases, to provide data layer service support for time step synchronization, data correlation comparison, and interactive verification analysis of time-related data such as simulation process data and test measured data.

[0038] Furthermore, using the simulation model instance as the operation entry object, heterogeneous data integration services based on the model architecture can be carried out, with the digital twin model architecture as the unified main architecture for various models and data. Test subjects, simulation tasks, system status, operating conditions, equipment status, and test simulation data are all defined and collected with reference to this main architecture, thereby providing support for data integration in various application scenarios.

[0039] Furthermore, based on the model data correlation check service of system composition, the system composition table is used as the BOM of the test system to describe the system composition relationship in a hierarchical manner. Then, for specific equipment objects such as the wind tunnel system as a whole, compressor, two-throat, semi-flexible wall nozzle, etc., the correlation relationships between them and the test subjects, operation data, simulation models, and result data are defined respectively, thereby supporting the system composition-driven model data correlation check and management.

[0040] Example:

[0041] The present invention proposes a model data management system for wind tunnel tasks. The system can combine wind tunnel tasks with model data, and correlate wind tunnel task information, experimental digital twin simulation data information generated by the model, and wind tunnel test device measurement point collection data.

[0042] From the perspective of software system architecture design, it can be divided into three architecture levels: data service layer, application function layer and interactive interface layer. For the architecture diagram, please refer to Figure 1 ;

[0043] The data service layer implements data storage management and data access services.

[0044] IoTDB time series database and SQL Server 2019 relational database are used for data storage. The time series database stores test data and simulation data, distinguishes data with parameter unique identifiers, and organizes data in timestamp sequence. The time series database is a category term for a database, not a proprietary term for the present invention. For the present invention, the time series database that stores test data and simulation data is called an "operation and maintenance history database" because it stores persistent cold data, which is "historical data" relative to the current wind tunnel test. The relational database stores wind tunnel test task information structured data and simulation model data, and uses a series of relational tables to store and record the relationship between the test task, virtual and real data, and simulation model. The database records the attribute parameters of the simulation model, and the entity files of the simulation model are regularly stored in the file warehouse.

[0045] Since data is continuously generated during the operation of the wind tunnel, the rate of data generation may be higher than the rate at which data is written to the database. Therefore, Redis is used as a real-time cache database, i.e., a real-time database, to store hot data. Hot data will be directly pushed to visualization applications through memory for interface display, and at the same time, data will be asynchronously dumped to the operation and maintenance history database. The technical method used is to achieve real-time migration and conversion of Redis and SQLServer databases based on the real-time data bus of the digital operation and maintenance system kernel;

[0046] Cold data in the operation and maintenance history database is stored in a dual data structure. In addition to being stored in the SQL Server database table, it is also stored in a more persistent form in the form of local files. The file name of each file is the Key in the SQL Server database, and the content in each file is the compressed binary data of the Value corresponding to this Key. The reason for using dual storage in database tables and local files is to meet the data usage requirements of various third-party applications. The data stored in the files is also convenient for users to perform data processing and drawing.

[0047] The data access service is developed based on the .Net framework and C# language, runs as a background service process, and provides an operation interface based on the WebAPI protocol.

[0048] The interactive interface layer provides a model data interactive management interface, which enables viewing of four types of data content and their relationships, and provides a browser interactive interface of B / S architecture. The technology selection of the front-end framework is based on the Vue.js framework; the interface uses curve charts, histograms, statistical charts, data tables and other commonly used graphics in data statistical analysis disciplines to present the four types of data information currently stored in multiple dimensions, and can edit and delete data in batches; system administrators can manage user roles and data operation permissions based on the interactive interface. In addition, the management software also provides a variety of tool options such as database migration backup, data operation log export, and data file download.

[0049] The application function layer is the core of the present invention, with the association mapping of four types of data as the core, and provides service support for digital operation and maintenance applications based on these data themselves and the relationship between them. The application functions provided are divided into several categories. The conventional data management service functions of the database system include: database access, database migration and backup, data operation log recording and consultation. In this category, data management services can be performed through the interface, and are also encapsulated as a WebAPI interface to be opened to external program calls;

[0050] The application function layer reorganizes the time series data and structured data into data sub-tables that meet the data structure design of each business, including the test plan coordination data table, test plan design data table, test plan scheduling data table, and engineering application twin data file table, which are used to store the corresponding data. The table not only stores the reorganized data structure, but also stores the collection of complete process files generated by user input, processing results, and output;

[0051] The following is an introduction to the above business data tables, and describes the implementation methods of supporting application functions based on these data;

[0052] Specifically, the fields of the test plan coordination data table are designed as shown in Table 1, which is used to store test plan coordination user data. When the user performs functional operations on the test plan coordination interface, the data can be stored in the table by clicking the Save button. Structured data is used for storage. Each test basic information data is stored in an independent field to facilitate the distinction of record business attributes. From a business perspective, it is divided into test plan coordination conclusion data and envelope data (including input and output data), and is uniformly stored in Json format.

[0053] Table 1

[0054]

[0055] In this embodiment, specifically, the fields of the experimental scheme design data table are shown in Table 2 and Table 3, which are used to store the experimental scheme design user data. From a business perspective, experimental scheme coordination is a part of experimental scheme design, so the experimental scheme design data table must be associated with the experimental scheme coordination data to achieve business data coupling. After the user performs a functional operation on the experimental scheme coordination interface, the data can be stored in the table by clicking the Save button, and the storage is performed in a structured data manner;

[0056] In addition to generating structured business data, the test plan design business will generate multi-order modal cloud diagrams during the natural frequency evaluation stage of the model support system. After the user exports the test plan design report, the user can modify the report and upload it to the operation and maintenance history database for storage. Therefore, the test plan design business also includes file storage, which is stored in an unstructured manner. The files are stored in the disk array, and the file path is stored in the data table.

[0057] Table 2

[0058]

[0059] Table 3

[0060]

[0061] In this embodiment, specifically, the fields of the test plan scheduling data table are designed as shown in Table 4, which is used to store test plan scheduling user data. When the user performs functional operations on the test plan scheduling interface, the data can be stored in the table by clicking the Save button. Structured data is used for storage. Each test basic information data is stored in an independent field to facilitate the distinction of record business attributes. From a business perspective, it is divided into test details and scheduling result data, and is uniformly stored in Json format.

[0062] Table 4

[0063]

[0064] In this embodiment, specifically, the operation and maintenance twin data generated during the test operation phase will be put into redis for real-time storage as soon as possible, and converted into cold data within the set time and stored in the operation and maintenance history database, including simulation data, historical comparison data, test data, personnel location data, etc. The amount of such data is large, so the data is first converted into Json format and written into the file before being stored in the table.

[0065] The field design of the engineering application twin data file table is shown in Table 5:

[0066] Table 5

[0067]

[0068] The field design of the engineering application data table is shown in Table 6:

[0069] Table 6

[0070]

[0071] In this embodiment, it should also be noted that the operation and maintenance history database has two forms of external interfaces: C++ dynamic library (dll) and WebAPI. The data access interface in the form of dll contains a series of interface functions, the input parameters of the function are input in the form of Json, and there are two output formats, one is based on the return value of Json, and the other is based on the return value of the file path name. The operation and maintenance history database application service module provides an external call interface in the form of C++ dynamic library (dll) or C interface. The development of the operation and maintenance history database application service module is implemented in a combination of C++ and ODBC. ODBC (Open Database Connectivity) is generated to solve the data sharing between heterogeneous databases. It has now become the main part of WOSA (The Windows OpenSystem Architecture) and a database access interface standard based on the Windows environment. ODBC provides a unified interface for heterogeneous database access, allowing applications to use SQL as the data access standard to access data managed by different DBMS; allowing applications to directly manipulate data in the DB and avoid changes with changes in the DB. ODBC can be used to access DB files on various computers.

[0072] In this embodiment, it should also be noted that the stored data can be divided into the following three categories:

[0073] 1. The first type of stored data: historical application data;

[0074] In the test preparation stage, users can create a new test plan design. The client interface provides basic test information input such as train number, demand source, and actual size of the aircraft to be tested, and the necessary input interface for processing such as balance load evaluation, model blockage calculation, and natural frequency calculation of the model support system is input on the software interface; these inputs are given to the background test plan and after a series of calculations, the best aircraft scale, recommended models of balances and struts, model blockage calculation results, and natural frequency analysis results of the model support system can be displayed in the client interface, and finally the test plan report document is generated. These user operations, including input parameters, output results, user names, time, and additional information will be saved in the operation and maintenance history database.

[0075] The test plan design saved in the database can be queried, downloaded and loaded into the client interface in other clients later, and the previous test plan can be reused while viewing the historical operation records.

[0076] 2. The second type of storage data: operation and maintenance twin data;

[0077] Operation and maintenance twin data consists of two types of data: physical equipment operation data and digital simulation model operation simulation data.

[0078] The physical equipment operation data is the data collected and summarized from the real equipment operation center. The kernel will obtain the original data of the physical equipment operation through the WebApi and MQTT communication protocols and methods. After processing, these data are returned to the client interface for real-time display. In addition, some equipment operation data will be used as simulation condition input parameters for the simulation model for digital simulation model. The database will save the input parameters such as test requirements, customized UI information and all returned physical equipment operation data.

[0079] The simulation data of the digital simulation model is the simulation data generated after the simulation engine service runs the simulation model. These data will be displayed in real time to the key electromechanical equipment status monitoring business function in the client after being parsed by the kernel, and will be synchronously compared with the data of the physical equipment operation. The database will save the input parameters such as the UI information of each function of the key electromechanical equipment status monitoring business, the simulation model information, as well as the real-time simulation results and early warning prompt information.

[0080] 3. The third type of stored data: personnel location data;

[0081] The personnel positioning data sub-library stores personnel positioning information data, interprets and formats the signals collected from the personnel positioning system hardware equipment, and mainly records some personnel activity trajectories, alarm information records, etc. These data will also be stored in the operation and maintenance history database, and the data can be retrieved at any time and viewed through the personnel positioning playback module of the operation and maintenance business client.

[0082] The above solution is only an illustration of a preferred embodiment, but is not limited thereto. When implementing the present invention, appropriate replacement and / or modification can be performed according to user needs.

[0083] Although the embodiments of the present invention have been disclosed above, they are not limited to the applications listed in the specification and the embodiments. It can be fully applied to various fields suitable for the present invention. For those familiar with the art, additional modifications can be easily realized. Therefore, without departing from the general concept defined by the claims and equivalent scope, the present invention is not limited to the specific details and the illustrations shown and described here.

Claims

1. A model data management system for wind tunnel tasks, characterized in that: include: The data layer is equipped with operation and maintenance history database and real-time database; Provides an operation and maintenance management interactive interface and is responsible for the UI layer that manages the operation and maintenance history database; A service layer that provides multiple data services; The multiple data services include: data access services, database migration and backup, data operation logs, and data hot and cold partitions; The data services are all packaged in the form of interfaces for operation and maintenance management interactive interfaces and external program calls; The operation and maintenance history database and the real-time database are used to store cold data and hot data respectively; The data stored in the data layer include: historical application engineering data related to wind tunnel mission information, operation and maintenance twin data related to the experimental digital twin simulation data information generated by the model, and personnel positioning data. The operation and maintenance twin data include physical equipment operation data and digital simulation model operation simulation data. The physical equipment operation data is the original data of the physical equipment operation collected and summarized from the real equipment operation center. These are returned to the client interface for real-time display after processing. Some other equipment operation data will be used as simulation condition input parameters of the simulation model for the digital simulation model. The digital simulation model operation simulation data is the simulation data generated after the simulation engine service runs the simulation model. After being parsed by the kernel, the simulation data is displayed in real time in the key electromechanical equipment status monitoring business function in the client, and is synchronously compared with the data of the physical equipment operation. Personnel positioning data will be transferred from the interpretation and formatting of signals collected by the hardware equipment of the personnel positioning system to the operation and maintenance history database, so that the data can be retrieved at any time and viewed through the personnel positioning playback module of the operation and maintenance business client; The operation and maintenance twin data includes: physical equipment operation data and digital simulation model operation simulation data; During the data storage process, the operation and maintenance history database has three sub-databases: the historical application engineering data sub-database, the operation and maintenance twin data sub-database, and the personnel location data sub-database. Each sub-database stores business data in the form of a single database with multiple tables. The historical application engineering data sub-database of the operation and maintenance history database manages different application data in the form of multiple tables, including: test plan coordination data table, test plan design data table, test plan scheduling data table, and engineering application data table; The test plan coordination data table, test plan scheduling data table, and engineering application data table are all stored in a structured data manner; The experimental design data table is stored in two data storage methods: structured and unstructured; The model data management system stores the virtual simulation data generated by the wind tunnel digital twin prototype model and the test operation data measured and collected by the wind tunnel measurement and control system in the time series database, and stores the test task data and simulation model data in the relational database, establishing a multi-dimensional association relationship between the four types of data: test task data, test operation data, simulation result data, and simulation model instance, to achieve data playback and reuse; The data service layer establishes the association relationship between four types of data. Each function in the application function layer sets any type of data as the operation entry object. After the user sets the operation entry object data through the interactive interface, the system identifies various types of data related to it according to the heterogeneous data relationship diagram, and completes routine operations such as reviewing, retrieving, editing, and managing these data, as well as conducting specific operations such as comparative analysis, trend analysis, curve data call, and data correlation traceability inspection based on these data.

2. The model data management system for wind tunnel tasks according to claim 1, characterized in that: Hot data that exceeds a predetermined time is converted to cold data. The cold data is asynchronously saved to the disk array for persistence when the program is idle, and the index path and index information of the persistent data are added to the operation and maintenance history database. When the user client initiates a data search request, the digital operation and maintenance system kernel will determine whether to obtain data from SqlServer or redis database based on the query conditions.

3. The model data management system for wind tunnel tasks according to claim 1, characterized in that: Cold data is a persistent database file. The file name of each file is the Key in the redis database, and the content of each file is the compressed binary data of the Value corresponding to the Key.

4. The model data management system for wind tunnel tasks according to claim 1, characterized in that: The operation and maintenance history database includes two forms of external interfaces: C++ dynamic library and WebAP; The data access interface in the form of a C++ dynamic library includes a series of interface functions. The input parameters of each function are input in Json format, and the output format includes a return value based on Json and a return value based on a file path name.

Images