Evaluation model debugging method and system of test evaluation system

Abstract

The embodiment of the invention discloses an evaluation model debugging method and system of a test evaluation system. In a specific embodiment, the method comprises the following steps: acquiring a debugging data source file and an interface configuration file in the test evaluation system; local debugging and compiling software is used for loading the model dynamic library, the evaluation model source code is compiled, an evaluation model dynamic library file is generated, and the evaluation model dynamic library file comprises at least one evaluation model; analyzing a debugging data source file according to a column sequence number of the debugging data source file corresponding to an evaluation model interface in the interface configuration file to obtain debugging data corresponding to an evaluation model; sending the debugging data to an input interface of the evaluation model; driving the evaluation model to run, and performing single-step debugging on the running evaluation model by using a debugging compiling environment; and uploading the debugged evaluation model to a test evaluation system through the debugging compiling environment. The debugging difficulty of the evaluation model can be reduced.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and more specifically, to an evaluation model debugging method and system for an experimental evaluation system. Background Art

[0002] Test evaluation is an important means of quantitatively evaluating equipment capabilities. Taking weapons and equipment as an example, before weapons and equipment are equipped to troops, they need to go through the processes of demonstration, project establishment, development, testing, and appraisal. Each process requires a large number of internal and external field tests such as digital simulation tests, semi-physical simulation tests, and flight tests. After being equipped to troops, tactical and combat training and combat exercises are also required. In order to evaluate the equipment capabilities and the effects of tests, training, and exercises, it is necessary to analyze and evaluate the data obtained from simulations, tests, training, and exercises. The test evaluation system based on the B / S architecture (Browser / Server) has technical features such as unified data storage, centralized algorithm scheduling, remote access, browser display, and multi-user parallel evaluation, which can provide users with a safe and stable test evaluation environment. However, when the evaluation index system is complex, the evaluation models are numerous, and the algorithms are complex, if unexpected results or errors occur in the evaluation, the evaluation model needs to be debugged.

[0003] At present, debugging C++ programs under the B / S architecture is usually done online on the server side by attaching processes, etc., so it is impossible to develop and debug multiple people at the same time, the security of the model code cannot be guaranteed, and the evaluation system will not be able to be used normally during the debugging process, which seriously affects the development progress and efficiency of the evaluation system. In addition, the debugging operation steps are complicated, and the technical threshold for the debugger is high. Professional software personnel and system maintenance personnel are required to cooperate in debugging. General model design and development personnel cannot carry out debugging work independently. Summary of the invention

[0004] The object of the present invention is to provide an evaluation model debugging method and system for a test evaluation system to solve at least one of the problems existing in the prior art.

[0005] In order to achieve the above object, the present invention adopts the following technical solutions:

[0006] A first aspect of the present invention provides an evaluation model debugging method for a test evaluation system, comprising:

[0007] Obtain the debugging data source file and interface configuration file in the test evaluation system;

[0008] Using local debugging and compiling software to load the model dynamic library, compile the evaluation model source code, and generate an evaluation model dynamic library file, wherein the evaluation model dynamic library file includes at least one evaluation model;

[0009] Parsing the debugging data source file according to the column number of the debugging data source file corresponding to the evaluation model interface in the interface configuration file to obtain debugging data corresponding to the evaluation model;

[0010] Sending the debugging data to the input interface of the evaluation model;

[0011] Driving the evaluation model to run, and using the debugging and compiling environment to perform single-step debugging on the running evaluation model;

[0012] The debugged evaluation model is uploaded to the test evaluation system through the debugging and compilation environment.

[0013] Optionally, an interface configuration file is used to describe the correspondence between the debugging data source file and the evaluation model interface; the interface configuration file is described in XML language or a text format in a custom format, including the correspondence node between the debugging file and the evaluation model interface, the evaluation model name, the evaluation model description, the debugging file column number and the data type.

[0014] Optionally, sending the debugging data to the input interface of the evaluation model includes: sending the debugging data to the input interface of the evaluation model in parameter form and JSON format.

[0015] Optionally, the debugging data obtains a data structure of parameter items by obtaining a matching relationship with the evaluation model interface and a corresponding data type through the evaluation model interface name in the interface configuration file.

[0016] Optionally, the evaluation model dynamic library file is a dll file and / or a so file.

[0017] A second aspect of the present invention provides an evaluation model debugging system for a test evaluation system, comprising:

[0018] Debug information export module, data source parsing module, evaluation model scheduling module and debugging compilation environment, among which

