CN116955274A - Test data management method - Google Patents
Test data management method Download PDFInfo
- Publication number
- CN116955274A CN116955274A CN202310767242.2A CN202310767242A CN116955274A CN 116955274 A CN116955274 A CN 116955274A CN 202310767242 A CN202310767242 A CN 202310767242A CN 116955274 A CN116955274 A CN 116955274A
- Authority
- CN
- China
- Prior art keywords
- test
- data
- product
- code
- test data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 194
- 238000000034 method Methods 0.000 title claims abstract description 25
- 238000013523 data management Methods 0.000 title claims abstract description 14
- 230000008520 organization Effects 0.000 claims abstract description 18
- 238000013461 design Methods 0.000 claims abstract description 13
- 239000007788 liquid Substances 0.000 claims abstract description 5
- 230000014509 gene expression Effects 0.000 claims description 8
- 230000006870 function Effects 0.000 claims description 5
- 230000008569 process Effects 0.000 claims description 5
- 230000008859 change Effects 0.000 claims description 3
- 238000010998 test method Methods 0.000 claims description 2
- 238000004519 manufacturing process Methods 0.000 abstract description 3
- 238000005259 measurement Methods 0.000 description 4
- 230000001133 acceleration Effects 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 238000003860 storage Methods 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000010606 normalization Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000011144 upstream manufacturing Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/11—File system administration, e.g. details of archiving or snapshots
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Testing Or Calibration Of Command Recording Devices (AREA)
Abstract
The invention discloses a test data management method, which comprises the steps of establishing a test data organization structure, wherein the test data organization structure comprises a complete machine thermal test run test data structure, a mechanical environment test data structure and a liquid flow test data structure; the whole machine hot test run test data structure is as follows: product code (engine code/production assembly code) - > product chart code (design chart number) - > product number- > test item- > test sequence number- > test parameter record; the mechanical environment test data structure is as follows: product code (engine code/product assembly code) - > product chart code (design chart number) - > product number- > test item- > test sequence number (the same test product is distinguished for multiple times at different times) - > test parameter record; the flow test data structure is as follows: the invention can fully cover all types of test data, and is suitable for expanding new test types and test data.
Description
Technical Field
The invention relates to the technical field of data management, in particular to a test data management method.
Background
Under the conditions of multiple test types, multiple test projects and complex test data of an engine, the attitude and orbit control power system is generally adopted at present to manage the test data, and the problems of non-standard test classification, non-uniform test project definition, non-convenient sharing of test data and the like exist in the management process.
Disclosure of Invention
The invention provides a test data management method according to the practical characteristics of an engine test, which aims to solve the defects in the prior background art, and performs normalized classification, conversion, storage and management on test data from high to low, so as to provide a data basis for machine learning and data analysis. The method comprises the following steps:
the method comprises the steps of establishing a test data organization structure, wherein the test data organization structure comprises a complete machine thermal test run test data structure, a mechanical environment test data structure and a liquid flow test data structure;
the whole machine hot test run test data structure is as follows: product code (engine code/production assembly code) - > product chart code (design chart number) - > product number- > test item- > test sequence number- > test parameter record;
the mechanical environment test data structure is as follows: product code (engine code/product assembly code) - > product chart code (design chart number) - > product number- > test item- > test sequence number (the same test product is distinguished for multiple times at different times) - > test parameter record;
the flow test data structure is as follows: product code (engine code/productization assembly code) - > product chart code (design chart number) - > product number- > test item- > test sequence number (the same test product is distinguished for multiple times at different times) - > test parameter record.
Further, the system also comprises a product data packet data structure, wherein the data packet data structure is as follows: product code (engine code/productization assembly code) - > product chart code (design chart number) - > product number-xxx.
Furthermore, the test data provided by the test unit in the test data organization structure generally comprises data, photos, videos, reports, test programs and measurement point information, and format requirements are required for files with each function, and the files are distinguished by specific suffixes and are specifically coded, so that the program analysis is facilitated.
Furthermore, the test data includes conventional data format with dat as suffix, and is mainly used for storing various time domain data (time related data) in the test run process, the coding is UTF-8, the dat format is text format, and txt is used as suffix in the vast majority in the past. However, txt is more random and cannot directly identify whether it is data, for example, "readme. Txt" is generally an explanatory file, wherein the file is natural language, in order to facilitate the evidence of its data attribute, dat is used as a suffix of the data file, and the dat format is mainly used for storing data formats which can be arranged in multiple columns, and is generally used for storing time-domain data such as pressure, temperature, flow and the like during a test, and is generally slow-data (the collection frequency is lower), and the basic requirements are as follows: the first row is a measuring point code row, which is required to be completely consistent with the requirements of the task book, and the measuring point code is not surrounded by a semicolon; starting from the 2 nd row as a data row, the number of the effective digits accords with the requirements of a task book, and generally at least 3 decimal places are adopted; the uncollected or corrupted data in the data is replaced with "/" or "-; the data of each row are separated by English commas; the first Time, the code number is unified as "Time".
Furthermore, the test data comprises frequency domain data (data related to frequency) in a format unv/unf, and the rapid change data collected by the mechanical environment test has large data volume, so that text data storage is large, and the frequency domain data are synchronously provided for the convenience of design and analysis.
Further, the test data includes a test program format seq.dat, and the specific format requirements are as follows: first act engine code row; the first Time column is the Time column, and the code number is unified as 'Time'; each row of data elements are separated by English commas; each data element may be identified by a single value, representing the duration of the opening, a test run pulse expression, or a file reference.
Further, the test data comprises a test point information format tp.dat, which is mainly used for defining a test point, and is encoded as utf-8, and comprises a code number, a name, a unit, a photo and remarks of the test point.
By adopting the technical scheme, the method has the following technical effects:
the invention classifies all tests related to engines into three main categories: the basic principle of classification is whether the organization form of the tested data and the organization mode of the test have great differences or not, and each test type corresponds to a relatively fixed data organization mode. The invention can fully cover all types of tests, test projects and test data, and is suitable for expanding new test types and test data.
Drawings
FIG. 1 is a diagram of an interface of a test data management method of the present invention;
FIG. 2 is a diagram of an interface of the test data management method of the present invention.
Detailed Description
The invention is further described below with reference to the accompanying drawings.
The test data management method comprises the steps of establishing a test data organization structure, wherein the test data organization structure comprises a complete machine thermal test run test data structure, a mechanical environment test data structure and a liquid flow test data structure;
the whole machine hot test run test data structure is as follows: product code (engine code/product assembly code) - > product chart code (design chart number) - > product number- > test item- > test sequence number (the same test product is distinguished for multiple times at different times) - > test parameter record;
the mechanical environment test data structure is as follows: product code (engine code/production assembly code) - > product chart code (design chart number) - > product number- > test item- > test sequence number- > test parameter record;
the flow test data structure is as follows: product code (engine code/productization assembly code) - > product chart code (design chart number) - > product number- > test item- > test sequence number (the same test product is distinguished for multiple times at different times) - > test parameter record.
The system also comprises a product data packet data structure, wherein the data packet data structure is as follows: product code (engine code/productization assembly code) - > product chart code (design chart number) - > product number-xxx.
The test data provided by the test unit in the test data organization structure generally comprises data, photos, videos, reports, test programs and measurement point information, and format requirements are required for files with each function, the files are distinguished by specific suffixes, meanwhile, the files are specifically encoded, and program analysis is facilitated.
The test data comprises a conventional data format taking dat as a suffix, is mainly used for storing various time domain data (time related data) in the test run process, is encoded into UTF-8, and is a text format, and the vast majority of the data formats take txt as the suffix in the past. However, txt is more random and cannot directly identify whether it is data, for example, "readme. Txt" is generally an explanatory file, wherein the file is natural language, in order to facilitate the evidence of its data attribute, dat is used as a suffix of the data file, and the dat format is mainly used for storing data formats which can be arranged in multiple columns, and is generally used for storing time-domain data such as pressure, temperature, flow and the like during a test, and is generally slow-data (the collection frequency is lower), and the basic requirements are as follows: the first row is a measuring point code row, which is required to be completely consistent with the requirements of the task book, and the measuring point code is not surrounded by a semicolon; starting from the 2 nd row as a data row, the number of the effective digits accords with the requirements of a task book, and generally at least 3 decimal places are adopted; the uncollected or corrupted data in the data is replaced with "/" or "-; the data of each row are separated by English commas; the first Time, the code number is unified as "Time".
The test data comprises frequency domain data (frequency related data) in a format unv/unf, and the rapid change data acquired by the mechanical environment test has large data volume, so that text data can be stored relatively large, and the frequency domain data are synchronously provided for the convenience of design and analysis.
The test data comprises a test run program format seq.dat, and the specific format requirements are as follows: first act engine code row; the first Time column is the Time column, and the code number is unified as 'Time'; each row of data elements are separated by English commas; each data element may be identified by a single value, representing the duration of the opening, a test run pulse expression, or a file reference.
The test data comprises a measuring point information format tp.dat, and is mainly used for defining measuring points, and the code is utf-8, including code numbers, names, units, photos and remarks of the measuring points.
The test data description comprises a photo video description and a report, wherein the photos in the photo video description are engine product photos and test photos, and also comprise photos of part of the test car, and are archived for examination. The video is recorded at a plurality of angles during test run, and is archived for future reference. Therefore, the photo and video data only need to be uploaded after the catalog is built in the system, and can be downloaded and opened for viewing when required in association with the test run number. The format requirements are as follows: the pictures are png or jpg, and the video is avi or mp4, wherein the former is in a recommended format.
The report content is generally a brief introduction of the test run condition, and the report test run date, station, time, program, environmental condition, preliminary result, slow-change parameter mean value, quick-change data statistics form and the like are reported, so that each test run is not completely consistent, and the system can be used as an accessory to directly upload a system, and can be downloaded and opened for viewing when needed.
In this example, the test data classification was normalized:
all tests involving engines are divided into three main categories: the basic principle of classification is whether the organization form of the tested data and the organization mode of the test have great differences or not, and each test type corresponds to a relatively fixed data organization mode, as shown in the following table:
in this embodiment, the test data organization is normalized:
for a certain type of test, the generated test data (data, photos, videos, test procedures, reports, test point information and the like) are organized by a specific directory structure, so that the management is more convenient.
The data structure of the test data is: product code number, product chart number, product number, test item, test number (the same test product is distinguished at different times), test parameter record.
The test data format is normalized in this embodiment:
standardized requirements such as storage forms, codes, naming and the like are set for various generated test data storage files, so that machine processing is facilitated, ambiguity is prevented, and files with different functions are distinguished by suffix names.
A) Slow data format: the data is stored in a dat format, is mainly used for storing various time domain data in the test run process, and is encoded into UTF-8. The dat format is a text format, and is mainly used for storing data formats which can be arranged into a plurality of columns, and is generally used for storing time domain data such as pressure, temperature, flow and the like during a test, and is generally slow data (the acquisition frequency is lower). The basic requirements are as follows:
1) The first row is a measuring point code row, which is required to be completely consistent with the requirements of the task book, and the measuring point code is not surrounded by a semicolon;
2) Starting from the 2 nd row as a data row, the number of the effective digits accords with the requirements of a task book, and generally at least 3 decimal places are adopted;
3) The uncollected or corrupted data in the data is replaced with "/" or "-;
4) The data of each row are separated by English commas (,) for each row;
5) The first Time, the code number is unified as "Time".
B) Fast-changing data format: when commercial software (e.g., LMS, dewetron, B & K, etc.) is required to collect frequency domain data, it is converted or saved to the universal format unv/uff, suffix ". Unv/uff".
C) Test run program format: the specific format requirements, based on "seq. Dat", are as follows:
1) First act engine code row;
2) The first Time column is the Time column, and the code number is unified as 'Time';
3) Each row of data elements are separated by English commas;
4) Each data element may be represented in the form of a single value, a test run pulse expression, or a file reference, the single value representing the duration of the opening.
D) Measurement point information format: the tp.dat format is mainly used for defining the measuring points, and is encoded into UTF-8, including code numbers, names, units, photos, remarks and the like of the measuring points.
Test data identification normalization in this embodiment:
various elements or specific functions possibly occurring in test data, such as test point codes, working condition expressions, test run program pulse expressions and the like, are normalized, so that a more uniform description method is provided, and information exchange among different personnel and different units is facilitated.
A) The code number rule of the hot test point is as follows:
1) The code number of the measuring point consists of letters, numbers and underlines, and can only start with capital letters, and the following letters are lowercase;
2) The code numbers of the measuring points generally consist of: physical quantity abbreviation + component abbreviation + underline + position abbreviation, such as differential tank inlet pressure (pzxc_in), if there is a measurement point in only one location of the component, the position abbreviation may be omitted as appropriate;
3) The abbreviations for physical quantities are generally the english word initials for the physical quantities, such as: pressure (P), temperature (T), flow (Q), acceleration/vibration (a), current (I), strain (S).
4) The abbreviation of position mainly indicates where the measuring point is located on the component, such as an inlet (in), an outlet (out) and the like, and if a plurality of measuring points are located on the same position, such as a differential storage tank wall surface temperature measuring point, numerical numbering can be adopted, and the principle of sequential numbering from upstream to downstream is followed when numbering.
5) The format of the name of the measuring point is as follows: number + component name + location + physical quantity type.
B) The code number rule of the measuring points of the mechanical environment test: in the mechanical environment test, only two types of acceleration measuring points and strain measuring points are generally used, the numbers are used for numbering, and the specific rules are as follows:
(1) The initial letters of the reference points are acceleration (A) or strain (S), followed by numerical numbers such as A1, A2, A3, … … or S1, S2, S3, … ….
C) The code number rule of the liquid flow test point is as follows: the station code consists of english letters, numbers and underlines, and generally starts with uppercase letters (excluding greek letters), with the following letters all being lowercase.
D) The operating mode expression is as follows: the working conditions are generally used to indicate how many thrust chambers are working simultaneously, and the general format is that (brackets represent that the content thereof can be omitted):
F1*n1[+F2*n2[+F3*n3[……]]]
wherein: thrust magnitude (unit may be N or kN), such as 100N, 20kN; the number is an integer after "+"; "+" indicates that the thrust chambers of different thrust orders operate simultaneously.
E) Test run program pulse expression: the multiple pulse operation is expressed in a simplified form in the test run procedure, so the following pulse format is defined (brackets represent their content may be omitted):
on1/off1*n1[+on2/off2*n2[+on3/off3*n3[……]]]
wherein: on represents on time (in seconds), off represents off time (in seconds), and n represents the number of repetitions (which may be omitted when 1).
While the basic principles and main features of the present invention have been described above, it will be understood by those skilled in the art that the present invention is not limited by the above-described embodiments, which are described in the foregoing description merely illustrate the principles of the present invention, and various changes and modifications may be made therein without departing from the spirit and scope of the invention as defined in the appended claims and their equivalents.
Claims (7)
1. The test data management method is characterized by comprising the steps of establishing a test data organization structure, wherein the test data organization structure comprises a complete machine thermal test run test data structure, a mechanical environment test data structure and a liquid flow test data structure;
the whole machine hot test run test data structure is as follows: product code number- > product chart number- > product number- > test item- > test sequence number- > test parameter record;
the mechanical environment test data structure is as follows: product code number- > product chart number- > product number- > test item- > test sequence number- > test parameter record;
the flow test data structure is as follows: product code number- > product chart number- > product number- > test item- > test sequence number- > test parameter record.
2. The method of claim 1, further comprising a product data packet data structure, the data packet data structure being: product code- > product drawing number- > product number-xxx.
3. The method for managing test data according to claim 1, wherein the test data provided by the test unit in the test data organization structure generally comprises data, photos, videos, reports, test procedures and test point information, and format requirements are necessarily set for each function file, and the files are distinguished by a clear suffix, and meanwhile clear codes are used for facilitating program analysis.
4. A test data management method according to claim 3, wherein the test data includes a conventional data format with dat as a suffix, and is mainly used for storing various time domain data (time related data) in a test run process, the coding is UTF-8, the dat format is a text format, and txt is used as a suffix in the past. However, txt is relatively random and cannot directly identify whether it is data, for example, "readme.txt" is generally an explanatory file, wherein the files are all natural languages, in order to facilitate the evidence of data attributes thereof, dat is used as a suffix of a data file, and the dat format is mainly used for storing data formats which can be arranged into multiple columns, and is generally used for storing time-domain data such as pressure, temperature, flow and the like during a test, and is generally slow-varying data, and the basic requirements are as follows: the first row is a measuring point code row, which is required to be completely consistent with the requirements of the task book, and the measuring point code is not surrounded by a semicolon; starting from the 2 nd row as a data row, the number of the effective digits accords with the requirements of a task book, and generally at least 3 decimal places are adopted; the uncollected or corrupted data in the data is replaced with "/" or "-; the data of each row are separated by English commas; the first Time, the code number is unified as "Time".
5. A test data management method according to claim 3, wherein the test data includes a frequency domain data (frequency related data) format unv/unf, and the rapid change data collected by the mechanical environment test is stored in a relatively large text data because of a large data volume, so that the design is easy to analyze, and the frequency domain data is synchronously provided for each test.
6. A test data management method according to claim 3, wherein the test data comprises a test run program format seq. First act engine code row; the first Time column is the Time column, and the code number is unified as 'Time'; each row of data elements are separated by English commas; each data element may be identified by a single value, representing the duration of the opening, a test run pulse expression, or a file reference.
7. A test data management method according to claim 3, wherein the test data includes a test point information format tp.dat, mainly used for defining a test point, and the code is utf-8, including a code number, a name, a unit, a photo and a remark of the test point.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310767242.2A CN116955274A (en) | 2023-06-27 | 2023-06-27 | Test data management method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310767242.2A CN116955274A (en) | 2023-06-27 | 2023-06-27 | Test data management method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116955274A true CN116955274A (en) | 2023-10-27 |
Family
ID=88453935
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310767242.2A Pending CN116955274A (en) | 2023-06-27 | 2023-06-27 | Test data management method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116955274A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN118010361A (en) * | 2024-04-08 | 2024-05-10 | 西安航天动力试验技术研究所 | Engine ground test command decision method, system, equipment and medium |
-
2023
- 2023-06-27 CN CN202310767242.2A patent/CN116955274A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN118010361A (en) * | 2024-04-08 | 2024-05-10 | 西安航天动力试验技术研究所 | Engine ground test command decision method, system, equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN116955274A (en) | Test data management method | |
| CN107390896B (en) | A kind of the dictionary management method and device of input method | |
| CN107193791B (en) | Action report visual display method based on transient data exchange general format | |
| CN113297238B (en) | Method and device for mining information based on history change record | |
| CN103399848A (en) | Engine test data standardized specific format leading-in processing method | |
| CN101089853B (en) | Apparatus and method for browsing contents | |
| CN110765325A (en) | Operation and maintenance analysis method and system of CEPH distributed storage system | |
| US8413121B2 (en) | Method and system for storing trace events in a database table | |
| US20130124482A1 (en) | Systems and methods for application reuse | |
| CN112395292B (en) | Data feature extraction and matching method and device | |
| CN114090673A (en) | Data processing method, equipment and storage medium for multiple data sources | |
| KR20230003184A (en) | information retrieval system | |
| CN113342687A (en) | Method for detecting code specification in batches | |
| CN101089850A (en) | System for global search using comparison single work position relation | |
| CN117389980B (en) | Log file analysis method and device, computer equipment and readable storage medium | |
| Kusuma et al. | Performance Analysis of Forensic Programs on SQLite Corpus | |
| Jiang et al. | A fault detection method for Auxiliary Power Unit based on monitoring parameters selection | |
| CN112559195B (en) | Database deadlock detection method and device, test terminal and medium | |
| CN113194354B (en) | Channel matching method, device and medium for acquiring EPG (electronic program guide) by using smart television operating system | |
| US20240143129A1 (en) | Providing enhanced functionality in an interactive electronic technical manual | |
| CN116974424A (en) | Method, apparatus and computer storage medium for a Cubing verification procedure | |
| Detwyler | CHAPTER 51 TWENTIETH-CENTURY BIBLIOGRAPHIES | |
| CN117194370A (en) | Universal mass airborne data management method based on metadata separation | |
| Rujiang et al. | A semantic information retrieval system based on KIM | |
| Kaufman | The IBM information retrieval center-(ITIRC) system techniques and applications |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |