A unified storage conversion method and system for finite element analysis result data

Abstract

The application discloses a unified storage conversion method and system for finite element analysis result data, relates to the field of data conversion, and solves the problem that current finite element result data cannot be effectively stored and converted. The method comprises the following steps: converting different original files into identifiable files through a converter plug-in, and extracting finite element result data in the identifiable files; processing three-dimensional result arrays in the finite element result data to obtain reorganized result arrays; performing data deduplication on the finite element result data, and intelligently grouping different standard physical quantities in the reorganized result arrays according to byte bits; storing node coordinate arrays, element connectivity arrays and different byte bit arrays into different subfolders respectively, and querying the byte bit arrays according to different query conditions. The application realizes effective storage and conversion of finite element result data.

Description

Technical Field

[0001] This invention belongs to the field of data conversion technology, specifically a unified storage and conversion method and system for finite element analysis result data. Background Technology

[0002] With the in-depth development of industrial software, CAE simulation technology is increasingly widely used in aerospace, equipment manufacturing, and new energy fields. Whether it is mainstream commercial software or independently developed industrial software solvers, they all face common technical challenges in the storage and management of simulation results. Each software system adopts its own data storage method, lacking a unified data standard and interoperability mechanism, which seriously restricts the promotion and application of CAE technology and the construction of the industrial software ecosystem. Among these challenges, the problem of wasted storage space is the most prominent, accompanied by secondary problems such as data format fragmentation, low access efficiency, inconsistent units, and difficulty in long-term storage.

[0003] Because existing data formats generally lack effective compression techniques, most existing unified storage and conversion methods for finite element analysis results data suffer from storage space waste. At the same time, current finite element analysis results data exist in multiple incompatible data formats, and different formats cannot be directly interoperated, which increases the difficulty of data operation. On the other hand, different solvers use different unit systems, and when comparing and analyzing results across solvers, inconsistent units will lead to numerical errors. Existing technologies cannot effectively store and convert finite element results data.

[0004] Therefore, this invention proposes a unified storage and conversion method and system for finite element analysis results data. Summary of the Invention

[0005] The purpose of this invention is to propose a unified storage and conversion method and system for finite element analysis results data, so as to solve the problem mentioned in the background art of the inability to effectively store and convert finite element results data.

[0006] To achieve the above objectives, the present invention adopts the following technical solution:

[0007] A unified storage and conversion method for finite element analysis result data, the method comprising:

[0008] Step S1: Convert different original files into recognizable files using a converter plugin, and extract finite element result data from the recognizable files;

[0009] Step S2: Process the three-dimensional result array in the finite element result data to obtain a reconstructed result array;

[0010] Step S3: Deduplicate the finite element result data and intelligently group different standard physical quantities in the recombined result array according to byte bits.

[0011] Step S4: Store the node coordinate array, the cell connectivity array, and the arrays of different byte positions into different subfolders, and query the byte positions arrays according to different query conditions.

[0012] Further, step S1 includes the following sub-steps:

[0013] Step S101: Collect the file extensions of different original files, query the converter plugins with the corresponding file extensions in the pluggable multi-format parser architecture, and use the corresponding converter plugins to convert the original files into different recognizable files.

[0014] Step S102: Obtain the node number and three-dimensional coordinates of different nodes in the identifiable file, and use the node number as the first element and the three-dimensional coordinates of the node as the second element to construct an array of node coordinates corresponding to different nodes in the identifiable file.

[0015] Step S103: Obtain the actual element type identifiers of different elements in the finite element network within the identifiable file, match the element type of the corresponding element based on the actual element type identifiers, and uniformly map the actual element type identifiers corresponding to the same element type to the standard element type identifiers.

[0016] Furthermore, step S1 also includes the following sub-steps:

[0017] Step S104: Count the number of different standard unit type identifiers in the identifiable file and record them as the standard type number; collect the number of nodes connected to the unit corresponding to the standard unit type identifier and record them as the connection node number; construct the unit connectivity array with the standard type number as the first element and the connection node number as the second element.

[0018] Step S105: Obtain the unit number of different units in the identifiable file, and associate the unit number with the standard unit type identifier of the corresponding unit to obtain unit type mapping data;

