A visual detection sub-process synchronization method and a synchronization system

Abstract

This application discloses a visual inspection sub-process synchronization method and system. Through a pre-defined sub-process management table, it stores the associations between sub-process templates and identical sub-processes. Specifically, the table identifies the sub-process templates and other sub-processes associated with the modified sub-process, i.e., the sub-process templates and identical sub-processes that need to be synchronized. During use, user modifications can be applied to other related sub-processes, achieving synchronized modification of identical sub-processes. This visual inspection sub-process synchronization method achieves the effect of "one modification, all applications," reducing labor costs, improving project setup efficiency, and enhancing project maintainability.

Description

Technical Field

[0001] This application relates to the field of visual technology, and in particular to a method and system for synchronizing visual inspection subprocesses. Background Technology

[0002] The visual inspection process is an inspection engineering project built using inspection software for visual inspection. Figure 1 This is a schematic diagram of the structure of a completed vision inspection program, such as... Figure 1 As shown, multiple locations in the detection process share the same process segments. For example, the image storage sub-processes 1, 2, and 3 (within the dashed boxes in the diagram) used in the image storage branch, or the line finding sub-processes 1, 2, and 3 (within the dashed boxes in the diagram) used in the line finding branch. In these sub-processes, image storage sub-processes 1, 2, and 3 share the same process elements (process elements include constituent nodes, connecting lines, and intra-section parameter information; intra-section parameter information refers to the parameter information possessed by each node itself, and each intra-section parameter has a fixed attribute identifier, commonly including indexes, signatures, etc.). Similarly, line finding sub-processes 1, 2, and 3 share the same process elements. In engineering, sub-processes with the same process elements are grouped into the same sub-process group, referred to as identical sub-processes.

[0003] During the setup of the testing process, sub-processes need to be modified, and similar sub-processes used in other branches generally require the same modifications. Currently, when modifying identical sub-processes, if only one process is modified, the modification cannot be simultaneously applied to other identical sub-processes. To complete the modification of identical sub-processes, other identical sub-processes need to be manually located, and each identical sub-process needs to be manually modified one by one. This results in poor synchronous maintainability of identical sub-processes, leading to low efficiency in setting up the testing process. In addition, multiple modification operations are prone to omissions and errors. Once omissions or errors occur, they will cause anomalies in the testing system, thereby affecting the normal operation of the entire production line. Summary of the Invention

[0004] This application provides a visual inspection subprocess synchronization method and system to solve the problem in the prior art that when adjusting a subprocess, the corresponding identical subprocess cannot be adjusted synchronously.

[0005] This application provides a method for synchronizing visual inspection subprocesses, including:

[0006] Receive a modification instruction and obtain the modification sub-process pointed to by the modification instruction;

[0007] Using a pre-defined identical subprocess management table, the corresponding subprocess template and identical subprocess of the modified subprocess are found, wherein the identical subprocess management table is used to store the association between the subprocess template and the identical subprocess;

[0008] Perform the modification operations corresponding to the modification instructions on the detected sub-process templates and identical sub-processes.

[0009] In some embodiments, the visual inspection sub-process synchronization method further includes constructing an identical sub-process management table, specifically:

[0010] Construct sub-process templates, and for each sub-process template, construct a group of sub-processes, wherein each sub-process template and the corresponding group of sub-processes share common process elements;

[0011] Each sub-process template and sub-process is uniquely identified;

[0012] Use identity identifiers to associate subprocess templates with subprocesses in the corresponding groups.

[0013] In some embodiments, the step of using a preset identical subprocess management table to find identical subprocesses that are being modified includes:

[0014] Using a pre-defined table of identical sub-processes, the sub-process template associated with the modified sub-process is found, i.e., the sub-process template is modified.

[0015] Then, using the preset same sub-process management table, other sub-processes associated with the modified sub-process template are found, that is, the same sub-processes of the modified sub-process.

[0016] In some embodiments, the visual inspection subprocess synchronization method further includes,

[0017] Based on the modification instructions, obtain the modification node of the modification sub-process;

[0018] Using a pre-defined identical subprocess management table, the template and identical subprocess are found. Then, using a pre-defined identical node management table, the modified nodes of the template and identical subprocess are found, i.e., identical modified nodes. The identical subprocess management table is used to store the association between the template and identical subprocess, and the identical node management table is used to store the association between the nodes in the subprocess template and the related nodes in the corresponding subprocess.

