CN113255058B

CN113255058B - Processing method, device, equipment and storage medium of finite element model of carrier rocket

Info

Publication number: CN113255058B
Application number: CN202110573879.9A
Authority: CN
Inventors: 不公告发明人
Original assignee: Sichuan Xinghe Power Space Technology Co ltd; Beijing Xinghe Power Equipment Technology Co Ltd; Galactic Energy Beijing Space Technology Co Ltd
Current assignee: Sichuan Xinghe Power Space Technology Co ltd; Beijing Xinghe Power Equipment Technology Co Ltd; Galactic Energy Beijing Space Technology Co Ltd
Priority date: 2021-05-25
Filing date: 2021-05-25
Publication date: 2021-10-22
Anticipated expiration: 2041-05-25
Also published as: CN113255058A

Abstract

The embodiment of the application provides a processing method, a device, equipment and a storage medium of a finite element model of a carrier rocket. The processing method of the finite element model of the carrier rocket comprises the following steps: leading at least one finite element model into a reference finite element model to carry out finite element grid assembly to form an assembly model; acquiring a connection main surface number, a connection slave surface number, connection information and a connection relation name in each connection relation information in each finite element model; searching connection faces corresponding to the connection main face number and the connection slave face number in each connection relation information in the assembly model, and respectively taking the connection faces as the associated connection main face and connection slave face; and establishing connection relation information of the assembly model according to the associated connection main surface, the connection auxiliary surface and the associated information. According to the embodiment of the application, through automatic processing, the technical problems of huge workload and high possibility of errors caused by manual operation are avoided, and the modeling efficiency is greatly improved.

Description

Processing method, device, equipment and storage medium of finite element model of carrier rocket

Technical Field

The application relates to the technical field of carrier rockets, in particular to a method, a device, equipment and a storage medium for processing a finite element model of a carrier rocket.

Background

The processing method of the finite element model of the carrier rocket is generally based on the self-contained function of finite element software, and only finite element grids can be assembled to form an assembly model. However, the connection relation information corresponding to the connection relation in the assembly model cannot be assembled.

Moreover, the establishment of the connection relation information is one of the most time-consuming operations of finite element modeling, and the number of the connection relations is huge, and the operations involved in the establishment of the single connection relation information are also more. At present, the connection relation information is established on an assembly model after finite element grid assembly, a manual operation assembly mode is generally adopted, and the mode has the problems of huge operation workload and easy error.

Disclosure of Invention

The application provides a processing method, a device, equipment and a storage medium of a finite element model of a carrier rocket aiming at the defects of the existing mode, and aims to solve the technical problems of huge operation workload and easy error existing in the establishment of connection relation information of the existing assembly model.

In a first aspect, an embodiment of the present application provides a method for processing a finite element model of a launch vehicle, including:

leading at least one finite element model into a reference finite element model to carry out finite element grid assembly to form an assembly model;

acquiring a connection main surface number, a connection slave surface number, connection information and a connection relation name in each connection relation information in each finite element model; the connection relation information comprises binding relation information and/or contact relation information;

searching connection faces corresponding to the connection main face number and the connection slave face number in each connection relation information in the assembly model, and respectively taking the connection faces as the associated connection main face and connection slave face;

establishing connection relation information of an assembly model according to the associated connection main surface, the associated connection auxiliary surface and the associated information; the association information includes connection information and connection relationship names corresponding to the associated connection primary face and connection secondary face.

In one possible implementation, the method of introducing at least one finite element model into a reference finite element model for finite element mesh assembly to form an assembly model includes:

storing at least two finite element models in a database;

selecting one of the at least two finite element models as a reference finite element model;

and writing the information of the rest finite element models into the reference finite element model to form an assembly model.

adjusting the names of all components in the finite element model to make the names of all the components different;

and importing the adjusted names of the components into an assembly model.

In one possible implementation, adjusting the names of the components in the finite element model so that the names of the components are different includes:

acquiring all component names in the reference finite element model, and storing the component names in a component name storage unit;

acquiring all component names in each finite element model, and sequentially adjusting all the component names in each finite element model;

if the component name of the finite element model is the same as the component name in the component name storage unit, modifying the component name of the finite element model and storing the component name into the component name storage unit;

if the component name of the finite element model is different from the component name in the component name storage unit, directly storing the component name of the finite element model in the component name storage unit;

and importing the adjusted names of the components into an assembly model, wherein the method comprises the following steps:

and importing the names of the components of the finite element model in the component name storage unit into the assembly model.

adjusting the names of the components used in the finite element model to make the names of the components used different;

and importing the adjusted component names used into an assembly model.

In one possible implementation, adjusting each used component name in the finite element model so that each used component name is different comprises:

acquiring a component name used in the reference finite element model, and storing the component name into a used component name storage unit;

acquiring the used component names of the finite element models, and sequentially adjusting the used component names of the finite element models;

if the used component name of the finite element model is the same as the component name in the used component name storage unit, modifying the used component name of the finite element model and storing the modified component name in the used component name storage unit;

if the component name used in the finite element model is different from the component name used in the component name storage unit, directly storing the component name used in the finite element model into the component name used storage unit;

and importing the adjusted component names for use into an assembly model, wherein the method comprises the following steps:

and importing the component names used by the finite element models in the component name storage unit into the assembly model.

In a possible implementation manner, after the finite element model is imported into a reference finite element model for finite element mesh assembly, and after the assembly model is formed, and before the connection main surface number, the connection slave surface number, the connection information, and the connection relation name in each connection relation information in each finite element model are obtained, the method further includes:

adjusting the connection relation names in the connection relation information in the assembly model to make the connection relation names different;

and importing the adjusted connection relation names into an assembly model.