[0019] The debugging information export module is used to obtain the debugging data source file and interface configuration file in the test evaluation system;

[0020] The debugging and compiling environment is used to load the model dynamic library using the local debugging and compiling software, compile the evaluation model source code, generate an evaluation model dynamic library file, the evaluation model dynamic library file includes at least one evaluation model, and is also used to publish the evaluation model after debugging, and upload the evaluation model after debugging to the test evaluation system;

[0021] The data source parsing module is used to parse the debugging data source file according to the column number of the debugging data source file corresponding to the evaluation model interface in the interface configuration file to obtain debugging data;

[0022] The evaluation model scheduling module is used to send the debugging data to the input interface of the evaluation model to drive the evaluation model to run; and is also used to use the debugging compilation environment to perform single-step debugging on the running evaluation model.

[0023] Optionally, an interface configuration file is used to describe the correspondence between the debugging data source file and the evaluation model interface; the interface configuration file is described in XML language or a text format in a custom format, including the corresponding relationship node between the debugging file and the model interface, the evaluation model name, the evaluation model description, the debugging file column number and the data type.

[0024] Optionally, sending the debugging data to the input interface of the evaluation model includes: sending the debugging data to the input interface of the evaluation model in parameter form and JSON format.

[0025] Optionally, the debugging data obtains a data structure of parameter items by obtaining a matching relationship with the evaluation model interface and a corresponding data type through the evaluation model interface name in the interface configuration file.

[0026] Optionally, the evaluation model dynamic library file is a dll file and / or a so file.

[0027] The beneficial effects of the present invention are as follows:

[0028] The present invention provides an effective technical approach to debugging the evaluation model, which can reduce the difficulty of debugging the evaluation model, improve the debugging efficiency of the evaluation model, increase the utilization rate of the test evaluation system, and ensure the security of the evaluation model, and has broad application prospects. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The specific implementation modes of the present invention are further described in detail below in conjunction with the accompanying drawings.

[0030] Figure 1 A flowchart of an evaluation model debugging method for a test evaluation system provided in an embodiment of the present application.

[0031] Figure 2 A block diagram of an evaluation model debugging system of a test evaluation system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0032] In order to more clearly illustrate the present invention, the following embodiments and accompanying drawings are provided. Figure 1-2The present invention is further described. Similar components in the drawings are indicated by the same reference numerals. Those skilled in the art should understand that the following specific description is illustrative rather than restrictive, and should not be used to limit the scope of protection of the present invention.

[0033] like Figure 1 As shown, a method for debugging an evaluation model system of a test evaluation system includes:

[0034] Obtain the debugging data source file and interface configuration file in the test evaluation system;

[0035] Using local debugging and compiling software to load the model dynamic library, compile the evaluation model source code, and generate an evaluation model dynamic library file, wherein the evaluation model dynamic library file includes at least one evaluation model;

[0036] Parsing the debugging data source file according to the column number of the debugging data source file corresponding to the evaluation model interface in the interface configuration file to obtain debugging data corresponding to the evaluation model;

[0037] Sending the debugging data to the input interface of the evaluation model;

[0038] Driving the evaluation model to run, and using the debugging and compiling environment to perform single-step debugging on the running evaluation model;

[0039] The debugged evaluation model is uploaded to the test evaluation system through the debugging and compilation environment.

[0040] In one possible implementation, an interface configuration file is used to describe the correspondence between a debugging data source file and an evaluation model interface; the interface configuration file is described in XML language or a text format in a custom format, including a debugging file and model interface correspondence node, an evaluation model name, an evaluation model description, a debugging file column number, and a data type.

[0041] In a possible implementation, sending the debugging data to the input interface of the evaluation model includes: sending the debugging data to the input interface of the evaluation model in parameter form and in JSON format.

[0042] In a possible implementation manner, the debugging data obtains a data structure of parameter items by obtaining a matching relationship with the evaluation model interface and a corresponding data type through the evaluation model interface name in the interface configuration file.

[0043] In a possible implementation, the evaluation model dynamic library file is a dll file and / or a so file.

[0044] In a possible implementation, a B / S architecture test evaluation system C++ evaluation model offline debugging method is implemented by a system, which includes: a debugging information export module, a data source parsing module, an evaluation model scheduling module, a debugging compilation environment and an evaluation model source code. The specific steps of the method are:

[0045] The first step is to export debugging information

