A parameter processing method, system and device

Abstract

This application discloses a parameter processing method, system, and device. The method involves obtaining a simulation project directory and extracting multiple simulation model files from it. From each simulation model file, a target file describing the model parameters is extracted, and parameter information is parsed from the target file. Based on the parameter information parsed from all simulation model files, a parameter management interface is constructed. In response to a parameter modification command received on the parameter management interface, the target file corresponding to the parameter information indicated by the modification command is modified, and the modified target file is repackaged into the corresponding simulation model file. This automatically and accurately synchronizes user operations on a unified interface back to the dispersed model files, achieving automatic distribution of modifications after a single modification. This improves operational efficiency and avoids errors that may be introduced by manually switching between different interfaces, thus enhancing the reliability, efficiency, and accuracy of parameter management.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a parameter processing method, system and device. Background Technology

[0002] In the field of integrated simulation engineering, complex system simulations often require the integration of multiple simulation models with different functions and interrelationships. These models typically exist as independent units, each encapsulating its own structure, behavior, and parameters. Currently, the management and modification of parameters in these simulation models generally adopts a decentralized, model-by-model approach. Specifically, when a user needs to adjust a specific parameter of a model in a project, they must first locate the target model in the project environment, open its independent configuration interface or property dialog box through interactive operations, and then find and modify the target parameter within its dedicated interface. For complex projects containing dozens or even hundreds of models, this process needs to be repeated.

[0003] The existing parameter management method has significant shortcomings. First, it is cumbersome and inefficient. Engineers need to memorize or check the location of each model individually, navigating to multiple independent interfaces, making it impossible to quickly view or uniformly adjust parameters across models in batches. Second, it lacks a global view and centralized control. Parameters are scattered and hidden within various models, making it difficult for engineers to intuitively and comprehensively grasp the current status, value range, and interrelationships of all parameters in the entire project, which is detrimental to system parameter analysis and optimization. Finally, it is prone to human error. During repeated switching between interfaces and models, parameters may be missed or incorrectly modified, affecting the accuracy and reliability of simulation results.

[0004] Therefore, the industry urgently needs a technical solution that can overcome the above-mentioned shortcomings in order to achieve unified, efficient, and intuitive management and modification of parameters scattered across multiple models in integrated simulation engineering, thereby improving the overall efficiency and reliability of simulation work. Summary of the Invention

[0005] To address the aforementioned issues, this application provides a parameter processing method, system, and device.

[0006] The embodiments of this application disclose the following technical solutions: The first aspect of this application provides a parameter processing method, including: Obtain the simulation project directory and extract the multiple simulation model files contained in the simulation project directory; Extract the target file describing the model parameters from each simulation model file, and parse the parameter information from the target file; A parameter management interface is constructed based on the parameter information parsed from all simulation model files; In response to a parameter modification command received on the parameter management interface, the target file corresponding to the parameter information indicated by the parameter modification command is modified, and the modified target file is repackaged into the corresponding simulation model file.

[0007] In one possible implementation, extracting the multiple simulation model files contained in the simulation project directory includes: Traverse the specified integrated simulation project directory and its corresponding subdirectories to extract all simulation model files with extensions including .fmu.

[0008] In one possible implementation, extracting the target file describing the model parameters from each simulation model file includes: Unzip the simulation model file as a compressed package; Based on the decompressed simulation model file, extract the XML file describing the model parameters.

[0009] In one possible implementation, the parameter information includes a parameter name, a current parameter value, and a parameter description. Parsing the parameter information from the target file includes: Parse the target file and read the model variable definition nodes in the target file; From the model variable definition nodes, identify the parameter variable nodes used to define model parameters; Extract the parameter name, current parameter value, and parameter description information from the parameter variable node.

[0010] In one possible implementation, the parameter management interface is constructed based on the parameter information parsed from all simulation model files, including: The parameter information is associated with the corresponding simulation model file to obtain a parameter-model mapping table; Based on the parameter-model mapping table, each parameter is grouped according to the simulation model file to which it belongs, and the parameter information of all parameters is displayed in a table. The parameter management interface supports filtering, sorting, and keyword search functions based on parameter name, simulation model file name to which the parameter belongs.