[0019] Step S106: Obtain the initial physical quantities corresponding to different nodes at different time points in the identifiable file. Construct a three-dimensional result array corresponding to different nodes at different time points with the node number as the first element, the time node as the second element, and the initial physical quantity as the third element.

[0020] Step S107: The node coordinate array, element type mapping data, and three-dimensional result array are all recorded as finite element result data.

[0021] Furthermore, the processing in step S2 includes the following sub-steps:

[0022] Step S201: Store different preset physical quantities in the database, and change the names of different initial physical quantities in the three-dimensional result array to the names of the corresponding preset physical quantities;

[0023] Step S202: Obtain the initial units of different initial physical quantities in the three-dimensional result array, divide the initial units by the standard units to obtain the conversion values, and multiply the initial physical quantities by the conversion values ​​to obtain the standard physical quantities corresponding to different units at different time points;

[0024] Step S203: Replace the initial physical quantity corresponding to the first element in the three-dimensional result array with the corresponding standard physical quantity, swap the positions of the first and second elements in the replaced array, and record the swapped array as the recombined result array.

[0025] Furthermore, step S3 includes the following sub-steps:

[0026] Step S301: Calculate the hash value corresponding to the node coordinate array at different time points and record it as the coordinate hash value;

[0027] Step S302: Compare the coordinate hash values ​​corresponding to the node coordinate arrays at different time points;

[0028] If any two sets of time nodes have the same coordinate hash value, then one set of node coordinate arrays is retained and the other set is discarded; if all time nodes have different coordinate hash values, then all node coordinate arrays are retained; and so on, the same analysis is performed on the cell connectivity arrays to obtain the retained cell connectivity arrays.

[0029] Step S303: Select the recombination result array corresponding to any time node, extract the standard physical quantities corresponding to different node numbers, and sort the standard physical quantities in ascending order according to the node numbers to obtain the sequence to be processed.

[0030] Furthermore, step S3 also includes the following sub-steps:

[0031] Step S304: Select adjacent multi-bit elements in the sequence to be processed from left to right, count the number of bytes of the corresponding multi-bit elements, and traverse and compare the number of bytes of the multi-bit elements to obtain the maximum number of bytes.

[0032] Step S305: Based on the maximum number of bytes, the corresponding multi-bit elements are split from left to right into the first byte, the second byte, ..., the nth byte, where n is the byte number;

[0033] Step S306: Store the first byte of the corresponding multi-bit element in the same array and record the corresponding array as the first byte array. Store the second byte of the different standard physical quantities in the same array and record the corresponding array as the second byte array. And so on, store the nth byte of the different standard physical quantities in the same array and record the corresponding array as the nth byte array.

[0034] Furthermore, the query process in step S4 includes the following sub-steps:

[0035] Step S401: When the query conditions are fixed node coordinates and query radius, obtain the node coordinates corresponding to different nodes, calculate the straight-line distance between the coordinates of different nodes and the fixed node coordinates using the distance formula, and take the nodes whose straight-line distance is less than or equal to the query radius as query result nodes, and extract different byte arrays according to the node number corresponding to the query result nodes.

[0036] Step S402: When the query conditions are fixed node coordinates and query quantity, obtain the node coordinates corresponding to different nodes, calculate the straight-line distance between the coordinates of different nodes and the fixed node coordinates using the distance formula, sort the different nodes in ascending order according to the straight-line distance, and obtain the node sequence. Select the same number of nodes as the query quantity from left to right and record them as query result nodes. Extract different byte arrays according to the node number corresponding to the query result nodes.

[0037] Step S403: When the query condition is a fixed time, obtain the node coordinates corresponding to different nodes, subtract the fixed time from the time corresponding to different time nodes and take the absolute value to obtain the time node deviation, traverse and compare the time node deviations to obtain the minimum time node deviation, and record the time node corresponding to the minimum time node deviation as the query time node, and extract different byte bit arrays based on the query time node.

[0038] Secondly, a unified storage and conversion system for finite element analysis results data includes:

[0039] The conversion and extraction module is used to convert different raw files into recognizable files through a converter plugin, and extract finite element result data from the recognizable files;

[0040] The intelligent processing module is used to process the three-dimensional result array in the finite element result data to obtain a reconstructed result array;

[0041] The data processing module is used to deduplicate the finite element result data and intelligently group different standard physical quantities in the recombined result array according to the byte bits.

[0042] The storage query module is used to store the node coordinate array, the cell connectivity array, and the arrays of different byte positions into different subfolders, and to query the byte position arrays according to different query conditions.

[0043] Compared with the prior art, the beneficial effects of the present invention are:

[0044] 1. This invention uses a converter plugin to convert different original files into recognizable files, thereby extracting finite element result data from the recognizable files. Then, the three-dimensional result array in the finite element result data is processed to obtain a reconstructed result array.

[0045] 2. This invention performs data deduplication on finite element result data, and intelligently groups different standard physical quantities in the recombined result array according to byte positions. Finally, the node coordinate array, element connectivity array and different byte position arrays are stored in different subfolders, and the byte position arrays are queried according to different query conditions. Attached Figure Description

[0046] To facilitate understanding by those skilled in the art, the present invention will be further described below with reference to the accompanying drawings.

[0047] Figure 1 This is a flowchart of the method of the present invention;

[0048] Figure 2 This is a logic flowchart of the present invention;

[0049] Figure 3 This is a system block diagram of the present invention. Detailed Implementation

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

[0051] Example 1: Please refer to Figure 1 and Figure 2As shown, the technical solution provided by this invention is: a unified storage and conversion method for finite element analysis result data. This method utilizes a plug-in multi-format parser architecture to convert different original files into recognizable files, wherein the finite element network within the recognizable file consists of multiple nodes and elements; then, finite element result data is extracted from the recognizable file, and the names and units of the finite element result data are unified. Simultaneously, the three-dimensional result arrays in the finite element result data are arranged in chronological order, and different finite element analysis result data are deduplicated and compressed. Next, the different finite element analysis result data are stored hierarchically. Finally, the corresponding query results are output according to different query conditions. The method includes the following steps:

[0052] Step S1: Convert different original files into recognizable files using a converter plugin, and extract finite element result data from the recognizable files;

[0053] In this embodiment, step S1 includes the following sub-steps:

[0054] Step S101: Collect the file extensions of different original files, query the converter plugins with the corresponding file extensions in the pluggable multi-format parser architecture, and use the corresponding converter plugins to convert the original files into different recognizable files.

[0055] In practical implementation, the pluggable multi-format parser architecture consists of multiple converter plugins. Different file extensions correspond to different independent converter plugins. When importing the original file, the pluggable multi-format parser architecture first automatically identifies the format type by the file extension, and then queries and calls the corresponding converter plugin. For example, the converter plugins include: Nastran H5 converter (processes .h5 / .hdf5 format, reads HDF5 datasets through the h5py library), CalculiXFRD converter (processes .frd format, reads fixed-column-width text through a self-developed ASCII line-by-line parser), and Abaqus ODB converter (processes .odb format, reads proprietary binary data through the odbAccess module of the Abaqus Python API).

[0056] Step S102: Obtain the node number and three-dimensional coordinates of different nodes in the identifiable file, and use the node number as the first element and the three-dimensional coordinates of the node as the second element to construct an array of node coordinates corresponding to different nodes in the identifiable file.

[0057] In this embodiment, nodes are the most basic geometric points in the finite element mesh, possessing spatial coordinates (X, Y, Z) and physical field degrees of freedom (displacement, temperature, etc.). Elements are discrete computational volumes composed of several nodes connected according to topological rules, used to approximate the mechanical behavior of continuous media (such as four-node shell elements, eight-node hexahedral elements, etc.). In Nastran H5 format, node numbers and node 3D coordinates are stored in the ID and X datasets under the / NASTRAN / INPUT / NODE / GRID group of the HDF5 file; in CalculiX FRD format, node numbers and node 3D coordinates are stored in fixed-width text lines starting with "2C", with each line containing the node number and X, Y, and Z coordinate values; in Abaqus ODB format, node numbers and node 3D coordinates are obtained by iterating through the rootAssembly.instances[name].nodes object.

