Analysis step associated data structure design method and system applied to structural finite element software development

Abstract

The invention belongs to the technical field of software development, and particularly relates to an analysis step associated data structure design method and system applied to structural finite element software development. The method comprises the following steps of: 1, calculating and analyzing a service background in combination with a structural finite element, abstracting analysis step associated data from a data level, and abstracting a finite element model into a data object and an analysis step; 2, data abstraction and data structure design need to be carried out on the data object to form a data object model based on management of the data object in the step 1, and the data object model should comprise a unique identifier of an analysis step, an analysis step state identifier and an analysis step data manager; and 3, based on the data object model in the step 2, according to the use requirement of structural finite element analysis and calculation on the data object and the interactive logic of a user on the UI level of structural finite element analysis and calculation software, carrying out data object model interface packaging design. The method is used for solving the problem of state and data management of analysis step associated data in an analysis step in the field of data structure design of an existing structural finite element model.

Description

Technical Field

[0001] The present invention belongs to the technical field of software development, and in particular relates to an analysis step associated data structure design method and system thereof applied to structural finite element software development. Background Art

[0002] Structural finite element numerical solution is an engineering analysis method in the field of structural mechanics that uses the finite element method to establish an analysis model and then solve it with the help of a computer. The finite element analysis model is the basis for numerical solution, and its data mainly includes mesh model, material property data, analysis step data, interaction data, and boundary and load data.

[0003] The mesh model consists of data such as nodes, units, node sets, unit geometry, and surfaces. A node is a point in three-dimensional space, which is uniquely identified by a unique integer id value. A unit is composed of multiple nodes, such as a tetrahedral unit composed of four nodes, a hexahedral unit composed of eight nodes, etc., which are also uniquely identified by a unique integer id value. A node set is composed of multiple points, which are uniquely identified by a name. A unit set is composed of multiple units, which are also uniquely identified by a name. A surface is composed of one or more faces of multiple units.

[0004] Material property data includes material data and section property data. Material data refers to the physical property data of the material, such as density, mechanical properties, thermal properties, etc. Section properties refer to the properties assigned to the mesh model, such as solid, thin shell, beam section, etc.

[0005] The analysis step data refers to the type and parameters of the finite element model to be solved, such as static analysis, dynamic analysis, etc. An analysis step is to perform a complete solution calculation on the model under certain conditions. The solution results are then obtained for engineering analysis.

[0006] The interaction data expresses the connection, contact and other interactions between the various components in the finite element model.

[0007] Boundary and load data are the boundary conditions (such as fixed constraints) and loads (such as concentrated forces, distributed forces) required to solve the finite element model.

[0008] From the above, we can see that the finite element model contains many types of data, a large amount of data, and not only static data. In the finite element analysis calculation process, there are also correlations between various data. As the activation state of the analysis step changes, the state of the data associated with it will change dynamically. This situation has high requirements for data structure design. If the data structure design is unreasonable, it will directly affect the stability and scalability of the program operation. It may be that adding only one material type will cause the data structure to not support it, which will bring a lot of code modification work.

[0009] For example, a structural finite element model contains multiple analysis steps (Step-1, Step-2, and Step-3). In Step-1, a load Load-1 is created. The data and status of Load-1 in the analysis step can be discussed separately.

[0010] as follows:

[0011] By default, the status of Load-1 in the analysis step where it is created is "Created", and the data is the data assigned when it is created; the status in Step-2 and all subsequent analysis steps is "Propagated" (meaning that the effect of the load on the model will continue to Step-2 and subsequent analysis steps), and the data is consistent with the data in Step-1. Fig.10 As shown;

[0012] If you want to modify the effect of Load-1 in Step-2 (for example, adjust the size of the load), you can modify the data of Load-1 in Step-2. At this time, the status and data of Load-1 in Step-1 remain unchanged; the status in Step-2 becomes "Modified" (meaning modified), and the data becomes the modified data; and the status in all analysis steps after Step-2 is "Propagated", and the data is consistent with the data in Step-2. Fig.11 As shown;

