Liquid rocket engine simulation data management method and system

Abstract

The invention discloses a liquid rocket engine simulation data management method and system, relates to the technical field of simulation data management, and aims to solve the problems that the existing simulation data management efficiency is low, and the learning cost and workload of simulation engineers are increased. 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 the simulation management structure tree according to the label information, and determining the simulation entries receiving the corresponding archiving information as target simulation entries; associating the target simulation entry with the simulation data according to the archiving information to generate associated information; and managing the simulation data based on the associated information. The liquid rocket engine simulation data management method provided by the invention is used for improving the simulation data management efficiency and reducing the learning cost and workload of simulation engineers.

Description

Technical Field

[0001] The present invention relates to the technical field of simulation data management, and in particular to a liquid rocket engine simulation data management method and system. Background Art

[0002] The development of liquid rocket engines is a systematic project integrating design, simulation analysis, and testing. During the development phase, extensive simulation analysis is required to optimize engine components and identify test risks. Research targets include complete engines, sub-systems, generators, thrust chambers, turbopumps, valves, and other product types, spanning multiple disciplines including systems, flow, combustion, heat transfer, fatigue, strength, and lifespan. Consequently, the resulting simulations generate a wide variety of raw data, including simulation models and results, and a substantial volume. Existing simulation data management typically requires users to upload relevant simulation files and data. However, in actual simulations, continuous product design improvements lead to a significant number of files during simulation iterations. Furthermore, due to limited hardware performance and network bandwidth in the management system, the efficiency of file uploads and downloads cannot meet the simulation data management requirements. Simulation engineers also need to complete corresponding control processes during daily management, increasing learning costs and workload, impacting overall control effectiveness. Summary of the Invention

[0003] The purpose of the present invention is to provide a liquid rocket engine simulation data management method and system for improving the simulation data management efficiency and reducing the learning cost and workload of simulation engineers.

[0004] In order to achieve the above object, the present invention provides the following technical solutions: In a first aspect, the present invention provides a liquid rocket engine simulation data management method, comprising: Receive tag information sent by the high-performance computing platform and archive information sent by the TeamCenter platform; the archive information includes a simulation report ID, a simulation model and example viewing link, and a simulation lightweight model viewing link; Creating and updating a simulation entry in a simulation management structure tree according to the tag information, and determining the simulation entry that receives the corresponding archive information as a target simulation entry; The target simulation entry is associated with the simulation data according to the archiving information to generate association information; and the simulation data is managed based on the association information.

[0005] Optionally, the step of creating and updating a simulation entry in the simulation management structure tree according to the tag information, and determining the simulation entry for which corresponding archive information has been received as the target simulation entry includes: Determine whether there is a simulation entry corresponding to the same simulation task book ID as the tag information in the simulation management structure tree; If it exists, update the corresponding simulation entry; If it does not exist, creating a simulation entry in the simulation management structure tree according to the tag information, and marking the state of the simulation entry as the first state; The simulation entry corresponding to the same simulation task book ID as the archive information is determined as a target simulation entry, and the state of the target simulation entry is updated to a second state.

[0006] Optionally, the simulation data includes a simulation report stored in the TeamCenter platform, a simulation model and calculation examples stored in the high-performance computing platform, and a simulation lightweight model stored in a lightweight module; and managing the simulation data based on the associated information includes: Receive viewing requests sent by users; When the viewing request is a simulation report viewing request, the user is redirected to the TeamCenter platform to view the simulation report; When the viewing request is a request for viewing simulation models and calculation examples, the system jumps to the high-performance computing platform to view the simulation models and calculation examples; When the viewing request is a simulation lightweight model viewing request, the process jumps to the lightweight module to view the simulation lightweight model.

[0007] Optionally, the label information includes model, component, discipline and version number; the simulation management structure tree includes simulation management structure trees corresponding to each model of liquid rocket engine, and the simulation management structure tree of 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.

