A liquid rocket engine simulation data management method and system

Abstract

The application discloses a liquid rocket engine simulation data management method and system, and relates to the technical field of simulation data management, aiming to solve the problems of low simulation data management efficiency and increased learning cost and workload of simulation engineers. The method comprises the following steps: receiving label information sent by a high-performance computing platform and archiving information sent by a TeamCenter platform; establishing and updating simulation entries in a simulation management structure tree according to the label information, and determining simulation entries corresponding to the received archiving information as target simulation entries; associating the target simulation entries with simulation data according to the archiving information to generate association information; and managing the simulation data based on the association information. The liquid rocket engine simulation data management method provided by the application is used for improving simulation data management efficiency and reducing the learning cost and workload of simulation engineers.

Description

Technical Field

[0001] This invention relates to the field of simulation data management technology, and in particular to a method and system for managing simulation data of liquid rocket engines. Background Technology

[0002] The development of liquid rocket engines is a complex systems engineering project integrating design, simulation analysis, and testing. During the development phase, extensive simulation analysis is required to optimize local engine designs and identify test risks. The research objects involve multiple types of products, including the entire engine, semi-systems, generators, thrust chambers, turbopumps, and valves. The research fields encompass multiple disciplines such as systems, flow, combustion, heat transfer, fatigue, strength, and lifespan. Therefore, the raw data generated by simulation work, including simulation models and results, is diverse and massive. Current simulation data management typically requires users to upload relevant simulation files themselves. However, in actual simulation work, continuous product design improvements result in a large number of files during simulation iterations. Furthermore, the limited hardware performance and network bandwidth of the management system make uploading and downloading files inefficient in meeting the management needs of simulation data. Simultaneously, simulation engineers need to complete corresponding control procedures during daily management, increasing learning costs and workload, and affecting the overall management effectiveness. Summary of the Invention

[0003] The purpose of this invention is to provide a method and system for managing simulation data of liquid rocket engines, which can improve the efficiency of simulation data management and reduce the learning cost and workload of simulation engineers.

[0004] To achieve the above objectives, the present invention provides the following technical solution:

[0005] In a first aspect, the present invention provides a method for managing simulation data of a liquid rocket engine, comprising:

[0006] Receive tag information sent by the high-performance computing platform and archive information sent by the TeamCenter platform; the archive information includes simulation report ID, simulation model and example viewing link, and simulation lightweight model viewing link;

[0007] Based on the tag information, simulation entries are created and updated in the simulation management structure tree, and simulation entries that receive corresponding archive information are identified as target simulation entries.

[0008] The target simulation entry is associated with the simulation data based on the archived information to generate association information; the simulation data is then managed based on the association information.

[0009] Optionally, the step of establishing and updating simulation entries in the simulation management structure tree based on the tag information, and determining the simulation entries that receive the corresponding archive information as target simulation entries, includes:

[0010] Determine whether there is a simulation entry in the simulation management structure tree that corresponds to the same simulation task book ID as the tag information;

[0011] If it exists, update the corresponding simulation entry;

[0012] If it does not exist, a simulation entry is created in the simulation management structure tree based on the tag information, and the status of the simulation entry is marked as the first state;

[0013] The simulation entry that corresponds to the same simulation task ID as the archived information is identified as the target simulation entry, and the status of the target simulation entry is updated to the second status.

[0014] Optionally, the simulation data includes simulation reports stored in the TeamCenter platform, simulation models and examples stored in the high-performance computing platform, and lightweight simulation models stored in the lightweight module; the management of the simulation data based on the associated information includes:

[0015] Receive viewing requests sent by users;

[0016] When the request is for viewing a simulation report, the user will be redirected to the TeamCenter platform to view the simulation report.

[0017] When the viewing request is for viewing simulation models and examples, the system will redirect to the high-performance computing platform to view the simulation models and examples.

[0018] When the viewing request is a simulation lightweight model viewing request, the user will be redirected to the lightweight module to view the simulation lightweight model.

[0019] Optionally, the tag information includes model, component, discipline, and version number; the simulation management structure tree includes the simulation management structure tree corresponding to each model of liquid rocket engine. The simulation management structure tree for each model includes a first level, a second level, a third level, and a fourth level. The first level is divided according to the main component categories of the engine system, the second level is divided according to the component simulation category, the third level is the simulation entry, and the fourth level is the simulation report ID, simulation model and example viewing link, and simulation lightweight model viewing link under the simulation entry.