[0013] If you want to cancel the effect of Load-1 in Step-2, you can deactivate Load-1 in Step-2. At this time, the status and data of Load-1 in Step-1 remain unchanged; the status in Step-2 becomes "Deactivated" (meaning deactivated), and the data is empty; and the status in the analysis after Step-2 is "No longer active" and the data is empty. Fig.12 As shown;

[0014] Load-1 can also support changes in the analysis step where it is created, such as "moving right" the analysis step where it is created to Step-2, so that the status of Load-1 in both Step-1 and Step-2 will change. The status and data in Step-1 are both empty; in Step-2, the status changes to "Created", and the data is the data at the time of creation; and in the analysis step after Step-2, the status is "Propagated", and the data is consistent with that in Step-2.

[0015] like Fig.13 As shown;

[0016] Analyzing the above cases, we can see that to achieve the state and data management of data objects in the analysis step, we need to manage data and manage the state.

[0017] The present invention is aimed at the state and data management issues of the analysis step-associated data objects in the analysis step as described above.

[0018] The disadvantages of the prior art are:

[0019] 1) Failure to encapsulate the logical types associated with the data objects and analysis steps results in each type of data having to be processed separately, resulting in poor software stability and excessive workload on the software development project.

[0020] 2) It requires users (data interface users, i.e. GUI developers or script interface developers) to be familiar with the state logic of business-level data objects and explicitly set their data and states, which increases the requirements for developers to understand the business;

[0021] 3) There is no scalability, which increases the difficulty and workload of software maintenance and expansion. Summary of the invention

[0022] The present invention provides an analysis step associated data structure design method and system thereof applied to structural finite element software development, so as to solve the problems in the above-mentioned background technology.

[0023] The present invention is achieved through the following technical solutions:

[0024] A method for designing an analysis step association data structure applied to structural finite element software development, the method comprising the following steps:

[0025] Step 1: Based on the business background of structural finite element calculation and analysis, the data associated with the analysis step is abstracted from the data level, and the finite element model is abstracted into data objects DataObject and analysis steps;

[0026] Step 2: Based on the data object DataObject of step 1, data abstraction and data structure design need to be performed on the data object DataObject to form a data object model. The data object model should include a unique identifier of the analysis step, an analysis step status identifier, and an analysis step data manager;

[0027] Step 3: Based on the data object model in step 2, according to the use requirements of the data object DataObject in the structural finite element analysis calculation, and the user interaction logic at the UI level of the structural finite element analysis calculation software, carry out the data object model interface encapsulation design;

[0028] Step 4: Based on the design of the data object DataObject in step 2 and step 3, first derive the specific data XData of the data object DataObject based on Data; then derive the data object DataObjectXDataObject based on DataObject.

[0029] Furthermore, the data object DataObject in step 1 includes a finite element mesh model data object DataObject, a material property data object, an interaction data object, a boundary condition data object and a load data object.

[0030] Furthermore, the unique identifier of the analysis step in step 2 cannot be modified, but the state of the analysis step can be modified. The created analysis step includes two states: activated and deactivated. When the analysis step is in the activated state, it participates in the calculation during the structural finite element analysis calculation process, while the deactivated state does not participate in the calculation during the structural finite element analysis calculation process.

[0031] Furthermore, the analysis step data manager in step 2 manages all analysis step loading data in a unified manner, wherein each analysis step can load different data.

[0032] Furthermore, the management object of the analysis step data manager in step 2 is the data in each analysis step. When the data object DataObject is created, only the data corresponding to the unique identifier of the analysis step is recorded; the subsequent analysis step data is recorded in the data manager only when the data of the analysis step is modified, otherwise it is not recorded.

[0033] Furthermore, in step 2, the analysis step data manager establishes a data mapping relationship between the analysis step unique identifier and the metadata in the analysis step data object manager, establishes a binding relationship between the analysis step unique identifier and the data object DataObject, and completes the analysis step data model to participate in the structural finite element analysis calculation;