[0058] Step S103: Obtain the actual element type identifiers of different elements in the finite element network within the identifiable file, match the element type of the corresponding element based on the actual element type identifiers, and uniformly map the actual element type identifiers corresponding to the same element type to the standard element type identifiers.

[0059] In the specific implementation process, the identifiable files all contain a mapping table between actual unit type identifiers and unit types, that is, the unit types corresponding to different actual unit type identifiers;

[0060] For example, Nastran's CQUAD4, CalculiX's S4R, and Abaqus's S4R all represent four-node shell elements, so the three actual element type identifiers are uniformly mapped to "quad4"; Nastran's CHEXA8, CalculiX's C3D8, and Abaqus's C3D8 all represent eight-node hexahedral solid elements, so the three actual element type identifiers are uniformly mapped to "hex8".

[0061] Step S104: Count the number of different standard unit type identifiers in the identifiable file and record them as the standard type number; collect the number of nodes connected to the unit corresponding to the standard unit type identifier and record them as the connection node number; construct the unit connectivity array with the standard type number as the first element and the connection node number as the second element.

[0062] Step S105: Obtain the unit number of different units in the identifiable file, and associate the unit number with the standard unit type identifier of the corresponding unit to obtain unit type mapping data;

[0063] Step S106: Obtain the initial physical quantities corresponding to different nodes at different time points in the identifiable file. Construct a three-dimensional result array corresponding to different nodes at different time points with the node number as the first element, the time node as the second element, and the initial physical quantity as the third element.

[0064] Step S107: The node coordinate array, element type mapping data, and three-dimensional result array are all recorded as finite element result data.

[0065] Step S2: Process the three-dimensional result array in the finite element result data to obtain a reconstructed result array;

[0066] In this embodiment, the processing in step S2 includes the following sub-steps:

[0067] Step S201: Store different preset physical quantities in the database, and change the names of different initial physical quantities in the three-dimensional result array to the names of the corresponding preset physical quantities;

[0068] In this embodiment, the preset physical quantities include, but are not limited to, kinematic quantities: displacement, velocity, acceleration, rotation angle, angular velocity, and angular acceleration; mechanical quantities: constraint reaction force, applied external force, resultant force at grid points, multi-point constraint force, and the corresponding four types of torque; stress and strain quantities: stress tensor, strain tensor, plastic strain tensor, equivalent stress, equivalent strain, equivalent plastic strain, and equivalent creep strain; thermal quantities: temperature, temperature gradient, and heat flux density; and modal quantities: modal displacement mode shape, modal rotation mode shape, natural frequency, and buckling factor. Energy-related: Strain energy, kinetic energy, internal energy and their density and percentage variants; Beam and shell-specific: Beam element force / moment / stress / strain, shell element force / moment; Composite materials: Layer stress, layer strain, interlaminar stress, layer thickness, layer fiber orientation angle, layer material ID; Contact-related: Contact normal force, contact tangential force, contact pressure, contact shear stress and contact gap; Damage and failure-related: Damage variables and failure indices; Fluid / electromagnetic: Fluid velocity, pressure, turbulent kinetic energy, electric field strength, magnetic field strength, electro / magnetic potential;

[0069] Step S202: Obtain the initial units of different initial physical quantities in the three-dimensional result array, divide the initial units by the standard units to obtain the conversion values, and multiply the initial physical quantities by the conversion values ​​to obtain the standard physical quantities corresponding to different units at different time points;

[0070] For example, if the actual unit is millimeters and the standard unit is meters, the converted value is 0.001. If the preset physical quantity is one millimeter, the standard physical quantity is 0.001 meters.

[0071] In this embodiment, the standard unit is the International System of Units (SI) corresponding to different initial physical quantities. For example, the SI unit for length is meter, the SI unit for mass is kilogram, the SI unit for time is second, the SI unit for electric current is ampere, and the SI unit for thermodynamic temperature is Kelvin.