[0008] In a second aspect, 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 at least includes: a basic layer and a capability layer; The basic layer is integrated into the TeamCenter platform in the form of a plug-in and is connected to the high-performance computing platform for communication; the basic layer is used to receive tag information sent by the high-performance computing platform and archive information sent by the TeamCenter platform; 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 entry that receives the corresponding archive information as the target simulation entry; and associate the target simulation entry with the simulation data according to the archive information to generate association information; and manage the simulation data based on the association information.

[0009] Optionally, the capability layer further 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 perform lightweight processing on the simulation models in the target folder that meet the conversion conditions, generate a simulation lightweight model and a simulation lightweight model viewing link, and then send the simulation lightweight model viewing link to the corresponding simulation report.

[0010] Optionally, the liquid rocket engine simulation data management system further 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, and the simulation project dashboard module is used to display the overall planning of the simulation project and the progress of the simulation project; the simulation knowledge base includes a standard specification library, a model and template library, a material library, and a knowledge and experience library.

[0011] Optionally, the liquid rocket engine simulation data management system also includes a platform layer and a presentation layer, wherein the platform layer is used to provide retrieval services, architecture services, and version services; the presentation layer is the interaction entrance between the user and the liquid rocket engine simulation data management system, and the presentation layer is used to display information corresponding to the viewing request input by the user to the user.

[0012] Optionally, the liquid rocket engine simulation data management system further includes a system management module, which is used to provide an administrator interface, and the administrator interface includes simulation management structure tree management, system logs, and file editing.

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

[0014] 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 a TeamCenter platform; Simulation entries are created and updated within the simulation management structure tree based on tag information, and simulation entries that receive corresponding archived information are identified as target simulation entries. The target simulation entries are then associated with simulation data based on the archived information to generate association information. Simulation data is then managed based on this association information. By forming fixed-format simulation entries and associating them with simulation data through archived information, the original storage location and method of the simulation data remain unchanged. Since the archived information includes the simulation report ID, simulation model and case view links, and simulation lightweight model view links, the original storage location and method of the simulation data remain unchanged. Therefore, simulation data storage and management can be achieved simply by structuring the simulation entries representing the simulation data, eliminating the need for large-scale migration and organization of simulation data and improving simulation data management efficiency. When users access the simulation management structure tree, they can simply jump to the corresponding platform using the association information to view simulation data. 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, significantly reducing the workload and learning costs of simulation staff.

[0015] 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 the beneficial effects of the liquid rocket engine simulation data management method, which will not be described in detail here. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings: Figure 1 This is a schematic structural diagram of a liquid rocket engine simulation data management system provided by the present invention; Figure 2 An example diagram of the simulation management structure tree provided by the present invention; Figure 3 A flow chart of a liquid rocket engine simulation data management method provided by the present invention; Figure 4 This is an operational flow chart of the liquid rocket engine simulation data management system provided by the present invention; Figure 5 The present invention provides an archiving flow chart. DETAILED DESCRIPTION

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

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

[0019] In the present invention, "at least one" means one or more, and "more" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers 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 mean: a, b, c, the combination of a and b, the combination of a and c, the combination of b and c, or the combination of a, b and c, where a, b, c can be single or plural.

[0020] Before introducing the embodiments of the present invention, the following definitions are given for the relevant terms involved in the embodiments of the present invention: The TeamCenter Platform (TC Platform) is a modern, adaptable PLM system that connects people and processes across functions through a digital thread to enable innovation and improve productivity. It is the industry's first to transform a single software application into a truly integrated PLM solution built on a Service-Oriented Architecture (SOA) foundation, spanning disciplines, project phases, and initiatives. During engine development, simulation engineers often use the platform to write simulation reports.

[0021] 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 often involve large amounts of data input and output, requiring enormous computing power and high-speed data processing capabilities.

[0022] The PDM system is a software system used to manage product-related data and processes. It aims to optimize data management, collaboration and process control in the product life cycle. By centrally storing, organizing and controlling product data, it supports enterprises in efficiently carrying out product design, development, manufacturing and after-sales service activities.