In one possible implementation manner, adjusting the connection relationship names in each piece of connection relationship information in the assembly model so that each connection relationship name is different includes:

acquiring connection relation names in each connection relation information in the reference finite element model, and storing the connection relation names in a connection relation name storage unit;

acquiring the connection relation names in the finite element models, and sequentially adjusting the connection relation names in the finite element models;

if the connection relation name of the finite element model is the same as the component name in the connection relation name storage unit, modifying the connection relation name of the finite element model and storing the modified connection relation name in the connection relation name storage unit;

if the connection relation name of the finite element model is different from the component name in the connection relation name storage unit, directly storing the connection relation name of the finite element model in the connection relation name storage unit;

and importing each adjusted connection relation name into an assembly model, wherein the method comprises the following steps:

and importing the connection relation names of the finite element model in the connection relation name storage unit into the assembly model.

In one possible implementation manner, the creating connection relationship information of the assembly model according to the associated connection main surface and connection slave surface and the association information includes:

adjusting the connection main surface number of the associated connection main surface and the connection slave surface number of the connection slave surface according to the adjusted used component names;

and establishing connection relation information of the assembly model according to the adjusted connection main surface number, connection slave surface number and association information.

In a second aspect, an embodiment of the present application provides a processing apparatus for a finite element model of a launch vehicle, including:

the assembly module is used for guiding at least one finite element model into a reference finite element model to carry out finite element grid assembly to form an assembly model;

the acquisition module is used for acquiring the connection main surface number, the connection slave surface number, the connection information and the connection relation name in each connection relation information in each finite element model; the connection relation information comprises binding relation information and/or contact relation information;

the searching module is used for searching the connection surfaces corresponding to the connection main surface numbers and the connection slave surface numbers in each connection relation information in the assembly model, and the connection surfaces are respectively used as the associated connection main surface and the associated connection slave surface;

the new building module is used for building connection relation information of the assembly model according to the associated connection main surface, the associated connection auxiliary surface and the associated information; the association information includes connection information and connection relationship names corresponding to the associated connection primary face and connection secondary face.

In a third aspect, an embodiment of the present application provides a processing device for a finite element model of a launch vehicle, including:

a processor;

a memory communicatively coupled to the processor;

at least one program stored in the memory and configured to be executed by the processor, the at least one program configured to: a processing method implementing the finite element model of the launch vehicle of the first aspect.

In a fourth aspect, an embodiment of the present application provides a launch vehicle, including: processing apparatus for a finite element model of a launch vehicle according to the third aspect.

In a fifth aspect, embodiments of the present application provide a computer-readable storage medium on which a computer program is stored, the computer program, when executed by an electronic device, implementing the method for processing a finite element model of a launch vehicle of the first aspect.

The beneficial technical effects brought by the technical scheme provided by the embodiment of the application comprise:

the method and the device can lead at least one finite element model into a reference finite element model to carry out finite element mesh assembly to form an assembly model; and searching the connection surface corresponding to the connection main surface number and the connection slave surface number in each connection relation information in each finite element model in the assembly model, and then establishing the connection relation information of the assembly model according to the associated connection main surface and connection slave surface and the associated information. According to the embodiment of the application, through automatic processing, the technical problems of huge workload and high possibility of errors caused by manual operation are avoided. Meanwhile, the method and the device can realize the rapid assembly of a plurality of finite element models with complex connection relations, and greatly improve the modeling efficiency.

Additional aspects and advantages of the present 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 the present application.

Drawings

The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:

FIG. 1 is a schematic flow chart illustrating a method for processing a finite element model of a launch vehicle according to an embodiment of the present disclosure;

FIG. 2 is a schematic flow chart illustrating an embodiment of introducing at least one finite element model into a reference finite element model for assembly to form an assembled model according to an embodiment of the present disclosure;

FIG. 3 is a schematic flow chart of another embodiment of the present application, in which at least one finite element model is imported into a reference finite element model for assembly to form an assembly model in step S101;

fig. 4 is a schematic flowchart between step S101 and step S102 according to an embodiment of the present disclosure;

FIG. 5 is a schematic flow chart diagram illustrating an embodiment of a method for processing a finite element model of a launch vehicle according to the present disclosure;

FIG. 6 is a block diagram of a processing device for a finite element model of a launch vehicle according to an embodiment of the present application;

fig. 7 is a schematic frame diagram of a processing device of a finite element model of a launch vehicle according to an embodiment of the present application.

Detailed Description

Reference will now be made in detail to the present application, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to the same or similar parts or parts having the same or similar functions throughout. In addition, if a detailed description of the known art is not necessary for illustrating the features of the present application, it is omitted. The embodiments described below with reference to the drawings are exemplary only for the purpose of explaining the present application and are not to be construed as limiting the present application.

It will be understood by those within the art that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the prior art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. As used herein, the term "and/or" includes all or any element and all combinations of one or more of the associated listed items.

The terms referred to in this application will first be introduced and explained:

finite element model database (model database, mdb): the file for storing the finite element model can be opened and operated only by professional finite element software. For abaqus software, the suffix of the model database filename is "cae".

Component in finite element model: the minimum geometric structure unit in the finite element model is called part in abaqus software, and information such as finite element meshes, materials and the like is stored in the part.

Assembly in finite element model: the structural system (such as a rocket structure) with one or more components assembled together is called as an assembly in abaqus software, wherein references (similar to pointers in C language) of the components for assembly are stored in the assembly, each reference of part is called as an instance, the name of the instance can be different from that of the part, and one part can correspond to a plurality of instances (for example, one bolt part is assembled for a plurality of times).