[0019] Perform the modification operation corresponding to the modification instruction on the same modified nodes that are detected.

[0020] In some embodiments, the visual inspection subprocess synchronization method further includes,

[0021] Based on the modification instructions, obtain the modified node and the parameters within the modified section of the modified node;

[0022] Using a pre-defined identical subprocess management table, identical subprocesses are found. Then, using a pre-defined identical node management table, modified nodes of the template and identical subprocesses are found, i.e., identical modified nodes. The identical subprocess management table is used to store the association between the template and identical subprocesses. The identical node management table is used to store the association between nodes in the subprocess template and related nodes in the corresponding subprocess.

[0023] Based on the fixed attribute identifier of the parameters within the modified section, the same parameters within the same modified node are found.

[0024] Perform the modification operation corresponding to the modification instruction on the parameters within the same modified section that were detected.

[0025] In some embodiments, the visual inspection subprocess synchronization method further includes constructing a common node management table, including:

[0026] Each sub-process template and node within the same sub-process is uniquely identified.

[0027] Using identity identifiers, establish an association index between nodes of a subprocess template and corresponding nodes of related subprocesses.

[0028] In some embodiments, the step of using a preset same node management table to find the modification node of the same sub-process includes:

[0029] Using a pre-defined table of identical sub-processes, the sub-process templates and other sub-processes associated with the modified sub-process are located, i.e., the templates and other sub-processes are modified.

[0030] Using a pre-defined same node management table, the modification node of the modified sub-process template associated with the modification node of the modified sub-process is found, i.e., the modification template node.

[0031] Then, using the pre-defined same node management table, find the nodes of other sub-processes associated with the modified template node, that is, the same modified nodes within the same sub-process.

[0032] In some embodiments, the identity identifier includes an ID identifier, a name identifier, a signature identifier, an index identifier, and a special string identifier.

[0033] In some embodiments, the construction of the same subprocess management table further includes deleting the association index between the subprocess and the subprocess template when the subprocess is no longer the same subprocess.

[0034] This application also provides a visual inspection subprocess synchronization system, including:

[0035] The subprocess information table stores the process element information of all subprocesses in the visual inspection process. The process element information includes the component node information, connection line information, and intra-node parameters of each node.

[0036] The module for obtaining the target is configured to: obtain the target modification sub-process based on the received modification instruction;

[0037] The same subprocess management table stores the association between subprocess templates and the same subprocesses;

[0038] The search module is configured to: use a preset identical subprocess management table to search for the corresponding subprocess template and identical subprocess of the modified subprocess;

[0039] The modification module is configured to perform the modification operation corresponding to the modification instruction on the detected subprocess template and the same subprocess.

[0040] This application provides a visual inspection sub-process synchronization method and system. Through a pre-defined sub-process management table, it stores the associations between sub-process templates and similar sub-processes. Specifically, the table identifies the sub-process templates and other sub-processes associated with the modified sub-process, i.e., the sub-process templates and similar sub-processes that need to be synchronized. During use, user modifications can be applied to other related sub-processes, achieving synchronized modification of similar sub-processes. This visual inspection sub-process synchronization method achieves the effect of "one modification, all applications," reducing labor costs, improving project setup efficiency, and enhancing project maintainability. Attached Figure Description

[0041] To more clearly illustrate the technical solution of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0042] Figure 1 A schematic diagram of the completed structure of the visual inspection project;

[0043] Figure 2 This is a schematic diagram of the structure after encapsulating identical process segments into sub-processes;

[0044] Figure 3 This is a schematic diagram of the ID for the inspection project;

[0045] Figure 4 This is a diagram illustrating the ID correspondence between subprocess templates, subprocesses, and internal nodes.

[0046] Figure 5This is a schematic diagram of the intra-section parameters corresponding to node id33. Detailed Implementation