[0072] Step S203: Replace the initial physical quantity corresponding to the first element in the three-dimensional result array with the corresponding standard physical quantity, swap the positions of the first and second elements in the replaced array, and record the swapped array as the recombined result array;

[0073] It needs to be explained that traditional solvers organize data by entity: first, they store the standard physical quantities of node 1 at all time points, then they store the standard physical quantities of node 2 at all time points, and so on. When it is necessary to read the standard physical quantities of all elements at a certain time point, the standard physical quantities are discretely distributed in the recognizable file, requiring jump readings at different locations within the recognizable file, resulting in a large number of random disk I / O operations and low efficiency. However, by swapping the axes of the 3D result array and reorganizing it, all entity data at the same time point are arranged continuously in memory.

[0074] Step S3: Deduplicate the finite element result data and intelligently group different standard physical quantities in the recombined result array according to byte bits.

[0075] In this embodiment, step S3 includes the following sub-steps:

[0076] Step S301: Calculate the hash value corresponding to the node coordinate array at different time points using a hash algorithm, and record it as the coordinate hash value;

[0077] It should be noted that the hash algorithm is an existing technology used to map data of arbitrary length to a fixed 256-bit digest;

[0078] Step S302: Compare the coordinate hash values ​​corresponding to the node coordinate arrays at different time points;

[0079] If any two sets of time nodes have the same coordinate hash value, then keep one set of node coordinate arrays and discard the other set of node coordinate arrays.

[0080] If the coordinate hash values ​​corresponding to the coordinate arrays of all time points are different, then all node coordinate arrays are retained;

[0081] Similarly, the same analysis is performed on the cell connectivity array to obtain the retained cell connectivity array;

[0082] Step S303: Select the recombination result array corresponding to any time node, extract the standard physical quantities corresponding to different node numbers, and sort the standard physical quantities in ascending order according to the node numbers to obtain the sequence to be processed;

[0083] Step S304: Select adjacent multi-bit elements in the sequence to be processed from left to right, count the number of bytes of the corresponding multi-bit elements, and traverse and compare the number of bytes of the multi-bit elements to obtain the maximum number of bytes.

[0084] Step S305: Based on the maximum number of bytes, the corresponding multi-bit elements are split from left to right into the first byte, the second byte, ..., the nth byte, where n is the byte number;

[0085] Step S306: Store the first byte of the corresponding multi-bit element in the same array and record the corresponding array as the first byte array; store the second byte of different standard physical quantities in the same array and record the corresponding array as the second byte array; and so on, store the nth byte of different standard physical quantities in the same array and record the corresponding array as the nth byte array.

[0086] For example, the selected multi-bit elements are [3.14, 3.15, 3.16]. Each element occupies 4 bytes, and the number of bits in each byte is equal to 4. Therefore, the 3 corresponding to the first byte is stored in the first byte array, the decimal point corresponding to the second byte is stored in the second byte array, the 1 corresponding to the third byte is stored in the third byte array, and the 4, 5, and 6 of the fourth byte are stored in the fourth byte array. Since the standard physical quantities of adjacent nodes are close, their high-order bytes are often the same. Grouping the same bytes together can reduce storage space.

[0087] Step S4: Store the node coordinate array, the cell connectivity array, and the arrays of different byte positions into different subfolders, and query the byte positions arrays according to different query conditions;

[0088] In this embodiment, the query process in step S4 includes the following sub-steps:

[0089] Step S401: When the query conditions are fixed node coordinates and query radius, obtain the node coordinates corresponding to different nodes, calculate the straight-line distance between the coordinates of different nodes and the fixed node coordinates using the distance formula, and take the nodes whose straight-line distance is less than or equal to the query radius as query result nodes, and extract different byte arrays according to the node number corresponding to the query result nodes.

[0090] Step S402: When the query conditions are fixed node coordinates and query quantity, obtain the node coordinates corresponding to different nodes, calculate the straight-line distance between the coordinates of different nodes and the fixed node coordinates using the distance formula, sort the different nodes in ascending order according to the straight-line distance, and obtain the node sequence. Select the same number of nodes as the query quantity from left to right and record them as query result nodes. Extract different byte arrays according to the node number corresponding to the query result nodes.

