Parametric Modeling Method and Apparatus for Finite Element Barrier Model

Abstract

This application relates to the field of finite element barrier model design technology, and particularly to a parametric modeling method and apparatus for finite element barrier models. The method includes: obtaining the format requirements for pre-processing software to process finite element barrier model files; determining the model format requirements for the finite element barrier model file based on the format requirements; generating, based on the model format requirements, the starting keyword, ending keyword, node number and coordinates of at least one honeycomb hole node, and mesh number and mesh component nodes of at least one honeycomb hole mesh in the finite element barrier model file that meet the model format requirements; and then constructing the finite element barrier model using pre-processing software. This solves the problems in related technologies, which not only require multiple rounds of optimization but also continuous adjustments and calculations to mesh size, material parameters, and connection methods, but also involve manual operation by engineers, resulting in low efficiency, numerous repetitive operations, and a high error rate.

Description

Technical Field

[0001] This application relates to the field of finite element barrier model design technology, and in particular to a parametric modeling method and apparatus for finite element barrier models. Background Technology

[0002] Due to their simple structure, stable lateral stiffness, and low cost, honeycomb aluminum barriers are widely used in vehicles, rail transportation, and aerospace, especially in vehicle safety testing. High-precision finite element barrier models closely resemble real barriers in geometry, mass distribution, material properties, and mechanical response. This allows engineers to quickly and efficiently improve constraint systems and vehicle structural designs through simulation calculations during the research and development phase, before parameters are finalized, thereby enhancing vehicle safety performance.

[0003] In related technologies, the acquired barrier components can be tested to obtain performance and structural data, and a side-impact honeycomb barrier finite element model can be created. The side-impact honeycomb barrier finite element model and the trolley equipment model can then be assembled to obtain a barrier trolley finite element model. Alternatively, an airbag unit built in the honeycomb aluminum to simulate airflow and a mounting plate model can be bonded to the honeycomb aluminum surface skin finite element model using adhesive units to form a barrier model. Then, the barrier parameters used in the actual collision test conditions can be substituted into the model to establish the required barrier model and perform collision finite element simulation analysis for the corresponding conditions.

[0004] However, in the development and benchmarking of high-precision finite element barrier models, multiple rounds of optimization are required, as well as continuous adjustments and calculations to mesh size, material parameters, and connection methods. The entire process requires manual operation by engineers, which is inefficient, involves a lot of repetitive operations, and has a high error rate, and urgently needs improvement. Summary of the Invention

[0005] This application provides a parametric modeling method and apparatus for finite element barrier models, which solves the problems in related technologies, such as the need for multiple rounds of optimization and continuous adjustment and trial calculation of mesh size, material parameters, connection methods, etc. in the development and benchmarking of high-precision finite element barrier models. The whole process requires manual operation by engineers, resulting in low efficiency, many repetitive operations and high error rate.

[0006] The first aspect of this application provides a parametric modeling method for a finite element barrier model, comprising the following steps: obtaining the format requirements for processing finite element barrier model files by preprocessing software; determining the model format requirements for the finite element barrier model file based on the format requirements; generating, based on the model format requirements, a starting keyword, an ending keyword, a node number and node coordinates of at least one cellular hole node, a mesh number and mesh component nodes of at least one cellular hole mesh that meet the model format requirements of the finite element barrier model in the finite element barrier model file; and constructing the finite element barrier model using the starting keyword, the ending keyword, the node number and node coordinates of the at least one cellular hole node, the mesh number and mesh component nodes of the at least one cellular hole mesh, and the preprocessing software.

[0007] The above technical solution allows for the determination of the finite element barrier model file format requirements based on the format requirements of the preprocessing software. This leads to the generation of the finite element barrier model file containing the starting and ending keywords, node numbers and coordinates of at least one honeycomb hole node, and mesh numbers and mesh component nodes that meet the format requirements. This enables the direct construction of the finite element barrier model using the preprocessing software. Key information such as nodes, meshes, and components of the finite element barrier model can be directly written using programming methods and read directly from the preprocessing software. This achieves parametric modeling of the finite element barrier model, improves modeling efficiency, reduces human error, and is particularly suitable for rapid iterative optimization in barrier development benchmarking, offering high flexibility.

[0008] Optionally, in one embodiment of this application, the step of generating the starting keyword, ending keyword, node number and node coordinates of at least one honeycomb hole node, and mesh number and mesh component nodes of at least one honeycomb hole mesh in the finite element barrier model file that meet the model format requirements, based on the model format requirements, includes: determining the barrier width, barrier height, and barrier depth of the honeycomb aluminum barrier; determining the hole depth direction of the honeycomb holes in the honeycomb aluminum, the mesh size in the hole depth direction, and the honeycomb hole width of each honeycomb hole; and generating the starting keyword, ending keyword, node number and node coordinates of at least one honeycomb hole node, and mesh number and mesh component nodes of at least one honeycomb hole mesh that meet the model format requirements based on the model format requirements, the barrier width, the barrier height, the barrier depth, the mesh size, and the honeycomb hole width.

[0009] The above technical solution can generate a finite element barrier model based on the barrier width, height, and depth of the honeycomb aluminum barrier, the depth direction of the honeycomb holes, the mesh size in the depth direction, the width of each honeycomb hole, and the model format requirements. This generates start and end keywords, node numbers and coordinates of at least one honeycomb hole node, and mesh numbers and mesh component nodes for at least one honeycomb hole mesh. By accurately determining the dimensions of the honeycomb aluminum barrier (barrier width, height, and depth) and the detailed characteristics of the honeycomb holes (depth direction, mesh size, and width), a highly accurate finite element barrier model can be generated. Furthermore, the generated finite element barrier model file follows specific model format requirements, resulting in a clear file structure that is easy to understand and maintain. This significantly optimizes the design and testing process, reduces errors and delays caused by manual operation, helps accelerate product development and testing, and improves overall efficiency.

[0010] Optionally, in one embodiment of this application, the step of generating a starting keyword, an ending keyword, a node number and node coordinates of at least one honeycomb hole node, a mesh number and mesh component nodes of at least one honeycomb hole mesh that satisfy the model format requirements based on the model format requirements, the barrier width, the barrier height, the barrier depth, the mesh size, and the honeycomb hole width includes: obtaining the number of honeycomb holes in the width direction of the finite element barrier model based on the model format requirements, the barrier width, and the honeycomb hole width; obtaining the number of meshes in the depth direction of the finite element barrier model based on the model format requirements, the barrier depth, and the mesh size; determining the starting keyword and the ending keyword based on the number of honeycomb holes and the number of meshes; determining the node number and node coordinates of the at least one honeycomb hole node based on the number of honeycomb holes, the number of meshes, the starting keyword, the ending keyword, and the objective function; and determining the mesh number and mesh component nodes of the at least one honeycomb hole mesh based on the node number and node coordinates of the at least one honeycomb hole node.