[0046] The debugging information export module is used to export and download the debugging data source file and interface configuration file in the test evaluation system to the local computer. Among them, the debugging data source file is generally a data file in the format of csv, xlsx, etc., and the interface configuration file is in the form of an XML file, which describes the correspondence between the data source file and the evaluation model interface. The interface configuration file includes nodes describing the evaluation model file name, the correspondence between the debugging file and the model interface, and supports interface mapping of multiple debugging files; the specific correspondence between a debugging file and the model interface, including the model interface name, the debugging file column number, the data type and other information; the specific value of the model interface in the form of a constant, and supports the input of multiple constant values.

[0047] The second step is to build a debugging environment

[0048] Use local debugging and compiling software (generally Visual Studio software) to load the source code of the model dynamic library; configure the debugging and running environment, set the generation file path, model running dependency environment, etc., and set the evaluation model scheduling module as the debugging entry; compile the evaluation model source code to generate an evaluation model dynamic library file, which is a dll file and / or a so file.

[0049] Step 3 Data source analysis

[0050] Before debugging the evaluation model, the data source parsing module obtains the data source file, parses the data source according to the data source file column number corresponding to the model interface in the interface configuration file, and passes the debugging data required for the evaluation model to the evaluation model scheduling module in JSON (JavaScript Object Notation) format. The data parameter description includes the data column number representing the data source file, the value of the column data, and the array value.

[0051] Step 4: Evaluation and Model Debugging

[0052] During the evaluation model debugging process, the evaluation model scheduling module schedules the evaluation model in the evaluation model dynamic library file; calls the evaluation model interface function, and sends the debugging data to the input interface of the evaluation model in the form of parameters, drives the evaluation model to run, and uses the debugging compilation environment to implement single-step debugging of the evaluation model code by setting breakpoints, etc.;

[0053] Among them, the data in the debugging data parameter is matched with the evaluation model interface by the model interface name in the interface configuration file and the corresponding data type to obtain the data structure of the parameter item.

[0054] Step 5: Upload the evaluation model

[0055] After the evaluation model is debugged, it can be published through the debugging compilation environment, and the latest version of the evaluation model can be uploaded to the test evaluation system deployed on the server through the browser page. At this point, the offline debugging of the evaluation model is completed.

[0056] The offline debugging method of the evaluation model in the test evaluation system of the present invention can reduce the debugging difficulty of the evaluation model, improve the debugging efficiency of the evaluation model, increase the utilization rate of the test evaluation platform, ensure the security of the evaluation model, and has broad application prospects. The specific effects are as follows:

[0057] (1) Reduce the difficulty of debugging the evaluation model. The evaluation model debugging process adopts an integrated process, builds a debugging environment for model developers (consistent with the development environment), simplifies the debugging steps (no need to start the test evaluation platform, user login, select evaluation indicators and test data, etc.), and lowers the threshold for model debugging (no need for platform maintenance personnel to cooperate);

[0058] (2) Improve the debugging efficiency of the evaluation model. A debugging environment equivalent to the server side is built locally, so that multiple people can carry out model debugging work on multiple computers at the same time, greatly improving the debugging efficiency of the evaluation model.

[0059] (3) Improve the utilization rate of the test evaluation platform. By adopting the offline debugging method, during the model debugging process, the test evaluation users can carry out the test evaluation work normally. After the evaluation model is debugged, the original model can be uploaded and updated without restarting the test evaluation platform, which does not affect the normal use of the test evaluation platform and improves the utilization rate of the test evaluation platform.

[0060] (4) Ensure the security of the evaluation model. The evaluation model is debugged locally and the model source code is saved on the local computer to avoid code leakage and other problems during server-side debugging, thus ensuring the security of the evaluation model.

[0061] Therefore, the embodiments of the present application provide an effective technical approach for offline debugging of the evaluation model, which can reduce the difficulty of debugging the evaluation model, improve the debugging efficiency of the evaluation model, increase the utilization rate of the test evaluation system, ensure the security of the evaluation model, save human resource investment, thereby bringing huge economic benefits and having broad application prospects.