[0023] Simulation data is typically managed using a PDM system. However, since PDM systems are integrated management platforms for development and testing documents, the development file directory for each engine model contains multiple types of files, including development and testing documents, design documents, 3D models, and simulation reports. This results in fragmented simulation data management and a lack of data sharing and integrated utilization. Simulation models and results generated during simulation work lack traceability and reusability, and there is no centralized organization and display of simulation results from the model development process. Furthermore, simulation data management requires users to individually enter information for each simulation data to be archived, describing the simulation input, simulation objects, and simulation content. However, due to the continuous iteration of designs during engine development and the increasing volume of simulation tasks, simulation engineers find it difficult to devote sufficient time and effort to this information entry, resulting in low platform management efficiency and poor file management practicality. Furthermore, traditional simulation data management platforms require reorganization of existing data storage methods during construction, and, when necessary, global data migration to ensure structured data management. This approach is only suitable for managing small amounts of simulation data. When the simulation data is large and stored across different system platforms, the workload of migrating and structuring the data is enormous, making it difficult to quickly complete platform construction and deployment, and it also conflicts with existing management systems. Secondly, file access requires appropriate permission management to ensure a controlled scope of access. Consequently, the management platform also requires the development of a separate user management system to control the viewing permissions of each accessing user, further increasing the complexity of platform development.

[0024] To address the above issues, the present invention provides a liquid rocket engine simulation data management method and system. By embedding the management process into the necessary stages of simulation work and simulation result archiving, and through automatic input in the early stages and automatic sorting in the later stages, the system reduces the additional workload and learning cost for simulation engineers in simulation data management. This is explained below with reference to the accompanying figures.

[0025] See also Figure 1 The present invention provides a liquid rocket engine simulation data management system comprising: Basic layer, platform layer, capability layer, application layer and presentation layer; 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 from the high-performance computing platform. This system, integrated into the TeamCenter platform as a plug-in, enables 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.

[0026] The platform layer is the basic common capability of the system. The platform layer is used to provide retrieval services, architecture services and version services. The retrieval service supports global search, fuzzy search and combined search functions. The architecture service can define structure trees and simulation projects. The version service stores the change records of the system version and performs version management.

[0027] The capability layer is a basic module that supports business capabilities. It receives tag information from simulation projects to enable rapid updates to the simulation management structure tree. It associates simulation reports, simulation models, examples, and simulation lightweight models under the same simulation entry to achieve centralized display of multi-domain simulation results. It also achieves web-based display of simulation CAE models through model compression, information extraction, and other means. Specifically, the capability layer includes a structure tree update module and a lightweight module. The structure update module is used to establish and update simulation entries in the simulation management structure tree based on tag information, and to identify the simulation entry that receives the corresponding archived information as the target simulation entry; and to associate the target simulation entry with the simulation data based on the archived information to generate association information; and to manage the simulation data based on the association information. Simulation data includes simulation reports, simulation lightweight 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, and lightweight the simulation models in the target folder that meet the conversion conditions through model compression, information extraction and other means, generate simulation lightweight models and simulation lightweight model viewing links, and then send the simulation lightweight model viewing links to the corresponding simulation reports, thereby realizing the WEB display of the simulation CAE model.

[0028] 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 includes a simulation management structure tree for various models. Through hierarchical division and information classification, it systematically displays the work and results of each simulation project: 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 simulation system construction and project progress. Category viewing and quick query facilitate the search and traceability of simulation projects. Data statistics are used to statistically process data in the system. Status display displays the completion status of simulation projects. Version tracing enables system version traceability through version editing. The simulation knowledge base builds a knowledge sharing platform. The simulation knowledge base contains specifications or related documents established during historical simulation work. It includes 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 logging, and file editing. Administrators can manually create, manage, and edit files in the model simulation management structure tree to ensure continuous updates and maintenance of the platform. Specifically, administrators can submit simulation project planning tables in the background. The data statistics unit of the simulation project dashboard is used to update the data in the simulation project planning table when simulation entries are created and updated in the simulation data structure tree, and to convert the updated data in the simulation project planning table into a list or statistical chart, which is then displayed through the status display unit. The display form of the status display unit can include a list of simulation systems in the form of a list and a bar chart, pie chart, etc. in the form of a statistical chart.