[0011] The above technical solution allows for the determination of the number of honeycomb holes based on model format requirements, barrier width, and honeycomb hole width. It also allows for the determination of the number of meshes in the depth direction based on model format requirements, barrier depth, and mesh size. This enables the determination of the starting and ending keywords, the node number and coordinates of at least one honeycomb hole node, and the mesh number and mesh component nodes of at least one honeycomb hole mesh. Precise calculation of the number of honeycomb holes and meshes improves the accuracy of simulation results. Automated calculation and generation support the creation of large-scale finite element barrier models, meeting the analytical needs of complex models and thus enhancing the comprehensiveness and accuracy of the analysis.

[0012] Optionally, in one embodiment of this application, the expression of the objective function may be, but is not limited to, the following:

[0013] X i =X i-1 -t

[0014] Y i =Y i-1

[0015] Z i =Z i-1

[0016] Among them, X i Let X be the X coordinate of the i-th node. i-1 Let X be the x-coordinate of the (i-1)th node, and Y be the y-coordinate of the (i i Let Y be the Y-coordinate of the i-th node. i-1 Let Z be the Y-coordinate of the (i-1)th node. i Let Z be the Z-coordinate of the i-th node. i-1 Let Z be the Z-coordinate of the (i-1)th node, and let Nt-1 be the number of iterations.

[0017] By using the above technical solutions, the expression of the objective function can be obtained, thereby improving the accuracy and reliability of the model and providing a more reliable basis for model design and optimization.

[0018] Optionally, in one embodiment of this application, the formula for calculating the number of cell holes may be, but is not limited to, the following:

[0019] Nt=d / t

[0020] Where d is the barrier depth and t is the grid size.

[0021] The formula for calculating the number of grid cells can be, but is not limited to, the following:

[0022] Nw = Int(a / e),

[0023] Where a is the barrier width and e is the width of each cell.

[0024] The above technical solution allows for the calculation of the number of cell holes and the number of meshes using the formulas for calculating the number of cell holes and the number of meshes, respectively. By accurately calculating the number of cell holes and the number of meshes, the accuracy of the finite element barrier model in the width and depth directions can be ensured, thereby improving the accuracy of the simulation results and enhancing the scalability and flexibility of the finite element barrier model.

[0025] A second aspect of this application provides a parametric modeling apparatus for a finite element barrier model, comprising: an acquisition module for acquiring the format requirements of a pre-processing software for processing a finite element barrier model file; a determination module for determining the model format requirements of the finite element barrier model file based on the format requirements; a generation module for generating, based on the model format requirements, a starting keyword, an ending keyword, a node number and node coordinates of at least one cellular hole node, a mesh number and mesh component nodes of at least one cellular hole mesh, and a construction module for constructing the finite element barrier model using the starting keyword, the ending keyword, the node number and node coordinates of the at least one cellular hole node, the mesh number and mesh component nodes of the at least one cellular hole mesh, and the pre-processing software.

[0026] The above technical solution allows for the determination of the finite element barrier model file format requirements based on the format requirements of the preprocessing software. This leads to the generation of the finite element barrier model file containing the starting and ending keywords, node numbers and coordinates of at least one honeycomb hole node, and mesh numbers and mesh component nodes that meet the format requirements. This enables the direct construction of the finite element barrier model using the preprocessing software. Key information such as nodes, meshes, and components of the finite element barrier model can be directly written using programming methods and read directly from the preprocessing software. This achieves parametric modeling of the finite element barrier model, improves modeling efficiency, reduces human error, and is particularly suitable for rapid iterative optimization in barrier development benchmarking, offering high flexibility.

[0027] Optionally, in one embodiment of this application, the generation module includes: a first determining unit, configured to determine the barrier width, barrier height, and barrier depth of the honeycomb aluminum barrier; a second determining unit, configured to determine the hole depth direction of the honeycomb holes in the honeycomb aluminum, the grid size in the hole depth direction, and the honeycomb hole width of each honeycomb hole; and a generation unit, configured to generate, based on the model format requirements, the barrier width, the barrier height, the barrier depth, the grid size, and the honeycomb hole width, a finite element barrier model that satisfies the model format requirements, including a start keyword, an end keyword, a node number and node coordinates of at least one honeycomb hole node, and a grid number and grid component nodes of at least one honeycomb hole mesh.

[0028] The above technical solution can generate a finite element barrier model based on the barrier width, height, and depth of the honeycomb aluminum barrier, the depth direction of the honeycomb holes, the mesh size in the depth direction, the width of each honeycomb hole, and the model format requirements. This generates start and end keywords, node numbers and coordinates of at least one honeycomb hole node, and mesh numbers and mesh component nodes for at least one honeycomb hole mesh. By accurately determining the dimensions (barrier width, height, and depth) and detailed features (depth direction, mesh size, and width) of the honeycomb aluminum barrier, a highly accurate finite element barrier model can be generated. Furthermore, the generated finite element barrier model file adheres to specific model format requirements, resulting in a clear, easy-to-understand, and maintain file structure. This significantly optimizes the design and testing process, reduces errors and delays caused by manual operations, accelerates product development and testing, and improves overall efficiency.

[0029] Optionally, in one embodiment of this application, the generation unit includes: a first generation subunit, configured to obtain the number of honeycomb holes in the width direction of the finite element barrier model based on the model format requirements, the barrier width, and the honeycomb hole width; a second generation subunit, configured to obtain the number of grids in the depth direction of the finite element barrier model based on the model format requirements, the barrier depth, and the grid size; a first determination subunit, configured to determine the start keyword and the end keyword based on the number of honeycomb holes and the number of grids; a second determination subunit, configured to determine the node number and node coordinates of the at least one honeycomb hole node based on the number of honeycomb holes, the number of grids, the start keyword, the end keyword, and the objective function; and a third determination subunit, configured to determine the grid number and grid component nodes of the at least one honeycomb hole grid based on the node number and node coordinates of the at least one honeycomb hole node.

[0030] The above technical solution allows for the determination of the number of honeycomb holes based on model format requirements, barrier width, and honeycomb hole width. It also allows for the determination of the number of meshes in the depth direction based on model format requirements, barrier depth, and mesh size. This enables the identification of starting and ending keywords, node numbers and coordinates of at least one honeycomb hole node, and mesh numbers and constituent nodes of at least one honeycomb hole mesh. Precise calculation of the number of honeycomb holes and meshes improves the accuracy of simulation results. Automated calculation and generation support the creation of large-scale finite element barrier models, meeting the analytical needs of complex models and thus enhancing the comprehensiveness and accuracy of the analysis.

[0031] Optionally, in one embodiment of this application, the expression of the objective function may be, but is not limited to, the following:

[0032] X i =Xi-1 -t

[0033] Y i =Y i-1

[0034] Z i =Z i-1

[0035] Among them, X i Let X be the X coordinate of the i-th node. i-1 Let X be the x-coordinate of the (i-1)th node, and Y be the y-coordinate of the (i i Let Y be the Y-coordinate of the i-th node. i-1 Let Z be the Y-coordinate of the (i-1)th node. i Let Z be the Z-coordinate of the i-th node. i-1 Let Z be the Z-coordinate of the (i-1)th node, and let Nt-1 be the number of iterations.

[0036] The above technical solutions can yield the expression for the objective function, thereby improving the accuracy and reliability of the model and providing a more reliable basis for model design and optimization.

[0037] Optionally, in one embodiment of this application, the formula for calculating the number of cell holes may be, but is not limited to, the following:

[0038] Nt=d / t

[0039] Where d is the barrier depth and t is the grid size.

[0040] The formula for calculating the number of grid cells can be, but is not limited to, the following:

[0041] Nw = Int(a / e),

[0042] Where a is the barrier width and e is the width of each cell.

[0043] The above technical solution allows for the calculation of the number of cell holes and the number of meshes using the formulas for calculating the number of cell holes and the number of meshes, respectively. By accurately calculating the number of cell holes and the number of meshes, the accuracy of the finite element barrier model in the width and depth directions can be ensured, thereby improving the accuracy of the simulation results and enhancing the scalability and flexibility of the finite element barrier model.

[0044] A third aspect of this application provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the parametric modeling method for the finite element barrier model as described in the above embodiments.

[0045] A fourth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the parametric modeling method for the finite element barrier model described above.

[0046] A fifth aspect of this application provides a computer program product, including a computer program that, when executed, implements the parametric modeling method for the finite element barrier model described above.

[0047] This application embodiment can determine the model format requirements of the finite element barrier model file based on the format requirements of the preprocessing software, and then generate the starting keyword, ending keyword, node number and coordinates of at least one honeycomb hole node, and mesh number and mesh component nodes of the finite element barrier model that meet the model format requirements in the finite element barrier model file. This allows for the direct construction of the finite element barrier model using the preprocessing software. Keyword information such as nodes, meshes, and components of the finite element barrier model can be directly written using programming methods and read directly from the preprocessing software, achieving parametric modeling of the finite element barrier model. This improves modeling efficiency, reduces human error, and is particularly suitable for rapid iterative optimization in barrier development benchmarking, offering high flexibility. Therefore, it solves the problems in related technologies where the development and benchmarking of high-precision finite element barrier models requires multiple rounds of optimization and continuous adjustments and calculations of mesh size, material parameters, and connection methods. The entire process requires manual operation by engineers, resulting in low efficiency, numerous repetitive operations, and a high error rate.

[0048] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0049] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:

[0050] Figure 1 This is a flowchart of a parametric modeling method for a finite element barrier model according to an embodiment of this application;

[0051] Figure 2 This is a schematic diagram of barrier dimensions provided according to one embodiment of this application;

[0052] Figure 3 This is a schematic diagram of the orientation of the honeycomb aluminum according to an embodiment of this application;

[0053] Figure 4 This is a schematic diagram of the honeycomb mesh size according to an embodiment of this application;

[0054] Figure 5 This is a schematic diagram illustrating the numbering of the first and second hexagonal nodes according to an embodiment of this application;

[0055] Figure 6 This is a flowchart illustrating the parametric modeling of a finite element barrier model according to an embodiment of this application;

[0056] Figure 7 This is a block diagram of a parametric modeling device for a finite element barrier model provided according to an embodiment of this application;

[0057] Figure 8 This is a schematic diagram of the structure of an electronic device provided according to an embodiment of this application. Attached image description:

[0059] Among them, 10-parametric modeling device for finite element barrier model; 100-acquisition module, 200-determination module, 300-generation module, 400-construction module; 801-memory, 802-processor, 803-communication interface. Detailed Implementation

[0060] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0061] The parametric modeling method and apparatus for finite element barrier models according to embodiments of this application are described below with reference to the accompanying drawings. To address the issues mentioned in the background art regarding the development and benchmarking of high-precision finite element barrier models, which require multiple rounds of optimization and continuous adjustments to mesh size, material parameters, and connection methods, resulting in low efficiency, repetitive operations, and a high error rate due to manual operation by engineers, this application provides a parametric modeling method for finite element barrier models. This method determines the model format requirements of the finite element barrier model file based on the format requirements of the pre-processing software, thereby generating the starting keywords, ending keywords, node numbers and coordinates of at least one honeycomb hole node, and mesh numbers and mesh component nodes of at least one honeycomb hole mesh that meet the model format requirements. This allows for the direct construction of the finite element barrier model using pre-processing software. Key information such as nodes, meshes, and components of the finite element barrier model can be directly written using programming methods and read directly from the pre-processing software, achieving parametric modeling of the finite element barrier model. This improves modeling efficiency, reduces human error, and is particularly suitable for rapid iterative optimization in barrier development and benchmarking, offering high flexibility. This solves the problems in related technologies, such as the need for multiple rounds of optimization and continuous adjustments and calculations to mesh size, material parameters, and connection methods during the development and benchmarking of high-precision finite element barrier models. The entire process requires manual operation by engineers, resulting in low efficiency, numerous repetitive operations, and a high error rate.