[0011] In one possible implementation, the method further includes: Configure an editable input control for the current value of each parameter in the table, wherein the input control is adapted to the data type corresponding to the parameter.

[0012] In one possible implementation, the modification of the target file corresponding to the parameter information indicated by the parameter modification instruction, and the re-encapsulation of the modified target file into the corresponding simulation model file, includes: Based on the parameter-model mapping table, determine the simulation model file to which the parameter information indicated by the parameter modification instruction belongs; The simulation model file can be decompressed or its internal structure accessed to modify the target file inside the simulation model file that describes the model parameters. In the target file, locate the parameter variable node corresponding to the parameter information indicated by the parameter modification instruction; Based on the parameter information indicated by the parameter modification instruction, the attribute representing the current value of the parameter in the parameter variable node is updated; The modified target file is repackaged into a compressed file format, while the compressed file format remains unchanged.

[0013] In one possible implementation, the method further includes: Load the updated simulation model file into the simulation environment and verify whether the parameter values ​​read by the simulation environment from the loaded simulation model file are consistent with the updated parameter information. Simulation calculations are performed in the simulation environment based on verified and consistent parameter values.

[0014] This application provides a parameter processing system in embodiment two, including: The extraction unit is used to obtain the simulation project directory and extract multiple simulation model files contained in the simulation project directory; The parsing unit is used to extract the target file describing the model parameters from each simulation model file, and parse the parameter information from the target file; The building unit is used to construct the parameter management interface based on the parameter information parsed from all simulation model files; The modification unit is used to respond to the parameter modification command received on the parameter management interface, modify the target file corresponding to the parameter information indicated by the parameter modification command, and repackage the modified target file into the corresponding simulation model file.

[0015] A third aspect of this application provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, it implements the parameter processing method described in the first aspect above.

[0016] A fourth aspect of this application provides a computer program product, which, when run on a computer, executes the parameter processing method described in the first aspect above.

[0017] A fifth aspect of this application provides a computer-readable storage medium storing instructions that, when executed on a terminal device, cause the terminal device to perform the parameter processing method described in the first aspect above.

[0018] Compared with the prior art, this application has the following beneficial effects: By traversing and extracting all simulation model files in the project directory, the system automatically aggregates model resources. It automatically parses the target files describing parameters from each model file and extracts structured parameter information, transforming the parameter data, originally hidden within each independent model, into a unified data set that can be processed uniformly. This lays the data foundation for establishing a global view. Furthermore, based on this centralized parameter information, a unified parameter management interface is built, providing users with a single control center to simultaneously browse, filter, and manage all model parameters, completely changing the previous situation of repeatedly switching between different model interfaces. Finally, when a user modifies parameters on the interface, the method automatically locates and modifies the corresponding target file within the model and repackages the file. This automatically and accurately synchronizes the user's interface operation back to the scattered model files, thereby improving operational efficiency and global visibility while ensuring the accuracy of parameter modifications and the consistency of model files. This represents a fundamental shift from scattered manual operation to centralized automatic management, overcoming the shortcomings of existing technologies such as cumbersome operation, low efficiency, lack of a global view, and susceptibility to errors. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 A flowchart illustrating a parameter processing method provided in an embodiment of this application; Figure 2 A flowchart illustrating another parameter processing method provided in this application embodiment; Figure 3 This is a schematic diagram of the core architecture and data flow of the parameter processing system involved in the embodiments of this application; Figure 4 This is a structural diagram of a parameter processing system provided in an embodiment of this application. Detailed Implementation

[0021] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0022] To facilitate understanding of the technical solutions provided in the embodiments of this application, the background technology involved in the embodiments of this application will be described below.