[0029] Among them, the simulation structure management tree includes simulation management structure trees corresponding to various types of liquid rocket engines. The simulation management structure tree of each model includes the first level, the second level, the third level and the fourth level. The construction rules of the simulation management structure tree are: 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 component simulation category, the third level is the simulation item, and the fourth level is the simulation report ID, simulation model and example viewing link and simulation lightweight model viewing link under the simulation item. Among them, the first level and the second level of the simulation management structure tree are established in advance, and the simulation items of the third level are established according to the label information as the project progresses. The number of simulation items is also determined according to the actual project development. For example, Figure 2As shown, for the XX model engine, the first level includes five parts: thermal components, turbo pumps, valves, assembly structures and systems. The second level of thermal components, turbo pumps, valves and assembly structures includes simulation subject category 1: flow heat transfer and combustion calculations and simulation subject category 2: structural strength and fatigue calculations. The second level of the system includes: simulation subject category 3: system simulation calculations; the third level corresponding to the thermal components includes simulation item 1: thrust chamber heat transfer calculations, simulation item 2: thrust chamber thermal control simulation... simulation item n, etc.; the third level corresponding to the flow heat transfer and combustion calculations of the turbo pump includes simulation item 1: turbo pump transmission... Thermal simulation analysis and structural strength and fatigue calculations are performed at the third level, including Simulation Item 1: Shell Structural Strength Calculation. Valve flow, heat transfer, and combustion calculations are performed at the third level, including Simulation Item 1: Main Valve Flow Field Simulation. Structural strength and fatigue calculations are performed at the third level, including Simulation Item 1: Shell Fatigue Assessment. Assembly flow, heat transfer, and combustion calculations are performed at the third level, including Simulation Item 1: Heat Transfer Temperature Field Calculation. Structural strength and fatigue calculations are performed at the third level, including Simulation Item 1: Swing Mechanism Strength Calculation. System simulation calculations are performed at the third level, including Simulation Item 1: System Static Characteristics Simulation and Simulation Item 2: System Dynamic Characteristics Simulation. Each simulation item's fourth level includes the simulation report ID, links to view the simulation model and example, and links to view the simulated lightweight model.

[0030] The presentation layer is the interactive entrance between the user and the liquid rocket engine simulation data management system. The presentation layer is used to display information corresponding to the viewing request based on the viewing request input by the user.

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

[0032] Based on the above liquid rocket engine simulation data management system, the present invention also provides a liquid rocket engine simulation data management method, such as Figure 3 As shown, the method includes the following steps: Step 301: receiving tag information sent by the high-performance computing platform and archive information sent by the TeamCenter platform; the archive information includes a simulation report ID, a simulation model and case viewing link, and a simulation lightweight model viewing link; The tag information includes model, component, 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 the figure, in actual applications, simulation work mainly includes three stages: simulation work startup, simulation work iteration, and simulation work archiving. In the simulation work startup stage, after receiving the simulation project input, simulation model input, and simulation condition input from the model department, the simulation engineer starts to create the simulation model and case. When submitting the job to the HPC platform, fill in the name of the simulation project, the simulation task book ID, and select the model, component, discipline, and version number corresponding to the simulation project one by one. The HPC platform sends the tag information, simulation project name, and simulation task book ID to the liquid rocket engine simulation data management system. The liquid rocket engine simulation data management system finds the corresponding hierarchical position in the corresponding model simulation management structure tree based on this information and creates a simulation entry. The simulation entry is generally the simulation project name. After receiving the simulation job, the HPC platform performs simulation calculations and obtains simulation result 1. Then the simulation engineer determines whether the simulation project is completed. If not, it enters the simulation work iteration stage. Due to the continuous improvement of product design during the R&D process, the simulation condition input and simulation model will have an iterative process of continuous modification. At this time, it means that the simulation project is not completed. The simulation engineer returns to the previous stage and resubmits the HPC job, that is, re-fills in the name of the simulation project, the simulation task book ID, and selects the model, component, subject, and version number corresponding to the simulation project. The HPC platform sends the tag information and the simulation task book ID and the name of the simulation project to the liquid rocket engine simulation data management system again. At the same time, the HPC platform continues to perform simulation calculations based on the submitted job and obtains simulation result 2. The simulation engineer determines whether the project is completed. If not, the HPC submission and simulation calculation process is repeated until the simulation project is completed. The simulation engineer archives the simulation work and combines it with Figure 5After the simulation engineer completes the writing of the simulation report on the TeamCenter platform, he finds the simulation model and example corresponding to the simulation report in the job data area of ​​the HPC platform and copies them to the controlled area of ​​the HPC platform. The controlled area automatically creates a target folder named after the simulation report ID according to the simulation report ID of the TC platform, and stores the corresponding simulation model and example in the target folder. The link of the target folder, that is, the link of the simulation model and example, is sent to the simulation report of the TC platform to complete the association between the simulation report and the simulation model and example. Later, the simulation model and example can be quickly traced by clicking the relevant link in the simulation report. After the association operation is completed, return to the TC platform to start the simulation model In the lightweight process, the lightweight module of the liquid rocket engine simulation data management system traverses the simulation models in the target folder, and lightweight-converts all simulation models that meet the conversion conditions, forming a simulation lightweight model viewing link on the web page, and sending the simulation lightweight model viewing link to the corresponding simulation report to complete the association operation between the simulation lightweight model and the simulation report. The simulation engineer returns to the TC platform to start the simulation report archiving process, archives the simulation report ID, simulation model and case link, and simulation lightweight model viewing link, and obtains the archive information. The corresponding simulation task book ID is added to the archive information, and the TC platform sends the archive information to the liquid rocket engine simulation data management system.

