Model code version management method and device, equipment and storage medium

Abstract

The embodiment of the invention discloses a code version management method and device of a model, equipment and a storage medium, and the method comprises the steps: generating updated platform codes of at least two to-be-updated platforms corresponding to an updated model under the condition that version updating of a target model is detected; determining a model code association table based on the updated model and the updated platform code; wherein the model code association table is used for representing a version corresponding relationship between the updated model and the updated platform code; and storing the model code association table in a preset database to complete a version management step for the target model. According to the technical scheme provided by the embodiment of the invention, the problem of version management limitation caused by version management generally aiming at the code or the model in the prior art is solved, the version corresponding relationship between the model and the multi-platform code can be established, the coverage range of version management is expanded, and convenience is provided for subsequent software automatic integration.

Description

Technical Field

[0001] Embodiments of the present invention relate to the technical field of model code management, and in particular to a model code version management method, apparatus, device and storage medium. Background Art

[0002] At present, with the increasing number of controller product platforms, the development of product control models has gradually shifted to the development of model libraries, that is, a Simulink model can be applied to multiple platform products. Among them, the SIMULINK model is a tool in MATLAB software for modeling, simulating and analyzing multi-domain dynamic systems. However, the existing version management technology mainly manages the version of the code itself or the model itself, which has limitations in version management and is not conducive to software quality control. Summary of the invention

[0003] The embodiments of the present invention provide a model code version management method, apparatus, device and storage medium, which can establish a version correspondence between the model and multi-platform code, improve the coverage of version management, and facilitate subsequent software automation integration.

[0004] In a first aspect, an embodiment of the present invention provides a code version management method for a model, the method comprising:

[0005] When it is detected that the target model is updated, generating updated platform codes of at least two to-be-updated platforms corresponding to the updated model;

[0006] Based on the updated model and the updated platform code, a model-code association table is determined; wherein the model-code association table is used to indicate the version correspondence between the updated model and the updated platform code;

[0007] The model code association table is stored in a preset database to complete the version management step for the target model.

[0008] In a second aspect, an embodiment of the present invention provides a code version management device for a model, the device comprising:

[0009] A platform code generation module, configured to generate updated platform codes of at least two to-be-updated platforms corresponding to the updated model when it is detected that the target model is updated;

[0010] An association table generating module, used to determine a model-code association table based on the updated model and the updated platform code; wherein the model-code association table is used to represent the version correspondence between the updated model and the updated platform code;

[0011] The association table storage module is used to store the model code association table in a preset database to complete the version management step for the target model.

[0012] In a third aspect, an embodiment of the present invention provides a computer device, the computer device comprising:

[0013] one or more processors;

[0014] A memory for storing one or more programs;

[0015] When the one or more programs are executed by the one or more processors, the one or more processors implement the code version management method of the model described in any embodiment.

[0016] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the code version management method of the model described in any one of the embodiments.

[0017] The technical solution provided by the embodiment of the present invention generates updated platform codes of at least two platforms to be updated corresponding to the updated model when a version update of the target model is detected; a model code association table is determined based on the updated model and the updated platform code; wherein the model code association table is used to represent the version correspondence between the updated model and the updated platform code. The technical solution of the embodiment of the present invention solves the problem of the limitations of version management in the prior art, which is usually performed on the code itself or the model itself. It can establish a version correspondence between the model and multi-platform codes, improve the coverage of version management, and facilitate subsequent software automation integration. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 is a flow chart of a code version management method of a model provided by an embodiment of the present invention;

[0019] Figure 2 It is a flow chart of a code version management method of another model provided by an embodiment of the present invention;

[0020] Figure 3 It is a workflow diagram for code version management of a model provided by an embodiment of the present invention;

[0021] Figure 4 is a schematic diagram of a folder hierarchy structure provided by an embodiment of the present invention;

[0022] Figure 5 It is a structural diagram of a code version management device of a model provided by an embodiment of the present invention;

[0023] Figure 6 It is a structural schematic diagram of a computer device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0024] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0025] Figure 1 It is a flow chart of a code version management method for a model provided by an embodiment of the present invention. The embodiment of the present invention can be applied to the scenario of managing the version of the target model and the corresponding platform code. The method can be executed by a code version management device of the model, and the device can be implemented by software and / or hardware.