[0047] Currently, process elements within sub-processes are displayed individually and separately, lacking encapsulation. This makes the entire testing process appear bulky and complex, reducing software usability. Therefore, this application provides a method to encapsulate and display multiple node tools as a whole, presented as a single element within the sub-process, thus reducing project complexity. Of course, the sub-process is editable, allowing users to customize its internal execution flow and tool parameters. Figure 2 As shown, the image storage process on each image storage branch is encapsulated into a sub-process, and the line finding process on each line finding branch is encapsulated into a sub-process.

[0048] To address the problem in existing technologies where modifications to a sub-process cannot be synchronized with the corresponding identical sub-processes, this application provides a visual inspection sub-process synchronization method that maintains synchronized adjustments between identical sub-processes. The visual inspection sub-process synchronization method of this application specifically includes the following steps.

[0049] Step S100: Construct a management table for identical sub-processes and a management table for identical nodes.

[0050] The identical subprocess management table is used to store the association between templates and identical subprocesses. In this application, constructing the identical subprocess management table specifically involves: constructing subprocess templates; for each subprocess template, constructing a group of subprocesses; each subprocess template and the corresponding group of subprocesses sharing common process elements; assigning unique identifiers to all subprocess templates and subprocesses; and using these identifiers to associate the subprocess templates with the corresponding group of subprocesses.

[0051] The construction of the same subprocess management table also includes deleting the association index between the subprocess and the subprocess template when the subprocess is no longer the same subprocess. That is, when a subprocess is deleted, the association relationship between the subprocess and the subprocess template will also be removed from the same subprocess management table.

[0052] The same node management table is used to store the association between nodes within a template and related nodes within related sub-processes. In this application, constructing the same node management table includes: assigning a unique identifier to each sub-process template and each node within the same sub-process; and using the identifier to establish the association between nodes in the sub-process template and corresponding nodes in related sub-processes.

[0053] In this application, the identity identifier includes an ID identifier, a name identifier, a signature identifier, an index identifier, and a special string identifier. Of course, other identifier methods can also be selected, as long as they are uniquely identified.

[0054] To help those skilled in the art better understand the process of creating related indexes, the following will provide a detailed explanation through examples.

[0055] Combination Figure 3 and 4 As shown, IDs are used to identify sub-process templates, related sub-processes, and process elements within the process. Each sub-process template, sub-process, node, and connector has its own corresponding ID. The sub-process template ID is id3, and the IDs for identical sub-processes are id28, id37, and id47. During the association establishment process, the identical sub-process management table stores the association between id3 and id28, id37, and id47, thereby achieving the association between sub-process templates and identical sub-processes. In this example, the data structure used to store the association is a map from the C++ Standard Template Library: `std::map<sub-process template ID, std::map<sub-process ID, sub-process internal information>>`. The sub-process template ID serves as the key, and the individual sub-process IDs and the process element information within the sub-process serve as the values ​​corresponding to the keys. In actual use, by utilizing the association between sub-process template IDs and related sub-process IDs, one can find the corresponding group of sub-processes through the sub-process template, or find the sub-process template or identical sub-processes through a specific sub-process. It should be noted that other data structures are also used to store the mapping relationship, such as std::set or split into multiple std::maps for storage.

[0056] Similarly, each process element within the process has a unique ID. Taking nodes as an example, the same node management table associates and stores the subprocess template node ID with the corresponding node ID within the subprocess, thereby achieving the association between nodes. For example, by storing the association between id4, id30, id39, and id49, the association between nodes is established, realizing the connection between nodes with an association relationship. Each node within the template corresponds one-to-one with each node within each subprocess. The same node management table uses a map data structure from the C++ standard template library: std::map<template ID, std::map<template node ID, std::map<subprocess ID, subprocess node ID>>>. The outer map uses the template ID as the key, and the inner map uses the template node ID as the key. Thus, a node in the template can be used to find all subprocess nodes, and a node in a subprocess can be used to find the corresponding template node, as well as the corresponding nodes in other subprocesses.

[0057] Step S200: Receive the modification instruction for the sub-process.

[0058] In this example, the modification instructions for a subprocess include deleting the subprocess, deleting nodes within the subprocess, modifying parameters within a subprocess section, adjusting the order of nodes within the subprocess, and adjusting parameter passing between multiple nodes within the subprocess. Of course, modification instructions can also include other types of instructions, depending on the actual needs.