[0020] Secondly, the present invention provides a liquid rocket engine simulation data management system, which is applied to the liquid rocket engine simulation data management method, and the system includes at least: a basic layer and a capability layer;

[0021] The base layer is integrated into the TeamCenter platform as a plug-in and communicates with the high-performance computing platform; the base layer is used to receive tag information sent by the high-performance computing platform and archive information sent by the TeamCenter platform.

[0022] The capability layer includes a structure tree update module, which is used to establish and update simulation entries in the simulation management structure tree according to the tag information, and determine the simulation entries that receive corresponding archive information as target simulation entries; and associate the target simulation entries with simulation data according to the archive information to generate association information; and manage the simulation data based on the association information.

[0023] Optionally, the capability layer may also include a lightweight module;

[0024] The lightweight module is used to access the target folders corresponding to each simulation report established in the controlled area of ​​the high-performance computing platform, and to perform lightweight processing on the simulation models in the target folders that meet the conversion conditions, generating a lightweight simulation model and a link to view the lightweight simulation model, and then sending the link to view the lightweight simulation model to the corresponding simulation report.

[0025] Optionally, the liquid rocket engine simulation data management system also includes an application layer;

[0026] The application layer includes at least a virtual prototype library, a simulation project dashboard module, a simulation knowledge base, and a system management module. The virtual prototype library includes simulation management structure trees of various models. The simulation project dashboard module is used to display the overall planning and implementation status of simulation projects. The simulation knowledge base includes a standard specification library, a model and template library, a material library, and a knowledge and experience library.

[0027] Optionally, the liquid rocket engine simulation data management system further includes a platform layer and a presentation layer. The platform layer is used to provide retrieval services, architecture services, and version services. The presentation layer is the interaction entry point between the user and the liquid rocket engine simulation data management system. The presentation layer is used to display information corresponding to the user's viewing request based on the user's input viewing request.

[0028] Optionally, the liquid rocket engine simulation data management system further includes a system management module, which provides an administrator interface, including simulation management structure tree management, system logs, and file editing.

[0029] Optionally, the user permissions of the liquid rocket engine simulation data management system are controlled by the TeamCenter platform; the user permissions include access permissions and browsing permissions.

[0030] Compared with the prior art, the present invention provides a liquid rocket engine simulation data management method, which includes receiving tag information sent by a high-performance computing platform and archive information sent by the TeamCenter platform;

[0031] Simulation entries are created and updated within the simulation management structure tree based on tag information, and simulation entries receiving corresponding archived information are identified as target simulation entries. Target simulation entries are then associated with simulation data based on the archived information, generating association information. Simulation data is managed based on this association information. By forming simulation entries in a fixed format and associating them with simulation data through archived information—since the archived information includes simulation report IDs, simulation model and example viewing links, and lightweight simulation model viewing links—the original storage location and method of the simulation data remain unchanged. Therefore, only the structured storage and management of the simulation entries representing the simulation data is required to achieve simulation data storage and management, eliminating the need for large-scale migration and organization of simulation data, thus improving management efficiency. When users access the simulation management structure tree, they can simply jump to the corresponding platform to view the simulation data through the association information. Furthermore, simulation engineers only need to submit simulation jobs on the high-performance computing platform and write and archive simulation reports on the TeamCenter platform to automatically store and manage simulation data, greatly reducing the workload and learning costs for simulation staff.

[0032] Compared with the prior art, the beneficial effects of the liquid rocket engine simulation data management system provided by the present invention are the same as those of the liquid rocket engine simulation data management method, and will not be elaborated here. Attached Figure Description

[0033] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this invention, illustrate exemplary embodiments of the invention and are used to explain the invention, but do not constitute an undue limitation of the invention. In the drawings:

[0034] Figure 1 A schematic diagram of the structure of a liquid rocket engine simulation data management system provided by the present invention;

[0035] Figure 2 Example diagram of the simulation management structure tree provided by the present invention;

[0036] Figure 3 A flowchart of a liquid rocket engine simulation data management method provided by the present invention;