[0023] As mentioned earlier, all the models integrated in the project are in a unified format (.fmu). This format file is actually a compressed file containing three folders named binaries, resources, and sources, as well as a file named modelDescription, which is in .xml format. This XML file includes the model's parameter names, current parameter values, unit of measurement, data type, and description information. The project includes different models, each an independent entity. When changing parameters in a particular model, one must locate the corresponding model, click on it, and then modify the parameters in the properties interface. This process is cumbersome and carries the risk of errors due to improper manual operation.

[0024] To address the aforementioned issues, this application's embodiments automatically acquire the simulation project directory and extract all simulation model files. This method replaces the tedious process of manually searching for each model, achieving automatic discovery and aggregation of model resources. Secondly, by extracting and parsing the parameter description files within each model file, this method proactively collects and transforms physically dispersed and logically isolated parameter definitions into structured, unified data, providing a data foundation for centralized management. Furthermore, based on this data, a unified parameter management interface is constructed, fundamentally changing the organization and presentation of parameters. This provides users with a global parameter view covering the entire project and a single control entry point, enabling browsing, filtering, comparing, and batch operations across model parameters, completely eliminating the pain point of lacking a global perspective. Finally, by responding to interface commands, automatically locating and modifying the corresponding parameter files within the model and re-encapsulating them, this method automatically and accurately synchronizes user operations on the unified interface back to the dispersed model files, achieving automatic distribution of modifications after a single modification. This greatly improves operational efficiency while avoiding errors that might be introduced by manually switching between different interfaces, thereby comprehensively improving the reliability, efficiency, and accuracy of parameter management.

[0025] It should be noted that the parameter processing methods, systems, products, devices, and media provided in this application can be applied to the field of computer technology. The above are merely examples and do not limit the application areas of the parameter processing methods, systems, products, devices, and media provided in this application. Furthermore, the embodiments of this application may not limit the executing entity of parameter processing. For example, the parameter processing method of the embodiments of this application can be applied to data processing devices such as terminal devices or servers. The terminal device can be an electronic device such as a computer or a personal digital assistant (PDA). The server can be a standalone server, a cloud server, or a cluster server composed of multiple servers.

[0026] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0027] The following embodiment illustrates a parameter processing method provided in this application. See also... Figure 1 ,Should Figure 1 A flowchart of a parameter processing method provided in this application embodiment, the method including: S101. Obtain the simulation project directory and extract the multiple simulation model files contained in the simulation project directory.

[0028] A simulation project directory refers to the folder path within simulation software or an integrated simulation platform used to organize and manage all relevant files for a specific simulation project. This directory typically contains multiple simulation model files, configuration files, resource files, and possible subdirectories.

[0029] A simulation model file refers to a digital file used to describe the behavior, structure, or characteristics of a simulated object. In this embodiment, it specifically refers to an FMU (Functional Mock-up Unit) format file conforming to the Functional Mock-up Interface (FMI) standard. This file is essentially a compressed package containing model code, resources, and metadata.

[0030] The system receives the simulation project directory path specified by the user or preset in the configuration file. Then, it automatically traverses this directory and all its subfolders, searching for and identifying simulation model files that conform to a preset format (e.g., with the extension .fmu). These files are the source for subsequent parameter extraction. This achieves automatic discovery and aggregation of all relevant models from the physical storage structure, thereby locating and collecting all simulation models that require unified parameter management.

[0031] S102. Extract the target file used to describe the model parameters from each simulation model file, and parse the parameter information from the target file.

[0032] In this embodiment of the application, the target file specifically refers to a file extracted from a simulation model file (such as an FMU file) and specifically used to describe the model parameters. Typically, this file is an Extensible Markup Language (XML) file conforming to a specific architecture, such as the modelDescription.XML file in the FMI standard, which defines variable information such as the model's inputs, outputs, and parameters.

[0033] Parameter information refers to the data set parsed from the target file that characterizes specific attributes of the model. It includes at least the parameter name to uniquely identify the parameter and the current value of the numerical parameter representing the parameter in the current model. Parameter information may further include metadata such as parameter units, parameter data types, and parameter descriptions.

