Methods, products, media and equipment to connect different software data flows in simulation process

Abstract

The present application discloses a method, product, medium and device for connecting different software data streams in a simulation process, and relates to the field of communication technology. The method comprises: obtaining private parameters of each node software in the simulation process; obtaining public parameters of all node software in the simulation process; determining the mapping relationship between private parameters and public parameters according to the logical relationship of the simulation process; and transmitting data based on private parameters, public parameters and the mapping relationship between private parameters and public parameters. The method, product, medium and device for connecting different software data streams in the simulation process can effectively improve the transmission efficiency of data between different software and reduce costs.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method, product, medium and device for connecting different software data flows in a simulation process. Background Art

[0002] Since traditional manual simulation has the disadvantages of high cost and low simulation efficiency, software development usually encapsulates traditional manual simulation to form a vertical professional industrial APP, in which the simulation process is divided into multiple stages, and different software is used in each stage. If an industrial APP is to be formed, the data between different software in each stage must be connected to form data flow and logic flow. Since the software used in the simulation process is developed by different manufacturers, opening up the data interface between different software is the key issue of the simulation process.

[0003] The traditional simulation process is to directly open up the data interfaces of different software. However, since different software complies with different protocols, if a new industrial software needs to be added to the simulation process, the data interfaces of all software need to be modified to be compatible with the new industrial software. This operation violates the open-closed principle of software development. In addition, each time new software is added, the operation of modifying the original system will bring great risks and workload, increase costs, and reduce data transmission efficiency. Summary of the invention

[0004] The purpose of this application is to provide a method, product, medium and equipment for connecting different software data flows in a simulation process, which can effectively improve the data transmission efficiency between different software and reduce costs.

[0005] To achieve the above-mentioned purpose, the present application provides the following solutions: On the first aspect, the present application provides a method for connecting different software data flows in a simulation process, including: obtaining private parameters of each node software in the simulation process; the private parameters are parameters used by each node software itself; obtaining public parameters of all node software in the simulation process; the public parameters are parameters transferred between different node software along with the simulation process; determining the mapping relationship between private parameters and public parameters according to the logical relationship of the simulation process; the mapping relationship includes an uplink parameter mapping relationship and a downlink parameter mapping relationship; and transmitting data based on private parameters, public parameters, and the mapping relationship between private parameters and public parameters.

[0006] Optionally, obtaining the private parameters of each node software in the simulation process specifically includes: obtaining the private parameters of each node software in the simulation process by parsing the XML file or model file of each node software in the simulation process; storing the private parameters of each node software in a private parameter table of each node software.

[0007] Optionally, storing the private parameters of each node software in a private parameter table of each node software further includes: storing, calling, modifying, querying and deleting the private parameters of each node software in the private parameter table of each node software.

[0008] Optionally, the obtaining of the public parameters of all node software in the simulation process specifically includes: obtaining the public parameters of all node software in the simulation process according to the logical relationship of the simulation process; and storing the public parameters of all node software in a public parameter pool of the simulation process.

[0009] Optionally, storing the public parameters of all node software in a public parameter pool of the simulation process further includes: storing, querying, modifying, deleting, calling and assigning values ​​to the public parameters in the public parameter pool.

[0010] Optionally, the mapping relationship between private parameters and public parameters is determined according to the logical relationship of the simulation process, specifically including: determining the mapping relationship between private parameters and public parameters of the previous node software of the two adjacent node software as the uplink parameter mapping relationship according to the logical relationship between the two adjacent node software in the simulation process; determining the mapping relationship between public parameters and private parameters of the latter node software of the two adjacent node software as the downlink parameter mapping relationship according to the logical relationship between the two adjacent node software in the simulation process.

[0011] Optionally, the data transmission based on private parameters, public parameters and the mapping relationship between private parameters and public parameters specifically includes: obtaining the latest private parameters of the previous node software of two adjacent node software after the execution is completed; based on the latest private parameters, updating the public parameters according to the uplink parameter mapping relationship to obtain updated public parameters; based on the updated public parameters, updating the private parameters of the latter node software of two adjacent node software according to the downlink parameter mapping relationship to transmit data.