[0037] Figure 4 The operation flowchart of the liquid rocket engine simulation data management system provided by the present invention;

[0038] Figure 5 The archiving flowchart provided for this invention. Detailed Implementation

[0039] To facilitate a clear description of the technical solutions in the embodiments of the present invention, the terms "first" and "second" are used to distinguish identical or similar items with essentially the same function and effect. For example, the first threshold and the second threshold are merely used to distinguish different thresholds and do not limit their order. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that the terms "first" and "second" are not necessarily different.

[0040] It should be noted that in this invention, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in this invention should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0041] In this invention, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, a combination of a and b, a combination of a and c, a combination of b and c, or a, b, and c, where a, b, and c can be single or multiple.

[0042] Before introducing the embodiments of the present invention, the relevant terms involved in the embodiments of the present invention are first defined as follows:

[0043] TeamCenter, or TC for short, is a modern and highly adaptable PLM system software that connects people and processes across functions through digital threads to achieve innovation and improve productivity. It is the industry's first PLM solution to transform a single software application into a truly integrated solution built on SOA, spanning different professions, project phases, and plans. In engine development, simulation engineers typically use this platform to write simulation reports.

[0044] HPC platforms, or high-performance computing platforms, aggregate the computing power of multiple computers and storage devices to process large amounts of data at extremely high speeds. These tasks typically involve massive data inputs and outputs, requiring enormous computing power and high-speed data processing capabilities.

[0045] A Product Data Management (PDM) system is a software system used to manage product-related data and processes. It aims to optimize data management, collaboration, and process control throughout the product lifecycle. By centrally storing, organizing, and controlling product data, it supports enterprises in efficiently carrying out product design, development, manufacturing, and after-sales service activities.

[0046] Currently, PDM (Product Data Management) systems are commonly used to manage simulation data. However, because PDM systems are comprehensive management platforms for research and development documents, each engine model's development document directory contains various types of files, including research and development documents, design documents, 3D models, and simulation reports. This results in fragmented management of simulation data, a lack of means for data sharing and comprehensive utilization, weak traceability and low reusability of simulation models and results generated during simulation work, and an inability to centrally organize and display simulation results during the model development process. Furthermore, managing simulation data requires users to individually enter information for the simulation data to be archived, describing the simulation inputs, simulation objects, and simulation content. However, due to the continuous iteration of engine design during development, the workload of simulation tasks continues to increase, making it difficult for simulation engineers to devote too much energy and time to information entry, resulting in low platform management efficiency and poor practicality of document management. In addition, traditional simulation data management platforms require a redesign of existing data storage methods during construction, and may necessitate a complete data migration to ensure structured data management. This approach is only suitable for managing small-scale simulation data. When the simulation data is large and stored on different system platforms, the workload for data migration and structuring is enormous, making it difficult to quickly build and deploy the platform. It also conflicts with existing management systems. Secondly, file viewing requires appropriate access control to ensure that the scope of access is controllable. Therefore, the management platform also needs to develop an additional user management system to control the viewing permissions of each user, further increasing the complexity of platform development.

[0047] To address the aforementioned problems, this invention provides a method and system for managing simulation data of liquid rocket engines. By embedding the management process into the necessary stages of simulation work and result archiving, and through automatic input in the early stages and automatic sorting in the later stages, it reduces the additional workload and learning cost for simulation engineers in simulation data management. The following description is in conjunction with the accompanying drawings.

[0048] See Figure 1 The present invention provides a liquid rocket engine simulation data management system comprising:

[0049] The layers are: foundation layer, platform layer, capability layer, application layer, and presentation layer.

[0050] The basic layer is integrated into the TeamCenter platform as a plug-in and communicates with the high-performance computing platform. The basic layer receives tag information, simulation project names, simulation task IDs, and archive information sent by the high-performance computing platform, as well as archiving information sent by the TeamCenter platform. By integrating into the TeamCenter platform as a plug-in, this system allows the TeamCenter platform to manage user access and browsing permissions for the liquid rocket engine simulation data management system. The TeamCenter platform is the TeamCenter platform, and the HPC platform is the high-performance computing platform.

[0051] The platform layer provides the system's fundamental common capabilities, including search services, architecture services, and version services. The search service supports global search, fuzzy search, and combined search. The architecture service allows for the definition of a structure tree and simulation projects. The version service stores system version change records and manages versioning.