Connection relation: the connection relationship in this patent refers specifically to the relationship between geometric surfaces, and includes a contact relationship (referred to as interaction in abaqus software) and a binding relationship (referred to as tie in abaqus software). The contact relationship means that normal penetration between two surfaces cannot occur, but tangential mutual movement is possible. The binding relationship indicates that the two surfaces can not move mutually, and the two surfaces are pasted together by glue.

Connecting main surfaces: any one of the two faces defining the connection relation may be a main face, but both faces may not be simultaneously main faces.

Connecting the slave surface: any one of the two surfaces defining the connection relation can be used as a slave surface, but the two surfaces can not be used as the slave surfaces at the same time.

Model in database: the model is a top-level container in a model database (cae) and is used for storing a complete set of finite element models, and comprises parts, assembly, tie, interaction, load related to calculation (load in abaqus software), boundary conditions (bc in abaqus software), analysis conditions (step in abaqus software) and other elements. A database may contain multiple models, each model being independent of the other.

The inventor of the application researches and discovers that various types of mechanical simulation, including statics calculation and dynamics calculation, need to be carried out on one carrier rocket in the design stage. Statics calculations, used to analyze the ability of a rocket to withstand extreme loads, are a local problem. Rocket cabin segments (such as a primary engine, a secondary engine, a tertiary engine, a secondary stage segment, a tertiary stage segment, a tail segment, an instrument cabin, a track attitude control cabin, a fairing, a boosting stage and the like) are modeled and calculated one by one, the process is completed by a plurality of designers together, and each designer is responsible for modeling and calculating different cabin segments; dynamics problems (such as modal analysis) are mostly global problems and need to be analyzed based on the general assembly model of the whole rocket.

At present, in each space unit, the two calculation tasks are responsible for by different departments, and the modeling methods and modeling software used by the two departments are generally different. For example, for static calculations of a cabin segment, it is possible to build a three-dimensional solid model using abaqus software. For the all-arrow modal computation, it is possible to build a simplified model of the beam-shell mixture using the nanostran software. Therefore, the modeling work of the two departments needs to be finished independently without inheritance.

The inventor of the application further researches and discovers that static force and dynamic calculation are unified under an abaqus platform, a rocket integral finite element model is directly assembled by using a cabin entity finite element model established by the static force calculation, and then modal calculation of the whole rocket is carried out. Therefore, the establishment time of a finite element model of the whole rocket and the verification time of the model precision (the model precision is verified in static calculation) can be saved, and the rocket development efficiency can be greatly improved. However, the existing finite element model assembling method is based on the self-contained function of the finite element software, only the finite element mesh can be assembled, and the connection relation information (such as binding constraints and contact relations among different components in the cabin) in the finite element model cannot be assembled. Moreover, the existing processing method of the connection relation information generally adopts a manual operation mode to establish the connection relation information of the assembled model after the finite element grid is assembled, and has the problems of huge operation workload and easy error.

The application provides a processing method, a processing device, processing equipment and a storage medium of a finite element model of a carrier rocket, and aims to solve the technical problems in the prior art.

The following describes the technical solutions of the present application and how to solve the above technical problems with specific embodiments.

The embodiment of the application provides a processing method of a finite element model of a launch vehicle, and referring to fig. 1, the processing method of the finite element model of the launch vehicle comprises steps S101 to S104.

S101, importing at least one finite element model into a reference finite element model to carry out finite element mesh assembly to form an assembly model.

S102, acquiring a connection main surface number, a connection slave surface number, connection information and a connection relation name in each connection relation information in each finite element model; the connection relationship information includes binding relationship information and/or contact relationship information.

Optionally, the names of the connection relations in S102 are not repeated, and are named uniquely.

And S103, searching connection faces corresponding to the connection main face numbers and the connection slave face numbers in each connection relation information in the assembly model, and taking the connection faces as the associated connection main faces and connection slave faces respectively.

S104, establishing connection relation information of the assembly model according to the associated connection main surface, the associated connection auxiliary surface and the associated information; the association information includes connection information and connection relationship names corresponding to the associated connection primary face and connection secondary face.

According to the embodiment of the application, through automatic processing, the technical problems of huge workload and high possibility of errors caused by manual operation are avoided. Meanwhile, the method and the device can realize the rapid assembly of a plurality of finite element models with complex connection relations, and greatly improve the modeling efficiency.

In some embodiments, the step S101 of importing at least one finite element model into a reference finite element model for assembly to form an assembly model includes:

storing at least two finite element models in a database;

Optionally, in step S101, at least one finite element model is imported into a reference finite element model for assembly, so as to form an assembled model, including steps a1 to A3.

Step A1: establishing a working directory on a computer hard disk, storing a finite element model database of all rocket cabin sections needing to be assembled into the working directory, selecting n finite element models with the names P1.cae and P2.cae … Pn. cae, wherein only one model in any one cae stores a finite element model of a certain cabin section of a rocket.

Step A2: and establishing an empty database named A.cae in the working directory, and storing the finite element model of the whole rocket in the subsequent steps.

Step A3: and respectively introducing P1. cae-Pn. cae into A.cae by using import function of Abaqus software, so that the model of each cabin section of the rocket exists in the A.cae in the form of model and is also named as P1 and P2 … Pn.

Optionally, if P1 is selected as the reference finite element model, the information of P2 … Pn is written into the reference finite element model, and the finite element mesh assembly is performed to form the assembly model.

and importing the adjusted names of the components into an assembly model.

In some embodiments, adjusting the component names in the finite element model such that the component names are different comprises:

Alternatively, referring to fig. 2, in step S101, a specific method for introducing at least one finite element model into a reference finite element model for assembly to form an assembly model includes the following steps S201 to S205.

S201, obtaining all component names in the reference finite element model, storing the component names into a component name storage unit, and then executing the step S202.

S202, obtaining all component names in each finite element model, sequentially adjusting all the component names in each finite element model, and sequentially executing the step S203 or the step S204 on all the component names in each finite element model.