[0062] In summary, the embodiment of the present application provides an evaluation model debugging method for an experimental evaluation system, which obtains the debugging data source file and interface configuration file in the experimental evaluation system; uses local debugging compilation software to load the model dynamic library, compiles the evaluation model source code, and generates an evaluation model dynamic library file, wherein the evaluation model dynamic library file includes at least one evaluation model; parses the debugging data source file according to the column number of the debugging data source file corresponding to the evaluation model interface in the interface configuration file, and obtains the debugging data corresponding to the evaluation model; sends the debugging data to the input interface of the evaluation model; drives the evaluation model to run, and uses the debugging compilation environment to perform single-step debugging on the running evaluation model; and uploads the debugged evaluation model to the experimental evaluation system through the debugging compilation environment. This realizes offline debugging of the evaluation model, reduces the difficulty of debugging the evaluation model, solves the problems of simultaneous debugging of multiple models and the inability of the evaluation system to be used normally during debugging, thereby shortening the development cycle of the evaluation system and improving the utilization rate of the evaluation system.

[0063] Based on the same technical concept, the embodiment of the present application provides an evaluation model debugging system for a test evaluation system, such as Figure 2 As shown, the system comprises:

[0064] Debug information export module, data source parsing module, evaluation model scheduling module and debugging compilation environment, among which

[0065] The debugging information export module is used to obtain the debugging data source file and interface configuration file in the test evaluation system;

[0066] A debugging and compiling environment is used to load the model dynamic library using local debugging and compiling software, compile the evaluation model source code, generate an evaluation model dynamic library file, and the evaluation model dynamic library file includes at least one evaluation model. The evaluation model is also used to publish the evaluation model after debugging, and upload the evaluation model after debugging to the test evaluation system;

[0067] A data source parsing module, used to parse the debugging data source file according to the column number of the debugging data source file corresponding to the evaluation model interface in the interface configuration file to obtain debugging data;

[0068] The evaluation model scheduling module is used to send the debugging data to the input interface of the evaluation model to drive the evaluation model to run; it is also used to use the debugging compilation environment to perform single-step debugging on the running evaluation model.

[0069] In a possible implementation, the debugging information export module and the evaluation model management are deployed on the server side;

[0070] The source code of the data source parsing module, evaluation model scheduling module, debugging compilation environment and model dynamic library are deployed on the local computer.

[0071] In one possible implementation, an interface configuration file is used to describe the correspondence between a debugging data source file and an evaluation model interface; the interface configuration file is described in XML language or a text format in a custom format, including a debugging file and model interface correspondence node, an evaluation model name, an evaluation model description, a debugging file column number, and a data type.

[0072] In a possible implementation, sending the debugging data to the input interface of the evaluation model includes: sending the debugging data to the input interface of the evaluation model in parameter form and JSON format.

[0073] In a possible implementation manner, the debugging data obtains the data structure of the parameter item by obtaining the matching relationship with the evaluation model interface and the corresponding data type through the evaluation model interface name in the interface configuration file.

[0074] In a possible implementation, the evaluation model dynamic library file is a dll file and / or a so file.

[0075] In this specification, each embodiment of the above method is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. For relevant parts, refer to the partial description of the method embodiment.

[0076] It should be noted that, although the operations of the method of the present invention are described in a specific order in the drawings, this does not require or imply that the operations must be performed in the specific order, or that all the operations shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.

[0077] Although the present application provides method operation steps such as embodiments or flow charts, more or less operation steps may be included based on conventional or non-creative means. The order of steps listed in the embodiment is only one way of executing the order of many steps and does not represent a unique execution order. When the device or client product in practice is executed, it can be executed in sequence or in parallel according to the method shown in the embodiment or the accompanying drawings (for example, a parallel processor or a multi-threaded processing environment, or even a distributed data processing environment). The term "includes", "comprising" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, product or equipment including a series of elements includes not only those elements, but also includes other elements that are not explicitly listed, or also includes elements inherent to such process, method, product or equipment. In the absence of more restrictions, it is not excluded that there are other identical or equivalent elements in the process, method, product or equipment including the elements.

[0078] The units, devices or modules described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. For the convenience of description, the above devices are described separately by functions divided into various modules. Of course, when implementing this application, the functions of each module can be implemented in the same or more software and / or hardware, or the modules that implement the same function can be implemented by a combination of multiple sub-modules or sub-units. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the coupling or direct coupling or communication connection between each other shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0079] Those skilled in the art also know that, in addition to implementing the controller in a purely computer-readable program code, the controller can be made to implement the same function in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, such a controller can be considered as a hardware component, and the devices for implementing various functions included therein can also be considered as structures within the hardware component. Or even, the devices for implementing various functions can be considered as both software modules for implementing the method and structures within the hardware component.