[0026] like Figure 1 As shown, the code version management method of the model includes the following steps:

[0027] S110 . When it is detected that the target model is updated, generating updated platform codes of at least two to-be-updated platforms corresponding to the updated model.

[0028] The target model may be a model that requires version management. The technical solution of the embodiment of the present invention can automatically update the target model code on different platforms after the target model version is updated, and establish a version association relationship between the updated target model and the updated platform code, so as to facilitate the subsequent management of the software program according to the version association relationship.

[0029] Furthermore, the platform to be updated may be a platform that needs to undergo a code update. Specifically, the platform to be updated may be manually set or automatically determined. Exemplarily, a platform having a code corresponding to a target model may be used as the platform to be updated. That is, after the target model is updated to a new version, the code version corresponding to the target model in the platform to be updated also needs to be updated. Furthermore, a code generation tool may be a tool for generating a new version of code for the target model in the platform to be updated. Code generation parameters may be parameters required to generate a new version of code corresponding to the target model in the platform to be updated. Specifically, the code generation tool may automatically determine the corresponding code generation parameters based on the target model after the version update.

[0030] Furthermore, the updated platform code may be the code corresponding to the target model in the platform to be updated after the version is updated. Specifically, after the target model is updated, the code version of the target model in the platform to be updated may be updated based on a preset platform code generation tool to obtain the updated platform code.

[0031] S120: Determine a model-code association table based on the updated model and the updated platform code.

[0032] The model code association table can be used to indicate the version correspondence between the updated model and the updated platform code. Specifically, the version numbers of the updated model and the updated platform code can be filled in the preset model code association table to obtain the model code association table.

[0033] S130: Storing the model code association table in a preset database to complete the version management step for the target model.

[0034] The preset model database may be a preset database for storing the association relationship between the target model and the platform code. After determining the target model association file, the model code association table may be stored in the preset database, that is, the version association relationship between the target model and the platform code after the version update is stored in the preset database.

[0035] The technical solution provided by the embodiment of the present invention generates updated platform codes of at least two platforms to be updated corresponding to the updated model when a version update of the target model is detected; a model code association table is determined based on the updated model and the updated platform code; wherein the model code association table is used to represent the version correspondence between the updated model and the updated platform code. The technical solution of the embodiment of the present invention solves the problem of the limitations of version management in the prior art, which usually involves version management for the code itself or the model itself. The version correspondence between the model and the multi-platform code can be established, thereby improving the coverage of version management and facilitating subsequent software automation integration.

[0036] Figure 2 It is a flow chart of a code version management method for another model provided by an embodiment of the present invention. The embodiment of the present invention can be applied to the scenario of managing the versions of the target model and the corresponding platform code. Based on the above embodiment, this embodiment further explains how to generate updated platform codes of at least two to-be-updated platforms corresponding to the updated model; how to determine the model code association table based on the updated model and the updated platform code; and how to store the model code association table in a preset database. The device can be implemented by software and / or hardware and integrated in a computer device with application development function.

[0037] like Figure 2 As shown, the code version management method of the model includes the following steps:

[0038] S210 . When it is detected that the target model is undergoing a version update, for each platform to be updated, determine a code generation parameter based on a code generation tool of the platform to be updated.

[0039] The target model may be a model that requires version management. The technical solution of the embodiment of the present invention can automatically update the target model code on different platforms after the target model version is updated, and establish a version association relationship between the updated target model and the updated platform code, so as to facilitate the subsequent management of the software program according to the version association relationship.

[0040] Furthermore, the platform to be updated may be a platform that needs to undergo a code update. Specifically, the platform to be updated may be manually set or automatically determined. Exemplarily, a platform having a code corresponding to a target model may be used as the platform to be updated. That is, after the target model is updated to a new version, the code version corresponding to the target model in the platform to be updated also needs to be updated. Furthermore, a code generation tool may be a tool for generating a new version of code for the target model in the platform to be updated. Code generation parameters may be parameters required to generate a new version of code corresponding to the target model in the platform to be updated. Specifically, the code generation tool may automatically determine the corresponding code generation parameters based on the target model after the version update.