S203, if the component name of the finite element model is the same as the component name in the component name storage unit, modifying the component name of the finite element model, storing the component name into the component name storage unit, and then executing the step S205.

S204, if the component name of the finite element model is different from the component name in the component name storage unit, directly storing the component name of the finite element model in the component name storage unit, and then executing the step S205.

S205, after all the component names in the finite element models are adjusted, the component names of the finite element models in the component name storage unit are led into the assembly model.

Optionally, the component names of all the finite element models are imported into the assembly model together after the adjustment is completed, or the component names of each finite element model are imported into the assembly model after the adjustment is completed.

Optionally, through the above steps, names of the components in the adjusted finite element model are all different, and then the names of the components in the adjusted finite element model are imported into the assembly model, so that the names of the components are named uniquely.

and importing the adjusted component names used into an assembly model.

In some embodiments, adjusting each used component name in the finite element model such that each used component name is different comprises:

and if the component name used in the finite element model is different from the component name used in the component name storage unit, directly storing the component name used in the finite element model into the component name used storage unit.

Alternatively, referring to fig. 3, in step S101, a specific method for introducing at least one finite element model into a reference finite element model for assembly to form an assembly model includes the following steps S301 to S305.

S301, obtaining the component name used in the reference finite element model, storing the component name into a used component name storage unit, and then executing the step S302.

S302, acquiring the used component names of the finite element models, sequentially adjusting the used component names of the finite element models, and sequentially executing the step S303 or the step S304 on the used component names of the finite element models.

S303, if the used component name of the finite element model is the same as the component name in the used component name storage unit, modifying the used component name of the finite element model, storing the modified component name in the used component name storage unit, and then executing the step S305.

S304, if the component name used in the finite element model is different from the component name in the used component name storage unit, directly storing the component name used in the finite element model in the used component name storage unit, and then executing the step S305.

S305, after the adjustment of all the used component names in the finite element models is finished, the used component names of the finite element models in the used component name storage unit are imported into the assembly model.

Alternatively, all the used component names of all the finite element models are introduced into the assembly model together after the adjustment is completed, or the used component names of each finite element model are introduced into the assembly model after the adjustment is completed.

Optionally, through the above steps, the names of the components used in the adjusted finite element model are all different, and then the names of the components used in the adjusted finite element model are introduced into the assembly model, so that the names of the components used are named uniquely.

Optionally, the component name used in each finite element model may also be associated with the component name in the finite element model, and when the component name used in the finite element model is adjusted, the component name used in the finite element model is also adjusted correspondingly, so that no additional adjustment of the component name used in the finite element model is required.

Optionally, as an example, in combination with step S101 in fig. 1 and the specific method for forming an assembly model shown in fig. 2 and fig. 3, at least one finite element model is introduced into a reference finite element model for assembly, so as to form the assembly model, including step B1 to step B7.

B1, optionally determining a reference model in a.cae, for writing information of the rest of the models into the reference model, which is used to store the assembly model of the entire rocket. In this embodiment, P1 is the reference model.

B2, identifying the names of all parts in P1 (part is a component, and the name of part is a component name), and storing the names into basepartname variables. The basepartname variable is stored in the component name storage unit.

B3, identifying all part names in P2, judging whether the names are repeated with the elements of the basepartname variable in the component name storage unit one by one, if so, modifying the names of the part, and if not, not modifying the names.

Optionally, all part names in the adjusted P2 are stored in the component name storage unit, so as to facilitate subsequent import into the assembly model.

B4, copying all the parts in P2 into the assembly model, and based on the steps, the parts in P1 and P2 have no repeated naming condition, so that the assembly model does not have the coverage problem of the parts with the same name.

B5, identifying the names of all the instances in P2 (an instance is a used component, and the name of an instance is a used component name), and storing the name of the part used by the assembly (namely the name of the instance) into the variable otherparatname. The otherpartname variable is stored in the used component name storage location.

Optionally, the name of instance is adjusted with the name of part

B6, according to the otherparatname, the otherparatname variable of P2 in the component name storage unit is referred to assembly of the assembly model.

B7, repeating the steps B3-B6 for P3-Pn, and then assembling the model to form an assembly including the complete rocket and each part of the carrier rocket.

Alternatively, steps B1 through B7 are performed after steps a1 through A3.

In some embodiments, between step S101 and step S102, after importing at least one finite element model into a reference finite element model for assembly, and forming an assembly model, and before acquiring a connection main surface number, a connection slave surface number, connection information, and a connection relationship name in each connection relationship information in each finite element model, the method further includes:

and importing the adjusted connection relation names into an assembly model.

In some embodiments, adjusting the connection relation names in each connection relation information in the assembly model so that each connection relation name is different includes:

Alternatively, as shown in fig. 4, between step S101 and step S102, step S401 to step S405 are further included.

S401, obtaining the connection relation name in each connection relation information in the reference finite element model, storing the connection relation name in a connection relation name storage unit, and then executing the step S402.

S402, obtaining the connection relation names in the finite element models, sequentially adjusting the connection relation names in the finite element models, and sequentially executing the step S403 or the step S404 on the connection relation names in the finite element models.

S403, if the connection relation name of the finite element model is the same as the component name in the connection relation name storage unit, modifying the connection relation name of the finite element model, storing the modified connection relation name in the connection relation name storage unit, and then executing the step S405.

S404, if the connection relation name of the finite element model is different from the component name in the connection relation name storage unit, directly storing the connection relation name of the finite element model in the connection relation name storage unit, and then executing the step S405.

S405, after all the connection relation names in the finite element models are adjusted, the connection relation names of the finite element models in the connection relation name storage unit are led into the assembly model.