[0080] The present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, classes, etc. that perform specific tasks or implement specific abstract data types. The present application may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0081] It can be known from the description of the above implementation methods that those skilled in the art can clearly understand that the present application can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution of the present application can be essentially or partly contributed to the prior art in the form of a software product, which can be stored in a storage medium such as ROM / RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which can be a personal computer, a mobile terminal, a server, or a network device, etc.) to execute the methods described in the various embodiments of the present application or certain parts of the embodiments.

[0082] The various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld devices or portable devices, tablet devices, multi-processor systems, microprocessor-based systems, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc.

[0083] In the description of the present invention, it should be noted that the terms "upper", "lower", etc. indicate positions or positional relationships based on the positions or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific position, be constructed and operated in a specific position, and therefore cannot be understood as a limitation on the present invention. Unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be an indirect connection through an intermediate medium, or it can be a connection between the two elements. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to the specific circumstances.

[0084] It should also be noted that, in the description of the present invention, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element.

[0085] Obviously, the above embodiments of the present invention are merely examples for clearly illustrating the present invention, and are not limitations on the embodiments of the present invention. For those skilled in the art, other different forms of changes or modifications can be made based on the above description. It is impossible to list all the embodiments here. All obvious changes or modifications derived from the technical solution of the present invention are still within the protection scope of the present invention.

Claims

1. A method for debugging an evaluation model of a test evaluation system, characterized in that: include: Obtain the debugging data source file and interface configuration file in the test evaluation system; Using local debugging and compiling software to load the model dynamic library, compile the evaluation model source code, and generate an evaluation model dynamic library file, wherein the evaluation model dynamic library file includes at least one evaluation model; Parsing the debugging data source file according to the column number of the debugging data source file corresponding to the evaluation model interface in the interface configuration file to obtain debugging data corresponding to the evaluation model; Sending the debugging data to the input interface of the evaluation model; Driving the evaluation model to run, and using the debugging and compiling environment to perform single-step debugging on the running evaluation model; The debugged evaluation model is uploaded to the test evaluation system through the debugging and compilation environment.

2. According to the method described in claim 1, the interface configuration file is used to describe the correspondence between the debugging data source file and the evaluation model interface; the interface configuration file is described in XML language or a text format in a custom format, including the corresponding relationship node between the debugging file and the evaluation model interface, the evaluation model name, the evaluation model description, the debugging file column number and the data type.

3. According to the method of claim 1, sending the debugging data to the input interface of the evaluation model comprises: sending the debugging data to the input interface of the evaluation model in parameter form and JSON format.

4. According to the method of claim 3, the debugging data obtains the data structure of the parameter item by obtaining the matching relationship with the evaluation model interface and the corresponding data type through the evaluation model interface name in the interface configuration file.

5. According to the method of claim 1, the evaluation model dynamic library file is a dll file and / or a so file.

6. An evaluation model debugging system for a test evaluation system, characterized in that: include: Debug information export module, data source parsing module, evaluation model scheduling module and debugging compilation environment, among which The debugging information export module is used to obtain the debugging data source file and interface configuration file in the test evaluation system; The debugging and compiling environment is used to load the model dynamic library using the local debugging and compiling software, compile the evaluation model source code, generate an evaluation model dynamic library file, the evaluation model dynamic library file includes at least one evaluation model, and is also used to publish the evaluation model after debugging, and upload the evaluation model after debugging to the test evaluation system; The data source parsing module is used to parse the debugging data source file according to the column number of the debugging data source file corresponding to the evaluation model interface in the interface configuration file to obtain debugging data; The evaluation model scheduling module is used to send the debugging data to the input interface of the evaluation model to drive the evaluation model to run; and is also used to use the debugging compilation environment to perform single-step debugging on the running evaluation model.

7. According to the system described in claim 6, the interface configuration file is used to describe the correspondence between the debugging data source file and the evaluation model interface; the interface configuration file is described in XML language or a text format in a custom format, including the corresponding relationship node between the debugging file and the model interface, the evaluation model name, the evaluation model description, the debugging file column number and the data type.

8. According to the system of claim 6, sending the debugging data to the input interface of the evaluation model comprises: sending the debugging data to the input interface of the evaluation model in parameter form and JSON format.

9. The system according to claim 8, wherein the debugging data obtains a data structure of parameter items by obtaining a matching relationship with the evaluation model interface and a corresponding data type through the evaluation model interface name in the interface configuration file.

10. According to the system of claim 6, the evaluation model dynamic library file is a dll file and / or a so file.

Images