[0034] By establishing a data status mapping relationship between the analysis step status identifier and the metadata in the analysis step data object manager, the metadata object DataObject bound to the analysis step in the activated state participates in the structural finite element analysis calculation, and the data bound to the analysis step in the deactivated state does not participate in the structural finite element analysis calculation.

[0035] Furthermore, the step 3 is specifically that the data object model interface encapsulation should include the analysis step status acquisition interface encapsulation, the status of the data object DataObject in the analysis step is obtained through the status acquisition interface getStatus; the interface receives the stepID of the analysis step as a parameter and returns the status Status; the logic of determining the status of the data object DataObject in the analysis step. The status Status specifically includes None, Created, Modified, Propagated, Deactivated, Nolongeractive

[0036] Further, the system uses the analysis step association data structure design method applied to structural finite element software development as claimed in any one of claims 1 to 7, and the system comprises:

[0037] Finite element model abstraction module: Combined with the business background of structural finite element calculation and analysis, it abstracts the analysis step-related data from the data level and abstracts the finite element model into data objects DataObject and analysis steps;

[0038] Data object model building module: Based on the finite element model abstract model, the data object DataObject is managed. Data abstraction and data structure design are performed on the data object DataObject to build a data object model. The data object model should include a unique identifier of the analysis step, an analysis step status identifier, and an analysis step data manager.

[0039] Analysis step associated data structure design unit: Based on the data object model established by the data object model establishment module, according to the use requirements of the data object DataObject in the structural finite element analysis calculation, and the user interaction logic at the UI level of the structural finite element analysis calculation software, the data object model interface encapsulation design is carried out. A computer device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the method described above is implemented.

[0040] A computer-readable storage medium stores a computer program, and the computer program implements the above method when executed by a processor.

[0041] The beneficial effects of the present invention are:

[0042] The present invention realizes the management of the state and data of the data object in the analysis step through the abstraction of data and the encapsulation of algorithms.

[0043] The present invention not only realizes lightweight association management of analysis steps and data structures, but also reduces the development workload and difficulty of structural finite element analysis software development engineers.

[0044] In the method of the present invention, the finite element model data structure is separated from the software business layer during the finite element model data structure design process, which greatly improves the scalability and maintainability of the structural finite element analysis software.

[0045] The present invention reduces the correlation between data structure design and the professional business level of structural finite element calculation and analysis, and implements it from the perspective of computer IT technology, thereby alleviating the professional familiarity requirements of structural finite element analysis for computer software development engineers and greatly lowering the threshold for computer software development projects. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1 It is a structural schematic diagram of the present invention.

[0047] Figure 2 It is a schematic diagram of the data structure design of the data object model of the present invention.

[0048] Figure 3 It is a schematic diagram of the analysis step state acquisition interface encapsulation design method of the present invention.

[0049] Figure 4 It is a schematic diagram of the analysis step data acquisition interface encapsulation design method of the present invention.

[0050] Figure 5 It is a schematic diagram of the analysis step data setting interface encapsulation design method of the present invention.

[0051] Figure 6 It is a schematic diagram of the analysis step change interface packaging design method of the present invention.

[0052] Figure 7 It is a schematic diagram of a deactivation interface encapsulation design method of the present invention.

[0053] Figure 8 It is a schematic diagram of the step-by-step reactivation interface package design method of the present invention.

[0054] Fig. 9 It is a schematic diagram of the data object extension design method of the present invention.

[0055] Fig.10 It is a schematic diagram of the states of Step-1, Step-2 and Step-3 under the default condition of Load-1 of the present invention.

[0056] Fig.11 It is a schematic diagram of the states of Step-1, Step-2 and Step-3 when the effect of Load-1 in Step-2 is modified in the present invention.

[0057] Fig.12It is a schematic diagram of the states of Step-1, Step-2 and Step-3 when the effect of Load-1 in Step-2 is canceled in the present invention.

