Flight parameter data preprocessing method and device based on custom template
By configuring flight parameter data preprocessing requirements through custom templates and a graphical interface, efficient and flexible flight parameter data processing is achieved, generating structured datasets. This solves the problems of low efficiency and poor compatibility in existing technologies and supports cross-platform applications.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- CHINA AERO POLYTECH ESTAB
- Filing Date
- 2026-01-07
- Publication Date
- 2026-05-08
AI Technical Summary
Existing flight parameter data processing methods suffer from low processing efficiency, poor compatibility, inflexible parameter extraction, weak batch processing capabilities, and insufficient cross-platform support.
A flight parameter data preprocessing method based on custom templates is adopted. The flight parameter data preprocessing requirements are configured through a graphical interface. Custom templates are used to configure the flight parameter file path, output format and parameter extraction. Combined with parallel processing technology and automatic decoder, a structured dataset is generated.
It improves the flexibility, adaptability, and maintainability of flight parameter data processing, shortens the time for large-scale data processing, lowers the technical threshold, supports cross-platform operation, and enhances versatility.
Smart Images
Figure CN121996912A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of aviation data processing technology, and specifically to a method and apparatus for preprocessing flight parameter data based on a custom template. Background Technology
[0002] Flight parameter data (FMR) is raw data collected by an aircraft through various sensors during flight, including key data such as aircraft status, engine parameters, and navigation information. This data is usually stored in a proprietary binary format, and is large in volume and complex in structure, making direct analysis difficult.
[0003] Existing flight parameter data processing methods suffer from the following technical problems: 1. Low processing efficiency: Traditional methods require manual parsing of binary files, and processing a single file can take hours or even days; 2. Poor compatibility: Flight parameter data generated by different aircraft models and recording devices are not in a unified format, and there is a lack of a unified processing method; 3. Inflexible parameter extraction: It is impossible to flexibly select the parameters to be extracted according to specific analysis needs; 4. Weak batch processing capability: It is impossible to efficiently process large amounts of historical flight parameter data; 5. Insufficient cross-platform support: Existing tools can usually only run on specific operating systems.
[0004] Therefore, there is a need for a method and apparatus that can convert any raw flight parameter data into flight parameter data that meets user needs, so as to facilitate the subsequent use of existing applications to perform various operations such as prediction, evaluation and judgment of aircraft using various flight parameter data. Summary of the Invention
[0005] The present invention aims to provide a flight parameter data preprocessing method and apparatus based on a custom template, so as to solve the problems of poor flexibility, low efficiency and insufficient reliability in flight parameter data processing in the prior art.
[0006] To achieve the above objectives, the present invention provides a flight parameter data preprocessing method based on a custom template, which includes the following steps: S1, users can configure flight parameter data preprocessing requirements through custom templates; Users input their flight parameter data preprocessing requirements through a graphical interface or configuration file, including the flight parameter file storage path, output data format, and parameter extraction. Parameter extraction includes at least the target parameter and sampling frequency. Users can directly select a saved parameter extraction template or save the newly configured parameter extraction as a new parameter extraction template. S2, based on the storage path, reads the original flight parameter file into memory or a streaming buffer and calls the decoder; Each raw flight parameter file is read into memory or a streaming buffer based on the storage path to obtain the raw data; when there are multiple raw flight parameter files, each raw flight parameter file is executed as an independent task by creating a thread pool or process pool. S3 parses the raw data in the original flight parameter file and generates a structured dataset; First, the original data is decoded using a decoder to obtain a data frame; then, the data frame is resampled according to the set sampling frequency to obtain a resampled frame; next, it is determined whether the target parameter needs to use a transformation relation. If so, the corresponding transformation relation of the target parameter is obtained, and the original code value in the resampled frame is converted into the actual value of the target parameter through the transformation relation; finally, all target parameters are aligned and serialized according to a unified time axis to generate a structured dataset. S4 encodes the structured dataset generated in S3 according to the output data format and writes it to a file to generate the final preprocessed result file.
[0007] Preferably, step S1 specifically includes the following steps: S101, Determine the flight parameter file path; The storage path of the original flight parameter files can be determined by directly entering or selecting the file directory, thus enabling flight parameter data preprocessing of the specified flight parameter files; or the storage path of a batch of original flight parameter files can be obtained by directly entering or selecting a root directory and then setting the original flight parameter file filtering conditions, thus enabling flight parameter data preprocessing of the batch of flight parameter files. S102, at the output format, the desired output data format is determined by directly inputting or selecting the format of the output file; S103, at the parameter extraction point, select whether to import an existing parameter extraction template. If yes, proceed to S104; otherwise, proceed directly to S105. S104, Select a parameter extraction template, obtain the target parameter and sampling frequency from the parameter extraction template, automatically fill them into the target parameter and sampling frequency fields respectively, and then end the step; S105, at the target parameter extraction point, select the target parameter from the system parameter library by checking the box or searching; S106, Set the frequency range at the sampling frequency of parameter extraction; S107, save the configured parameter extraction as a parameter extraction template.
[0008] Preferably, in step S101, the storage path of a batch of original flight parameter files is obtained by directly inputting or selecting a root directory and then setting the original flight parameter file filtering conditions. Specifically: The filtering criteria are a date range, an aircraft number, or a combination of both. The specific filtering process is as follows: First, all files in the root directory are recursively scanned. Then, raw flight parameter files that match the date range and aircraft number are filtered out based on the file name. Finally, for the files that pass the initial screening, the format identifier in their file header is read to confirm that the file is a flight parameter file. Finally, a list of raw flight parameter files that meet the criteria is obtained, and the storage path of each raw flight parameter file is obtained based on the list of raw flight parameter files.
[0009] Preferably, the system parameter library in S103 contains metadata and conversion relationships of all available parameters of the aircraft, including conversion formulas, conversion curves, or conversion tables.
[0010] Preferably, the parameter extraction template in S107 is stored in JSON, XML or database format.
[0011] Preferably, in step S2, the decoder is determined by the file extension, magic name, and aircraft type information of the original flight parameter file obtained by parsing the file header information.
[0012] Preferably, in step S2, based on the aircraft type information of the original flight parameter file, the decoder is determined by reading the timestamp and aircraft version information inside the file.
[0013] Preferably, step S3 involves parsing the raw data in the original flight parameter file to generate a structured dataset. The specific steps are as follows: S301, call the decoder determined by S2 to parse the binary stream into data frames containing timestamps and raw code values; S302, based on the sampling frequency of each target parameter in the parameter extraction, resample the parsed data frame to obtain a resampled frame. The resampling includes upsampling, downsampling or interpolation, and each target parameter is resampled to the set sampling frequency. S303: Determine whether the target parameter needs to be transformed. If not, proceed directly to S305; otherwise, proceed to S304. S304: Obtain the pre-stored conversion relationship of the target parameters from the system parameter library, and convert the original code value in the resampled frame into the actual value of the target parameter through the conversion relationship; after all the conversion relationships of the target parameters are executed, execute S305. S305, Time Series Organization, integrates the resampled frame sequences of all target parameters according to the timestamp order through methods such as linear interpolation, nearest neighbor interpolation or mean aggregation, forming a structured dataset with time as the index and each parameter as the column. The timestamp in the structured dataset is based on the highest sampling frequency among all target parameters.
[0014] Preferably, it also includes S5, which allows interaction through a graphical interface; During flight parameter data preprocessing, users can monitor the execution progress of preprocessing tasks in real time through a graphical interface, including: displaying the estimated remaining processing time, current processing status, number of processed files, processing speed, and error messages; users can also pause, continue, or cancel preprocessing tasks through the interactive interface.
[0015] In another aspect, this invention discloses an apparatus for a flight parameter data preprocessing method based on a custom template, comprising: a configuration receiving module, a file acquisition module, a format recognition module, a template management module, a data processing module, a format conversion module, a storage module, and a system parameter library, with the specific connection relationships as follows: The configuration receiving module is used to provide an interface to receive user configuration input, which includes the flight parameter file storage path, output data format, and parameter extraction. The configuration receiving module sends the flight parameter file storage path to the file acquisition module, sends the output data format to the format conversion module, sends the new parameter extraction to the template management module or directly calls the existing parameter extraction template from the template management module, and sends the target parameter and sampling frequency in the parameter extraction to the data processing module. The template management module is used to store, retrieve, and load parameter-extracted templates. The file acquisition module is used to read files into memory or a streaming buffer based on the storage path received from the configuration receiving module; The format recognition module automatically detects and recognizes the format of the original flight parameter file based on the file extension, file magic word, and information of the original flight parameter file in memory or streaming buffer, and determines the corresponding decoder. The data processing module uses a decoder to decode the original flight parameter file, resamples the original flight parameter file according to the target parameters, sampling frequency, and conversion relationships in the system parameter library received from the configuration receiving module to obtain the target parameters, and serializes all target parameters to obtain a structured dataset; the structured dataset is then sent to the format conversion module. The system parameter library is used to store the metadata and conversion relationships of all available parameters of the aircraft; The format conversion module is used to encode the structured dataset into the output data format received from the configuration receiving module to obtain a preprocessed result file, and then send the preprocessed result file to the storage module. The storage module is used to save the preprocessed result files.
[0016] Compared with the prior art, the beneficial effects of the present invention include: 1. This invention decouples data processing logic from program code through parameter extraction templates. Users can freely configure the parameters to be extracted and sampling frequency through a visual interface without modifying the code, which greatly improves the system's flexibility, adaptability and maintainability.
[0017] 2. This invention achieves automatic identification of flight parameter files by automatically determining the decoder, and obtains a structured dataset by resampling and reconstructing time-series data, thus realizing the preprocessing of flight parameter data.
[0018] 3. This invention uses parallel processing technology and batch processing mode, which can make full use of multi-core CPU resources and process multiple flight parameter files at the same time, significantly shortening the total time of large-scale data processing.
[0019] 4. This invention provides a graphical user interface that encapsulates the complex underlying decoding and calculation logic, lowering the technical threshold for users and enabling engineering technicians to easily complete data preprocessing work.
[0020] 5. This invention supports multiple output formats, has cross-platform operation capabilities, and can be easily integrated into different data processing pipelines or analysis platforms, thus improving the versatility of flight parameter data preprocessing. Attached Figure Description
[0021] Figure 1 This is a flowchart of the flight parameter data preprocessing method based on a custom template according to the present invention; Figure 2 A flowchart illustrating the configuration requirements for flight parameter data preprocessing in this invention; Figure 3 This is a flowchart illustrating the process of generating a structured dataset by parsing the original flight parameter file in this invention; Figure 4 This is a schematic diagram of the apparatus for the flight parameter data preprocessing method based on a custom template according to the present invention. Detailed Implementation
[0022] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments.
[0023] This embodiment provides a flight parameter data preprocessing method based on a custom template, such as... Figure 1 As shown, it includes the following steps: S1 allows users to configure flight parameter data preprocessing requirements using custom templates.
[0024] Users input their flight parameter data preprocessing requirements through a graphical interface or configuration file, including the flight parameter file storage path, output data format, and parameter extraction. Parameter extraction includes at least the target parameter and sampling frequency.
[0025] The completed parameter extraction settings will be saved as a parameter extraction template. This saved template can be directly selected or modified by the user, improving the speed of parameter extraction configuration for preprocessed flight parameter data.
[0026] Flight parameter data preprocessing requirements configuration as follows Figure 2 As shown, the specific process is as follows: S101, Determine the flight parameter file path.
[0027] Determining the flight parameter file path involves two scenarios: First, the storage path of the original flight parameter files can be determined by directly inputting or selecting a file directory, enabling preprocessing of the specified flight parameter files. Second, the storage path of a batch of original flight parameter files can be obtained by directly inputting or selecting a root directory and then setting filtering conditions for the original flight parameter files, enabling preprocessing of the batch of flight parameter files.
[0028] The filtering criteria are date range, aircraft number, or a combination of both. In the root directory of the storage path, all raw flight parameter files that meet the filtering criteria are selected as flight parameter files requiring preprocessing. Since the filenames of the raw flight parameter files consist of the aircraft number and the latest modification time, the specific filtering process is as follows: First, all files in the root directory are recursively scanned. Then, raw flight parameter files that meet the date range and aircraft number are quickly pre-filtered based on their filenames. Finally, for the files that pass the initial screening, the format identifier in their file header is read to confirm that the file is a flight parameter file, resulting in a list of raw flight parameter files that meet the criteria. The storage path for each raw flight parameter file is then determined based on this list.
[0029] If the input storage path is: working directory on drive D, when the storage path is detected as a root directory rather than a file, two filter conditions will appear: date range and aircraft number. If the date range is set to: January 1, 2023 to December 31, 2023, and the aircraft number is set to B-XXXX, then all original flight parameter files in the working directory on drive D whose names contain B-XXXX and whose dates are between January 1, 2023 and December 31, 2023 will be filtered out as the original flight parameter files that need to be preprocessed.
[0030] S102, at the output format, the desired output data format is determined by directly inputting or selecting the output file format; the desired output data format can be MessagePack for efficient storage or CSV for manual viewing.
[0031] S103, at the parameter extraction point, select whether to import an existing parameter extraction template. If yes, proceed to S104; otherwise, proceed directly to S105.
[0032] S104, Select a parameter extraction template, obtain the target parameter and sampling frequency from the parameter extraction template, automatically fill them into the target parameter and sampling frequency fields respectively, and then end the step.
[0033] S105, at the target parameter extraction point, select one or more target parameters from the integrated system parameter library by checking a box or searching. The system parameter library contains metadata and conversion relationships for all available aircraft parameters. Conversion relationships typically include conversion formulas, conversion curves, or conversion tables. These conversion relationships do not convert between different parameters; they only convert the original parameter values in the original flight parameter file. For example, if the pressure value of a device in the original flight parameter file is 9, it does not mean the device pressure is only 9 Pa, but rather 90,000 Pa. Therefore, after reading the pressure value of a device in the original flight parameter file, a conversion relationship is needed to convert it to its actual value. Target parameters can be aircraft parameters contained in the original flight parameter file, such as altitude, airspeed, pressure, temperature, and engine speed.
[0034] S106, set the frequency range at the parameter extraction sampling frequency; the frequency range supports from low to 1Hz to high to 100Hz, and can be flexibly set according to analysis needs. For example, the sampling frequency of slowly changing cabin temperature parameters can be selected as 1Hz, and the sampling frequency of high-frequency vibration signals can be selected as 100Hz.
[0035] S107 saves the configured parameter extraction as a parameter extraction template, which can be directly called during similar preprocessing later. When saving a new parameter extraction template, the system can search for an existing template. If an identical template exists, a prompt should be displayed to confirm whether a new template needs to be saved. If not, the user should be prompted to enter a name for the new template. Multiple parameter extraction templates can be pre-saved to meet different flight parameter data preprocessing needs, such as an "engine performance analysis template" or a "flight dynamics analysis template." Parameter extraction templates can be stored in JSON, XML, or database record formats.
[0036] S2 reads the original flight parameter file into memory or a streaming buffer and calls the decoder, depending on the storage path.
[0037] Each raw flight parameter file is read into memory or a streaming buffer based on its storage path to obtain the raw data. The aircraft type information of the raw flight parameter file is determined by its file extension, magic number, and header information. For formats that embed flight information, the timestamp and aircraft version within the file can be further read. The encoding format of the raw flight parameter file is automatically identified through precise matching, and the corresponding decoder is invoked.
[0038] When there are multiple raw flight parameter files, each raw flight parameter file can be executed as an independent task by creating a thread pool or process pool.
[0039] S3 parses the raw data in the original flight parameter file and generates a structured dataset.
[0040] First, the original data is decoded using a decoder to obtain data frames. Then, the data frames are resampled according to the set sampling frequency to obtain resampled frames. Next, it is determined whether the target parameters need to use transformation relations. If so, the corresponding transformation relations for the target parameters are obtained, and the original code values in the resampled frames are converted into the actual values of the target parameters using the transformation relations. Finally, all target parameters are aligned and serialized according to a unified time axis to generate a structured dataset. Figure 3 As shown, the specific steps are as follows: S301, Format Parsing; calls the decoder determined by S2 to parse the binary stream into data frames containing timestamps and raw code values. The raw code values can be of two data types: floating-point numbers (Float) and Boolean values (Boolean).
[0041] S302, based on the sampling frequency of each target parameter in the parameter extraction, the parsed data frame is resampled to obtain a resampled frame; resampling includes upsampling, downsampling or interpolation, and each target parameter is resampled to the set sampling frequency.
[0042] S303: Determine whether the target parameter needs to be transformed. If not, execute S305 directly; otherwise, execute S304.
[0043] S304: Obtain the pre-stored conversion relationship of the target parameters from the system parameter library, and convert the original code value in the resampled frame into the actual value of the target parameter through the conversion relationship; after all the conversion relationships of the target parameters are executed, S305 is executed.
[0044] S305, Time Series Organization, integrates the resampled frame sequences of all target parameters according to timestamp order using methods such as linear interpolation, nearest neighbor interpolation, or mean aggregation, forming a structured dataset with time as the index and each parameter as the column. The timestamps in the structured dataset are based on the highest sampling frequency among all target parameters. The structured dataset can be a Pandas DataFrame or an array of in-memory structures.
[0045] S4 encodes the structured dataset generated in S3 according to the output data format and writes it to a file to generate the final preprocessed result file.
[0046] The preprocessed result files are usually in MessagePack or CSV format.
[0047] The filename of the preprocessed result file is formed by appending the name of the parameter extraction template to the original flight parameter file name. When preprocessing multiple flight parameter files, all generated preprocessed result files can be automatically organized and stored according to preset rules, and a batch processing summary report can be generated. For example, the preset rule is to store the final preprocessed result files in a directory structure of "aircraft number / date".
[0048] The batch processing summary report may include information such as processing time, number of files processed, and a list of file names.
[0049] S5 allows for interaction through a graphical interface.
[0050] During flight parameter data preprocessing, users can also monitor the execution progress of preprocessing tasks in real time through a graphical interface, including: displaying the estimated remaining processing time, current processing status, number of processed files, processing speed, and error messages; it also supports users to pause, continue, or cancel preprocessing tasks through an interactive interface.
[0051] This invention also provides an apparatus for a flight parameter data preprocessing method based on a custom template, corresponding to the above method, such as... Figure 4 As shown, it includes: a configuration receiving module 401, a file acquisition module 402, a format recognition module 403, a template management module 404, a data processing module 405, a format conversion module 406, a storage module 407, and a system parameter library 408, specifically: The configuration receiving module 401 provides an interface for receiving user configuration input, which includes the flight parameter file storage path, output data format, and parameter extraction. Parameter extraction includes at least the target parameter and sampling frequency. The configuration receiving module 401 sends the flight parameter file storage path to the file acquisition module 402, the output data format to the format conversion module 406, and new parameter extractions to the template management module 404, or directly calls an existing parameter extraction template from the template management module 404. It also sends the target parameter and sampling frequency from the parameter extraction to the data processing module 405.
[0052] The template management module returned a 404 error, which is used to store, retrieve, and load templates with extracted parameters.
[0053] The file acquisition module 402 is used to read files into memory or a streaming buffer according to the storage path received from the configuration receiving module 401.
[0054] The format recognition module 403 automatically detects and recognizes the format of the original flight parameter file based on the file extension, file magic word, and information of the original flight parameter file in memory or streaming buffer, and determines the corresponding decoder.
[0055] The data processing module 405 uses a decoder to decode the original flight parameter file. Based on the target parameters, sampling frequency, and conversion relationships received from the configuration receiving module 401 and the system parameter library 408, it resamples the original flight parameter file to obtain resampled frames of the target parameters. It then serializes all the resampled frames of the target parameters to obtain a structured dataset. The structured dataset is then sent to the format conversion module 406.
[0056] System parameter library 408 stores metadata and conversion relationships for all available aircraft parameters. Conversion relationships typically include conversion formulas, conversion curves, or conversion tables.
[0057] The format conversion module 406 is used to encode the structured dataset into the output data format received from the configuration receiving module 401 to obtain a preprocessed result file, and send the preprocessed result file to the storage module 407.
[0058] Storage module 407 is used to save preprocessed result files.
[0059] Furthermore, it may also include auxiliary function modules, including an error handling submodule for handling operational exceptions, a logging submodule for auditing and debugging, and a performance monitoring submodule for ensuring timely processing.
[0060] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.
Claims
1. A method for preprocessing flight parameter data based on a custom template, characterized in that: It includes the following steps: S1, users can configure flight parameter data preprocessing requirements through custom templates; Users input their flight parameter data preprocessing requirements through a graphical interface or configuration file, including the flight parameter file storage path, output data format, and parameter extraction. Parameter extraction includes at least the target parameter and sampling frequency. Users can directly select a saved parameter extraction template or save the newly configured parameter extraction as a new parameter extraction template. S2, based on the storage path, reads the original flight parameter file into memory or a streaming buffer and calls the decoder; Each raw flight parameter file is read into memory or a streaming buffer based on the storage path to obtain the raw data; when there are multiple raw flight parameter files, each raw flight parameter file is executed as an independent task by creating a thread pool or process pool. S3 parses the raw data in the original flight parameter file and generates a structured dataset; First, the original data is decoded using a decoder to obtain a data frame; then, the data frame is resampled according to the set sampling frequency to obtain a resampled frame; next, it is determined whether the target parameter needs to use a transformation relation. If so, the corresponding transformation relation of the target parameter is obtained, and the original code value in the resampled frame is converted into the actual value of the target parameter through the transformation relation; finally, all target parameters are aligned and serialized according to a unified time axis to generate a structured dataset. S4 encodes the structured dataset generated in S3 according to the output data format and writes it to a file to generate the final preprocessed result file.
2. The flight parameter data preprocessing method based on a custom template according to claim 1, characterized in that: S1 includes the following specific steps: S101, Determine the flight parameter file path; The storage path of the original flight parameter files can be determined by directly entering or selecting the file directory, thus enabling flight parameter data preprocessing of the specified flight parameter files; or the storage path of a batch of original flight parameter files can be obtained by directly entering or selecting a root directory and then setting the original flight parameter file filtering conditions, thus enabling flight parameter data preprocessing of the batch of flight parameter files. S102, at the output format, the desired output data format is determined by directly inputting or selecting the format of the output file; S103, at the parameter extraction point, select whether to import an existing parameter extraction template. If yes, proceed to S104; otherwise, proceed directly to S105. S104, Select a parameter extraction template, obtain the target parameter and sampling frequency from the parameter extraction template, automatically fill them into the target parameter and sampling frequency fields respectively, and then end the step; S105, at the target parameter extraction point, select the target parameter from the system parameter library by checking the box or searching; S106, Set the frequency range at the sampling frequency of parameter extraction; S107, save the configured parameter extraction as a parameter extraction template.
3. The flight parameter data preprocessing method based on a custom template according to claim 2, characterized in that: In S101, the storage path for a batch of raw flight parameter files can be obtained by directly inputting or selecting a root directory and then setting the raw flight parameter file filtering conditions. Specifically: The filtering criteria are a date range, an aircraft number, or a combination of both. The specific filtering process is as follows: First, all files in the root directory are recursively scanned. Then, raw flight parameter files that match the date range and aircraft number are filtered out based on the file name. Finally, for the files that pass the initial screening, the format identifier in their file header is read to confirm that the file is a flight parameter file. Finally, a list of raw flight parameter files that meet the criteria is obtained, and the storage path of each raw flight parameter file is obtained based on the list of raw flight parameter files.
4. The flight parameter data preprocessing method based on a custom template according to claim 2, characterized in that: The system parameter library in S103 contains metadata and conversion relationships for all available aircraft parameters. These conversion relationships include conversion formulas, conversion curves, or conversion tables.
5. The flight parameter data preprocessing method based on a custom template according to claim 2, characterized in that: In S107, parameter extraction templates are stored in JSON, XML, or database formats.
6. The flight parameter data preprocessing method based on a custom template according to claim 1, characterized in that: In S2, the decoder is determined by the file extension, magic word, and aircraft type information of the original flight parameter file obtained by parsing the file header information.
7. The flight parameter data preprocessing method based on a custom template according to claim 6, characterized in that: In S2, based on the aircraft type information already determined in the original flight parameter file, the decoder is determined by reading the timestamp and aircraft version information inside the file.
8. The flight parameter data preprocessing method based on a custom template according to claim 1, characterized in that: S3 parses the raw data in the original flight parameter file to generate a structured dataset. The specific steps are as follows: S301, call the decoder determined by S2 to parse the binary stream into data frames containing timestamps and raw code values; S302, based on the sampling frequency of each target parameter in the parameter extraction, resample the parsed data frame to obtain a resampled frame. The resampling includes upsampling, downsampling or interpolation, and each target parameter is resampled to the set sampling frequency. S303: Determine whether the target parameter needs to be transformed. If not, proceed directly to S305; otherwise, proceed to S304. S304: Obtain the conversion relationship of the pre-stored target parameters from the system parameter library, and convert the original code value in the resampled frame into the actual value of the target parameter through the conversion relationship; Once all the transformation relationships of the target parameters have been executed, S305 is executed. S305, Time Series Organization, integrates the resampled frame sequences of all target parameters according to the timestamp order through methods such as linear interpolation, nearest neighbor interpolation or mean aggregation, forming a structured dataset with time as the index and each parameter as the column. The timestamp in the structured dataset is based on the highest sampling frequency among all target parameters.
9. The flight parameter data preprocessing method based on a custom template according to claim 1, characterized in that: It also includes S5, which allows interaction through a graphical interface; During flight parameter data preprocessing, users can monitor the execution progress of the preprocessing task in real time through a graphical interface, including: displaying the estimated remaining processing time, current processing status, number of processed files, processing speed, and error messages; It also allows users to pause, resume, or cancel preprocessing tasks through an interactive interface.
10. An apparatus for using the flight parameter data preprocessing method based on a custom template as described in claim 1, characterized in that: It includes: Configure the receiving module, file acquisition module, format recognition module, template management module, data processing module, format conversion module, storage module, and system parameter library. The specific connection relationships are as follows: The configuration receiving module is used to provide an interface to receive user configuration input, which includes the flight parameter file storage path, output data format, and parameter extraction. The configuration receiving module sends the flight parameter file storage path to the file acquisition module, sends the output data format to the format conversion module, sends the new parameter extraction to the template management module or directly calls the existing parameter extraction template from the template management module, and sends the target parameter and sampling frequency in the parameter extraction to the data processing module. The template management module is used to store, retrieve, and load parameter-extracted templates. The file acquisition module is used to read files into memory or a streaming buffer based on the storage path received from the configuration receiving module; The format recognition module automatically detects and recognizes the format of the original flight parameter file based on the file extension, file magic word, and information of the original flight parameter file in memory or streaming buffer, and determines the corresponding decoder. The data processing module uses a decoder to decode the original flight parameter file, and then resamples the original flight parameter file according to the target parameters, sampling frequency, and conversion relationships in the system parameter library received from the configuration receiving module to obtain the target parameters. Finally, it serializes all target parameters to obtain a structured dataset. Send the structured dataset to the format conversion module; The system parameter library is used to store the metadata and conversion relationships of all available parameters of the aircraft; The format conversion module is used to encode the structured dataset into the output data format received from the configuration receiving module to obtain a preprocessed result file, and then send the preprocessed result file to the storage module. The storage module is used to save the preprocessed result files.