[0062] Specifically, Figure 1 This is a flowchart of a parametric modeling method for a finite element barrier model provided according to an embodiment of this application.

[0063] like Figure 1 As shown, the parametric modeling method for this finite element barrier model includes the following steps:

[0064] In step S101, the format requirements for the finite element barrier model file processed by the preprocessing software are obtained.

[0065] It is understood that, in the embodiments of this application, the preprocessing software may include, but is not limited to, HyperMesh (HyperMesh Software, a finite element model preprocessing tool), ANSA (Ansa Software, a high-performance finite element preprocessor), Patran (finite element analysis pre / postprocessing software), etc. The specific software can be set by those skilled in the art according to the actual situation, and this application does not impose any specific restrictions.

[0066] Furthermore, the format requirements for processing finite element barrier model files can be determined according to different preprocessing software. For example, HyperMesh supports text formats including .bdf files and .inp files, and this application does not impose specific limitations. ANSA supports formats including .dat files and .bdf files, and this application does not impose specific limitations. Patran supports a variety of common CAD (Computer-Aided Design) file formats, such as IGES (Initial Graphics Exchange Specification) and STEP (Standard for the Exchange of Product model data), and also supports file formats of various finite element solvers. The specific settings can be configured by those skilled in the art according to the actual situation, and this application does not impose specific limitations.