[0058] Fig.13 It is a schematic diagram of the states of Step-1, Step-2 and Step-3 when the analysis step where Load-1 of the present invention creates is changed. DETAILED DESCRIPTION

[0059] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0060] It should be understood that when used in this specification and the appended claims, the term "comprising" indicates the presence of described features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof.

[0061] It should also be understood that the terms used in this application specification are only for the purpose of describing specific embodiments and are not intended to limit the application. As used in this application specification and the appended claims, the singular forms "a", "an" and "the" are intended to include plural forms unless the context clearly indicates otherwise.

[0062] The following is attached to this application specification Figure 1-9 , the technical solutions in the embodiments of the present application are clearly and completely described. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present application.

[0063] In the following description, many specific details are set forth to facilitate a full understanding of the present application, but the present application may also be implemented in other ways different from those described herein, and those skilled in the art may make similar generalizations without violating the connotation of the present application. Therefore, the present application is not limited to the specific embodiments disclosed below.

[0064] Implementation Method 1

[0065] This embodiment provides a method for designing an analysis step-related data structure for use in structural finite element software development. Figure 1As shown, the method comprises the following steps:

[0066] Step 1: Based on the business background of structural finite element calculation and analysis, the analysis step-related data is abstracted from the data level, and the finite element model is abstracted into data objects and analysis steps; the data object in the finite element model is defined as DataObject, and is managed by the data object manager in the data model, where the data object manager is defined as DataObjectManager; the analysis step in the finite element model is defined as Step, with the id of the analysis step as the unique identifier, and is managed by the analysis step manager, where the analysis step manager is defined as StepManager;

[0067] Step 2: Based on the data object management in step 1, data abstraction and data structure design are required to form a data object model. In order to realize the management of metadata and data status by the data object model, the data object model should include the unique identifier of the analysis step, the status identifier of the analysis step, and the analysis step data manager, such as Figure 2 As shown;

[0068] Step 3: Based on the data object model in step 2, according to the requirements of structural finite element analysis and calculation for data objects, and the user interaction logic at the UI level of structural finite element analysis and calculation software, carry out data object model interface encapsulation design;

[0069] Step 4: Based on the design of the data object DataObject in steps 2 and 3, when implementing specific interaction, load, boundary and other analysis step-associated data types, first derive the specific data XData of the data object DataObject based on Data; then derive the data object DataObjectXDataObject based on DataObject.

[0070] Furthermore, the data objects in step 1 include finite element mesh model data objects, material property data objects, interaction data objects, boundary condition data objects and load data objects.

[0071] Furthermore, the unique identifier of the analysis step is specifically generated when the analysis step is created, will not be changed during the entire life cycle of the analysis step, and also serves as a unique identification code in the structural finite element calculation process. The unique identifier of the analysis step corresponds to the analysis step one by one. For the convenience of describing the method of the present invention, it is assumed in the present invention that three calculation analysis steps are created, and analysis step 1, analysis step 2, and analysis step 3 are used as the unique identifiers of the three analysis steps.

[0072] The analysis step life cycle refers to the entire process from the creation of the analysis step to the deletion of the analysis step. During the life of the analysis step, its unique identifier will not be changed. The analysis step life cycle includes data that can be modified, interactions, boundary conditions, loads, etc.

[0073] The unique identifier of the analysis step in step 2 cannot be modified, but the status of the analysis step can be modified. The created analysis step can include two states: activated and deactivated. When the analysis step is in the activated state, it participates in the calculation during the structural finite element analysis calculation process, while the deactivated state does not participate in the calculation during the structural finite element analysis calculation process.

[0074] Furthermore, the analysis step data manager in step 2 uniformly manages all analysis step loading data, wherein each analysis step can load different data, such as analysis step 1 loads mesh, material properties, boundary conditions; analysis step 2 loads mesh, material properties, boundary conditions, load data; and analysis step 3 loads mesh, material properties, boundary conditions, loads, and interaction data.