[0041] Optionally, detecting that the target model is updated for version includes: determining that the version of the target model is updated when detecting that a model version number of the target model is changed and / or receiving a model version update instruction regarding the target model.

[0042] Among them, the model version number can be the version number of the target model. Specifically, after the target model version is updated, the version number corresponding to the target model will be automatically generated. Therefore, after detecting that the model version number of the target model has changed, the model version number of the target model can be determined. Further, the model version update instruction can be a trigger instruction for updating the target model version. Specifically, the user can set relevant parameters for the version update of the target model on the preset interactive interface. After setting the relevant parameters, the corresponding update trigger control can be clicked in the preset interface so that the device receives the model version update instruction, and subsequently starts to establish a version association relationship between the updated target model and the updated platform code.

[0043] S220: Generate updated platform code corresponding to the platform to be updated according to the code generation parameters and the updated model.

[0044] The updated platform code may be the code corresponding to the target model on the platform to be updated after the version is updated. Specifically, the updated platform code corresponding to the platform to be updated may be automatically generated according to the code generation parameters and the updated model.

[0045] S230: Obtain an initial association table, determine an updated model version number corresponding to the updated model, and determine an updated code version number corresponding to the updated platform code.

[0046] Among them, the initial association table can be a table of version associations between the target model and the platform code that has not been updated. Specifically, the initial association table includes multiple items to be associated, which can represent the version correspondence between the target model and the platform code. Among them, the association items can include a model name, a model version number, and at least two platform code version numbers. Further, the updated model version number can be the version number of the target model after the version update. Specifically, after the target model is updated, the updated model version number corresponding to the target model after the version update can be automatically generated. Further, the updated code version number can be the version number of the platform code after the version update. Specifically, after the platform code version is updated, the version number corresponding to the updated platform code can be automatically generated, and then the updated code version number is obtained.

[0047] Optionally, determining the updated code version number corresponding to the updated platform code includes: obtaining the previous version number of the previous version of the platform code corresponding to the updated platform code; incrementing the last number of the previous version number based on a preset ascending order, and using the incremented previous version number as the updated code version number.

[0048] Among them, the previous version number can be the version number of the platform code before the version update. Specifically, the previous version number of the previous version corresponding to the current version (that is, the updated version) can be determined from the historical version number of the platform code. Further, the preset incremental sequence can be a preset ascending and descending order for adjusting the version number after the code version is updated. Exemplarily, the preset incremental sequence can be to add one to the last digit of the previous version number after the version is updated, and then use the new version number after the last digit is added by one as the updated code version number.

[0049] S240. For each item to be associated in the initial association table, determine the filling result corresponding to the item to be associated according to the updated model version number and the updated code version number, fill the filling result into the to-be-filled column corresponding to the item to be associated, and obtain the model-code association table.

[0050] The model code association table can be used to indicate the version correspondence between the updated model and the updated platform code. Specifically, for each item to be associated in the presented association table, the filling result corresponding to the item to be associated can be matched from the updated model version number and the updated code version number, and the filling result can be filled into the to-be-filled column corresponding to the item to be associated to obtain the model code association table.

[0051] Exemplarily, Table 1 is a schematic diagram of a model code association table provided by an embodiment of the present invention. As shown in Table 1, the model code association table includes items such as a model name, a model version number, and a plurality of two platform code version numbers.

[0052] Table 1: Model code association table

[0053]

[0054] As shown in Table 1, the model code association table includes items such as a model name, a model version number, and a plurality of two platform code version numbers.

[0055] S250. Match the target model associated file corresponding to the target model from a preset database, and store the model code association table in a subpath corresponding to the target model associated file.

[0056] Among them, the preset model association file can be a preset file for storing the association relationship between the target model and the platform code. Specifically, the model identification information of the target model can be obtained, and then the model association file corresponding to the model identification information can be matched from the preset database, and the matched model association file can be used as the target model association file. Furthermore, after determining the target model association file, the model code association table can be stored in the subpath corresponding to the target model association file. That is, the version association relationship between the target model and the platform code after the version update is stored in the preset database.