[0052] The capability layer is a foundational module supporting business capabilities. It enables rapid updates to the simulation management structure tree by receiving tag information from simulation projects. It centrally displays simulation results from multiple domains by associating simulation reports, simulation models and examples, and lightweight simulation models under the same simulation entry. It also enables web-based display of simulation CAE models through model compression and information extraction. Specifically, the capability layer includes a structure tree update module and a lightweight module. The structure update module creates and updates simulation entries within the simulation management structure tree based on tag information, and identifies simulation entries receiving corresponding archived information as target simulation entries. It then associates these target simulation entries with simulation data based on the archived information, generating association information. Simulation data includes simulation reports, lightweight simulation models, and simulation models and examples. The lightweight module is used to access the target folders corresponding to each simulation report established in the controlled area of ​​the high-performance computing platform. It performs lightweight processing on the simulation models that meet the conversion conditions in the target folder through model compression, information extraction and other means, generating a lightweight simulation model and a link to view the lightweight simulation model. Then, the link to view the lightweight simulation model is sent to the corresponding simulation report, thereby realizing the web-based display of the simulation CAE model.

[0053] The application layer includes a virtual prototype library, a simulation project dashboard module, a simulation knowledge base, and a system management module. The virtual prototype library comprises simulation management structure trees for various models, systematically displaying the work and results of each simulation project through hierarchical division and information classification: simulation reports, simulation models and examples, and lightweight simulation models. The simulation models and examples include 3D models. The simulation project dashboard module displays the overall planning and progress of simulation projects. Specifically, the genealogy view displays the construction of the simulation system and the progress of simulation projects; category viewing and quick query enable searching and tracing simulation projects; data statistics perform statistical processing on system data; status display shows the completion status of simulation projects; and version tracking allows for version tracing through version editing. The simulation knowledge base is used to build a knowledge-sharing platform. It contains specifications and related documents established in historical simulation work, including a standard specification library, a model and template library, a material library, and a knowledge and experience library. The system management module provides an administrator interface, which includes simulation management structure tree management, system logs, and file editing. Administrators can manually create, manage, and edit files within the model simulation management structure tree, ensuring continuous platform updates and maintenance. Specifically, administrators can submit simulation project planning tables in the backend. The data statistics unit of the simulation project dashboard updates the data in the simulation project planning table when simulation entries are created or updated in the simulation data structure tree. It then converts the updated data into lists or charts, displaying it through the status display unit. The status display unit can present simulation system lists as lists or charts as bar charts, pie charts, etc.

[0054] The simulation structure management tree includes simulation management structure trees corresponding to various models of liquid rocket engines. Each model's simulation management structure tree includes a first level, a second level, a third level, and a fourth level. The construction rules for the simulation management structure tree are as follows: the first level is divided according to the categories of the main components of the engine system; the second level is divided according to the simulation categories of components; the third level is the simulation entry; and the fourth level contains the simulation report ID, simulation model and example viewing links, and simulation lightweight model viewing links under each simulation entry. The first and second levels of the simulation management structure tree are established in advance, while the simulation entries at the third level are established based on tag information as the project progresses. The number of simulation entries is also determined based on the actual project progress. For example, as shown... Figure 2As shown, for the XX model engine, the first level includes five parts: thermal components, turbopump, valves, assembly structure, and system. The second level for thermal components, turbopump, valves, and assembly structure includes simulation subject category 1: flow heat transfer and combustion calculation and simulation subject category 2: structural strength and fatigue calculation. The second level for the system includes simulation subject category 3: system simulation calculation. The third level corresponding to the thermal components includes simulation item 1: thrust chamber heat transfer calculation, simulation item 2: thrust chamber thermal control simulation, ... simulation item n, etc. The third level corresponding to the flow heat transfer and combustion calculation of the turbopump includes simulation item 1: turbopump heat transfer... The third level of thermal simulation analysis, corresponding to structural strength fatigue calculation, includes simulation item 1: shell structure strength calculation; the third level of valve flow heat transfer and combustion calculation, corresponding to main valve flow field simulation, includes simulation item 1: shell fatigue assessment; the third level of assembly structure flow heat transfer and combustion calculation, corresponding to heat transfer temperature field calculation, includes simulation item 1: sway device strength calculation; the third level of system simulation calculation includes simulation item 1: system static characteristics simulation, and simulation item 2: system dynamic characteristics simulation. The fourth level for each simulation item includes the simulation report ID, links to view the simulation model and examples, and links to view the lightweight simulation model.