Optionally, the connection relation names of all the finite element models are introduced into the assembly model together after the adjustment is completed, or the connection relation names of each finite element model are introduced into the assembly model after the adjustment is completed.

Optionally, through the above steps, the connection relation names in the adjusted finite element model are all different, and then the connection relation names in the adjusted finite element model are imported into the assembly model, so that the connection relation names are named uniquely.

In some embodiments, in step S104, creating connection relationship information of the assembly model according to the associated connection primary surface and connection secondary surface and the association information includes:

Optionally, the adjusted connection primary surface number and connection secondary surface number correspond to the connection information and connection relationship name of the connection primary surface number and connection secondary surface number before adjustment in the connection relationship information, and the adjusted connection primary surface number, connection secondary surface number, and corresponding connection information and connection relationship name are bound to implement new creation of the connection relationship information of the assembly model.

Optionally, the connection relationship information includes binding relationship information and/or contact relationship information, the binding relationship information corresponds to a binding relationship tie, the contact relationship information corresponds to a contact relationship interaction, and the connection information includes the binding information and/or the contact information.

Optionally, as an example, in combination with steps S102 to S104 and the steps shown in fig. 4, the embodiment of the present application provides a new method for creating binding information of an assembly model, including:

step C1: the names of all the tie in P1 are identified and stored in the basetiename variable. The basetiename variable is stored in the connection relationship name storage unit.

Step C2: identifying the names of all the tie in the P2, judging whether the names are repeated with the element of the basetiename variable one by one, if so, modifying the names of the tie, and if not, not modifying the names. The names of all tie adjusted in P2 are stored in the variable othertiename. The othertiename variable is stored in the connection relationship name storage unit.

Step C3: the numbers and binding information identifying the master and slave surfaces of all the tie in P2 are stored in variables, i.e., attentiemID, attentiesID, and attentinfo, respectively.

Step C4: connection faces named as othertiemID and othertiesID are searched one by one in the assembly model, the connection faces are used as a main face and a slave face, the othertiename is used as a name, and the othertieInfo is used as binding information to establish the connection relation of the binding information tie. At this time, tie linkage in P2 was reproduced in the assembly model.

Step C5: repeating the steps C2-C4 for P3-Pn.

Optionally, after the steps B1-B7 are performed, the steps C1-C5 are performed.

Optionally, in this embodiment of the present application, based on steps S102 to S104 and the steps shown in fig. 4, a method for creating contact information of an assembly model is provided, including:

step D1: the names of all interactions in P1 are identified and stored in the variable baseintname. The baseintname variable is stored in the connection relationship name storage unit.

Step D2: identifying the names of all interactions in P2, judging whether the names are repeated with the element of the baseintname variable one by one, if so, modifying the names of the interactions, and if not, not modifying the names. The names of all interactions in P2 are then stored in the variable otherntname. The othermentname variable is stored in the connection relationship name storage unit.

Step D3: the numbers and contact information for identifying the master and slave surfaces of all interactions in P2 are stored in the variables otherntmid, otherrintsid, and otherrintinfo, respectively.

Step D4: the surfaces named as the other IDs and the other IDs are searched one by one in the assembly model, the surfaces are used as a main surface and a slave surface, the other name is used as a name, the other info is used as contact information, and the interaction connection relation is established. At this time, the interaction connection relationship in P2 was reproduced in P1.

Step D5: repeating the steps D2-D4 for P3-Pn.

Optionally, after the steps B1-B7 are performed, the steps D1-D5 are performed.

Optionally, the steps D1-D5 and the steps C1-C5 may be executed sequentially or simultaneously.

Optionally, as an example, an embodiment of the present application provides an embodiment of a processing method of a finite element model of a launch vehicle, and taking P2 introduced into P1 as an example, referring to fig. 5, the processing method of the finite element model of the launch vehicle includes the following steps:

s501, establishing a working directory, and storing the working directory into a CAE database P1. CAE-Pn.cae for storing each cabin section of the rocket.

Step S502, an empty database A.cae is established in the working catalog.

And S503, importing the A.cae from P1.cae to Pn.cae.

And step S504, identifying the names of all parts in the P1, and storing the names into the basepartname variable.

In step S505, when i =1, it is determined whether i is equal to or less than P2, if so, step S506 is executed, and if not, step S509 is executed.

Step S506, whether the part [ i ] name in P2 is in the basepartname or not is judged, if yes, step S507 is executed, and if not, step S508 is executed.

Step S507, modifying the name of part [ i ] of P2.

Part [ i ] of the steps S508 and P2 is stored in the component name storage unit, so that the combined model can be conveniently imported subsequently, and then i is changed into i +1 to continue to execute the step S505.

In step S509, the names of all instances of P2 are identified and saved in the otherparatname.

Step S510, all parts named in the otherparatname in P2 are referred to in assembly of the assembly model.

And step S511, identifying the names of all the tie in the P1, and storing the names into the basetiename.

Step S512, when i =1, determines whether i is equal to or less than tie number of P2, if yes, step S513 is executed, and if no, step S517 is executed.

Step S513, whether the tie [ i ] name in P2 is in the basetiename is judged, if yes, step S514 is executed, and if not, step S515 is executed.

Step S514, modifying the name of tie [ i ] of P2, and saving the name to othertime [ i ].

Step S515, identify the connection master surface number, othertiemID [ i ], the connection slave surface number, othertiesID [ i ], and the binding information, othertieInfo [ i ] of tie [ i ].

Step S516, in the assembly model, using othertiename [ i ] as name, using othertiemID [ i ] and othertiesID [ i ] as master-slave surface, using othertieInfo [ i ] as binding information to establish tie connection, then changing i to i +1, and continuing to execute step S512.