[0033] Step 302: Create and update a simulation entry in the simulation management structure tree according to the tag information, and determine the simulation entry for which the corresponding archive information has been received as the target simulation entry; Specifically, step 302 is implemented based on the following steps: Determine whether there is a simulation entry corresponding to the same simulation task book ID as the tag information in the simulation management structure tree; If it exists, update the corresponding simulation entry; Specifically, the iteration count corresponding to the simulation entry is updated. The iteration count is the number of times the simulation project performs simulation calculations. In actual applications, for a simulation entry corresponding to the same simulation task book ID, when the simulation entry is initially established, the iteration count corresponding to the simulation entry is 1. When the tag information corresponding to the same simulation task book ID is received for the second time, the iteration count corresponding to the simulation entry is updated to 2, and so on.

[0034] If it does not exist, a simulation entry is created in the simulation management structure tree according to the tag information, and the state of the simulation entry is marked as a first state; the first state is in progress.

[0035] The simulation item corresponding to the same simulation task book ID as the archived information is determined as the target simulation item, and the state of the target simulation item is updated to a second state. The second state is completed. The first state and the second state are the completion states of the simulation project.

[0036] In practical applications, such as Figure 2 As shown, when the received tag information does not establish a simulation entry, the tag information is subjected to subordinate analysis to determine the model structure tree to which the tag information belongs, the corresponding first level, the corresponding second level, and the simulation entry under the third level, and the simulation entry is marked as in progress. For example, the submitted tag information corresponds to model A, corresponds to the first level B1, and there is already a simulation entry under the corresponding third level. In this case, only the number of iterations of the simulation entry is updated. If there is no simulation entry under the corresponding third level, a simulation entry is established. After the simulation entry is established or updated, the completion status of the corresponding simulation project will be updated in the simulation project planning table submitted by the administrator. The simulation project planning table is displayed in the form of a list or a statistical chart, and can also be viewed through a quick search.

[0037] Step 303: Associating the target simulation entry with the simulation data according to the archiving information to generate association information; and managing the simulation data based on the association information.

[0038] Among them, the associated information is information that can be used to jump to the original storage location of the simulation report, simulation model and example, and simulation lightweight model. The simulation data includes the simulation report stored in the TeamCenter platform, the simulation model and example stored in the high-performance computing platform, and the simulation lightweight model stored in the lightweight module. Specifically, the steps for generating the associated information are: associating the simulation report ID under the simulation item with the simulation report in the TC platform, so that it is possible to jump to the TC platform to view the simulation report; associating the simulation model and example viewing link under the simulation item with the simulation model and example in the simulation report ID folder established in the controlled area of ​​the HPC platform, so that it is possible to jump to the storage location of the simulation model and example of the HPC platform for viewing the simulation model and example; associating the simulation lightweight model viewing link with the simulation lightweight model stored in the lightweight module, so that it is possible to jump to the storage location of the simulation lightweight model of the lightweight module for viewing the simulation lightweight model.