[0055] The presentation layer serves as the interaction entry point between the user and the liquid rocket engine simulation data management system. Based on the user's input viewing request, the presentation layer displays the information corresponding to the viewing request.

[0056] The basic layer of this system is embedded in the TeamCenter platform, so the TeamCenter platform can control user permissions without the need to develop a user permission management system, which reduces the workload and complexity of the overall platform development.

[0057] Based on the aforementioned liquid rocket engine simulation data management system, this invention also provides a liquid rocket engine simulation data management method, such as... Figure 3 As shown, the method includes the following steps:

[0058] Step 301: Receive tag information sent by the high-performance computing platform and archive information sent by the TeamCenter platform; the archive information includes simulation report ID, simulation model and example viewing link, and simulation lightweight model viewing link;

[0059] The tag information includes model number, component, academic discipline, and version number; the high-performance computing platform is a platform for simulation engineers to perform simulation calculations, and the TeamCenter platform is a platform for simulation engineers to write and archive simulation reports, such as... Figure 4As shown, in practical applications, simulation work mainly includes three stages: simulation initiation, simulation iteration, and simulation archiving. In the simulation initiation stage, after receiving the simulation project input, simulation model input, and simulation condition input from the model department, the simulation engineer creates the simulation model and calculation examples. When submitting the job on the HPC platform, the engineer fills in the name of the simulation project, the simulation task book ID, and selects the corresponding model, component, discipline, and version number, among other tag information. The HPC platform sends the tag information, simulation project name, and simulation task book ID to the liquid rocket engine simulation data management system. Based on this information, the liquid rocket engine simulation data management system finds the corresponding hierarchical position in the model's simulation management structure tree and creates a simulation entry, which is generally the simulation project name. After receiving a simulation job, the HPC platform performs simulation calculations, obtaining simulation result 1. The simulation engineer then determines whether the simulation project is complete. If not, it enters the simulation work iteration phase. Due to continuous product design improvements during R&D, the simulation input conditions and simulation model undergo continuous modification and iteration. At this point, it indicates the simulation project is incomplete. The simulation engineer returns to the previous stage and resubmits the HPC job, re-entering the simulation project name, simulation task ID, and selecting the corresponding model, component, discipline, and version number, among other tag information. The HPC platform resends the tag information, along with the corresponding simulation task ID and simulation project name, to the liquid rocket engine simulation data management system. Simultaneously, the HPC platform continues simulation calculations based on the submitted job, obtaining simulation result 2. The simulation engineer then determines whether the project is complete. If not, the HPC submission and simulation calculation process is repeated until the simulation project is complete. Finally, the simulation engineer archives the simulation work. Figure 5The simulation engineer first completes the simulation report on the TeamCenter platform. Then, in the HPC platform's job data area, they locate the simulation model and examples corresponding to the report and copy them to the HPC platform's controlled area. The controlled area automatically creates a target folder named after the simulation report ID based on the TC platform's simulation report ID, and stores the corresponding simulation model and examples in the target folder. The engineer then sends the link to the target folder (i.e., the link to the simulation model and examples) to the simulation report on the TC platform, thus completing the association between the simulation report and the simulation model and examples. Later, the engineer can quickly access the simulation model and examples by clicking the relevant links within the simulation report. After the association is complete, the engineer returns to the TC platform to open the simulation model. The lightweighting process involves the liquid rocket engine simulation data management system's lightweighting module traversing the simulation models in the target folder. All simulation models meeting the conversion criteria are lightweighted and converted, creating a web-based link to view the lightweight simulation model. This link is then sent to the corresponding simulation report, completing the association between the lightweight simulation model and the simulation report. The simulation engineer returns to the TC platform to initiate the simulation report archiving process, archiving the simulation report ID, simulation model and example link, and the lightweight simulation model viewing link to obtain archiving information. The archiving information includes the corresponding simulation task book ID. The TC platform then sends the archiving information to the liquid rocket engine simulation data management system.