[0091] Step S403: When the query condition is a fixed time, obtain the node coordinates corresponding to different nodes, subtract the fixed time from the time corresponding to different time nodes and take the absolute value to obtain the time node deviation, traverse and compare the time node deviations to obtain the minimum time node deviation, and record the time node corresponding to the minimum time node deviation as the query time node, and extract different byte bit arrays based on the query time node.

[0092] In the specific implementation process, after obtaining the byte array based on the query conditions, the elements in the byte array are combined according to the number to obtain the standard physical quantity.

[0093] Example 2: Please refer to Figure 3 As shown, based on another concept of the same invention, a unified storage and conversion system for finite element analysis result data is proposed, including a conversion and extraction module, an intelligent processing module, a data processing module, and a storage and query module. The conversion and extraction module is used to convert different original files into recognizable files through a converter plugin and extract the finite element result data within the recognizable files. The intelligent processing module is used to process the three-dimensional result array in the finite element result data to obtain a reconstructed result array. The data processing module is used to deduplicate the finite element result data and intelligently group different standard physical quantities in the reconstructed result array according to byte positions. The storage and query module is used to store the node coordinate array, the element connectivity array, and the arrays of different byte positions into different subfolders, and to query the byte position arrays according to different query conditions.

[0094] The preferred embodiments of the present invention disclosed above are merely illustrative of the invention. These preferred embodiments do not exhaustively describe all details, nor do they limit the invention to any specific implementation. Clearly, many modifications and variations can be made based on the content of this specification. This specification selects and specifically describes these embodiments to better explain the principles and practical applications of the invention, thereby enabling those skilled in the art to better understand and utilize the invention. The invention is limited only by the claims and their full scope and equivalents.

Claims

1. A unified storage and conversion method for finite element analysis result data, characterized in that, The methods include: Step S1: Convert different original files into recognizable files using a converter plugin, and extract finite element result data from the recognizable files; Step S2: Process the three-dimensional result array in the finite element result data to obtain a reconstructed result array; Step S3: Deduplicate the finite element result data and intelligently group different standard physical quantities in the recombined result array according to byte bits. Step S4: Store the node coordinate array, the cell connectivity array, and the arrays of different byte positions into different subfolders, and query the byte positions arrays according to different query conditions.

2. The unified storage and conversion method for finite element analysis result data according to claim 1, characterized in that, Step S1 includes the following sub-steps: Step S101: Collect the file extensions of different original files, query the converter plugins with the corresponding file extensions in the pluggable multi-format parser architecture, and use the corresponding converter plugins to convert the original files into different recognizable files. Step S102: Obtain the node number and three-dimensional coordinates of different nodes in the identifiable file, and use the node number as the first element and the three-dimensional coordinates of the node as the second element to construct an array of node coordinates corresponding to different nodes in the identifiable file. Step S103: Obtain the actual element type identifiers of different elements in the finite element network within the identifiable file, match the element type of the corresponding element based on the actual element type identifiers, and uniformly map the actual element type identifiers corresponding to the same element type to the standard element type identifiers.

3. The unified storage and conversion method for finite element analysis result data according to claim 2, characterized in that, Step S1 further includes the following sub-steps: Step S104: Count the number of different standard unit type identifiers in the identifiable file and record them as the standard type number; collect the number of nodes connected to the unit corresponding to the standard unit type identifier and record them as the connection node number; construct the unit connectivity array with the standard type number as the first element and the connection node number as the second element. Step S105: Obtain the unit number of different units in the identifiable file, and associate the unit number with the standard unit type identifier of the corresponding unit to obtain unit type mapping data; Step S106: Obtain the initial physical quantities corresponding to different nodes at different time points in the identifiable file. Construct a three-dimensional result array corresponding to different nodes at different time points with the node number as the first element, the time node as the second element, and the initial physical quantity as the third element. Step S107: The node coordinate array, element type mapping data, and three-dimensional result array are all recorded as finite element result data.