[0059] Step S300: Obtain the modification sub-process pointed to by the modification instruction, the modification node of the modification sub-process, or the parameters within the modification section of the modification node.

[0060] The modification instruction for a sub-process includes the sub-process to be modified pointed to by the modification instruction, as well as the modification node or node parameters of the sub-process. In this application, based on the received modification instruction for the sub-process, the modification sub-process to be modified pointed to by the modification instruction and the modification node or intra-section parameters of the sub-process are obtained, that is, the modification object of the modification instruction is obtained. Each intra-section parameter has a fixed attribute identifier. In this example, the fixed attribute identifiers of the intra-section parameters include name, type, index, signature, etc.

[0061] Step S400: Using a preset identical subprocess management table, find the identical subprocesses of the modified subprocess; and using a preset identical node management table, find the identical modified nodes of the modified nodes. The identical subprocess management table stores the association between templates and identical subprocesses, and the identical node management table stores the association between nodes within a subprocess template and related nodes within the corresponding subprocess group.

[0062] In this application, the method of using a preset identical subprocess management table to find identical subprocesses of the modified subprocess includes: using the preset identical subprocess management table to find the subprocess template associated with the modified subprocess, i.e., the modified subprocess template; and then using the preset identical subprocess management table to find other subprocesses associated with the modified subprocess template, i.e., identical subprocesses of the modified subprocess.

[0063] In this application, a preset same node management table is used to find modification nodes within the same sub-process, i.e., same modification nodes. This includes: using the preset same sub-process management table to find the sub-process template and other sub-processes associated with the modified sub-process, i.e., modification templates and other sub-processes; then using the preset same node management table to find the modification nodes of the modified sub-process template associated with the modification node of the modified sub-process, i.e., modification template nodes; and then using the preset same node management table to find the nodes of other sub-processes associated with the modification template node, i.e., same modification nodes within the same sub-process.

[0064] Step S500: Based on the fixed attribute identifier of the parameter within the modified section, find the same parameter within the same modified node.

[0065] In this application, firstly, the fixed attribute identifiers of the parameters within the modified section are obtained using the sub-process information table; then, the same modified section parameters within the same modified node are found using the fixed attribute identifiers of the parameters within the modified section. The sub-process information table stores process element information for all sub-processes in the visual inspection process. Process element information includes the component node information, connection line information, and section parameters for each node. Each section parameter has a fixed attribute identifier. In this example, the fixed attribute identifiers for section parameters include name, type, index, signature, etc. A diagram of section parameters can be found in [reference needed]. Figure 5 .

[0066] It should be noted that each node can be identified by an ID, and the parameters of each node can be identified by information such as parameter name, parameter index, and parameter signature.

[0067] Step S600: Perform the modification operation corresponding to the modification instruction on the detected sub-process template and the same sub-process, and perform the modification operation corresponding to the modification instruction on the parameters of the same modification node or the same modification section in the detected sub-process template and the same sub-process.

[0068] In this example, the modification instructions for a subprocess include deleting the subprocess, deleting nodes within the subprocess, modifying parameters within a subprocess section, adjusting the order of nodes within the subprocess, and adjusting parameter passing between multiple nodes within the subprocess. Of course, modification instructions can also include other types of instructions, depending on the actual needs.

[0069] When identical subprocesses are found, the modification operation corresponding to the modification command is executed on the identical subprocesses. For example, if the modification command is to delete a subprocess, then the deletion operation is performed on the identical subprocesses according to the command requirements.

[0070] When identical modified nodes or parameters within the same sub-process are detected, the modification operation corresponding to the modification instruction is performed. That is, based on the specific content of the modification instruction, the corresponding operation is performed on the modified nodes or parameters within the same sub-process. For example, if the modification instruction is to delete a node within a sub-process, then the modified node within the same sub-process is deleted according to the instruction. As another example, if the modification instruction is to modify a parameter within a section of a sub-process, then the parameter within the modified section within the same sub-process is modified according to the instruction.

[0071] It should be noted that when modifying the same subprocess or the same modified node or the same modified section parameters of the same subprocess, the same modification can be performed simultaneously on the modified subprocess template or the modified node or section parameters of the modified subprocess template. The modification process is the same as the modification process of the same subprocess or the modified node or section parameters of the same subprocess, and will not be repeated here.