[0060] Step 302: Establish and update simulation entries in the simulation management structure tree according to the tag information, and determine the simulation entries that receive the corresponding archive information as target simulation entries;

[0061] Specifically, step 302 is implemented based on the following steps:

[0062] Determine whether there is a simulation entry in the simulation management structure tree that corresponds to the same simulation task book ID as the tag information;

[0063] If it exists, update the corresponding simulation entry;

[0064] Specifically, the iteration count corresponding to the simulation entry is updated. The iteration count is the number of simulation calculations performed by the simulation project. In practical applications, for simulation entries corresponding to the same simulation task ID, the initial iteration count for the simulation entry is 1. When the same tag information corresponding to the same simulation task ID is received for the second time, the iteration count for the simulation entry is updated to 2, and so on. Further details are omitted.

[0065] If it does not exist, a simulation entry is created in the simulation management structure tree based on the tag information, and the status of the simulation entry is marked as the first status; the first status is in progress.

[0066] The simulation entry corresponding to the same simulation task ID as the archived information is identified as the target simulation entry, and the status of the target simulation entry is updated to the second status. The second status is "completed". The first and second statuses represent the completion status of the simulation project.

[0067] In practical applications, such as Figure 2 As shown, when the received tag information does not have a simulation entry, the tag information undergoes a subordinate analysis to determine its model structure tree, including the first level, the second level, and the third level. The simulation entry is then created and marked as "in progress." For example, if the submitted tag information corresponds to model A, the first level B1, and a simulation entry already exists at the third level, only the iteration count of the simulation entry is updated. If no simulation entry exists at the third level, a simulation entry is created. After creating or updating a simulation entry, the completion status of the corresponding simulation project is updated in the simulation project planning table submitted by the administrator. The simulation project planning table is displayed in list or chart form and can also be viewed through a quick search.

[0068] Step 303: Associate the target simulation entry with the simulation data according to the archived information to generate association information; manage the simulation data based on the association information.

[0069] The associated information refers to the information that allows users to jump to the original storage location of simulation reports, simulation models and examples, and lightweight simulation models. Simulation data includes simulation reports stored in the TeamCenter platform, simulation models and examples stored in the high-performance computing platform, and lightweight simulation models stored in the lightweight module. Specifically, the steps for generating the associated information are as follows: Associating the simulation report ID under the simulation entry with the simulation report in the TC platform, allowing users to jump to the TC platform to view the simulation report; associating the simulation model and example viewing link under the simulation entry with the simulation models and examples in the simulation report ID folder created in the controlled area of ​​the HPC platform, allowing users to jump to the storage location of the simulation models and examples on the HPC platform to view them; and associating the lightweight simulation model viewing link with the lightweight simulation model stored in the lightweight module, allowing users to jump to the storage location of the lightweight simulation model in the lightweight module to view it.

[0070] As an optional approach, managing the simulation data based on the associated information includes:

[0071] Receive viewing requests sent by users;

[0072] When the request is for viewing a simulation report, the user will be redirected to the TeamCenter platform to view the simulation report.

[0073] When the viewing request is for viewing simulation models and examples, the system will redirect to the high-performance computing platform to view the simulation models and examples.

[0074] When the viewing request is a simulation lightweight model viewing request, the user will be redirected to the lightweight module to view the simulation lightweight model.

[0075] In practical applications, users first log in to the TC platform and access the liquid rocket engine simulation data management system via the menu bar on the web interface to view the data. Figure 4 As shown, when a user accesses the virtual prototype library, they can find the corresponding model's structure tree within the prototype library. By expanding the hierarchy of this structure tree, they can locate the desired simulation entry, such as model A's structure tree V2. To view the simulation report, clicking the "View Simulation Report" button will take them to the TC platform for quick viewing. To view the simulation model and examples, clicking the "Simulation Model and Examples" button will take them to the controlled area of ​​the HPC platform. To view the lightweight simulation model, clicking the "View Lightweight Simulation Model" button will take them to the lightweight module. When a user accesses the simulation project dashboard, the quick search bar allows for rapid retrieval of the desired simulation project. The statistical charts under the data statistics unit provide a quick overview of the simulation project's progress, allocation, and overall planning. When a user accesses the simulation knowledge base, they can view the content stored in the standards and specifications library, model library, template library, materials library, and knowledge and experience library.