[0039] As an optional manner, managing the simulation data based on the association information includes: Receive viewing requests sent by users; When the viewing request is a simulation report viewing request, the user is redirected to the TeamCenter platform to view the simulation report; When the viewing request is a request for viewing simulation models and calculation examples, the system jumps to the high-performance computing platform to view the simulation models and calculation examples; When the viewing request is a simulation lightweight model viewing request, the process jumps to the lightweight module to view the simulation lightweight model.

[0040] In actual application, the user first logs in to the TC platform and enters the liquid rocket engine simulation data management system on the web through the menu bar to view it, such as Figure 4 As shown, when users access the virtual prototype library, they can find the corresponding model structure in the virtual library prototype and expand the hierarchical directory of the structure to find the simulation entry they want to view, such as the structure tree V2 of model A. When they need to view the simulation report, they click the Simulation Report View button to jump to the TC platform for quick viewing. When they need to view the simulation model and case, they click the Simulation Model and Case button to jump to the controlled area of ​​the HPC platform for viewing. When they need to view the simulation lightweight model, they click the Simulation Lightweight Model View button to jump to the lightweight module for viewing. When users access the simulation project dashboard, they can quickly retrieve the simulation project they want to view using the quick search bar. The statistical charts under the data statistics unit can quickly view the progress and allocation of simulation projects, as well as the overall planning of simulation projects. When users access the simulation knowledge base, they can specifically view the content stored in the standard specification library, model library, template library, material library, and knowledge and experience library.

[0041] From the above steps, it can be seen that the management process of this method is carried out simultaneously with the simulation work of the simulation engineer. At the start of the simulation work, the simulation engineer only needs to submit the job on the high-performance computing platform when performing the simulation work, select the built-in tag information in the submission interface, and enter the simulation project ID number. The HPC platform can automatically form a simulation entry based on the tag information. The simulation engineer can complete the comprehensive description of the simulation work after submitting the job. Every time the tag information is received, a simulation entry is created or updated. Therefore, no matter how many rounds of simulation work are iterated, the corresponding simulation information will be automatically and quickly entered through the submission of each round of job information. When the simulation engineer completes the archiving process, the storage and management of the simulation data can be completed according to the archiving process, thereby greatly reducing the workload and learning cost of the simulation engineer. In addition, this method is based on the management method of simulation item index. By forming a fixed form of simulation items, it is associated with the simulation data according to the archiving information. Since the archiving information is the simulation report ID, the simulation model and the case viewing link, and the simulation lightweight model viewing link, when the simulation item is associated with the simulation data, the original storage location and method of the simulation data do not need to be changed. It is only necessary to store and manage the simulation items representing the simulation data in a structured manner to achieve the storage and management of the simulation data. There is no need to migrate and organize the simulation data on a large scale, which improves the management efficiency of the simulation data. When the user accesses the simulation management structure tree, he only needs to query the corresponding file library by model and expand the file hierarchy level by level to quickly find the simulation item he needs to view. When he needs to view the simulation data corresponding to the simulation item, he jumps to the original storage platform for viewing. The viewing permission is controlled by the TC platform.

[0042] The above embodiments can be implemented in whole or in part through software, hardware, firmware, or any combination thereof. When implemented using software, they can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer programs or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present invention are fully or partially executed. 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 accessible by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be magnetic media, such as floppy disks, hard disks, or magnetic tapes; optical media, such as digital video discs (DVDs); or semiconductor media, such as solid-state drives (SSDs).

[0043] Although the present invention is described herein in conjunction with various embodiments, in the process of implementing the claimed invention, those skilled in the art may understand and implement other variations of the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. 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 may implement several functions listed in the claims. The fact that certain measures are recorded in mutually different dependent claims does not mean that these measures cannot be combined to produce good results.