Optionally, the othertimID [ i ], the otherthiesID [ i ] are adjusted accordingly according to the adjustment of the othertiename [ i ], such that the names of the othertimID [ i ] and the otherthiesID [ i ] are unique.

And S517, identifying the names of all interactions in the P1, and storing the names into the baseintname.

In step S518, when i =1, it is determined whether i is equal to or less than the number of contacts of P2, if so, step S519 is executed, and if not, step S523 is executed.

Step S519, whether the interaction [ i ] name in P2 is in the baseintname or not is judged, if yes, step S520 is executed, and if not, step S521 is executed.

Step S520, modify the name of interaction [ i ] of P2, and save to other name [ i ].

Step S521, identifying the master-slave surface numbers, othermentmID [ i ], and the contact information, othermentInfo [ i ], of the interaction [ i ].

Step S522, in P1, the other name [ i ] is used as the name, the other material ID [ i ] and the other material ID [ i ] are used as the master-slave surfaces, the other material Info [ i ] is used as the contact information to establish the interaction connection, and then the i is changed to i +1 to continue to execute step S518.

Step S523, save database a.cae.

Optionally, steps S504 to S523 are repeatedly executed for P3 to Pn.

Optionally, the example is developed through a Python program, all operations can be implemented through the program, more parameters are needed in the program implementation process, for example, the interaction connection relationship contains selection of a plurality of parameters such as a slippage formula, a discrete formula, a contact attribute, contact control, slave surface adjustment and the like, and similarly, a plurality of detail parameters of tie connection are collectively called as binding relationship information.

According to the embodiment of the application, the assembly of the finite element model of each cabin section of the carrier rocket is realized in abaqus, and the heavy operation of reestablishing the binding and contact connection relation in an assembly body is avoided. For hundreds of part models, the assembly time of the whole carrier rocket model is shortened to a minute level from the original time of several days, and the design efficiency is greatly improved. In addition, the python program is automatically processed, various errors possibly caused by manual operation are avoided, and therefore modeling efficiency is greatly improved.

Based on the same inventive concept, the present application provides a processing apparatus for a finite element model of a launch vehicle, and referring to fig. 6, the processing apparatus 600 for a finite element model of a launch vehicle includes: an assembly module 601, an acquisition module 602, a lookup module 603, and a new build module 604.

The assembling module 601 is configured to introduce at least one finite element model into a reference finite element model for assembling, so as to form an assembled model.

The obtaining module 602 is configured to obtain a connection primary surface number, a connection secondary surface number, connection information, and a connection relationship name in each connection relationship information in each finite element model; the connection relationship information includes binding relationship information and/or contact relationship information.

The searching module 603 is configured to search, in the assembly model, connection faces corresponding to the connection primary face number and the connection secondary face number in each piece of connection relationship information, as associated connection primary faces and connection secondary faces, respectively.

The new building module 604 is configured to build connection relationship information of the assembly model according to the associated connection main surface, connection slave surface, and associated information; the association information includes connection information and connection relationship names corresponding to the associated connection primary face and connection secondary face.

Optionally, the assembling module 601 is further configured to store at least two finite element models in a database; selecting one of the at least two finite element models as a reference finite element model; and writing the information of the rest finite element models into the reference finite element model to form an assembly model.

Optionally, the assembling module 601 is further configured to adjust names of the components in the finite element model, so that the names of the components do not obtain all names of the components in the reference finite element model, and are stored in the component name storage unit.

Optionally, the assembling module 601 is further configured to obtain all component names in each finite element model, and sequentially adjust all component names in each finite element model; if the component name of the finite element model is the same as the component name in the component name storage unit, modifying the component name of the finite element model and storing the component name into the component name storage unit; if the component name of the finite element model is different from the component name in the component name storage unit, directly storing the component name of the finite element model in the component name storage unit; and importing the names of the components of the finite element model in the component name storage unit into the assembly model.

Optionally, the assembling module 601 is further configured to adjust each used component name in the finite element model, so that each used component name is different; and importing the adjusted component names used into an assembly model.

Optionally, the assembly module 601 is further configured to obtain a component name used in the reference finite element model, and store the component name into the used component name storage unit; acquiring the used component names of the finite element models, and sequentially adjusting the used component names of the finite element models; if the used component name of the finite element model is the same as the component name in the used component name storage unit, modifying the used component name of the finite element model and storing the modified component name in the used component name storage unit; if the component name used in the finite element model is different from the component name used in the component name storage unit, directly storing the component name used in the finite element model into the component name used storage unit; and importing the component names used by the finite element models in the component name storage unit into the assembly model.

Optionally, the assembling module 601 is further configured to adjust connection relationship names in each connection relationship information in the assembling model, so that each connection relationship name is different; and importing the adjusted connection relation names into an assembly model.

Optionally, the assembling module 601 is further configured to obtain a connection relationship name in each connection relationship information in the reference finite element model, and store the connection relationship name in the connection relationship name storage unit; acquiring the connection relation names in the finite element models, and sequentially adjusting the connection relation names in the finite element models; if the connection relation name of the finite element model is the same as the component name in the connection relation name storage unit, modifying the connection relation name of the finite element model and storing the modified connection relation name in the connection relation name storage unit; if the connection relation name of the finite element model is different from the component name in the connection relation name storage unit, directly storing the connection relation name of the finite element model in the connection relation name storage unit; and importing the connection relation names of the finite element model in the connection relation name storage unit into the assembly model.

Optionally, the newly building module 604 is further configured to adjust a connection primary surface number of the associated connection primary surface and a connection secondary surface number of the connection secondary surface according to the adjusted component names used respectively; and establishing connection relation information of the assembly model according to the adjusted connection main surface number, connection slave surface number and association information.