[0067] In step S102, the model format requirements for the finite element barrier model file are determined based on the format requirements.

[0068] It is understood that the model format requirements in this application embodiment may include, but are not limited to, text type and format, such as binary format or text format, model file naming, compatibility between versions, etc., which can be set by those skilled in the art according to the actual situation, and this application does not impose specific restrictions.

[0069] As one possible approach, embodiments of this application can determine the model format requirements of the finite element barrier model file based on the format requirements of the finite element barrier model file processed by the preprocessing software.

[0070] For example, this application takes the LSDYNA solver as an example to determine the model format requirements of the model file, such as keywords, decimal places, placeholders, etc. This application does not impose specific restrictions. Then, by modifying the basic parameters defined in the early stage, the finite element barrier model file can be quickly generated and iterative optimization simulation can be performed without changing the relationship between nodes and coordinates, thus eliminating a lot of repetitive operations in the preprocessing software.

[0071] In step S103, based on the model format requirements, the starting keyword, ending keyword, node number and node coordinates of at least one cellular hole node, and mesh number and mesh component nodes of at least one cellular hole mesh are generated in the finite element barrier model file to meet the model format requirements.

[0072] It is understood that in the embodiments of this application, the start keyword can be used to indicate the start of the finite element barrier model, and can be represented by "*KEYWORD" but is not limited to it. This application does not impose any specific restrictions. Correspondingly, the end keyword can be used to indicate the end of the finite element barrier model, and can be represented by "*END" but is not limited to it. This application does not impose any specific restrictions.

[0073] Furthermore, for honeycomb aluminum, there is more than one node and one mesh. Therefore, in the embodiments of this application, at least one node number and node coordinate of a honeycomb hole node can be defined. For example, the keyword for a honeycomb hole node can be, but is not limited to, represented by "*NODE", which can include, but is not limited to, node number and node coordinates. This application does not impose specific limitations. At least one mesh number and mesh component nodes of a honeycomb mesh can be defined. For example, the keyword for a honeycomb mesh can be, but is not limited to, represented by "*ELEMENT_SHELL", which can include, but is not limited to, mesh number, component number, mesh component nodes, etc. This application does not impose specific limitations.

[0074] As one possible implementation, embodiments of this application can obtain the starting keyword, ending keyword, node number and node coordinates of at least one cellular hole node, and mesh number and mesh component nodes of at least one cellular hole mesh, provided that the model format requirements are met.

[0075] Optionally, in one embodiment of this application, based on model format requirements, generating a finite element barrier model file that meets the model format requirements includes: a start keyword, an end keyword, a node number and coordinates of at least one honeycomb hole node, a mesh number and mesh component nodes of at least one honeycomb hole mesh, and a set of starting keywords, an end keyword, a node number and coordinates of at least one honeycomb hole node, a set of mesh numbers of at least one honeycomb hole mesh, and a set of mesh component nodes. This includes: determining the barrier width, barrier height, and barrier depth of the honeycomb aluminum barrier; determining the hole depth direction of the honeycomb holes in the honeycomb aluminum, the mesh size in the hole depth direction, and the width of each honeycomb hole; and generating a finite element barrier model that meets the model format requirements based on the model format requirements, barrier width, barrier height, barrier depth, mesh size, and honeycomb hole width. The formula for calculating the number of honeycomb holes can be, but is not limited to, the following:

[0076] Nt=d / t

[0077] Where d is the barrier depth and t is the grid size.

[0078] The formula for calculating the number of grid cells can be, but is not limited to, the following:

[0079] Nw = Int(a / e),

[0080] Where a is the barrier width and e is the width of each cell.

[0081] In some embodiments of this application, the width of the honeycomb aluminum barrier can be set to 'a', the height to 'h', and the depth to 'd', as shown in the schematic diagram below. Figure 2 As shown.

[0082] In some embodiments, the depth direction of the honeycomb holes in the honeycomb aluminum can be represented as the T-direction, and the directions perpendicular to the T-direction can be represented as the W-direction and L-direction, respectively, as shown in the schematic diagram. Figure 3 As shown.

[0083] Furthermore, in this embodiment, the grid size in the T direction is set to t, and the width of each honeycomb cell is set to e, as shown in the schematic diagram. Figure 4 As shown.

[0084] Additionally, it should be noted that in this embodiment, smaller dimensions result in higher precision, but larger calculation steps and lower efficiency. Furthermore, in this embodiment, for model uniformity and ease of modeling, 'a' is set to an integer multiple of 'e', ​​and 'd' is set to an integer multiple of 't'. These specific settings can be made by those skilled in the art according to actual circumstances, and this application does not impose any specific limitations.

[0085] Furthermore, embodiments of this application can obtain the starting keyword, ending keyword, node number and node coordinates of at least one cell hole node, and mesh number and mesh component nodes of the finite element barrier model based on model format requirements, barrier width, barrier height, barrier depth, mesh size and cell hole width.

[0086] Optionally, in one embodiment of this application, based on model format requirements, barrier width, barrier height, barrier depth, mesh size, and cell hole width, a starting keyword, an ending keyword, a node number and node coordinates of at least one cell hole node, and a mesh number and mesh component nodes of at least one cell hole mesh are generated for a finite element barrier model that meets the model format requirements. This includes: obtaining the number of cell holes in the width direction of the finite element barrier model based on model format requirements, barrier width, and cell hole width; obtaining the number of meshes in the depth direction of the finite element barrier model based on model format requirements, barrier depth, and mesh size; determining the starting keyword and ending keyword based on the number of cell holes and meshes; determining the node number and node coordinates of at least one cell hole node based on the number of cell holes, meshes, starting keyword, ending keyword, and objective function; and determining the mesh number and mesh component nodes of at least one cell hole mesh based on the node number and node coordinates of at least one cell hole node. The formula for calculating the number of cell holes may be, but is not limited to, the following:

[0087] Nt=d / t

[0088] Where d is the barrier depth and t is the grid size.

[0089] The formula for calculating the number of grid cells can be, but is not limited to, the following:

[0090] Nw = Int(a / e),

[0091] Where a is the barrier width and e is the width of each cell.

[0092] The expression for the objective function can be, but is not limited to, the following:

[0093] X i =X i-1 -t

[0094] Y i =Y i-1

[0095] Z i =Z i-1

[0096] Among them, X i Let X be the X coordinate of the i-th node. i-1 Let X be the x-coordinate of the (i-1)th node, and Y be the y-coordinate of the (i i Let Y be the Y-coordinate of the i-th node. i-1 Let Z be the Y-coordinate of the (i-1)th node. i Let Z be the Z-coordinate of the i-th node. i-1 Let Z be the Z-coordinate of the (i-1)th node, and let Nt-1 be the number of iterations.

[0097] In some embodiments, this application can calculate the number of honeycomb holes in the width direction of the finite element barrier model based on the barrier width and the honeycomb hole width, according to model format requirements. The formula for calculating the number of honeycomb holes can be, but is not limited to, the following:

[0098] Nt=d / t

[0099] Where d is the barrier depth and t is the grid size.

[0100] In some embodiments, this application can calculate the number of meshes in the depth direction of the finite element barrier model based on the barrier depth and mesh size, according to model format requirements. The formula for calculating the number of meshes can be, but is not limited to, the following:

[0101] Nw = Int(a / e),

[0102] Where a is the barrier width and e is the width of each cell.

[0103] In some embodiments, the present application can determine the start keyword and the end keyword based on the model format requirements, using the number of cell holes and the number of meshes. For example, based on the LSDYNA format requirements, the start keyword of the finite element barrier model can be set to *KEYWORD, and the end keyword can be set to *END, etc. The present application does not impose specific limitations.

[0104] Furthermore, in this embodiment of the application, the node number and node coordinates of at least one cell hole node are determined based on the number of cell holes, the number of grids, the start keyword, the end keyword, and the objective function.

[0105] For example, in this embodiment of the application, the keyword of the cellular hole node of the finite element barrier model can be set to *NODE. Furthermore, in this embodiment of the application, the starting point coordinates can be set, which can start from the zero point (0, 0, 0) or from other points. The specific settings can be made by those skilled in the art according to the actual situation, and this application does not impose any specific restrictions.

[0106] Further, in this embodiment, the node number and coordinates of the first cell node are obtained according to the objective function, which can be, but are not limited to, expressed as: 1 0 0e*tan30° / 2; the node number and coordinates of the second cell node can be, but are not limited to, expressed as: 2 0 0e*tan30° / 2+e*sin30° / 2; the node number and coordinates of the third cell node can be, but are not limited to, expressed as: 3 0e / 2,e*tan30° / 2+esin30°; the node number and coordinates of the fourth cell node can be, but are not limited to, expressed as: 4 0e e*tan30° / 2+sin30°e / 2; the node number and coordinates of the fifth cell node can be, but are not limited to, expressed as: 5 0e e*tan30° / 2; the node number and coordinates of the sixth cell node can be, but are not limited to, expressed as: 6 0e / 2 0; where Sin() is the sine function and Cos() is the cosine function.

[0107] Additionally, it should be noted that the text format of this application embodiment is standardized according to the solver format requirements, with each data point occupying 10 characters in length, and spaces used to pad any data points that are insufficient.

[0108] Furthermore, in this embodiment, the X coordinate of the offset node is repeatedly shifted to generate the first honeycomb hole node and mesh along the T direction. However, in this embodiment, only the X coordinate is changed during each offset, while the Y and Z coordinates remain unchanged. The generated node numbering diagram is shown below. Figure 5 As shown, the expression for the objective function can be, but is not limited to, the following:

[0109] X i =X i-1-t

[0110] Y i =Y i-1

[0111] Z i =Z i-1

[0112] Among them, X i Let X be the X coordinate of the i-th node. i-1 Let X be the x-coordinate of the (i-1)th node, and Y be the y-coordinate of the (i i Let Y be the Y-coordinate of the i-th node. i-1 Let Z be the Y-coordinate of the (i-1)th node. i Let Z be the Z-coordinate of the i-th node. i-1 Let Z be the Z-coordinate of the (i-1)th node, and let Nt-1 be the number of iterations.

[0113] In some embodiments, embodiments of this application may determine the grid number and grid constituent nodes of at least one cellular mesh based on the node number and node coordinates of at least one cellular hole node.

[0114] For example, in this application embodiment, the cellular mesh keyword of the finite element barrier model can be set to *ELEMENT_SHELL, and mesh elements can be defined to obtain mesh numbers and mesh component nodes.

[0115] For example, such as Figure 5As shown, in this embodiment, nodes 1, 2, 7, and 8 can be used to form the first grid, thereby obtaining the grid number of the first honeycomb grid, the component number of the first honeycomb grid, and the grid composition nodes of the first honeycomb grid. The text of the first honeycomb grid can be, but is not limited to, represented as: 1 11 27 8. Nodes 2, 3, 8, and 9 can be used to form the second grid, and the text of the second honeycomb grid can be, but is not limited to, represented as: 2 1 2 3 8 9. Nodes 3, 4, 9, and 10 can be used to form the third grid, and the text of the third honeycomb grid can be, but is not limited to, represented as: 3 1 3 4 9 10. Nodes 4, 5, 10, and 11 can be used to form the fourth grid, and the text of the fourth honeycomb grid can be, but is not limited to, represented as: 4 1 4 5 10 11. Nodes 5, 6, 11, and 12 can be used to form the fifth grid, and the text of the fifth honeycomb grid can be, but is not limited to, represented as: 5 1 5 6. 1112; The sixth mesh is formed using nodes 6, 1, 12, and 7. The text of the sixth honeycomb mesh can be, but is not limited to, represented as: 6 1 6 1 12 7; and so on, generating all the meshes for the first honeycomb. Here, the first digit represents the mesh number, the second digit represents the component number (default is 1), and the third to sixth digits represent the nodes that make up the mesh. In this embodiment, only one row of mesh is set for each edge of the honeycomb. To improve simulation accuracy, multiple rows of mesh can also be set. The specific settings can be made by those skilled in the art according to the actual situation, and this application does not impose specific limitations.

[0116] Furthermore, in this embodiment, the entire mesh of the finite element barrier model is generated by offsetting and replicating the honeycomb holes, as shown in the flowchart below. Figure 6 As shown, the main contents include:

[0117] Step S601: Determine the barrier width, barrier height, and barrier depth of the honeycomb aluminum barrier.

[0118] Step S602: Determine the depth direction of the honeycomb holes in the honeycomb aluminum, the grid size in the depth direction, and the width of each honeycomb hole.

[0119] Step S603: Set the starting keyword for the finite element barrier model.

[0120] Step S604: Set the starting point coordinates.

[0121] Step S605: Obtain the node number and node coordinates of the first cellular hole node according to the objective function.

[0122] Step S606: Obtain the first honeycomb mesh text according to the objective function.

[0123] Step S607: Generate a finite element barrier model by offsetting and copying the honeycomb holes.

[0124] Step S608: Set the termination keyword for the finite element barrier model.

[0125] Additionally, it should be noted that in the embodiments of this application, nodes in the entire plane can be generated first, and then arrayed to obtain a finite element barrier model. The specific settings can be made by those skilled in the art according to the actual situation, and this application does not impose any specific limitations.

[0126] In step S104, a finite element barrier model is constructed using start keywords, end keywords, node numbers and coordinates of at least one cellular hole node, mesh numbers and mesh composition nodes of at least one cellular hole mesh, and preprocessing software.

[0127] In some embodiments, the starting keyword, ending keyword, node number and coordinates of at least one cellular hole node, and mesh number and mesh constituent nodes of at least one cellular hole mesh can be directly read in the pre-processing software to achieve parametric modeling of the finite element barrier model, thereby improving the modeling efficiency of the finite element barrier model and reducing the occurrence of human operation errors. It is especially suitable for rapid iterative optimization in barrier development benchmarking. The finite element barrier model can be quickly obtained by simply modifying the input parameters. In addition, the embodiments of this application can also generate some operations parametrically and perform some operations in the pre-processing software according to actual needs. It is highly flexible, suitable for different use scenarios, and has a wider range of applications.

[0128] The parametric modeling method for the finite element barrier model proposed in this application will be introduced below with reference to a specific embodiment.

[0129] Example 1:

[0130] In this embodiment, the width of the honeycomb aluminum barrier can be set to 'a', the height to 'h', and the depth to 'd', as shown in the schematic diagram below. Figure 2 As shown; the depth direction of the honeycomb holes in the honeycomb aluminum can be represented as the T-direction, and the directions perpendicular to the T-direction can be represented as the W-direction and L-direction, respectively. A schematic diagram is shown below. Figure 3 As shown; the grid size in the T direction can be set to t, and the width of each cell can be set to e, as illustrated in the diagram. Figure 4 As shown, the embodiments of this application further utilize relevant calculation formulas to obtain the number of honeycomb holes and the number of grids.

[0131] Furthermore, based on the LSDYNA format requirements, this embodiment sets the starting keyword of the finite element barrier model to *KEYWORD, the ending keyword to *END, and the keyword for the honeycomb hole node to *NODE. Further, this embodiment sets the starting point coordinates, starting from zero (0, 0, 0), and then obtains the node number and coordinates of the first honeycomb hole node according to the objective function, which can be, but is not limited to, expressed as: 1 0 0e*tan30° / 2; the node number and coordinates of the second honeycomb hole node can be, but is not limited to, expressed as: 2 0 0e*tan30° / 2+e*sin30° / 2; the node number and coordinates of the third honeycomb hole node can be, but is not limited to, expressed as: 3 0e / 2,e*tan30° / 2+esin30°; the node number and coordinates of the fourth honeycomb hole node can be, but is not limited to, expressed as: 4 0e e*tan30° / 2+sin30°e / 2; The node number and coordinates of the fifth cell node can be, but are not limited to, expressed as: 5 0e e*tan30° / 2; The node number and coordinates of the sixth cell node can be, but are not limited to, expressed as: 60e / 2 0.

[0132] Furthermore, in this embodiment, the X coordinate of the offset node is repeatedly shifted to generate the first honeycomb hole node and mesh along the T direction. However, in this embodiment, only the X coordinate is changed during each offset, while the Y and Z coordinates remain unchanged. The generated node numbering diagram is shown below. Figure 5 As shown.

[0133] Furthermore, in this embodiment of the application, the honeycomb mesh keyword of the finite element barrier model can be set to *ELEMENT_SHELL, and mesh elements can be defined to obtain the mesh number and mesh component nodes, such as... Figure 5 As shown, Figure 5As shown, in this embodiment, nodes 1, 2, 7, and 8 can be used to form the first grid, thereby obtaining the grid number of the first honeycomb grid, the component number of the first honeycomb grid, and the grid composition nodes of the first honeycomb grid. The text of the first honeycomb grid can be, but is not limited to, represented as: 1 1 1 2 7 8. Nodes 2, 3, 8, and 9 can be used to form the second grid, and the text of the second honeycomb grid can be, but is not limited to, represented as: 2 1 2 3 8 9. Nodes 3, 4, 9, and 10 can be used to form the third grid, and the text of the third honeycomb grid can be, but is not limited to, represented as: 3 1 3 4 9 10. Nodes 4, 5, 10, and 11 can be used to form the fourth grid, and the text of the fourth honeycomb grid can be, but is not limited to, represented as: 4 1 4 5 10 11. Nodes 5, 6, 11, and 12 can be used to form the fifth grid, and the text of the fifth honeycomb grid can be, but is not limited to, represented as: 5 1 56 11. 12; The sixth grid is formed using nodes 6, 1, 12, and 7. The text for the sixth honeycomb grid can be, but is not limited to, represented as: 6 1 6 1 12 7; and so on, generating all the grids for the first honeycomb. The first digit represents the grid number, the second digit represents the component number (default is 1), and the third to sixth digits represent the nodes that make up the grid.

[0134] Furthermore, in this embodiment, the entire mesh of the finite element barrier model is generated by offsetting and replicating the honeycomb holes, as shown in the flowchart below. Figure 6 As shown.

[0135] The parametric modeling method for finite element barrier models proposed in this application can determine the model format requirements of the finite element barrier model file based on the format requirements of the preprocessing software. This allows for the generation of the finite element barrier model file containing the starting keyword, ending keyword, node number and coordinates of at least one honeycomb hole node, and mesh number and mesh component nodes that meet the model format requirements. This enables the direct construction of the finite element barrier model using preprocessing software. Keyword information such as nodes, meshes, and components of the finite element barrier model can be directly written using programming methods and read directly from the preprocessing software. This achieves parametric modeling of the finite element barrier model, improving modeling efficiency, reducing human error, and is particularly suitable for rapid iterative optimization in barrier development and benchmarking, offering high flexibility. Therefore, this method solves the problems in related technologies where the development and benchmarking of high-precision finite element barrier models requires multiple rounds of optimization and continuous adjustments and calculations to mesh size, material parameters, and connection methods. The entire process requires manual operation by engineers, resulting in low efficiency, numerous repetitive operations, and a high error rate.

[0136] Next, referring to the accompanying drawings, a parametric modeling apparatus for a finite element barrier model proposed according to an embodiment of this application is described.

[0137] Figure 7 This is a block diagram of a parametric modeling apparatus for a finite element barrier model provided according to an embodiment of this application.

[0138] like Figure 7 As shown, the parametric modeling device 10 for the finite element barrier model includes: an acquisition module 100, a determination module 200, a generation module 300, and a construction module 400.

[0139] The acquisition module 100 is used to acquire the format requirements of the finite element barrier model file processed by the preprocessing software.

[0140] Module 200 is used to determine the model format requirements of the finite element barrier model file based on the format requirements.

[0141] The generation module 300 is used to generate, based on the model format requirements, the starting keyword, ending keyword, node number and node coordinates of at least one cellular hole node, and mesh number and mesh component nodes of at least one cellular hole mesh in the finite element barrier model file.

[0142] Module 400 is used to construct a finite element barrier model using start keywords, end keywords, node numbers and coordinates of at least one cellular hole node, mesh numbers and mesh composition nodes of at least one cellular hole mesh, and preprocessing software.

[0143] Optionally, in one embodiment of this application, the generation module 300 includes: a first determining unit, a second determining unit, and a generation unit.

[0144] The first determining unit is used to determine the barrier width, barrier height, and barrier depth of the honeycomb aluminum barrier.

[0145] The second determining unit is used to determine the depth direction of the honeycomb holes in the honeycomb aluminum, the grid size in the depth direction, and the width of each honeycomb hole.

[0146] The generation unit is used to generate the starting keyword, ending keyword, node number and node coordinates of at least one cell hole node, and mesh number and mesh component nodes of at least one cell hole mesh, based on the model format requirements, barrier width, barrier height, barrier depth, mesh size and cell hole width.

[0147] Optionally, in one embodiment of this application, the generation unit includes: a first generation subunit, a second generation subunit, a first determination subunit, a second determination subunit, and a third determination subunit.

[0148] The first generating sub-unit is used to obtain the number of honeycomb holes in the width direction of the finite element barrier model based on the model format requirements, barrier width, and honeycomb hole width.

[0149] The second generated sub-element is used to obtain the number of meshes in the depth direction of the finite element barrier model based on the model format requirements, barrier depth, and mesh size.

[0150] The first determining sub-unit is used to determine the starting key and the ending key based on the number of cell holes and the number of grids.

[0151] The second determining sub-unit is used to determine the node number and node coordinates of at least one cell node based on the number of cell holes, the number of grids, the start keyword, the end keyword, and the objective function.

[0152] The third determining sub-unit is used to determine the grid number and grid component nodes of at least one cellular mesh based on the node number and node coordinates of at least one cellular hole node.

[0153] Optionally, in one embodiment of this application, the expression of the objective function may be, but is not limited to, the following:

[0154] X i =X i-1 -t

[0155] Y i =Y i-1

[0156] Z i =Z i-1

[0157] Among them, X i Let X be the X coordinate of the i-th node. i-1 Let X be the x-coordinate of the (i-1)th node, and Y be the y-coordinate of the (i i Let Y be the Y-coordinate of the i-th node. i-1 Let Z be the Y-coordinate of the (i-1)th node. i Let Z be the Z-coordinate of the i-th node. i-1 Let Z be the Z-coordinate of the (i-1)th node, and let Nt-1 be the number of iterations.

[0158] Optionally, in one embodiment of this application, the formula for calculating the number of cell holes may be, but is not limited to, the following:

[0159] Nt=d / t

[0160] Where d is the barrier depth and t is the grid size.

[0161] The formula for calculating the number of grid cells can be, but is not limited to, the following:

[0162] Nw = Int(a / e),

[0163] Where a is the barrier width and e is the width of each cell.

[0164] It should be noted that the explanation of the parametric modeling method embodiment for the finite element barrier model described above also applies to the parametric modeling device for the finite element barrier model in this embodiment, and will not be repeated here.

[0165] The parametric modeling device for finite element barrier models proposed in this application can determine the model format requirements of the finite element barrier model file based on the format requirements of the preprocessing software. This allows for the generation of the finite element barrier model file containing the starting keyword, ending keyword, node number and coordinates of at least one honeycomb hole node, and mesh number and mesh component nodes that meet the model format requirements. This enables the direct construction of the finite element barrier model using preprocessing software. Keyword information such as nodes, meshes, and components of the finite element barrier model can be directly written using programming methods and read directly from the preprocessing software. This achieves parametric modeling of the finite element barrier model, improving modeling efficiency, reducing human error, and is particularly suitable for rapid iterative optimization in barrier development and benchmarking, offering high flexibility. Therefore, this solves the problems in related technologies where the development and benchmarking of high-precision finite element barrier models requires multiple rounds of optimization and continuous adjustments and calculations of mesh size, material parameters, and connection methods. The entire process requires manual operation by engineers, resulting in low efficiency, numerous repetitive operations, and a high error rate.

[0166] Figure 8 This is a schematic diagram of the structure of an electronic device provided according to an embodiment of this application. The electronic device may include:

[0167] The memory 801, the processor 802, and the computer program stored on the memory 801 and capable of running on the processor 802.

[0168] When the processor 802 executes the program, it implements the parametric modeling method of the finite element barrier model provided in the above embodiments.

[0169] Furthermore, electronic devices also include:

[0170] Communication interface 803 is used for communication between memory 801 and processor 802.

[0171] The memory 801 is used to store computer programs that can run on the processor 802.

[0172] The memory 801 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0173] If the memory 801, processor 802, and communication interface 803 are implemented independently, then the communication interface 803, memory 801, and processor 802 can be interconnected via a bus to complete communication between them. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized into address buses, data buses, control buses, etc. For ease of representation, Figure 8 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0174] Optionally, in a specific implementation, if the memory 801, processor 802, and communication interface 803 are integrated on a single chip, then the memory 801, processor 802, and communication interface 803 can communicate with each other through an internal interface.

[0175] The processor 802 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.

[0176] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the parametric modeling method for the finite element barrier model described above.

[0177] This application also provides a computer program product, including a computer program that, when executed, implements the parametric modeling method for the finite element barrier model described above.

[0178] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0179] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0180] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or N executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0181] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0182] It should be understood that the various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. If implemented in hardware, as in another embodiment, it can be implemented using any one or more of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0183] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0184] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0185] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of this application.