[0075] Furthermore, the management object of the analysis step data manager in step 2 is the data in each analysis step. When the data object is created, only the data corresponding to the unique identifier of the analysis step is recorded; the subsequent analysis step data is recorded in the data manager only when the data of the analysis step is modified, otherwise it is not recorded.

[0076] Furthermore, in step 2, the analysis step data manager establishes a data mapping relationship between the analysis step unique identifier and the metadata in the analysis step data object manager, establishes a binding relationship between the analysis step unique identifier and the data object, and completes the analysis step data model to participate in the structural finite element analysis calculation;

[0077] By establishing a data status mapping relationship between the analysis step status identifier and the metadata in the analysis step data object manager, the metadata objects bound to the analysis step in the activated state participate in the calculation in the structural finite element analysis calculation, and the data bound to the analysis step in the deactivated state does not participate in the calculation in the structural finite element analysis calculation.

[0078] Specifically, the analysis step-associated data structure design method for structural finite element software development described in step 2 has the following advantages: first, this method not only realizes lightweight association management between analysis steps and data structures, but also effectively reduces the workload and development difficulty of structural finite element analysis software development engineers; second, this method realizes the separation of data structure and software business layer in the finite element model data structure design process, which significantly improves the scalability and maintainability of structural finite element analysis software; third, the finite element model data structure design strategy proposed by this method reduces the association between data structure design and the professional business level of structural finite element calculation and analysis. From the perspective of computer information technology, it reduces the professional familiarity requirements for computer software development engineers in the field of structural finite element analysis, thereby greatly reducing the threshold of computer software development projects.

[0079] like Figure 3-Figure 9 As shown, further, the step 3 is specifically that the data object model interface encapsulation should include the analysis step status acquisition interface encapsulation, the status of the data object in the analysis step is obtained through the status acquisition interface getStatus; the interface receives the stepID of the analysis step (i.e., the status of the data object in which analysis step is to be obtained) as a parameter, and returns the status Status; the logic of determining the status of the data object in the analysis step. The status Status specifically includes None, Created, Modified, Propagated, Deactivated, and Nolongeractive.

[0080] Furthermore, the data object model interface encapsulation in step 3 should also include an analysis step data acquisition interface encapsulation, specifically the data of the data object model in the analysis step, which is acquired through the data acquisition interface getData. The interface receives the stepID of the analysis step (i.e., the data of the data object in which analysis step is to be acquired) as a parameter and returns the data Data.

[0081] Furthermore, the data object model interface encapsulation in step 3 should include an analysis step data setting interface encapsulation, specifically setting the data of the data object in a certain analysis step, which is implemented through the data interface setData. This interface is used when creating a data object in the data object model and modifying data of the data object. The interface receives the analysis step StepID and data Data to be set as parameters. The set data is uniformly stored and managed in the data manager in the data object model described in step 2.

[0082] Furthermore, the data object model interface encapsulation in step 3 should also include an analysis step change interface encapsulation, specifically, when the analysis step where the data object is created needs to be changed, the creation analysis step change interface setCreatedStepID is used to implement it. This interface receives the analysis step StepID as a parameter.

[0083] Furthermore, the data object model interface encapsulation in step 3 should also include a deactivation interface encapsulation, which is implemented by calling the deactivation analysis step interface setDeactivatedStepID when the data object is deactivated in a certain analysis step. The interface receives the deactivation analysis step StepID as a parameter

[0084] Furthermore, the data object model interface encapsulation in step 3 should also include analysis step reactivation interface encapsulation, which is specifically achieved by calling the setReactive interface when reactivating the data object in the deactivated analysis step.

[0085] Specifically, step 3 is based on the data structure design proposed in step 2. From the perspective of business level and user UI operation level, the data structure is further encapsulated to simplify the code complexity, thereby improving development efficiency and reducing the difficulty of software code upgrade and maintenance.

[0086] Based on the characteristics of the analysis step-related data, such as a variety of data types, a large amount of data, data state migration and dynamic data changes, the present invention analyzes the association between data objects and analysis steps, carries out the design of data object model data structure and interface encapsulation, and realizes the encapsulation of data object status and data management.