Optionally, in this embodiment of the present application, the Python program is used for development, all operations in the following steps are implemented by a program, the program mainly includes an assembly module 601, an acquisition module 602, a lookup module 603, and a new module 604, the assembly module 601 includes a database establishment module, a cae import module, and a part import module, the new module 604 includes a tie establishment module and an interaction establishment module, and the database establishment module, the cae import module, the part import module, the tie establishment module, and the interaction establishment module may be in a serial execution relationship, and a process of the above modules is sequentially executed, including:

the method comprises the following steps: a pre-established finite element model database (cae file) of each bay section of the rocket is obtained.

Step two: a database building module is executed to build a new empty model database (default name a.cae).

Step three: and executing a cae importing module, importing all the finite element models of the cabin sections in the step one into the newly-built A.cae in the step two, updating the A.cae and storing the updated A.cae.

Step four: and executing a part import module, importing all parts in all models in the A.cae into a certain reference model, updating the A.cae and storing the updated A.cae.

Step five: the acquisition module 602 and the search module 603 find a connection main surface and a connection slave surface, execute a tie establishment module, establish tie connection relation information of each cabin segment in a reference model of the a.cae, and update and store the a.cae.

Step six: the connection main surface and the connection slave surface are found through the acquisition module 602 and the search module 603, an interaction establishing module is executed, interaction connection of each cabin section is established in a reference model of the A.cae, and the A.cae is updated and stored.

Based on the same inventive concept, the embodiment of the application provides a processing device of a finite element model of a launch vehicle, which comprises:

a processor;

a memory communicatively coupled to the processor;

at least one program stored in the memory and configured to be executed by the processor, the at least one program configured to: a method of processing a finite element model of a launch vehicle according to any of the embodiments of the present application.

Alternatively, an embodiment of the present application provides a processing device for a finite element model of a launch vehicle, as shown in fig. 7, and the processing device 2000 for a finite element model of a launch vehicle shown in fig. 7 includes: a processor 2001 and a memory 2003. The processor 2001 and memory 2003 are communicatively coupled, such as via a bus 2002, among others.

The Processor 2001 may be a CPU (Central Processing Unit), general Processor, DSP (Digital Signal Processor), ASIC (Application Specific Integrated Circuit), FPGA (Field Programmable Gate Array) or other Programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor 2001 may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs and microprocessors, and the like.

Bus 2002 may include a path that conveys information between the aforementioned components. The bus 2002 may be a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. The bus 2002 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 7, but this is not intended to represent only one bus or type of bus.