[0034] Since simulation model files (such as FMU files) are typically compressed packages, the system first decompresses them or accesses their contents via streaming. From this, it locates and extracts the target file specifically used to describe model metadata, such as the modelDescription.XML file in the FMI standard. This target file (XML format) is parsed to identify the structured portions defining model variables. Parameter information is extracted by finding nodes with specific attributes (such as causality="parameter"), i.e., parameter variable nodes. This information includes at least the parameter name and current value, and usually also includes parameter descriptions, data types, units, etc., forming a complete digital profile of each parameter. During the parsing process, the source simulation model file to which each parameter belongs is recorded, laying the foundation for subsequent centralized management and traceability.

[0035] S103. Based on the parameter information parsed from all simulation model files, construct a parameter management interface.

[0036] The parameter management interface refers to a visual graphical user interface that provides users with the ability to view, edit, and filter parameters. Based on the parameter-model mapping table, this interface provides a unified display and management of parameter information scattered across different models.

[0037] Using all the parameter information extracted and associated in the preceding steps, a graphical parameter management interface is generated. This interface is primarily tabular, logically grouping parameters according to their model origin and clearly displaying each parameter's name, current value, and description. Simultaneously, the interface provides powerful interactive functions, such as filtering by name or model, sorting, and global search. Each parameter value is equipped with type-matched editable input controls (such as numeric input boxes and dropdown selection boxes), enabling users to intuitively and efficiently browse and manage all parameters throughout the entire project.

[0038] In one possible implementation, the step of constructing a parameter management interface based on the parameter information parsed from all simulation model files includes: establishing an association between the parameter information and the model to obtain a parameter-model mapping table; and based on the parameter-model mapping table, grouping according to the simulation model file to which each parameter belongs, and displaying the parameter information of all parameters in tabular form.

[0039] A parameter-model mapping table is a data structure built in memory or a database to record and maintain the correspondence between all parameter information parsed from various simulation model files and their respective source simulation model files. This mapping table is key to achieving centralized parameter management and traceability. The parameter management interface supports filtering, sorting, and keyword search functions based on parameter name, the name of the simulation model file to which the parameter belongs.

[0040] S104. In response to the parameter modification instruction received on the parameter management interface, modify the target file corresponding to the parameter information indicated by the parameter modification instruction, and repackage the modified target file into the corresponding simulation model file.

[0041] When a user modifies and confirms the value of a parameter through the aforementioned management interface, the system receives a modification instruction for that specific parameter. The system doesn't merely update the interface display; instead, it directly locates the target file storing the original definition of this parameter based on the instruction. The system accesses the simulation model file containing the target file, finds it, and modifies the specific numerical attributes of the corresponding parameter. After modification, it ensures that the updated target file is correctly repackaged back into its parent simulation model file, maintaining the integrity of the original file format and structure. Through this step, the user's actions on the interface are automatically and accurately synchronized and saved to the underlying simulation model file, completing a closed loop from user interaction to model file update.

[0042] The following embodiment illustrates a parameter processing method provided in this application. See also... Figure 2 , Figure 2A flowchart of another parameter processing method provided in this application embodiment includes: S201, FMU file scanning and extraction.

[0043] The system initiates a comprehensive search of the specified project directory, covering not only the directory itself but also all its subdirectories at all levels to ensure that no potential simulation model files are missed. During the search, the system performs precise filtering based on file extensions, automatically identifying and aggregating all files with the extension .FMU. These files represent the individual model files included in the integrated simulation project, laying the groundwork for subsequent unified extraction of parameter information.

[0044] Since FMU files are essentially ZIP archives, the system will decompress each FMU file according to the corresponding archive parsing rules. The decompression process strictly adheres to file compression standards to ensure that internal data is not corrupted or lost. After decompression, the system automatically accesses and displays the complete internal structure of the file, clearly showing the hierarchical relationships of folders such as binaries, resources, and sources, as well as various related files, providing clear path guidance for accurately locating parameter-related files later.

[0045] Within the file system corresponding to each decompressed FMU file, the system performs a targeted search. Focusing on finding the XML format file that carries model parameter information, the system accurately locates the target XML file from among numerous decompressed files by identifying file format characteristics, naming patterns, and functional association attributes. This XML file is the key carrier of core model parameter information; successful location provides a direct and effective data source for subsequent parameter information parsing and extraction.