[0012] In a second aspect, the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the method of connecting different software data flows of a simulation process.

[0013] In a third aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method of connecting different software data flows of a simulation process.

[0014] In a fourth aspect, the present application provides a computer device, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method of connecting different software data flows in a simulation process.

[0015] According to the specific embodiments provided by the present application, the present application has the following technical effects: the present application provides a method, product, medium and equipment for connecting different software data flows in a simulation process. By ignoring the data interfaces between different software, a public data pool concept of a public parameter pool is constructed, and all data flows that need to be transmitted in the simulation process are managed through the public parameter pool. When adding new industrial software, it is only necessary to make the new industrial software compatible with the public parameter pool without changing the existing software interface, thereby following the open and closed principle, saving workload, reducing costs, improving software scalability, and reducing the risks brought by expansion. It can simply and quickly solve the problem of data transmission between different software, effectively improve the data transmission efficiency between different software, and thus build the simulation process more quickly. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0017] Figure 1 A flowchart of the method provided in this application for connecting different software data flows in a simulation process.

[0018] Figure 2 A schematic diagram of the principles of the method provided in this application for connecting different software data flows in the simulation process.

[0019] Figure 3 Schematic diagram of the aircraft shape structure fluid simulation process provided for this application. DETAILED DESCRIPTION

[0020] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. 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 this application.

[0021] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, the present application is further described in detail below in conjunction with the accompanying drawings and specific implementation methods.

[0022] In the process of complex product development and design, industrial simulation software can improve R&D efficiency. The simulation process encapsulates the engineering business in a professional field to form an industrial APP in a vertical field. The simulation process of different businesses is different, and the node software in the simulation process is also different. Figure 3 As shown in the figure, the node software in the fluid simulation process of an aircraft shape structure mainly includes UG software, ICEM software, Fluent software, CFD-POST software and Word software, a total of five node software, and the node software can be referred to as nodes. Among them, UG software, ICEM software, Fluent software, CFD-POST software and Word software are all software used in the fluid simulation process of the aircraft shape structure. UG node software is used for three-dimensional modeling, ICEM node software is used for meshing, Fluent node software is used for fluid calculation, CFD-POST node software is used for post-processing, and Word node software is used to generate reports.

[0023] Specifically, in Figure 3 During the simulation process, the UG node is responsible for 3D modeling. According to the logical order of the simulation process, the model files and related data created by the UG node are passed to the ICEM node for use. The ICEM node is responsible for meshing, and so on. According to the logical order, the execution result data of the previous node is passed to the next node to guide the completion of the simulation process.

[0024] exist Figure 3 In the simulation process, the UG node performs three-dimensional modeling, and then passes the obtained three-dimensional model and parameter data to the ICEM node for meshing. This process includes two parts: logic flow and parameter flow. The subsequent nodes are processed in the same way. There are two ways to transfer the data to be transferred in the node during this process. One is direct transmission, and the other is a transmission method using the method proposed in this application to connect different software data flows in the simulation process. The specific transmission method of the method proposed in this application to connect different software data flows in the simulation process is as follows.

[0025] like Figure 1 and Figure 2 As shown, the present application discloses a method for connecting different software data flows in a simulation process, including:

[0026] Step 1: Get the private parameters of each node software in the simulation process.

[0027] The private parameters obtained by the present application refer to the parameters used by each node software itself, which are not common to other node software. As a specific embodiment, the present application obtains the private parameters of each node software in the simulation process by parsing the XML file or model file of each node software in the simulation process and stores the private parameters of each node software in the private parameter table of each node software. In addition, the private parameters in the private parameter table of each node software can also be stored, called, modified, queried, and deleted.

[0028] Specifically, the parameters in the corresponding data file of the software of the previous node between two adjacent nodes in the simulation process are extracted, which are private parameters by default. Private parameters are managed in the corresponding nodes, including storage, calling, modification, query and deletion of private parameter data. For example, Figure 3 In the simulation process, the private parameters of the UG node are extracted and managed: the model file of the UG node or the known parameters in advance during parametric modeling are parsed to obtain the private parameters of the UG node, and a UG private parameter table is created in the UG node for management. Take the three-dimensional model of the fuselage and wing of an aircraft as an example: the main parameters extracted include the three-dimensional model file, wingspan, span ratio, airfoil, chord length, sweep angle, span-sweep angle, and wing area, etc., which are saved in the UG private parameter table in the database of the simulation process as the private parameters of the UG node. The private parameters of the UG node can be modified to change the three-dimensional model.