[0072] To help those skilled in the art better understand this technical solution, the following examples will provide further explanation.

[0073] Example 1: Receive a modification instruction for a sub-process, specifying the deletion of a node within the sub-process; delete the node in the sub-process according to the modification instruction; use the ID of the modified sub-process to search for a related sub-process template in the same sub-process management table; use the ID of the node to search for a related node within the sub-process template in the same node management table; delete the found node within the sub-process template.

[0074] Using the ID of the subprocess template, search for other subprocesses that are related to the subprocess template in the same subprocess management table; using the ID of the deleted node in the subprocess template, search for nodes in other subprocesses that are related to the deleted node in the same node management table; delete the nodes in the other subprocesses one by one.

[0075] Example 2: Receive a modification instruction for a sub-process, where the instruction is to change the parameters within a section of the sub-process; modify the parameters within the section of the sub-process according to the modification instruction; use the ID of the sub-process to search for a related sub-process template in the same sub-process management table; use the ID of the node to search for a related node within the sub-process template and section in the same node management table, i.e., the modified template node.

[0076] Using the ID of the subprocess template, find other subprocesses that are related to the modified subprocess template in the same subprocess management table; using the ID of the node within the subprocess template, find the same modified node within other subprocesses that is related to the modified template node in the same node management table.

[0077] Based on the fixed attribute identifier of the parameter within the modified section in the modified subprocess, the same parameter within the same modified section in the same modified node is found;

[0078] Change the parameters in the same modified section one by one.

[0079] Furthermore, the visual inspection sub-process synchronization method of this application is scalable, and can also support situations where parameters within sub-process sections are not synchronized. Users can reconfigure the relationships stored in the management table of the same sub-nodes, dividing the parameters within sub-process sections into those that need to be synchronized and those that do not, based on the user's configuration. When a parameter within a section of a sub-process is modified, the modification operation will be synchronously applied to the parameters within the sub-process sections that need to be synchronized; however, the modification operation will not be synchronously applied to the parameters within the sub-process sections that do not need to be synchronized.

[0080] This application also provides a visual inspection sub-process synchronization system, including a sub-process information table, an acquisition pointer module, a similar sub-process management table, a search module, and a modification module. The sub-process information table stores process element information for all sub-processes in the visual inspection process, including component node information, connection line information, and intra-node parameters for each node. The acquisition pointer module is configured to acquire the specified sub-process to be modified based on a received modification instruction. The similar sub-process management table stores the association between sub-process templates and similar sub-processes. The search module is configured to use the preset similar sub-process management table to search for the corresponding sub-process template and similar sub-process of the modified sub-process. The modification module is configured to perform the modification operation corresponding to the modification instruction on the detected sub-process template and similar sub-process.

[0081] In existing technologies, process elements within sub-processes are displayed individually and separately, lacking encapsulation. This makes the entire detection program appear cluttered and bulky, reducing the usability of the detection software. To address this issue, this application adopts an encapsulated display method for process elements within sub-processes, displaying the sub-process and its internal process elements as a single element, thereby reducing the complexity of the detection program.

[0082] This application provides a visual inspection sub-process synchronization method and system. It stores the association between identical sub-processes and their corresponding sub-process templates through a pre-defined sub-process management table, achieving associated management of identical sub-processes. That is, all sub-processes can be found through a sub-process template, or a sub-process template or other sub-processes can be found through a specific sub-process. During use, user modifications can be applied to other related sub-processes, achieving synchronized modifications to identical sub-processes. This visual inspection sub-process synchronization method achieves the effect of "one modification, all applications," reducing manual costs, improving the efficiency of inspection process setup, and enhancing the maintainability of the inspection process.

[0083] The above descriptions are examples of the best embodiments of this application, and the parts not described in detail are common knowledge to those skilled in the art. The scope of protection of this application is determined by the content of the claims, and any equivalent modifications made based on the technical teachings of this application are also within the scope of protection of this application.

Claims