[0087] From the perspective of software development, this method establishes a mapping relationship between analysis steps and data objects to achieve the association between analysis steps and data, and realizes lightweight management of finite element model data, reducing the development workload and difficulty of software development engineers.

[0088] There are only a limited number of teams or individuals engaged in finite element software development in China. In recent years, the country's emphasis on industrial software has triggered investment enthusiasm in this field, which has led to a rapid increase in the number of participants. In the existing field of structural finite element model data structure design, few people have mentioned the status of analysis step-related data in the analysis step and data management issues.

[0089] The common idea or method is to directly store the state and data of each analysis step in the data object and open the read and write interface. The specific state and data are left to the user (the user of the data interface) to handle. For example:

[0090] 1. In the specific business of "Modify the value of Load-1 in Step-2", the user will complete it through the following steps:

[0091] 1) Set the load data in Step-2;

[0092] 2) Set the status in Step-2 to "Modified";

[0093] 3) Set the load status in Step-3 and subsequent analysis steps to "Propagated";

[0094] 4) Set the load data in Step-3 and subsequent analysis steps to be consistent with the data in Step-2.

[0095] 2. In the specific business of "Deactivate Load-1 in Step-2", the user needs to do the following:

[0096] 1) Set the load status in Step-2 to "Deactivated";

[0097] 2) Set the status of the load in Step-3 and subsequent analysis steps to "No longer active";

[0098] 3) Clear the data in Step-2 and its subsequent analysis steps.

[0099] 3. In the specific business of "Change the analysis step where Load-1 is created from Step-1 to Step-2", the user needs to do the following:

[0100] 1) Set the creation analysis step of Load-1 to Step-2;

[0101] 2) Set the status of the load in Step-1 to "None";

[0102] 3) Set the status of the load in Step-2 to "Created";

[0103] 4) Clean up the data in the analysis step before Step-2;

[0104] 5) Set the data in Step-2 and subsequent analysis steps to be consistent with the data in Step-2.

[0105] 4. When the number of analysis steps changes due to "create or delete analysis steps", the user needs to create or delete analysis step data and status for each data object.

[0106] From the perspective of the user of the structural finite element analysis calculation software, the present invention designs the data structure and develops the business logic according to this method to be more concise, and simplifies the operation of the user of the structural finite element analysis calculation software. The simplified operation is specifically as follows:

[0107] 1. In the specific business of "Modify the value of Load-1 in Step-2", the user will complete it through the following steps:

[0108] 1) Set the load value in Step-2.

[0109] 2. In the specific business of "Deactivate Load-1 in Step-2", the user needs to do the following:

[0110] 1) Deactivate Load-1 in Step-2.

[0111] 3. In the specific business of "Change the analysis step where Load-1 is created from Step-1 to Step-2", the user needs to do the following:

[0112] 1) Set the creation analysis step of Load-1 to Step-2.

[0113] 4. When the number of analysis steps changes, such as "New or deleted analysis steps", etc., no operation is required.

[0114] The adjustments of other states and data are all implemented in the interface encapsulation process in step 3. Based on this design, all analysis step-related data classes can be derived from this data structure, thereby achieving the reuse of state and data management algorithms, maintaining the scalability of data types while reducing the development burden.

[0115] The present invention not only realizes lightweight association management between analysis steps and data structures, but also reduces the development workload and difficulty of structural finite element analysis software development engineers; secondly, in the method, the finite element model data structure design process separates the finite element model data structure from the software business layer, which greatly improves the scalability and maintainability of the structural finite element analysis software; thirdly, the finite element model data structure design method proposed in the method reduces the association between data structure design and the professional business level of structural finite element calculation and analysis, and is implemented from the perspective of computer IT technology, which reduces the requirements for computer software development engineers to be familiar with the structural finite element analysis profession, and greatly reduces the threshold for computer software development projects.

[0116] Implementation Method 2