[0044] Although the present invention has been described with reference to specific features and embodiments thereof, it will be apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the invention. Accordingly, this specification and drawings are merely illustrative of the invention as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the invention. It will be apparent that various modifications and variations may be made to the present invention by those skilled in the art without departing from the spirit and scope of the invention. Thus, the present invention is intended to include such modifications and variations as fall within the scope of the claims of the present invention and their equivalents.

Claims

1. A liquid rocket engine simulation data management method, characterized in that: include: Receive tag information sent by the high-performance computing platform and archive information sent by the TeamCenter platform; The archived information includes a simulation report ID, a simulation model and example viewing link, and a simulation lightweight model viewing link; Creating and updating a simulation entry in a simulation management structure tree according to the tag information, and determining the simulation entry that receives the corresponding archive information as a target simulation entry; Associating the target simulation entry with simulation data according to the archive information to generate association information; The simulation data is managed based on the association information.

2. The liquid rocket engine simulation data management method according to claim 1, characterized in that: The step of establishing and updating a simulation entry in the simulation management structure tree according to the tag information, and determining the simulation entry receiving the corresponding archive information as the target simulation entry includes: Determine whether there is a simulation entry corresponding to the same simulation task book ID as the tag information in the simulation management structure tree; If it exists, update the corresponding simulation entry; If it does not exist, creating a simulation entry in the simulation management structure tree according to the tag information, and marking the state of the simulation entry as the first state; The simulation entry corresponding to the same simulation task book ID as the archive information is determined as a target simulation entry, and the state of the target simulation entry is updated to a second state.

3. The liquid rocket engine simulation data management method according to claim 1, characterized in that: 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 managing the simulation data based on the association information includes: Receive viewing requests sent by users; When the viewing request is a simulation report viewing request, the user is redirected to the TeamCenter platform to view the simulation report; When the viewing request is a request for viewing simulation models and calculation examples, the system jumps to the high-performance computing platform to view the simulation models and calculation examples; When the viewing request is a simulation lightweight model viewing request, the process jumps to the lightweight module to view the simulation lightweight model.

4. The liquid rocket engine simulation data management method according to claim 1, characterized in that: The label 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, and the simulation management structure tree of each model includes the first level, the second level, the third level and the fourth level. The first level is divided according to the main component category 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.

5. A liquid rocket engine simulation data management system, characterized in that: A liquid rocket engine simulation data management method according to any one of claims 1 to 4, wherein the system comprises at least: a base layer and a capability layer; The basic layer is integrated into the TeamCenter platform in the form of a plug-in and is connected to the high-performance computing platform for communication; the basic layer is used to receive tag information sent by the high-performance computing platform and archive information sent by the TeamCenter platform; 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 entry that receives the corresponding archive information as the target simulation entry; and associate the target simulation entry with the simulation data according to the archive information to generate association information; and manage the simulation data based on the association information.

6. The liquid rocket engine simulation data management system according to claim 5, 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 perform lightweight processing on the simulation models in the target folder that meet the conversion conditions, generate a simulation lightweight model and a simulation lightweight model viewing link, and then send the simulation lightweight model viewing link to the corresponding simulation report.

7. The liquid rocket engine simulation data management system according to claim 5, 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, and the simulation project dashboard module is used to display the overall planning of the simulation project and the progress of the simulation project; the simulation knowledge base includes a standard specification library, a model and template library, a material library, and a knowledge and experience library.

8. The liquid rocket engine simulation data management system according to claim 5, 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 entrance between the user and the liquid rocket engine simulation data management system. The presentation layer is used to display information corresponding to the viewing request input by the user to the user.

9. The liquid rocket engine simulation data management system according to claim 5, characterized in that: The liquid rocket engine simulation data management system also includes a system management module, which is used to provide an administrator interface. The administrator interface includes simulation management structure tree management, system logs, and file editing.

10. The liquid rocket engine simulation data management system according to claim 5, characterized in that: The user rights of the liquid rocket engine simulation data management system are managed and controlled by the TeamCenter platform; the user rights include access rights and browsing rights.

Images