[0046] S202, Parameter Information Analysis.

[0047] The system reads the entire content of the target XML file and uses an XML parser to construct its Document Object Model (DOM). The core of the parsing lies in identifying and locating specific nodes in the file that are dedicated to defining model parameters. These nodes typically follow certain naming rules and attribute specifications; for example, in files conforming to the FMI standard, they are wrapped within specific tag levels. Through parsing, the system can clearly understand the file's logical structure, thereby accurately locating the source locations of all stored parameter definitions, preparing for subsequent information extraction.

[0048] Parameter information can include parameter name (name), current parameter value (Real start), and parameter description (Description). Within each defined parameter definition node, the system extracts key parameter attributes one by one. The parameter name is obtained from the `name` attribute of each node; this name is the core identifier distinguishing different parameters. The value of the `start` attribute is extracted from the `Real` tags nested under the node, serving as the parameter's current value and intuitively reflecting its initial configuration state. Simultaneously, the `description` attribute of the node is read to obtain the parameter description information, helping users understand the parameter's function and purpose. During the extraction process, the attribute information undergoes integrity verification to ensure that no core attributes of each parameter are missing, providing comprehensive and reliable data support for centralized parameter management.

[0049] To achieve precise association between parameters and their corresponding models, the system establishes a mapping relationship between the extracted attribute information of each parameter and its corresponding FMU model. The mapping includes core data such as parameter name, current parameter value, and parameter description, as well as key identifiers such as the filename and storage path of the FMU model to which it belongs. This is ultimately integrated into a parameter-model mapping table. This table clearly presents the affiliation of each parameter, providing data for the grouped display in the subsequent parameter management interface. It also enables quick location of the FMU model and target file to which a parameter belongs when it is modified, significantly improving the efficiency and accuracy of parameter management.

[0050] S203, Implementation of centralized parameter management interface.

[0051] The unified parameter display is based on all parsed parameter information, establishing a clear parameter organization logic within the graphical user interface. The interface presents parameters grouped according to their respective FMU models, with each model corresponding to an independent parameter set area. This allows users to intuitively distinguish parameters from different models, avoiding confusion between parameters from multiple models. Basic information for all parameters is neatly displayed in tabular form, with columns covering key information such as parameter name, current value, and description. The data is clearly and systematically arranged, facilitating quick browsing and comparison. The interface also supports diverse parameter search functions. Users can filter by model name, parameter type, and other criteria, and sort by parameter name or numerical value in ascending or descending order. They can also perform precise searches by entering keywords to quickly locate target parameters, significantly improving parameter retrieval efficiency.

[0052] The parameter value editing function provides editable input controls adapted to the data type of each parameter. Users can modify parameter values ​​directly within the current management interface without navigating to other interfaces, making the operation simple and efficient. To ensure the accuracy of parameter modifications, the system incorporates multiple verification mechanisms. Data type verification automatically checks whether the input content conforms to the preset requirements for integer, floating-point, and Boolean values, eliminating format errors; unit consistency checks compare the units of the input value with the original units of the parameter to avoid simulation data anomalies caused by unit confusion; parameter value range verification refers to the preset reasonable range of the parameter to determine whether the modified value is within the valid range, preventing extreme values ​​from affecting simulation results. These multiple verification mechanisms effectively reduce erroneous modifications, ensure the reliability of parameter configuration, and guarantee the accuracy of subsequent simulation calculations.

[0053] S204. Parameter modification and distribution.

[0054] The parameter modification logging process comprehensively tracks and records all parameter adjustment operations performed by the user on the parameter management interface. The system automatically captures key information for each modification, including the unique identifier of the modified parameter, the name of the associated FMU model, the original value before modification, the target value after modification, the modification timestamp, and the user's identifier. This information is then integrated into a complete modification log set. This log set not only provides a traceable basis for parameter modification operations, facilitating users' subsequent query of historical modification paths, but also supports parameter configuration rollback operations based on these records when simulation results do not meet expectations, significantly improving the security and flexibility of parameter management.