[0117] This embodiment provides an analysis step associated data structure design system applied to structural finite element software development, the system uses the analysis step associated data structure design method applied to structural finite element software development as described in embodiment 1, the system includes:

[0118] Finite element model abstraction module: Combined with the business background of structural finite element calculation and analysis, the analysis step-related data is abstracted from the data level, and the finite element model is abstracted into data objects and analysis steps; the data object in the finite element model is defined as DataObject, and is managed by the data object manager in the data model, where the data object manager is defined as DataObjectManager. The analysis step in the finite element model is defined as Step, with the id of the analysis step as the unique identifier, and is managed by the analysis step manager, where the analysis step manager is defined as StepManager;

[0119] Data object model building module: The management of data objects based on the finite element model abstraction model requires data abstraction and data structure design of the data objects to establish a data object model. In order to realize the management of metadata and data status by the data object model, the data object model should include the unique identification of the analysis step, the status identification of the analysis step, and the analysis step data manager;

[0120] Analysis step associated data structure design unit: Based on the data object model established by the data object model establishment module, carry out data object model interface encapsulation design according to the data object usage requirements of the structural finite element analysis calculation and the user interaction logic at the UI level of the structural finite element analysis calculation software.

[0121] Implementation Method 3

[0122] An embodiment of the present invention provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the memory is used to store software programs and modules, and the processor executes various functional applications and data processing by running the software programs and modules stored in the memory. The memory and the processor are connected via a bus. Specifically, the processor implements any step in the first embodiment above by running the computer program stored in the memory.

[0123] It should be understood that in the embodiments of the present invention, the processor referred to may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0124] The memory may include a read-only memory, a flash memory, and a random access memory, and provides instructions and data to the processor. A part or all of the memory may also include a nonvolatile random access memory.

[0125] It can be seen from the above that the electronic device provided by the embodiment of the present invention can implement the analysis step associated data structure design method as described in the first embodiment by running a computer program, which not only realizes the lightweight association management of the analysis step and the data structure, but also reduces the development workload and difficulty of the structural finite element analysis software development engineers; secondly, in the method, the finite element model data structure design process separates the finite element model data structure from the software business layer, which greatly improves the scalability and maintainability of the structural finite element analysis software; thirdly, the finite element model data structure design method proposed in the method reduces the association between the data structure design and the professional business level of the structural finite element calculation and analysis, and is implemented from the perspective of computer IT technology, which reduces the professional familiarity requirements for computer software development engineers in structural finite element analysis, and greatly reduces the threshold for computer software development projects.

[0126] It should be understood that if the above-mentioned integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the present invention implements all or part of the processes in the above-mentioned implementation method, and can also be completed by instructing the relevant hardware through a computer program. The above-mentioned computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method implementations when executed by the processor. Among them, the above-mentioned computer program includes computer program code, and the above-mentioned computer program code can be in source code form, object code form, executable file or some intermediate form. The above-mentioned computer-readable medium may include: any entity or device capable of carrying the above-mentioned computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the above-mentioned computer-readable storage medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction.

[0127] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest range consistent with the principles and novel features disclosed herein.

[0128] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In actual applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the above-mentioned device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the implementation method can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of the present invention. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method implementation method, which will not be repeated here.

[0129] It should be noted that the methods and detailed examples provided in the above embodiments can be combined with the devices and equipment provided in the embodiments, and references can be made to each other, and no further details will be given.

[0130] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0131] In the embodiments provided by the present invention, it should be understood that the disclosed device / terminal equipment and method can be implemented in other ways. For example, the device / equipment implementation described above is only illustrative, for example, the division of the above modules or units is only a logical function division, and in actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.

[0132] The above-mentioned embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit them. Although the present invention has been described in detail with reference to the above-mentioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above-mentioned embodiments, or replace some of the technical features therein by equivalents. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present invention, and should all be included in the protection scope of the present invention.

Claims