[0076] As shown in the above steps, the management process of this method is carried out simultaneously with the simulation work of the simulation engineer. During the simulation initiation phase, the simulation engineer only needs to submit the job on the high-performance computing platform, select the built-in tag information in the submission interface, and enter the simulation project ID. The HPC platform automatically generates a simulation entry based on the tag information. After submitting the job, the simulation engineer can complete a comprehensive description of the simulation work. Each time tag information is received, a simulation entry is created or updated. Therefore, regardless of the number of simulation iterations, the corresponding simulation information is automatically and quickly entered through the completion of each round of job submissions. Once the simulation engineer completes the archiving process, the simulation data can be stored and managed according to the archiving process, thereby greatly reducing the workload and learning cost for the simulation engineer. Furthermore, this method is based on a simulation entry index management approach. It creates simulation entries in a fixed format and associates them with simulation data based on archived information. Since the archived information includes simulation report IDs, simulation model and example viewing links, and lightweight simulation model viewing links, the original storage location and method of the simulation data do not need to be changed when associating simulation entries with simulation data. Only the structured storage and management of the simulation entries representing the simulation data is required to achieve the storage and management of simulation data, eliminating the need for large-scale migration and reorganization of the simulation data, thus improving the management efficiency. When a user accesses the simulation management structure tree, they only need to query the corresponding file library by model number and expand the file hierarchy level to quickly find the desired simulation entry. When viewing the simulation data corresponding to that entry, the user is redirected to the original storage platform, and viewing permissions are controlled by the TC platform.

[0077] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present invention are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a terminal, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video disc (DVD); or it can be a semiconductor medium, such as a solid-state drive (SSD).

[0078] Although the invention has been described herein in conjunction with various embodiments, those skilled in the art will understand and implement other variations of the disclosed embodiments by reviewing the accompanying drawings, the disclosure, and the appended claims in carrying out the claimed invention. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0079] Although the invention has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made therein without departing from the spirit and scope of the invention. Accordingly, this specification and drawings are merely exemplary descriptions of the invention as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of the invention. Clearly, those skilled in the art can make various alterations and modifications to the invention without departing from its spirit and scope. Thus, if such modifications and modifications of the invention fall within the scope of the claims and their equivalents, the invention is also intended to include such modifications and modifications.

Claims

1. A method for managing simulation data of a liquid rocket engine, characterized in that, include: The system receives tag information from the high-performance computing platform and archive information from the TeamCenter platform; the archive information includes simulation report ID, simulation model and example viewing links, and simulation lightweight model viewing links; the tag information includes model, component, discipline, and version number. Simulation entries are created and updated within the simulation management structure tree based on the tag information, and simulation entries that receive corresponding archived information are identified as target simulation entries. The simulation management structure tree includes simulation management structure trees corresponding to each type of liquid rocket engine. Each type of simulation management structure tree includes a first level, a second level, a third level, and a fourth level. The first level is divided according to the main component categories of the engine system, the second level is divided according to the component simulation category, the third level is the simulation entry, and the fourth level includes the simulation report ID, simulation model and example viewing link, and simulation lightweight model viewing link under the simulation entry. The target simulation entry is associated with the simulation data based on the archived information to generate association information; The simulation data is managed based on the associated information; the simulation data includes simulation reports stored in the TeamCenter platform, simulation models and examples stored in the high-performance computing platform, and lightweight simulation models stored in the lightweight module; the associated information is information that enables jumping to the original storage location of the simulation reports, simulation models and examples, and lightweight simulation models; The steps to generate the association information are as follows: associate the simulation report ID under the simulation entry with the simulation report in the TC platform so that the simulation report can be viewed on the TC platform; associate the simulation model and case viewing link under the simulation entry with the simulation model and case in the simulation report ID folder created in the controlled area of ​​the HPC platform so that the simulation model and case can be viewed at the storage location of the simulation model and case in the HPC platform. Link the simulation lightweight model viewing link to the simulation lightweight model stored within the lightweight module, so that you can jump to the storage location of the simulation lightweight model in the lightweight module to view the simulation lightweight model.