[0029] Specifically, the parameters in the corresponding data file of the software of the next node between two adjacent nodes in the simulation process are extracted, which are private parameters by default and are managed in the corresponding nodes. Figure 3 In the simulation process, the next node after the UG node is the ICEM node. By parsing the XML file of the ICEM node, the designer manually selects the data in the XML file, creates parameter data of the data in the ICEM node, and saves it to the ICEM private parameter table in the database of the simulation process. As the private parameters of the ICEM node, the private parameters of the ICEM node can be modified to change the grid.

[0030] Step 2: Get the public parameters of all node software in the simulation process.

[0031] The public parameters obtained in this application are parameters that are passed between different node software along with the simulation process. According to the logical relationship of the simulation process, the public parameters of all node software in the simulation process are obtained and the public parameters of all node software are stored in the public parameter pool of the simulation process. In addition, the public parameters can also be stored, queried, modified, deleted, called, and assigned in the public parameter pool.

[0032] When the simulation process is running, if the parameters of the previous node between two adjacent nodes need to be passed to the next node, the parameters are set as public parameters and a public parameter pool is established. Public parameters are managed in the public parameter pool of the simulation process, including storage, query, modification, deletion, call, and assignment. Specifically, each simulation process will create a public parameter pool, which corresponds to a separate table in the database.

[0033] Step 3: Determine the mapping relationship between private parameters and public parameters based on the logical relationship of the simulation process.

[0034] According to the logical relationship between the two adjacent node software in the simulation process, that is, Figure 2 The logic flow in determines the mapping relationship between the private parameters and public parameters of the previous node software in two adjacent node software as the uplink parameter mapping relationship. As a specific embodiment, if the private parameters of the UG node need to be used as public parameters, the relationship between the private parameters and public parameters of the UG node is connected through the computer operation interface, and the mapping relationship between the private parameters and public parameters of the UG node is established to form the mapping relationship of the uplink parameters.

[0035] According to the logical relationship between the two adjacent node software in the simulation process, the mapping relationship between the public parameters and the private parameters of the latter node software in the two adjacent node software is determined as the downlink parameter mapping relationship. Specifically, when the simulation process is running, the private parameters of the latter node between the two adjacent nodes need to be derived from the previous node. At this time, it is necessary to select from the public parameter pool of the simulation process to establish the mapping relationship of the downlink parameters. As a specific embodiment, if it is necessary to use the private parameters of the ICEM node as public parameters, the operation is performed through the computer operation interface to establish the mapping relationship between the private parameters and the public parameters of the ICEM node to form the mapping relationship of the downlink parameters.

[0036] Step 4: Data transmission is performed based on private parameters, public parameters, and the mapping relationship between private parameters and public parameters.

[0037] First, obtain the latest private parameters of the previous node software in the two adjacent node software after execution; based on the latest private parameters, update the public parameters according to the uplink parameter mapping relationship to obtain the updated public parameters. That is, during the simulation process, after the software of the previous node in the two adjacent node software is executed, according to the uplink parameter mapping relationship, update the latest private parameter value to the public parameter pool of the simulation process. Figure 3 During the simulation process, the UG node is executed. The execution result of the UG node changes. According to the upstream parameter mapping relationship, the public parameters in the public parameter pool are updated. Parametric modeling exists in the UG node. By setting parameters, a new 3D model is generated. Both the parameters and the model are transferred to the public parameter pool and indirectly to the next node.

[0038] Then, based on the updated public parameters, the private parameters of the software of the next node in the two adjacent nodes are updated according to the downlink parameter mapping relationship to perform data transmission. That is, during the execution of the simulation process, when the software of the next node of the two adjacent nodes is executed, the public parameter values ​​in the public parameter pool of the simulation process are updated to the private parameters of the next node according to the downlink parameter mapping relationship, thereby forming data transmission from the previous node to the next node software. Figure 3During the execution of the simulation process, the ICEM node is executed. The ICEM node reads the public parameters of the public parameter pool according to the downlink parameter mapping relationship to modify the private parameter value of the corresponding ICEM node.