[0055] For each modified parameter's corresponding FMU file, the update process offers two efficient update methods. The first method involves unzipping the target FMU file to a temporary directory and quickly locating the XML file storing the parameter information within the unzipped file structure. The second method utilizes a professional ZIP file operation interface to directly access the internal structure of the FMU archive, accurately locating the target XML file without complete unzipping, significantly improving operational efficiency. Regardless of the method used, the system quickly matches the parameter definition node in the XML file corresponding to the modified parameter based on the parameter-model mapping table association information. Subsequently, it updates the attribute content representing the parameter's current value in that node to the user-modified value. The entire update process strictly adheres to the original syntax of the XML file, maintaining the file format and encoding unchanged to prevent model malfunction due to abnormal file structure.

[0056] The file repackaging process integrates the modified XML file back into the original FMU compressed package. During packaging, the system fully preserves the original folder hierarchy within the FMU file, including core directories such as binaries, resources, and sources, while ensuring that all original files except the target XML file are unaffected and fully preserved. The repackaged FMU file strictly adheres to the original compression standards, maintaining the same compression level as the original file to ensure that it can be correctly recognized and loaded by various simulation tools. The repackaged FMU file contains the updated parameter configurations while maintaining the integrity and compatibility of the original file, laying a solid foundation for subsequent simulation execution.

[0057] S205, Simulation Execution.

[0058] During the model loading process, the system supports two flexible loading methods to adapt to different engineering needs. One is batch loading mode, which loads all updated FMU files into the simulation environment at once, eliminating the need to operate on individual models individually and significantly improving loading efficiency for multi-model integration projects. The other is on-demand loading mode, where users can select only key or modified FMU files based on simulation scenario requirements, reducing resource consumption. During loading, the system automatically verifies the integrity and format compliance of the FMU files. If file corruption, structural abnormalities, or parameter configuration incompatibility are detected, clear error messages will be output immediately, indicating the abnormal file name and problem type, facilitating quick troubleshooting and ensuring the simulation environment can correctly recognize and read all loaded model files.

[0059] Parameter value application verification is a crucial step in ensuring simulation accuracy. After the simulation environment successfully loads the FMU file, it automatically reads the current values ​​of the modified parameters from the XML target files within each file and compares them one by one with the corresponding target values ​​in the parameter modification record set. The comparison process covers all modified parameters, including core information such as parameter name, model to which it belongs, and modified value, ensuring no omissions. If the comparison results of all parameters are completely consistent, it indicates that the parameters have been successfully applied, and the system automatically proceeds to the subsequent simulation calculation steps after verification. If there are inconsistencies in values ​​or missing parameters, the system will immediately output detailed error messages, clearly indicating the name of the inconsistent parameter, the FMU file to which it belongs, and the current read value, awaiting user confirmation and handling to avoid simulation result distortion due to incorrect parameter application.

[0060] The simulation triggering method is flexibly configurable. It can automatically start the simulation after parameter modifications are issued and verified, achieving seamless integration between parameter adjustment and simulation execution, reducing manual intervention. Alternatively, users can manually trigger the simulation through the simulation control interface, allowing for flexible scheduling based on project progress. During simulation, the simulation engine's basic calculation configuration prioritizes the parameters defined in the default simulation experiment nodes of the original FMU file, including calculation step size, start time, and stop time, ensuring simulation continuity. Users can also customize these configurations before simulation starts to meet the accuracy and efficiency requirements of different scenarios. The simulation engine strictly performs calculations based on the updated parameter values, maintaining stability and accuracy throughout the calculation process.