4. The unified storage and conversion method for finite element analysis result data according to claim 3, characterized in that, The processing procedure in step S2 includes the following sub-steps: Step S201: Store different preset physical quantities in the database, and change the names of different initial physical quantities in the three-dimensional result array to the names of the corresponding preset physical quantities; Step S202: Obtain the initial units of different initial physical quantities in the three-dimensional result array, divide the initial units by the standard units to obtain the conversion values, and multiply the initial physical quantities by the conversion values ​​to obtain the standard physical quantities corresponding to different units at different time points; Step S203: Replace the initial physical quantity corresponding to the first element in the three-dimensional result array with the corresponding standard physical quantity, swap the positions of the first and second elements in the replaced array, and record the swapped array as the recombined result array.

5. The unified storage and conversion method for finite element analysis result data according to claim 4, characterized in that, Step S3 includes the following sub-steps: Step S301: Calculate the hash value corresponding to the node coordinate array at different time points and record it as the coordinate hash value; Step S302: Compare the coordinate hash values ​​corresponding to the node coordinate arrays at different time points; If any two sets of time nodes have the same coordinate hash value, then one set of node coordinate arrays is retained and the other set is discarded; if all time nodes have different coordinate hash values, then all node coordinate arrays are retained; and so on, the same analysis is performed on the cell connectivity arrays to obtain the retained cell connectivity arrays. Step S303: Select the recombination result array corresponding to any time node, extract the standard physical quantities corresponding to different node numbers, and sort the standard physical quantities in ascending order according to the node numbers to obtain the sequence to be processed.

6. The unified storage and conversion method for finite element analysis result data according to claim 5, characterized in that, Step S3 further includes the following sub-steps: Step S304: Select adjacent multi-bit elements in the sequence to be processed from left to right, count the number of bytes of the corresponding multi-bit elements, and traverse and compare the number of bytes of the multi-bit elements to obtain the maximum number of bytes. Step S305: Based on the maximum number of bytes, the corresponding multi-bit elements are split from left to right into the first byte, the second byte, ..., the nth byte, where n is the byte number; Step S306: Store the first byte of the corresponding multi-bit element in the same array and record the corresponding array as the first byte array. Store the second byte of the different standard physical quantities in the same array and record the corresponding array as the second byte array. And so on, store the nth byte of the different standard physical quantities in the same array and record the corresponding array as the nth byte array.

7. The unified storage and conversion method for finite element analysis result data according to claim 6, characterized in that, The query process in step S4 includes the following sub-steps: Step S401: When the query conditions are fixed node coordinates and query radius, obtain the node coordinates corresponding to different nodes, calculate the straight-line distance between the coordinates of different nodes and the fixed node coordinates using the distance formula, and take the nodes whose straight-line distance is less than or equal to the query radius as query result nodes, and extract different byte arrays according to the node number corresponding to the query result nodes. Step S402: When the query conditions are fixed node coordinates and query quantity, obtain the node coordinates corresponding to different nodes, calculate the straight-line distance between the coordinates of different nodes and the fixed node coordinates using the distance formula, sort the different nodes in ascending order according to the straight-line distance, and obtain the node sequence. Select the same number of nodes as the query quantity from left to right and record them as query result nodes. Extract different byte arrays according to the node number corresponding to the query result nodes. Step S403: When the query condition is a fixed time, obtain the node coordinates corresponding to different nodes, subtract the fixed time from the time corresponding to different time nodes and take the absolute value to obtain the time node deviation, traverse and compare the time node deviations to obtain the minimum time node deviation, and record the time node corresponding to the minimum time node deviation as the query time node, and extract different byte bit arrays based on the query time node.

8. A unified storage and conversion system for finite element analysis result data, characterized in that, A unified storage and conversion method for finite element analysis result data according to any one of claims 1-7 includes: The conversion and extraction module is used to convert different raw files into recognizable files through a converter plugin, and extract finite element result data from the recognizable files; The intelligent processing module is used to process the three-dimensional result array in the finite element result data to obtain a reconstructed result array; The data processing module is used to deduplicate the finite element result data and intelligently group different standard physical quantities in the recombined result array according to the byte bits. The storage query module is used to store the node coordinate array, the cell connectivity array, and the arrays of different byte positions into different subfolders, and to query the byte position arrays according to different query conditions.

Images