1. A method for synchronizing visual inspection subprocesses, characterized in that, include: Receive a modification instruction and obtain the modification sub-process pointed to by the modification instruction; Using a pre-defined identical subprocess management table, the corresponding subprocess template and identical subprocess of the modified subprocess are found, wherein the identical subprocess management table is used to store the association between the subprocess template and the identical subprocess; Perform the modification operations corresponding to the modification instructions on the detected sub-process templates and identical sub-processes; The visual inspection sub-process synchronization method also includes constructing an identical sub-process management table, specifically: Construct sub-process templates, and for each sub-process template, construct a group of sub-processes, wherein each sub-process template and the corresponding group of sub-processes share common process elements; Each sub-process template and sub-process is uniquely identified; Use identity identifiers to associate sub-process templates with sub-processes of the corresponding groups; The visual inspection subprocess synchronization method also includes, Based on the modification instructions, obtain the modified node and the parameters within the modified section of the modified node; Using a pre-defined identical subprocess management table, identical subprocesses are found. Then, using a pre-defined identical node management table, modified nodes of the template and identical subprocesses are found, i.e., identical modified nodes. The identical subprocess management table is used to store the association between the template and identical subprocesses. The identical node management table is used to store the association between nodes in the subprocess template and related nodes in the corresponding subprocess. Based on the fixed attribute identifier of the parameters within the modified section, the same parameters within the same modified node are found. Perform the modification operation corresponding to the modification instruction on the parameters within the same modified section that were detected.

2. The visual inspection sub-process synchronization method according to claim 1, characterized in that, The step of using a preset identical subprocess management table to find identical subprocesses that are being modified includes: Using a pre-defined table of identical sub-processes, the sub-process template associated with the modified sub-process is found, i.e., the sub-process template is modified. Then, using the preset same sub-process management table, other sub-processes associated with the modified sub-process template are found, that is, the same sub-processes of the modified sub-process.

3. The visual inspection sub-process synchronization method according to claim 1, characterized in that, The visual inspection subprocess synchronization method also includes, Based on the modification instructions, obtain the modification node of the modification sub-process; Using a pre-defined identical subprocess management table, the template and identical subprocess are found. Then, using a pre-defined identical node management table, the modified nodes of the template and identical subprocess are found, i.e., identical modified nodes. The identical subprocess management table is used to store the association between the template and identical subprocess, and the identical node management table is used to store the association between the nodes in the subprocess template and the related nodes in the corresponding subprocess. Perform the modification operation corresponding to the modification instruction on the same modified nodes that are detected.

4. The visual inspection sub-process synchronization method according to claim 3, characterized in that, The visual inspection sub-process synchronization method also includes constructing a shared node management table, including: Each sub-process template and node within the same sub-process is uniquely identified. Using identity identifiers, establish an association index between nodes of a subprocess template and corresponding nodes of related subprocesses.

5. The visual inspection sub-process synchronization method according to claim 3, characterized in that, The step of using a preset same node management table to find modified nodes of the same sub-process includes: Using a pre-defined table of identical sub-processes, the sub-process templates and other sub-processes associated with the modified sub-process are located, i.e., the templates and other sub-processes are modified. Using a pre-defined same node management table, the modification node of the modified sub-process template associated with the modification node of the modified sub-process is found, i.e., the modification template node. Then, using the pre-defined same node management table, find the nodes of other sub-processes associated with the modified template node, that is, the same modified nodes within the same sub-process.

6. The visual inspection sub-process synchronization method according to claim 4, characterized in that, The identity identifiers include ID identifiers, name identifiers, signature identifiers, index identifiers, and special string identifiers.

7. The visual inspection sub-process synchronization method according to claim 1, characterized in that, The construction of the same subprocess management table also includes deleting the association index between the subprocess and the subprocess template when the subprocess is no longer the same subprocess.

8. A visual inspection sub-process synchronization system, characterized in that, The system is configured with the visual inspection subprocess synchronization method as described in claim 1, and the system includes: The subprocess information table stores the process element information of all subprocesses in the visual inspection process. The process element information includes the component node information, connection line information, and intra-node parameters of each node. The module for obtaining the target is configured to: obtain the target modification sub-process based on the received modification instruction; The same subprocess management table stores the association between subprocess templates and the same subprocesses; The search module is configured to: use a preset identical subprocess management table to search for the corresponding subprocess template and identical subprocess of the modified subprocess; The modification module is configured to perform the modification operation corresponding to the modification instruction on the detected subprocess template and the same subprocess.

Images