[0061] In the results output and analysis phase, the system offers diverse result presentation formats to meet the analytical needs of different users. Simulation results can be intuitively output in various ways, such as tables, trend curves, and data logs. The output not only includes the complete output data of the model but also automatically extracts key simulation indicators, such as peak values, steady-state values, response times, and fluctuation amplitudes of output variables, allowing users to quickly grasp the core simulation results. Simultaneously, the system supports the comparison of simulation results before and after parameter modifications, automatically aligning key indicator data at the same time point or under the same operating conditions to generate a visual difference report. This clearly presents the impact trend of parameter adjustments on simulation effects, helping users accurately judge the rationality and effectiveness of parameter modifications. This provides data support for subsequent parameter optimization or engineering decisions, achieving an integrated closed-loop process from parameter management to simulation analysis.

[0062] See Figure 3 , Figure 3 This diagram illustrates the core architecture and data flow of the parameter processing system described in this application. The system enables automated and centralized management of parameters from multiple models in an integrated simulation project.

[0063] The entire process begins at the project file layer, which stores all the FMU model files required for the simulation project, including FMU model 1, FMU model 2, and so on up to FMU model n. These files are the physical carriers of parameter information. The core processing system, as the central hub of the architecture, is responsible for scheduling and execution. Its internal FMU parsing and parameter extraction module is activated first. This module reads each FMU model file in the project file layer, decompresses it, and parses the model description files within, thereby completing the raw extraction of parameter information. The extracted parameter information is not stored in a scattered manner, but is sent to a parameter database or cache for structured storage and management. Here, not only are the basic attributes such as the parameter name, value, and description stored, but more importantly, the association between the parameters and the source FMU model is established and maintained, that is, a parameter-model mapping table is generated, which lays the data foundation for subsequent unified management.

[0064] The unified parameter management interface serves as the user's interaction window with the system, displaying content directly from the parameter database / cache. It centrally presents all parameters to the user in a grouped, searchable, and editable manner. Any parameter viewing, filtering, or modification operations performed by the user on this interface are based on this unified and accurate parameter data view.

[0065] Once the user confirms the parameter modifications on the interface, the parameter update and delivery engine begins its work. Based on the mapping relationships in the parameter database / cache, this engine precisely locates the original FMU model file that needs modification. It accesses the file's internal structure, updates the parameter values ​​in the corresponding model description file, and then repackages the modified file into a complete FMU format.

[0066] Finally, the modified FMU model file is written back to the project file layer, overwriting or replacing the original file, thus completing a closed loop from user instructions to model file updates. The entire process embodies an integrated automated processing workflow from decentralized extraction, centralized management, interactive modification to precise distribution.

[0067] The above are some specific implementations of the parameter processing method provided in the embodiments of this application. Based on this, this application also provides a corresponding parameter processing system. The system provided in the embodiments of this application will be described below from the perspective of functional modularity. Figure 4 This is a structural diagram of a parameter processing system provided in an embodiment of this application.

[0068] The system includes: Extraction unit 110 is used to obtain the simulation project directory and extract multiple simulation model files contained in the simulation project directory; The parsing unit 111 is used to extract the target file describing the model parameters from each simulation model file, and parse the parameter information from the target file; Building unit 112 is used to build a parameter management interface based on the parameter information parsed from all simulation model files; Modification unit 113 is used to respond to a parameter modification instruction received on the parameter management interface, modify the target file corresponding to the parameter information indicated by the parameter modification instruction, and repackage the modified target file into the corresponding simulation model file.

[0069] This application also provides corresponding devices and computer storage media for implementing the parameter processing scheme provided in this application.

[0070] The device includes a memory and a processor. The memory is used to store instructions or code, and the processor is used to execute the instructions or code to cause the device to perform the parameter processing method described in any embodiment of this application.

[0071] The computer storage medium stores code, and when the code is run, the device running the code implements the parameter processing method described in any embodiment of this application.

[0072] It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the systems or apparatus disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple, and relevant parts can be referred to the method section.

[0073] It should be understood that in this application, "at least one" refers to one or more items, and "more" refers to two or more items. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: only A exists, only B exists, and both A and B exist simultaneously, 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" or similar expressions refer to any combination of these items, including any combination of singular or plural items. For example, "at least one" of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0074] It should be understood that the terms center, longitudinal, transverse, up, down, front, back, left, right, vertical, horizontal, top, bottom, inside, outside, etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the present invention.