[0057] Optionally, when the model association file corresponding to the target model cannot be matched in the preset database, an initial model association file for the target model can be established, and the model code association table is stored in the initial model association file.

[0058] The initial model association file may be an empty file for recording the version association relationship between the target model and the platform code. Specifically, when the model association file corresponding to the model identification information cannot be matched in the preset database, an initial model association file for the target model may be established, and the model code association table may be stored in the initial model association file. After the initial model association file is created, an association relationship may be established between the initial model association file and the model identification information of the target model. For example, the model name of the target model may be included in the file name of the initial model association file.

[0059] For example, Figure 3 This is a workflow diagram for managing model code versions provided by an embodiment of the present invention. Figure 3 As shown in the figure, the workflow for code version management of the model includes the following steps:

[0060] The first step is to establish a folder hierarchy for the model and the multi-platform code generated by the model, and use this folder hierarchy as the basis for code version management. For example, Figure 4 It is a schematic diagram of the structure of a folder hierarchy provided by an embodiment of the present invention.

[0061] The second step is to call the API (Application Programming Interface) of the version management tool, and complete the automatic upload of the platform codes corresponding to the model based on the model and code folders established in the first step. The operation process of the entire script is: real-time monitoring of model changes in the model library, once a new model is uploaded, the model generation code tool is called to generate the C code of the corresponding platform with the configuration file of the corresponding platform. And save the C code in the folder of the corresponding platform. Then call the API of the code management platform to update the code and version number of the entire folder. In this process, the version number of each platform code can be obtained, which is convenient for database storage and the establishment of the corresponding relationship between model code versions.

[0062] The third step is to establish a database of the correspondence between the model version and the code version of each platform generated by it. The model version can be obtained when the model is uploaded to the code management platform. The code version corresponding to each platform is obtained by calling the API of the code management platform after the automatic upload of the code is completed.

[0063] Compared with the previous method of only controlling the model version or only controlling the code version, this patent realizes the dual control of the model and the generated code by automating the process of generating C code from the model and uploading the generated code to the code management platform, thus strengthening the quality control of the code. At the same time, by establishing a corresponding relationship database of the model corresponding to the C code of multiple platforms, the model library and the code library are quickly indexed, laying the foundation for automatic code extraction during subsequent software integration.

[0064] The technical solution provided by the embodiment of the present invention is to determine the code generation parameters for each platform to be updated based on the code generation tool of the platform to be updated when the target model is detected to be updated; generate the updated platform code corresponding to the platform to be updated according to the code generation parameters and the updated model; obtain the initial association table, determine the updated model version number corresponding to the updated model, and determine the updated code version number corresponding to the updated platform code; for each item to be associated in the initial association table, determine the filling result corresponding to the item to be associated according to the updated model version number and the updated code version number, fill the filling result into the to-be-filled column corresponding to the item to be associated, and obtain the model code association table; match the target model association file corresponding to the target model from the preset database, and store the model code association table in the subpath corresponding to the target model association file. The technical solution of the embodiment of the present invention solves the problem that the prior art usually performs version management on the code itself or the model itself, and there are limitations in version management. It can establish the version correspondence between the model and the multi-platform code, improve the coverage of version management, and provide convenience for subsequent software automation integration.

[0065] Figure 5 It is a structural diagram of a code version management device for a model provided in an embodiment of the present invention. The embodiment of the present invention can be applied to the scenario of managing the version of the target model and the corresponding platform code. The device can be implemented by software and / or hardware and integrated into a computer device with application development function.

[0066] like Figure 5 As shown, the model code version management device includes: a platform code generation module 310, an association table generation module 320 and an association table storage module 330.

[0067] Among them, the platform code generation module 310 is used to generate updated platform codes of at least two to-be-updated platforms corresponding to the updated model when it is detected that the target model has been updated; the association table generation module 320 is used to determine the model code association table based on the updated model and the updated platform code; wherein the model code association table is used to represent the version correspondence between the updated model and the updated platform code; the association table storage module 330 is used to store the model code association table in a preset database to complete the version management steps for the target model.