2. The liquid rocket engine simulation data management method according to claim 1, characterized in that, The step of establishing and updating simulation entries in the simulation management structure tree based on the tag information, and determining the simulation entries that receive the corresponding archived information as target simulation entries, includes: Determine whether there is a simulation entry in the simulation management structure tree that corresponds to the same simulation task book ID as the tag information; If it exists, update the corresponding simulation entry; If it does not exist, a simulation entry is created in the simulation management structure tree based on the tag information, and the status of the simulation entry is marked as the first state; The simulation entry that corresponds to the same simulation task ID as the archived information is identified as the target simulation entry, and the status of the target simulation entry is updated to the second status.

3. The liquid rocket engine simulation data management method according to claim 1, characterized in that, The management of the simulation data based on the association information includes: Receive viewing requests sent by users; When the request is for viewing a simulation report, the user will be redirected to the TeamCenter platform to view the simulation report. When the viewing request is for viewing simulation models and examples, the system will redirect to the high-performance computing platform to view the simulation models and examples. When the viewing request is a simulation lightweight model viewing request, the user will be redirected to the lightweight module to view the simulation lightweight model.

4. A liquid rocket engine simulation data management system, characterized in that, The liquid rocket engine simulation data management method described in any one of claims 1-3, wherein the system comprises at least: a basic layer and a capability layer; The base layer is integrated into the TeamCenter platform as a plug-in and communicates with the high-performance computing platform. The base layer is used to receive tag information sent by the high-performance computing platform and archive information sent by the TeamCenter platform. The tag information includes model, component, discipline, and version number. The capability layer includes a structure tree update module, used to establish and update simulation entries in the simulation management structure tree according to the tag information, and to determine the simulation entries that receive corresponding archive information as target simulation entries; and to associate the target simulation entries with simulation data according to the archive information to generate association information; and to manage the simulation data based on the association information; the simulation management structure tree includes simulation management structure trees corresponding to each type of liquid rocket engine, and each type of simulation management structure tree includes a first level, a second level, a third level, and a fourth level. The first level is divided according to the main component categories of the engine system, the second level is divided according to the component simulation category, the third level is the simulation entry, and the fourth level is the simulation report ID, simulation model and calculation example viewing link, and simulation lightweight model viewing link under the simulation entry; the simulation data includes simulation reports stored in the TeamCenter platform, simulation models and calculation examples stored in the high-performance computing platform, and simulation lightweight models stored in the lightweight module; the association information is information that enables jumping to the original storage location of simulation reports, simulation models and calculation examples, and simulation lightweight models.

5. The liquid rocket engine simulation data management system according to claim 4, characterized in that, The capability layer also includes a lightweight module; The lightweight module is used to access the target folders corresponding to each simulation report established in the controlled area of ​​the high-performance computing platform, and to perform lightweight processing on the simulation models in the target folders that meet the conversion conditions, generating a lightweight simulation model and a link to view the lightweight simulation model, and then sending the link to view the lightweight simulation model to the corresponding simulation report.

6. The liquid rocket engine simulation data management system according to claim 4, characterized in that, The liquid rocket engine simulation data management system also includes an application layer; The application layer includes at least a virtual prototype library, a simulation project dashboard module, a simulation knowledge base, and a system management module. The virtual prototype library includes simulation management structure trees of various models. The simulation project dashboard module is used to display the overall planning and implementation status of simulation projects. The simulation knowledge base includes a standard specification library, a model and template library, a material library, and a knowledge and experience library.

7. The liquid rocket engine simulation data management system according to claim 4, characterized in that, The liquid rocket engine simulation data management system also includes a platform layer and a presentation layer. The platform layer is used to provide retrieval services, architecture services, and version services. The presentation layer is the interaction entry point between the user and the liquid rocket engine simulation data management system. The presentation layer is used to display the information corresponding to the user's viewing request based on the user's input viewing request.

8. The liquid rocket engine simulation data management system according to claim 4, characterized in that, The liquid rocket engine simulation data management system also includes a system management module, which provides an administrator interface. The administrator interface includes simulation management structure tree management, system logs, and file editing.

9. The liquid rocket engine simulation data management system according to claim 4, characterized in that, User permissions for the liquid rocket engine simulation data management system are controlled by the TeamCenter platform; these permissions include access permissions and browsing permissions.

Images