Claims

1. A parametric modeling method for a finite element barrier model, characterized in that, Includes the following steps: Obtain the format requirements for pre-processing software to process finite element barrier model files; Based on the aforementioned format requirements, the model format requirements for the finite element barrier model file are determined; Based on the model format requirements, the finite element barrier model file is generated with the following start keywords, end keywords, node numbers and coordinates of at least one cellular hole node, and mesh numbers and mesh component nodes of at least one cellular hole mesh that meet the model format requirements. The finite element barrier model is constructed using the starting keyword, the ending keyword, the node number and node coordinates of the at least one cellular hole node, the grid number and grid component nodes of the at least one cellular hole mesh, and the preprocessing software. The step of generating the finite element barrier model file that meets the model format requirements, based on the model format requirements, includes the following: starting keyword, ending keyword, node number and node coordinates of at least one cellular hole node, and mesh number and mesh component nodes of at least one cellular hole mesh. Determine the barrier width, barrier height, and barrier depth of the cellular aluminum barrier; Determine the depth direction of the honeycomb holes in the honeycomb aluminum, the grid size in the depth direction, and the width of each honeycomb hole; Based on the model format requirements, the barrier width, the barrier height, the barrier depth, the mesh size, and the honeycomb hole width, generate the starting keyword, ending keyword, node number and node coordinates of at least one honeycomb hole node, and mesh number and mesh component nodes of at least one honeycomb hole mesh that meet the model format requirements; The step of generating a finite element barrier model that meets the model format requirements based on the model format requirements, the barrier width, the barrier height, the barrier depth, the mesh size, and the honeycomb aperture width, including the starting keyword, the ending keyword, the node number and node coordinates of at least one honeycomb aperture node, and the mesh number and mesh component nodes of at least one honeycomb aperture mesh, comprises: The number of honeycomb holes in the width direction of the finite element barrier model is obtained based on the model format requirements, the barrier width, and the honeycomb hole width. The number of meshes in the depth direction of the finite element barrier model is obtained based on the model format requirements, the barrier depth, and the mesh size. The starting keyword and the ending keyword are determined based on the number of cellular holes and the number of grids; The node number and node coordinates of the at least one cell node are determined based on the number of cell holes, the number of grids, the starting keyword, the ending keyword, and the objective function. The grid number and grid constituent nodes of the at least one cellular hole node are determined based on the node number and node coordinates of the at least one cellular hole node.