[0075] It should be noted that, unless otherwise explicitly specified and limited, the terms installation, connection, and linking should be interpreted broadly. For example, they can refer to fixed connections, detachable connections, or integral connections; they can refer to mechanical connections or electrical connections; they can refer to direct connections or indirect connections through an intermediate medium; and they can refer to the internal communication between two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0076] It should also be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the statement "including a…" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0077] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0078] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A parameter processing method, characterized in that, The method includes: Obtain the simulation project directory and extract the multiple simulation model files contained in the simulation project directory; Extract the target file describing the model parameters from each simulation model file, and parse the parameter information from the target file; A parameter management interface is constructed based on the parameter information parsed from all simulation model files; In response to a parameter modification command received on the parameter management interface, the target file corresponding to the parameter information indicated by the parameter modification command is modified, and the modified target file is repackaged into the corresponding simulation model file.

2. The method according to claim 1, characterized in that, The extraction of multiple simulation model files contained in the simulation project directory includes: Traverse the specified integrated simulation project directory and its corresponding subdirectories to extract all simulation model files with extensions including .fmu.

3. The method according to claim 1, characterized in that, The step of extracting the target file describing the model parameters from each simulation model file includes: Unzip the simulation model file as a compressed package; Based on the decompressed simulation model file, extract the XML file describing the model parameters.

4. The method according to claim 1, characterized in that, The parameter information includes parameter name, current parameter value, and parameter description information. Parsing the parameter information from the target file includes: Parse the target file and read the model variable definition nodes in the target file; From the model variable definition nodes, identify the parameter variable nodes used to define model parameters; Extract the parameter name, current parameter value, and parameter description information from the parameter variable node.

5. The method according to claim 1, characterized in that, The parameter management interface is constructed based on the parameter information parsed from all simulation model files, including: The parameter information is associated with the corresponding simulation model file to obtain a parameter-model mapping table; Based on the parameter-model mapping table, each parameter is grouped according to the simulation model file to which it belongs, and the parameter information of all parameters is displayed in a table. The parameter management interface supports filtering, sorting, and keyword search functions based on parameter name, simulation model file name to which the parameter belongs.

6. The method according to claim 5, characterized in that, The method further includes: Configure an editable input control for the current value of each parameter in the table, wherein the input control is adapted to the data type corresponding to the parameter.

7. The method according to claim 5, characterized in that, The modification of the target file corresponding to the parameter information indicated by the parameter modification instruction, and the re-encapsulation of the modified target file into the corresponding simulation model file, includes: Based on the parameter-model mapping table, determine the simulation model file to which the parameter information indicated by the parameter modification instruction belongs; The simulation model file can be decompressed or its internal structure accessed to modify the target file inside the simulation model file that describes the model parameters. In the target file, locate the parameter variable node corresponding to the parameter information indicated by the parameter modification instruction; Based on the parameter information indicated by the parameter modification instruction, the attribute representing the current value of the parameter in the parameter variable node is updated; The modified target file is repackaged into a compressed file format, while the compressed file format remains unchanged.

8. The method according to claim 1, characterized in that, The method further includes: Load the updated simulation model file into the simulation environment and verify whether the parameter values ​​read by the simulation environment from the loaded simulation model file are consistent with the updated parameter information. Simulation calculations are performed in the simulation environment based on verified and consistent parameter values.

9. A parameter processing system, characterized in that, The system includes: The extraction unit is used to obtain the simulation project directory and extract multiple simulation model files contained in the simulation project directory; The parsing unit is used to extract the target file describing the model parameters from each simulation model file, and parse the parameter information from the target file; The building unit is used to construct the parameter management interface based on the parameter information parsed from all simulation model files; The modification unit is used to respond to the parameter modification command received on the parameter management interface, modify the target file corresponding to the parameter information indicated by the parameter modification command, and repackage the modified target file into the corresponding simulation model file.

10. An electronic device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the parameter processing method as described in any one of claims 1-8.

Images