The Memory 2003 may be a ROM (Read-Only Memory) or other type of static storage device that can store static information and instructions, a RAM (random access Memory) or other type of dynamic storage device that can store information and instructions, an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read-Only Memory) or other optical Disc storage, optical Disc storage (including Compact Disc, laser Disc, optical Disc, digital versatile Disc, blu-ray Disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these.

Optionally, the processing device 2000 of the finite element model of the launch vehicle may further comprise a transceiver 2004. The transceiver 2004 may be used for reception and transmission of signals. The transceiver 2004 may allow the processing device 2000 of the finite element model of the launch vehicle to communicate wirelessly or wiredly with other devices to exchange data. It should be noted that the number of the transceivers 2004 is not limited to one.

Optionally, the processing device 2000 of the finite element model of the launch vehicle may further comprise an input unit 2005. The input unit 2005 may be used to receive input numerical, character, image and/or sound information, or to generate key signal inputs related to user settings and function control of the processing device 2000 of the finite element model of the launch vehicle. The input unit 2005 may include, but is not limited to, one or more of a touch screen, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, a camera, a microphone, and the like.

Optionally, the processing device 2000 of the finite element model of the launch vehicle may further comprise an output unit 2006. The output unit 2006 may be used to output or show information processed by the processor 2001. The output unit 2006 may include, but is not limited to, one or more of a display device, a speaker, a vibration device, and the like.

While fig. 7 illustrates the processing apparatus 2000 of a finite element model of a launch vehicle having various means, it is to be understood that not all of the means shown are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.

Optionally, the memory 2003 is used for storing application program code for performing the disclosed aspects, and is controlled in execution by the processor 2001. The processor 2001 is configured to execute the application program codes stored in the memory 2003 to implement the processing method of the finite element model of the launch vehicle according to any of the embodiments provided in the present application.

Based on the same inventive concept, the embodiment of the application provides a launch vehicle, which comprises: a processing apparatus for a finite element model of a launch vehicle as in any one of the embodiments of the present application.

Based on the same inventive concept, embodiments of the present application provide a computer-readable storage medium on which a computer program is stored, the computer program, when executed by an electronic device, implementing a method for processing a finite element model of a launch vehicle according to any of the embodiments of the present application.

The computer readable storage medium includes, but is not limited to, any type of disk including floppy disks, hard disks, optical disks, CD-ROMs, and magneto-optical disks, ROMs, RAMs, EPROMs (Erasable Programmable Read-Only memories), EEPROMs, flash Memory, magnetic or optical cards. That is, a readable medium includes any medium that stores or transmits information in a form readable by a device (e.g., a computer).

The application of the method and the device can at least realize the following technical effects:

(1) according to the embodiment of the application, through automatic processing, the technical problems of huge workload and high possibility of errors caused by manual operation are avoided.

(2) The method and the device can realize the rapid assembly of a plurality of finite element models with complex connection relations, and greatly improve the modeling efficiency.

(3) The embodiment is developed through a Python program, and all operations can be realized through the program, so that the automatic processing process is realized, various errors possibly caused by manual operation are avoided, and the modeling efficiency is greatly improved.

(4) According to the embodiment of the application, the assembly of the finite element model of each cabin section of the carrier rocket is realized in abaqus, and the heavy operation of reestablishing the binding and contact connection relation in an assembly body is avoided. For hundreds of part models, the assembly time of the whole carrier rocket model is shortened to a minute level from the original time of several days, and the design efficiency is greatly improved.

Those of skill in the art will appreciate that the various operations, methods, steps in the processes, acts, or solutions discussed in this application can be interchanged, modified, combined, or eliminated. Further, other steps, measures, or schemes in various operations, methods, or flows that have been discussed in this application can be alternated, altered, rearranged, broken down, combined, or deleted. Further, steps, measures, schemes in the prior art having various operations, methods, procedures disclosed in the present application may also be alternated, modified, rearranged, decomposed, combined, or deleted.

The terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the present application, "a plurality" means two or more unless otherwise specified.

In the description herein, particular features, structures, materials, or characteristics may be combined in any suitable manner in any one or more embodiments or examples.

It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least a portion of the steps in the flow chart of the figure may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

The foregoing is only a partial embodiment of the present application, and it should be noted that, for those skilled in the art, several modifications and decorations can be made without departing from the principle of the present application, and these modifications and decorations should also be regarded as the protection scope of the present application.

Claims

1. A method of processing a finite element model of a launch vehicle, comprising:

leading at least one finite element model into a reference finite element model for finite element mesh assembly to form an assembly model, comprising: adjusting the names of the used components in the finite element model to ensure that the names of the used components are different; guiding the adjusted names of the used components into an assembly model;

acquiring a connection main surface number, a connection slave surface number, connection information and a connection relation name in each connection relation information in each finite element model; the connection relation information comprises binding information and/or contact information;

establishing connection relation information of the assembly model according to the associated connection main surface, the associated connection auxiliary surface and the associated information; the association information includes the connection information and the connection relationship name corresponding to the associated connection primary face and connection secondary face.

2. The method of processing finite element models of a launch vehicle of claim 1 wherein said introducing at least one finite element model into a reference finite element model for finite element mesh assembly to form an assembled model comprises:

storing at least two finite element models in a database;

3. The method of processing finite element models of a launch vehicle of claim 1 wherein said introducing at least one finite element model into a reference finite element model for finite element mesh assembly to form an assembled model comprises:

adjusting the names of the components in the finite element model to enable the names of the components to be different;

and importing the adjusted names of the components into an assembly model.

4. The method of processing a finite element model of a launch vehicle of claim 3, wherein said adjusting each component name in the finite element model such that each component name is different comprises:

acquiring all component names in the finite element models, and sequentially adjusting all the component names in the finite element models;

and importing each adjusted component name into an assembly model, wherein the method comprises the following steps:

and importing the names of the components of the finite element model in the component name storage unit into an assembly model.

5. The method of processing a finite element model of a launch vehicle of claim 1, wherein said adjusting each used component name in the finite element model such that each used component name is different comprises:

acquiring the component name used in the reference finite element model, and storing the component name into a used component name storage unit;

if the component name used in the finite element model is different from the component name in the used component name storage unit, directly storing the component name used in the finite element model into the used component name storage unit;

and importing each adjusted used component name into an assembly model, wherein the steps of:

and importing the component names used by the finite element models in the component name storage unit into an assembly model.

6. The method for processing finite element models of a launch vehicle according to claim 1, wherein after the finite element model is imported into a reference finite element model for finite element mesh assembly, and after the assembly model is formed, and before the obtaining of the connection main surface number, the connection slave surface number, the connection information, and the connection name in each connection information of the finite element models, the method further comprises:

adjusting the connection relation names in the connection relation information in the assembly model to enable the connection relation names to be different;

and importing the adjusted connection relation names into an assembly model.

7. The method of processing a finite element model of a launch vehicle of claim 6, wherein adjusting the connection names in each connection information in the assembled model so that each connection name is different comprises:

acquiring connection relation names in the connection relation information in the reference finite element model, and storing the connection relation names in a connection relation name storage unit;

and importing the connection relation names of the finite element model in the connection relation name storage unit into an assembly model.

8. The method for processing a finite element model of a launch vehicle of claim 1, wherein said creating connection relationship information of said assembly model based on said associated connecting major and minor faces and association information comprises:

adjusting the connection main surface number of the associated connection main surface and the connection slave surface number of the connection slave surface according to each adjusted used component name;

9. A processing apparatus for a finite element model of a launch vehicle, comprising:

the assembly module is used for leading at least one finite element model into a reference finite element model to carry out finite element mesh assembly to form an assembly model, and comprises the following components: adjusting the names of the used components in the finite element model to ensure that the names of the used components are different; guiding the adjusted names of the used components into an assembly model;

the acquisition module is used for acquiring the connection main surface number, the connection slave surface number, the connection information and the connection relation name in each connection relation information in the finite element models; the connection relation information comprises binding relation information and/or contact relation information;

the searching module is used for searching the connection surfaces corresponding to the connection main surface numbers and the connection slave surface numbers in each piece of connection relation information in the assembly model, and the connection surfaces are respectively used as the associated connection main surface and connection slave surface;

the new building module is used for building the connection relation information of the assembly model according to the associated connection main surface, the associated connection auxiliary surface and the associated information; the association information includes the connection information and the connection relationship name corresponding to the associated connection primary face and connection secondary face.

10. A processing apparatus for finite element modeling of a launch vehicle, comprising:

a processor;

a memory communicatively coupled to the processor;

at least one program stored in the memory and configured to be executed by the processor, the at least one program configured to: processing method to implement a finite element model of a launch vehicle according to any of claims 1-8.

11. A launch vehicle, comprising: processing equipment for a finite element model of a launch vehicle according to claim 10.

12. A computer-readable storage medium, on which a computer program is stored, which computer program, when being executed by an electronic device, carries out a method of processing a finite element model of a launch vehicle according to any one of claims 1 to 8.