2. The method according to claim 1, characterized in that, The expression for the objective function is: X i =X i-1 -t AND i =Y i-1 WITH i =Z i-1 Among them, X i Let X be the X coordinate of the i-th node. i-1 Let X be the x-coordinate of the (i-1)th node, and Y be the y-coordinate of the (i-1)th node. i Let Y be the Y-coordinate of the i-th node. i-1 Let Z be the Y-coordinate of the (i-1)th node. i Let Z be the Z-coordinate of the i-th node. i-1 Let Z be the Z-coordinate of the (i-1)th node, and let Nt-1 be the number of iterations.

3. The method according to claim 1, characterized in that, in, The formula for calculating the number of honeycomb holes is: Nt=d / t Where d is the barrier depth and t is the grid size; The formula for calculating the number of grid cells is: Nw = Int(a / e). Where a is the barrier width and e is the width of each cell.

4. A parametric modeling device for a finite element barrier model, characterized in that, include: The acquisition module is used to obtain the format requirements of the finite element barrier model files processed by the preprocessing software. The determination module is used to determine the model format requirements of the finite element barrier model file based on the aforementioned format requirements; The generation module is used to generate, based on the model format requirements, the starting keyword, ending keyword, node number and node coordinates of at least one cellular hole node, and mesh number and mesh component nodes of at least one cellular hole mesh in the finite element barrier model file that meet the model format requirements. A construction module is used to construct the finite element barrier model using the start keyword, the end keyword, the node number and node coordinates of the at least one cellular hole node, the grid number and grid component nodes of the at least one cellular hole mesh, and the preprocessing software. The generation module includes: The first determining unit is used to determine the barrier width, barrier height, and barrier depth of the honeycomb aluminum barrier; The second determining unit is used to determine the depth direction of the honeycomb holes in the honeycomb aluminum, the grid size in the depth direction, and the width of each honeycomb hole; The generation unit is used to generate, based on the model format requirements, the barrier width, the barrier height, the barrier depth, the mesh size, and the honeycomb hole width, the starting keyword, the ending keyword, the node number and node coordinates of at least one honeycomb hole node, and the mesh number and mesh component nodes of at least one honeycomb hole mesh, to a finite element barrier model that meets the model format requirements. The generation unit includes: The first generation sub-unit is used to obtain the number of honeycomb holes in the width direction of the finite element barrier model based on the model format requirements, the barrier width, and the honeycomb hole width. The second generation sub-unit is used to obtain the number of meshes in the depth direction of the finite element barrier model based on the model format requirements, the barrier depth, and the mesh size; The first determining subunit is used to determine the starting keyword and the ending keyword based on the number of cell holes and the number of grids; The second determining subunit is used to determine the node number and node coordinates of the at least one cell node based on the number of cell holes, the number of grids, the starting keyword, the ending keyword, and the objective function; The third determining sub-unit is used to determine the grid number and grid component nodes of the at least one cellular hole grid based on the node number and node coordinates of the at least one cellular hole node.

5. An electronic device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, the processor executing the program to implement the parametric modeling method for the finite element barrier model as described in any one of claims 1-3.

6. A computer-readable storage medium having a computer program stored thereon, characterized in that, The program is executed by the processor to implement the parametric modeling method for the finite element barrier model as described in any one of claims 1-3.

7. A computer program product, characterized in that, Includes a computer program, which, when executed, is used to implement the parametric modeling method for the finite element barrier model as described in any one of claims 1-3.

Images