[0068] The technical solution provided by the embodiment of the present invention generates updated platform codes of at least two platforms to be updated corresponding to the updated model when a version update of the target model is detected; a model code association table is determined based on the updated model and the updated platform code; wherein the model code association table is used to represent the version correspondence between the updated model and the updated platform code. The technical solution of the embodiment of the present invention solves the problem of the limitations of version management in the prior art, which is usually performed on the code itself or the model itself. It can establish a version correspondence between the model and multi-platform codes, improve the coverage of version management, and facilitate subsequent software automation integration.

[0069] In an optional implementation, the platform code generation module 310 includes: a model update detection unit, configured to: determine whether the version of the target model has been updated upon detecting that the model version number of the target model has changed and / or receiving a model version update instruction regarding the target model.

[0070] In an optional implementation, the platform code generation module 310 includes: a platform code update unit, used to: for each platform to be updated, determine code generation parameters based on the code generation tool of the platform to be updated; and generate updated platform code corresponding to the platform to be updated according to the code generation parameters and the updated model.

[0071] In an optional implementation, the association table generation module 320 is specifically used to: obtain an initial association table, determine the updated model version number corresponding to the updated model, and determine the updated code version number corresponding to the updated platform code; for each item to be associated in the initial association table, determine the fill result corresponding to the item to be associated according to the updated model version number and the updated code version number; wherein the item to be associated includes: a model name, a model version number, and at least two platform code version numbers; fill the fill result into the to-be-filled column corresponding to the item to be associated to obtain the model-code association table.

[0072] In an optional embodiment, the association table generation module 320 includes: a code version number determination unit, used to: obtain the previous version number of the previous version of the platform code corresponding to the updated platform code; increment the last number of the previous version number based on a preset ascending order, and use the incremented previous version number as the updated code version number.

[0073] In an optional implementation, the association table storage module 330 is specifically used to: after determining the model code association table, match the target model association file corresponding to the target model from a preset database; and store the model code association table in a subpath corresponding to the target model association file.

[0074] In an optional embodiment, the association table storage module 330 includes: an association file creation unit, which is used to: when the model association file corresponding to the target model cannot be matched in the preset database, establish an initial model association file about the target model, and store the model code association table in the initial model association file.

[0075] The model code version management device provided in the embodiment of the present invention can execute the model code version management method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0076] Figure 6 A schematic diagram of the structure of a computer device provided in an embodiment of the present invention. Figure 6 A block diagram of an exemplary computer device 12 suitable for use in implementing embodiments of the present invention is shown. Figure 6 The computer device 12 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention. The computer device 12 can be any terminal device with computing capability and can be configured in the code version management device of the model.

[0077] like Figure 6 As shown, the computer device 12 is in the form of a general-purpose computing device. The components of the computer device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that connects various system components (including the system memory 28 and the processing unit 16).

[0078] The bus 18 may be one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. For example, these architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MAC) bus, an Enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.

[0079] The computer device 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the computer device 12, including volatile and non-volatile media, removable and non-removable media.

[0080] The system memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache 32. The computer device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 34 may be used to read and write non-removable, non-volatile magnetic media ( Figure 6 not shown, usually called a "hard drive"). Although Figure 6 Not shown in the figure, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 18 via one or more data medium interfaces. The system memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present invention.

[0081] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in system memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. Program modules 42 generally perform the functions and / or methods of the embodiments described herein.

[0082] The computer device 12 may also communicate with one or more external devices 14 (e.g., keyboards, pointing devices, displays 24, etc.), one or more devices that enable a user to interact with the computer device 12, and / or any device that enables the computer device 12 to communicate with one or more other computing devices (e.g., network cards, modems, etc.). Such communication may be performed through an input / output (I / O) interface 22. Furthermore, the computer device 12 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) through a network adapter 20. Figure 6 As shown, the network adapter 20 communicates with other modules of the computer device 12 via the bus 18. It should be understood that although Figure 6 Not shown, other hardware and / or software modules may be used in conjunction with computer device 12, including but not limited to microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0083] The processing unit 16 executes various functional applications and data processing by running the program stored in the system memory 28, for example, implementing the code version management method of the model provided in the embodiment of the present invention, the method comprising:

[0084] When it is detected that the target model is updated, generating updated platform codes of at least two to-be-updated platforms corresponding to the updated model;

[0085] Based on the updated model and the updated platform code, a model-code association table is determined; wherein the model-code association table is used to indicate the version correspondence between the updated model and the updated platform code;

[0086] The model code association table is stored in a preset database to complete the version management step for the target model.

[0087] This embodiment provides a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, the code version management method of the model provided in any embodiment of the present invention is implemented, including:

[0088] When it is detected that the target model is updated, generating updated platform codes of at least two to-be-updated platforms corresponding to the updated model;

[0089] Based on the updated model and the updated platform code, a model-code association table is determined; wherein the model-code association table is used to indicate the version correspondence between the updated model and the updated platform code;

[0090] The model code association table is stored in a preset database to complete the version management step for the target model.

[0091] The computer storage medium of the embodiment of the present invention can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0092] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0093] The program code embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0094] Computer program code for performing the operations of the present invention may be written in one or more programming languages ​​or combinations thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0095] It should be understood by those skilled in the art that the modules or steps of the present invention described above can be implemented by a general-purpose computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, optionally, they can be implemented by a program code executable by a computer device, so that they can be stored in a storage device and executed by the computing device, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0096] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A code version management method for a model, characterized in that: include: When it is detected that the target model is updated, generating updated platform codes of at least two to-be-updated platforms corresponding to the updated model; Based on the updated model and the updated platform code, a model-code association table is determined; wherein the model-code association table is used to indicate the version correspondence between the updated model and the updated platform code; The model code association table is stored in a preset database to complete the version management step for the target model.

2. The method according to claim 1, characterized in that Detecting the target model for version update includes: When it is detected that the model version number of the target model has changed and / or a model version update instruction for the target model has been received, it is determined that the version of the target model has been updated.

3. The method according to claim 1, characterized in that The generating of updated platform codes of at least two to-be-updated platforms corresponding to the updated model includes: For each platform to be updated, determining code generation parameters based on a code generation tool of the platform to be updated; Generate updated platform code corresponding to the platform to be updated according to the code generation parameters and the updated model.

4. The method according to claim 1, characterized in that: The step of determining a model-code association table based on the updated model and the updated platform code comprises: Obtaining an initial association table, determining an updated model version number corresponding to the updated model, and determining an updated code version number corresponding to the updated platform code; For each item to be associated in the initial association table, determine the filling result corresponding to the item to be associated according to the updated model version number and the updated code version number; wherein the item to be associated includes: a model name, a model version number and at least two platform code version numbers; The filling result is filled into the to-be-filled column corresponding to the to-be-associated item to obtain the model code association table.

5. The method according to claim 4, characterized in that The determining the updated code version number corresponding to the updated platform code includes: Obtaining the previous version number of the previous version of the platform code corresponding to the updated platform code; The last number of the previous version number is incremented based on a preset incrementing order, and the incremented previous version number is used as the updated code version number.

6. The method according to claim 1, characterized in that The storing of the model code association table in a preset database comprises: After determining the model code association table, matching the target model association file corresponding to the target model from a preset database; The model code association table is stored in a sub-path corresponding to the target model association file.

7. The method according to claim 6, characterized in that The method further comprises: When the model association file corresponding to the target model cannot be matched in the preset database, an initial model association file for the target model is established, and the model code association table is stored in the initial model association file.

8. A code version management device for a model, characterized in that: The device comprises: A platform code generation module, configured to generate updated platform codes of at least two to-be-updated platforms corresponding to the updated model when it is detected that the target model is updated; An association table generating module, used to determine a model-code association table based on the updated model and the updated platform code; wherein the model-code association table is used to represent the version correspondence between the updated model and the updated platform code; The association table storage module is used to store the model code association table in a preset database to complete the version management step for the target model.

9. A computer device, characterized in that: The computer device comprises: one or more processors; A memory for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the code version management method of the model as described in any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the code version management method of the model as described in any one of claims 1 to 7 is implemented.

Images