[0039] During the execution of the simulation process, the public parameter pool of the simulation process serves as the management center of public parameters, and each node can upload parameters and download updated parameters.

[0040] At this point, by constructing a mapping relationship between private parameters of different nodes and a public parameter pool, private parameters and public parameters are automatically modified according to the execution logic of the simulation process, thereby overcoming the problem of data transmission between different software in the prior art.

[0041] In some embodiments, the present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the method of connecting different software data flows in a simulation process.

[0042] In some embodiments, the present application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method of connecting different software data flows of a simulation process.

[0043] In some embodiments, the present application also provides a computer device, including a processor, a memory, an input / output interface (I / O for short), a communication interface, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method of connecting different software data flows of a simulation process.

[0044] Wherein, the processor, memory and input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Wherein, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store pending transactions. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, the method of connecting different software data flows of the simulation process is implemented.

[0045] It should be noted that the object information (including but not limited to object device information, object personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the object or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards.

[0046] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0047] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0048] This article uses specific examples to illustrate the principles and implementation methods of this application. The description of the above embodiments is only used to help understand the method and core ideas of this application. At the same time, for those skilled in the art, according to the ideas of this application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as limiting this application.

Claims

1. A method for connecting different software data flows in a simulation process, characterized in that: include: Obtaining private parameters of each node software in the simulation process; the private parameters are parameters used by each node software itself; Get the public parameters of all node software in the simulation process; The public parameters are parameters that are transferred between different node software along with the simulation process; Determine the mapping relationship between private parameters and public parameters according to the logical relationship of the simulation process; The mapping relationship includes an uplink parameter mapping relationship and a downlink parameter mapping relationship, specifically including: According to the logical relationship between two adjacent node software in the simulation process, the mapping relationship between the private parameters and the public parameters of the previous node software in the two adjacent node software is determined as the uplink parameter mapping relationship; according to the logical relationship between the two adjacent node software in the simulation process, the mapping relationship between the public parameters and the private parameters of the latter node software in the two adjacent node software is determined as the downlink parameter mapping relationship; Data transmission is performed based on private parameters, public parameters, and the mapping relationship between private parameters and public parameters, including: Obtain the latest private parameters of the previous node software after the execution of two adjacent node softwares; Based on the latest private parameters, the public parameters are updated according to the uplink parameter mapping relationship to obtain updated public parameters; Based on the updated public parameters, the private parameters of the latter node software of two adjacent node software are updated according to the downlink parameter mapping relationship to perform data transmission.

2. The method for connecting different software data flows in a simulation process according to claim 1, characterized in that: The obtaining of private parameters of each node software in the simulation process specifically includes: Obtain the private parameters of each node software in the simulation process by parsing the XML file or model file of each node software in the simulation process; The private parameters of each node software are stored in the private parameter table of each node software.

3. The method for connecting different software data flows in a simulation process according to claim 2, characterized in that: The storing of the private parameters of each node software in the private parameter table of each node software also includes: The private parameters of each node software are stored, called, modified, queried and deleted in the private parameter table of each node software.

4. The method for connecting different software data flows in a simulation process according to claim 1, characterized in that: The obtaining of the public parameters of all node software in the simulation process specifically includes: Obtain the public parameters of all node software in the simulation process according to the logical relationship of the simulation process; The public parameters of all node software are stored in the public parameter pool of the simulation process.

5. The method for connecting different software data flows in a simulation process according to claim 4, characterized in that: The method of storing the public parameters of all node software in the public parameter pool of the simulation process also includes: The public parameters are stored, queried, modified, deleted, called and assigned in the public parameter pool.

6. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the method for connecting different software data flows in a simulation process as described in any one of claims 1 to 5 is implemented.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for connecting different software data flows in a simulation process as described in any one of claims 1 to 5 is implemented.

8. A computer device comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method for connecting different software data flows in a simulation process as described in any one of claims 1 to 5.

Images