1. A method for designing analysis step-related data structures for structural finite element software development, characterized in that: The method comprises the following steps: Step 1: Based on the business background of structural finite element calculation and analysis, the data associated with the analysis step is abstracted from the data level, and the finite element model is abstracted into data objects DataObject and analysis steps; Step 2: Based on the data object DataObject of step 1, data abstraction and data structure design need to be performed on the data object DataObject to form a data object model. The data object model should include a unique identifier of the analysis step, an analysis step status identifier, and an analysis step data manager; Step 3: Based on the data object model in step 2, according to the use requirements of the data object DataObject in the structural finite element analysis calculation, and the user interaction logic at the UI level of the structural finite element analysis calculation software, carry out the data object model interface encapsulation design; Step 4: Based on the design of the data object DataObject in step 2 and step 3, first derive the specific data XData of the data object DataObject based on Data; then derive the data object DataObjectXDataObject based on DataObject.

2. The method for designing an analysis step association data structure according to claim 1, characterized in that: The data object DataObject in step 1 includes a finite element mesh model data object DataObject, a material property data object, an interaction data object, a boundary condition data object and a load data object.

3. The method for designing an analysis step association data structure according to claim 1, characterized in that: The unique identifier of the analysis step in step 2 cannot be modified, but the status of the analysis step can be modified. The created analysis step includes two states: activated and deactivated. When the analysis step is in the activated state, it participates in the calculation during the structural finite element analysis calculation process, while the deactivated state does not participate in the calculation during the structural finite element analysis calculation process.

4. The method for designing an analysis step association data structure according to claim 1, characterized in that: The analysis step data manager in step 2 manages all analysis step loading data in a unified manner, wherein each analysis step can load different data.

5. The method for designing an analysis step association data structure according to claim 4, characterized in that: The management object of the analysis step data manager in step 2 is the data in each analysis step. When the data object DataObject is created, only the data corresponding to the unique identifier of the analysis step is recorded; the subsequent analysis step data is recorded in the data manager only when the data of the analysis step is modified, otherwise it is not recorded.

6. The method for designing an analysis step association data structure according to claim 5, characterized in that: In step 2, the analysis step data manager establishes a data mapping relationship between the analysis step unique identifier and the metadata in the analysis step data object manager, establishes a binding relationship between the analysis step unique identifier and the data object DataObject, and completes the analysis step data model to participate in the structural finite element analysis calculation; By establishing a data status mapping relationship between the analysis step status identifier and the metadata in the analysis step data object manager, the metadata object DataObject bound to the analysis step in the activated state participates in the structural finite element analysis calculation, and the data bound to the analysis step in the deactivated state does not participate in the structural finite element analysis calculation.

7. The method for designing an analysis step association data structure according to claim 2, characterized in that: Specifically, the step 3 is that the data object model interface encapsulation should include the analysis step status acquisition interface encapsulation, and the status of the data object DataObject in the analysis step is obtained through the status acquisition interface getStatus; the interface receives the stepID of the analysis step as a parameter and returns the status Status; and determines the logic of the status of the data object DataObject in the analysis step.

8. An analysis step-associated data structure design system for structural finite element software development, characterized in that: The system uses the analysis step association data structure design method applied to structural finite element software development as claimed in any one of claims 1 to 7, and the system comprises: Finite element model abstraction module: Combined with the business background of structural finite element calculation and analysis, it abstracts the analysis step-related data from the data level and abstracts the finite element model into data objects DataObject and analysis steps; Data object model building module: Based on the finite element model abstract model, the data object DataObject is managed. Data abstraction and data structure design are performed on the data object DataObject to build a data object model. The data object model should include a unique identifier of the analysis step, an analysis step status identifier, and an analysis step data manager. Analysis step associated data structure design unit: Based on the data object model established by the data object model establishment module, carry out data object model interface encapsulation design according to the usage requirements of the data object DataObject in the structural finite element analysis calculation, and the user's interaction logic at the UI level of the structural finite element analysis calculation software.

9. A computer device, characterized in that: The method comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images