Method and apparatus for visually displaying flowchart interface data, device and storage medium
By receiving data flow viewing requests, the system identifies and displays related nodes and interactive data information in the flowchart, solving the problem of not being able to fully view the flowchart and improving data viewing efficiency and experience.
Patent Information
- Application Number
- PCT/CN2026/095159
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-07
- Filing Date
- 2026-05-07
- Publication Date
- 2026-11-12
AI Technical Summary
Existing technologies cannot effectively display all related nodes and interactive data information in flowcharts, resulting in a poor data viewing experience.
By receiving data flow viewing requests, related and non-related nodes are identified, and information viewing interface elements are output, displaying the identification information and interactive data information of related nodes, and displaying relevant information in the form of floating windows or pop-ups.
Even when not all process nodes are displayed, users can still view all associated nodes and interactive data information of the target process node, thus optimizing the data viewing experience.
Smart Images

Figure CN2026095159_12112026_PF_FP_ABST
Abstract
Description
Flowchart interface data visualization methods, devices, equipment and storage media Technical Field
[0001] This application relates to the field of machine vision technology, and in particular to a method, apparatus, device and storage medium for visualizing flowchart interface data. Background Technology
[0002] Machine vision refers to the process of enabling machines to "see" and "understand" their environment through computers and related technologies. It involves using technologies such as cameras, sensors, image processing algorithms, and artificial intelligence to allow machines to simulate human visual capabilities, thereby acquiring and processing image or video data for recognition, analysis, judgment, and decision-making.
[0003] To execute machine vision tasks, several different programs can be combined into a complete and logical task flow. In a flowchart, these programs are grouped and encapsulated into several visual modules based on their functions, making it easy for users to edit and view them. Each visual module added to the flowchart can be considered a process node. Summary of the Invention
[0004] In view of this, this application provides a method, apparatus, device and storage medium for visualizing flowchart interface data.
[0005] According to a first aspect of the embodiments of this application, a method for visualizing data in a flowchart interface is provided, comprising:
[0006] Receive a request to view the data flow direction of a target process node; wherein, the target process node is any process node in the flowchart displayed in the visual flowchart interface;
[0007] Identify the associated and non-associated nodes in the flowchart; wherein, the associated nodes are the flowchart nodes that have data flow interaction with the target flowchart node; the non-associated nodes are the remaining flowchart nodes other than the target flowchart node and the associated nodes; and,
[0008] Output information viewing interface elements; wherein, the information viewing interface elements are used to display the identification information of the associated nodes, as well as the interaction data information between each associated node and the target process node.
[0009] According to a second aspect of the embodiments of this application, a flowchart interface data visualization display device is provided, comprising:
[0010] The receiving unit is used to receive a data flow viewing request for a target process node; wherein, the target process node is any process node in the flowchart displayed in the visual flowchart interface.
[0011] A determining unit is used to determine associated nodes and non-associated nodes in a flowchart; wherein, the associated nodes are the flowchart nodes that have data flow interaction with the target flowchart node; and the non-associated nodes are the remaining flowchart nodes other than the target flowchart node and the associated nodes.
[0012] An output unit is used to output information viewing interface elements; wherein the information viewing interface elements are used to display the identification information of the associated nodes, as well as the interaction data information between each associated node and the target process node.
[0013] According to a third aspect of the present application, an electronic device is provided, including a processor and a memory, the memory storing machine-executable instructions executable by the processor, the processor being configured to execute the machine-executable instructions to implement the method provided in the first aspect.
[0014] According to a fourth aspect of the embodiments of this application, a machine-readable storage medium is provided, wherein machine-executable instructions are stored therein, and when the machine-executable instructions are executed by a processor, the method provided in the first aspect is implemented.
[0015] The flowchart interface data visualization method of this application, upon receiving a request to view the data flow of a target process node, outputs an information viewing interface element. This information viewing interface element can be used to display the identification information of associated nodes, as well as the interaction data information between each associated node and the target process node. Thus, it can effectively ensure that even when not all display nodes in the flowchart can be displayed, all associated nodes and corresponding interaction data information of the target process node can still be viewed through this information viewing interface element, thereby optimizing the data viewing experience. Attached Figure Description
[0016] Figure 1 is a flowchart illustration of a data visualization method for a flowchart interface provided in an embodiment of this application;
[0017] Figure 2 is a schematic diagram of an information viewing floating window provided in an embodiment of this application;
[0018] Figure 3 is a flowchart illustrating the construction and execution of a flowchart according to an embodiment of this application;
[0019] Figure 4A is a schematic diagram of a normal process node provided in an embodiment of this application;
[0020] Figure 4B is a schematic diagram of a process node in an abnormal state provided in an embodiment of this application;
[0021] Figure 5A is a schematic diagram of an anomaly statistics list of hidden states provided in an embodiment of this application;
[0022] Figure 5B is a schematic diagram of a complete display status anomaly statistics list provided in an embodiment of this application;
[0023] Figure 6 is a schematic diagram of the flowchart execution result provided in an embodiment of this application;
[0024] Figure 7 is a schematic diagram of a process for viewing process data information provided in an embodiment of this application;
[0025] Figure 8A is a schematic diagram of an error message viewing mode provided in an embodiment of this application;
[0026] Figure 8B is a schematic diagram of a time consumption information viewing mode provided in an embodiment of this application;
[0027] Figure 9 is a flowchart illustrating the data flow direction of process nodes in a flowchart according to an embodiment of this application.
[0028] Figure 10 is a screenshot of a data flow information display interface provided in an embodiment of this application.
[0029] Figure 11 is a schematic diagram of an information viewing floating window in case of parameter error provided in an embodiment of this application;
[0030] Figure 12 is a schematic diagram of the structure of a flowchart interface data visualization display device provided in an embodiment of this application;
[0031] Figure 13 is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application. Detailed Implementation
[0032] To enable those skilled in the art to better understand the technical solutions provided in the embodiments of this application, some terms involved in the embodiments of this application will be briefly explained below.
[0033] 1. Node Configuration Integrity: A process node can be a whole composed of multiple program sets, containing multiple parameters. For it to be executable within the process, it needs to have one or more data input sources. The existence of input sources, whether all input sources are configured, and whether the input sources are valid are all considered part of the node's configuration integrity.
[0034] For example, a process node that has an input source, all input sources are configured, and the input sources are valid can be identified as a fully configured process node; a process node that meets any of the following conditions—no input source, incomplete input sources, or invalid input sources—can be identified as an incompletely configured process node.
[0035] 2. Data flow direction: The direction of the source of the data input to the selected process node and the direction of the data output from the selected process node are collectively referred to as the data flow direction.
[0036] 3. Subscribing to data: In order for subsequent process nodes to obtain specific data from preceding process nodes, after the basic connection logic has been created in the flowchart, it is necessary to use a subscription binding method to enable subsequent process nodes to obtain specific data output by preceding process nodes.
[0037] For example, for a process node used to find a circle in an input image, its output data may include the coordinates of the circle's center and its radius.
[0038] To make the above-mentioned objectives, features and advantages of the embodiments of this application more apparent and understandable, the technical solutions of the embodiments of this application will be further described in detail below with reference to the accompanying drawings.
[0039] It should be noted that the sequence number of each step in the embodiments of this application does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0040] Please refer to Figure 1, which is a flowchart interface data visualization method provided in an embodiment of this application. As shown in Figure 1, the flowchart interface data visualization method may include the following steps:
[0041] Step S100: Receive a request to view the data flow direction of the target process node; wherein, the target process node is any process node in the flowchart displayed in the visual flowchart interface.
[0042] For example, in the embodiments of this application, unless otherwise specified, the flowchart mentioned may refer to the flowchart corresponding to the machine vision task.
[0043] In this embodiment of the application, for the flowchart displayed in the visualization flowchart interface, relevant personnel can view the data flow of any process node (which can be called the target process node) in the flowchart according to their needs.
[0044] For example, relevant personnel can initiate a data flow viewing request for a target process node by inputting a data flow viewing command for that target process node displayed in the visual flowchart interface.
[0045] Step S110: Determine the associated nodes and non-associated nodes in the flowchart; wherein, associated nodes are process nodes in the flowchart that have data flow interaction with the target process node; non-associated nodes are the remaining process nodes in the flowchart other than the target process node and associated nodes.
[0046] In this embodiment of the application, when a request to view the data flow of a target process node is received, the process nodes in the flowchart that have data flow interaction with the target process node (which can be called associated nodes) and the remaining process nodes other than the target process node and associated nodes (which can be called non-associated nodes) can be determined.
[0047] In some embodiments, the flowchart interface data visualization method provided in this application may further include:
[0048] The associated nodes and the non-associated nodes are displayed with different display effects respectively.
[0049] For example, in order to distinguish between related nodes and unrelated nodes in a flowchart so that relevant personnel can better differentiate between process nodes that have data flow interaction with the target process node and other process nodes, related nodes and unrelated nodes in the flowchart can be displayed with different display effects.
[0050] In one example, displaying related nodes and non-related nodes with different display effects could include:
[0051] Highlight associated nodes and / or downplay unassociated nodes.
[0052] For example, to make it easier for relevant personnel to see the related nodes, once the related and non-related nodes in the flowchart are determined, the related nodes can be highlighted and / or the non-related nodes can be weakened.
[0053] For example, for related nodes displayed in a visual flowchart interface, the related nodes can be highlighted by one or more of the following methods: increasing their display brightness, increasing their display size, changing their color, increasing their contrast, increasing their color saturation, and increasing their border thickness.
[0054] For example, for non-associated nodes displayed in a visual flowchart interface, the display of associated nodes can be weakened by one or more of the following methods: reducing their display brightness, shrinking their display size, changing their color, reducing their contrast, reducing their color saturation, and reducing their border thickness.
[0055] As an example, related nodes and unrelated nodes can be displayed with different effects by highlighting related nodes and displaying unrelated nodes normally, or by displaying related nodes normally and displaying unrelated nodes in a weakened manner, so as to achieve differentiated display of related nodes and unrelated nodes with less information processing.
[0056] As another example, by highlighting related nodes and downplaying non-related nodes, we can display related nodes and non-related nodes with different display effects, thereby enhancing the difference in display effects between related nodes and non-related nodes and making it easier to distinguish between them.
[0057] Step S120: Output information viewing interface elements; wherein, the information viewing interface elements are used to display the identification information of associated nodes, as well as the interaction data information between each associated node and the target process node.
[0058] In this embodiment of the application, considering that when there are a large number of process nodes in the flowchart, the visualization flowchart interface may not be able to display all process nodes in the current visualization window, thus making it impossible to view all related nodes through the current visualization window.
[0059] Based on this, in order to optimize the information viewing experience, when a request to view the data flow of a target process node is received, in addition to distinguishing and displaying related and unrelated nodes as described above, an information viewing interface element can also be output. This information viewing interface element is used to display the identification information of related nodes, as well as the interaction data information between each related node and the target process node. Thus, relevant personnel can view all the interaction node information and specific interaction data through this information viewing interface element, bringing a more complete data viewing experience.
[0060] As can be seen in the method flow shown in Figure 1, when a request to view the data flow of the target process node is received, an information viewing interface element is output. This information viewing interface element can be used to display the identification information of the associated nodes, as well as the interaction data information between each associated node and the target process node. Thus, it can effectively ensure that even if not all the display nodes in the flowchart can be displayed, all the associated nodes and corresponding interaction data information of the target process node can still be viewed through this information viewing interface element, thus optimizing the data viewing experience.
[0061] In some embodiments, receiving a data flow viewing request for a target process node may include:
[0062] A keyword search command matching the node name of the target process node was detected.
[0063] For example, to quickly locate the target process node whose data flow needs to be viewed, relevant personnel can search by entering the node name (or part of the node name) as keywords. If a keyword search command matching the node name of the target process node is detected, it can be determined that a request to view the data flow of the target process node has been received. Using keyword search allows for faster and more convenient location of the target process node, improving the efficiency of data flow viewing.
[0064] In some embodiments, information viewing interface elements may include an information viewing floating window;
[0065] The associated nodes displayed in the above information viewing pop-up include input nodes and / or output nodes. For any input node, the interactive data information includes the input parameter name and the parameter name of the corresponding bound target process node.
[0066] For any output node, the interactive data information includes the output parameter name and the parameter name of the corresponding output node.
[0067] For example, in order to optimize space utilization and realize real-time information display, the above-mentioned information viewing interface elements can be in the form of floating windows, that is, the relevant information of related nodes can be displayed through the information viewing floating window.
[0068] For example, the associated nodes displayed in the information viewing pop-up may include input nodes (if they exist) and / or output nodes (if they exist).
[0069] For any input node, the interactive data information may include the name of the input parameter, as well as the name of the parameter of the corresponding bound target process node;
[0070] For any output node, the interactive data information may include the output parameter name and the parameter name of the corresponding output node.
[0071] For example, a schematic diagram of the information viewing floating window can be seen in Figure 2. As shown in Figure 2, the information viewing floating window can display the identification information (such as the node name) of the current process node (such as the target process node mentioned above), as well as all the associated nodes (which can be called input nodes) to which the input data of the current process node is sent and the associated nodes (which can be called output nodes) to which the output data of the current process node is sent.
[0072] As shown in Figure 2, for process node 8, the input nodes may include process node 0 and process node 2, and the output node may include process node 9 (see Figure 10).
[0073] For process node 0, the input parameters include parameter value 1, parameter value 2, parameter value 3 and parameter value 4, and each parameter is input to parameter 1, parameter 2, parameter 3 and parameter 4 of process node 8 respectively.
[0074] For process node 2, the input parameters include parameter value 5, which is input to parameter 5 in process node 8.
[0075] For process node 9, the parameters output by this process node include parameter 6, which is the parameter 6 output to process node 9.
[0076] It should be noted that, in the embodiments of this application, the information viewing interface elements are not limited to floating windows, but can also be in other forms, such as pop-ups, sub-windows (such as small windows displayed on the side of the main window), etc., the specific implementation of which will not be elaborated here.
[0077] In one example, the target process node is a process node that outputs a failure result during the execution of the flowchart.
[0078] The information viewing pop-up window can also display the reasons for node errors that caused the target process node to fail to output results; and / or,
[0079] The information viewing pop-up window can also indicate the data flow that caused the target process node to fail to output a result; and / or,
[0080] The information viewing pop-up window can also display specific error information that caused the target process node to fail to output results.
[0081] For example, the flowchart displayed in the visual flowchart interface can run according to control instructions, and during the run, each process node in the flowchart can output a success result or a failure result. The specific implementation will be explained below. When the target process node is a process node that outputs a failure result during the flowchart run, the information viewing pop-up window can also display information such as the reasons for the output result of the target process node.
[0082] As an example, the information viewing pop-up window can display the node error reasons that cause the target process node to fail to output results, as shown in Figure 2.
[0083] For example, if a target process node fails to output a result due to a parameter error in a certain data flow direction, the node error could be due to a parameter error, as illustrated in Figure 11.
[0084] As an example, the information viewing pop-up can indicate the data flow that caused the target process node to fail to output a result.
[0085] For example, the information viewing pop-up window can correspond to the data flow that caused the target process node to fail to output a result, and mark the specific error information that caused the target process node to fail to output a result.
[0086] Taking the information viewing floating window shown in Figure 11 as an example, the data flow that causes the target process node to fail to output is as follows: the output 3 of node name 2 is output to the input 2 of node name 3. The reason why this data flow causes the target process node to fail to output is that the parameter value of the output 3 of node name 2 output to the input 2 of node name 3 is greater than 5.0 (the specific parameter value is 11.0).
[0087] As an example, the information viewer can display specific error messages that caused the target process node to fail to output a result.
[0088] Taking the information viewing floating window shown in Figure 11 as an example, the specific error message that caused the target process node to fail to output the result is that the parameter value of the output 3 of node name 2 to the input 2 of node name 3 is greater than 5.0.
[0089] In one example, when the flowchart is in a running state, the information viewing pop-up can also display the running time of the target process node.
[0090] Taking the information viewing floating window shown in Figure 11 as an example, the execution time of the target process node is 23ms.
[0091] In some embodiments, before receiving the data flow viewing request for the target process node, the following may also be included:
[0092] Upon detecting an instruction to enable the information viewing function, control the flowchart in the visual flowchart interface to enter the information viewing mode;
[0093] The aforementioned receiving of a data flow viewing request for a target process node may include:
[0094] When the flowchart is in information viewing mode, receive selection instructions for the target process node.
[0095] For example, since conventional flowchart display interfaces do not support viewing the data flow direction of process nodes, in order to improve the convenience and efficiency of data flow viewing, as well as the controllability and compatibility of the solution, an information viewing function can be designed for the flowchart in the visual flowchart interface. When this information viewing function is enabled, relevant personnel (such as users) can view the data flow direction of process nodes; when this information viewing function is disabled, relevant personnel cannot view the data flow direction of process nodes.
[0096] For example, when the information viewing function is enabled, the flowchart in the visual flowchart interface can enter the information viewing mode. In this mode, relevant personnel can select a process node in the flowchart to trigger the viewing of the data flow of the selected process node.
[0097] Accordingly, upon detecting an instruction to enable the information viewing function, the flowchart in the visual flowchart interface can be controlled to enter the information viewing mode.
[0098] When the flowchart is in information viewing mode, selection instructions for process nodes in the flowchart can be detected, and if a selection instruction for a target process node is detected, it can be determined that a data flow viewing request for the target process node has been received.
[0099] It should be noted that, in the embodiments of this application, the method of initiating a data flow viewing request for a target process node described in the above embodiments is only a specific example of the embodiments of this application, and is not a limitation on the protection scope of the embodiments of this application. The technical solution provided by the embodiments of this application can also implement the initiation of a data flow viewing request in other ways. For example, a data flow viewing function can be added to the function menu of the process node in the flowchart (for example, the function menu can be triggered by right-clicking or long-pressing the mouse). Relevant personnel can initiate a data flow viewing request for the selected process node by selecting the data flow viewing function in the function menu of the process node.
[0100] In some embodiments, the flowchart interface data visualization method provided in this application may further include:
[0101] Determine the node status of at least one process node in the flowchart;
[0102] For process nodes in abnormal states, the cause information of the abnormal state is displayed in the visual flowchart interface.
[0103] For example, in order to facilitate relevant personnel to quickly locate and handle problems in the flowchart, the node status of at least one process node in the flowchart can be determined.
[0104] For example, the above-mentioned at least one process node may include all process nodes in the flowchart, or some process nodes, such as the process node selected by the user.
[0105] For process nodes in abnormal states, the cause information of the abnormal state can be displayed in the visual flowchart interface, thereby helping relevant personnel to understand the cause of the abnormality more intuitively.
[0106] For example, the abnormal state cause information is used to locate the reason why a process node is in an abnormal state.
[0107] In one example, determining the node state of at least one process node in the flowchart as described above may include:
[0108] For any process node added in the visual flowchart interface, determine the configuration integrity status of the process node, and display the node status of the process node in the visual flowchart interface based on the configuration integrity status of the process node; wherein, the node status includes normal status or abnormal status. The node status corresponding to the process node with complete and valid configuration parameters is normal status, and the node status corresponding to the process node with incomplete configuration parameters and / or invalid parameters is abnormal status.
[0109] For example, in order to ensure that the flowchart can function properly, it is necessary to ensure that each process node in the flowchart is configured completely.
[0110] Correspondingly, for any process node added in the visual flowchart interface, a configuration integrity check can be performed on the process node, and the node status of the process node can be determined and displayed based on the check results.
[0111] In one example, for any process node added in the visual flowchart interface, a configuration integrity check can be performed on the process node if a connection creation operation instruction for that process node is detected.
[0112] For example, for any process node added in the visual flowchart interface, the node status of the process node can be displayed in the visual flowchart interface according to the configuration integrity status of the process node.
[0113] For example, for any process node added in the visual flowchart interface, the data inherited by the process node from the corresponding existing process node can be determined based on the logical connection relationship between the process node and the existing process nodes in the flowchart interface, and the configuration integrity status of the process node can be determined based on the data inherited by the process node.
[0114] For example, for a process node with complete and valid configuration parameters (i.e., a fully configured process node), the node status is normal.
[0115] For process nodes with incomplete configuration parameters and / or invalid parameters (i.e., process nodes with incomplete configuration), the corresponding node status is an abnormal status.
[0116] In one example, process nodes in normal and abnormal states can be displayed with different visual effects.
[0117] For example, no special display effects are needed for process nodes in normal states; for process nodes in abnormal states, they can be highlighted, such as by displaying them in red, so that relevant personnel can more intuitively view process nodes in abnormal states.
[0118] In one example, determining the node state of at least one process node in the flowchart as described above may include:
[0119] After the flowchart starts running, the node status of at least one process node in the flowchart is determined based on the success or failure result output by at least one process node in the flowchart. The node status includes normal status or abnormal status. The node status corresponding to the process node that outputs a successful result is normal status, and the node status corresponding to the process node that outputs a failure result is abnormal status.
[0120] For example, after the flowchart starts running, the node status can be determined based on the successful results (which can be called OK results) or failed results (which can be called NG results) output by each process node.
[0121] For process nodes that output successful results, their node status is determined to be normal; for process nodes that output failed results, their node status is determined to be abnormal. This allows for a dynamic reflection of the actual operation of specified process nodes during flowchart execution, facilitating monitoring and problem localization.
[0122] As an example, during the execution of the flowchart, for any process node, the input data can be processed using the algorithm contained in the process node, and a success or failure result can be output based on the comparison result between the processing result and the configuration value of the process node. In addition, if the process node is not the tail node, the specified data can be output to the next associated node.
[0123] For example, for any process node, the configuration value of this process node can be a threshold range. If the processing result of the input data processed by this process node is within the threshold range, a success result can be output; otherwise, a failure result can be output.
[0124] For example, if the current process node is not the tail node (i.e., there are other process nodes that use the output data of this process node as input data), the specified data can also be output to the next associated node.
[0125] For example, in order to help relevant personnel better distinguish between process nodes that output successful results and process nodes that output failed results in a flowchart, the process nodes that output successful results and process nodes that output failed results can be displayed with different display effects based on the successful or failed results output by each process node in the current flowchart.
[0126] For example, you can use colors to distinguish between process nodes that output successful results and process nodes that output failed results.
[0127] For example, process nodes that output successful results can be displayed in green; process nodes that output failed results can be displayed in red.
[0128] As an example, displaying the cause information of an abnormal state in a visual flowchart interface can include:
[0129] For any process node in an abnormal state, first abnormal state cause information is displayed in a designated area associated with that process node. The first abnormal state cause information is used to indicate the main reason for the abnormality of that process node.
[0130] For example, for any process node in an abnormal state, the cause information of the abnormal state (which can be called the first cause information of the abnormal state) can be displayed in a designated area associated with the process node (such as below the display area of the process node in the visual flowchart interface), so that relevant personnel can intuitively determine the cause of the abnormal state of the process node.
[0131] For example, the first abnormal state cause information can be used to indicate the main reason for the abnormality of the process node.
[0132] In one example, if the length of the first abnormal state cause information exceeds the display range of the specified area associated with the process node, and a selection instruction for the specified area is detected (such as the current operation cursor being mapped to the specified area), the complete first abnormal state cause information is displayed.
[0133] As an example, displaying the cause information of an abnormal state in a visual flowchart interface can include:
[0134] An exception statistics list is displayed in a designated area of the visual flowchart interface; the exception statistics list is used to record exception process node information; the exception process node information includes the identification information of the process node in the exception state, and the second exception state cause information of the process node in the exception state, the second exception state cause information includes the exception value code, and / or, the exception cause information.
[0135] For example, a list of anomaly statistics can be added to a designated area of the visual flowchart interface so that relevant personnel can view more comprehensive information about the process nodes with abnormal states in the flowchart.
[0136] For example, the exception statistics list is used to record information about exception process nodes.
[0137] For example, the abnormal process node information includes the identification information of the process node in an abnormal state, and the abnormal state cause information of the process node in an abnormal state (which can be referred to as the second abnormal state cause information).
[0138] For example, the second abnormal state cause information may include an abnormal value code and / or an abnormal cause information.
[0139] Among them, outlier codes can be used to identify a type of abnormal state, and relevant personnel can determine the relevant cause information of the abnormal process node based on the outlier code.
[0140] In one example, the exception statistics list is hidden when not triggered, and the hidden exception statistics list displays at least some exception process node information.
[0141] For example, in order to reduce the impact of displaying the anomaly statistics list on the display of other information, the anomaly statistics list can be hidden when not triggered.
[0142] For example, relevant personnel can trigger the display of the abnormal statistics list by clicking on it or placing the cursor in the corresponding area of the list.
[0143] For example, the hidden anomaly statistics list displays at least some of the anomaly process node information.
[0144] For example, if there is only one abnormal process node in the abnormal statistics list, the hidden abnormal statistics list can display all abnormal process node information; if there is more than one abnormal process node in the abnormal statistics list, the hidden abnormal statistics list can display some abnormal process node information.
[0145] For example, a hidden anomaly statistics list can display the information of the first anomaly process node in the list (which can be sorted according to the order in which the anomaly was determined).
[0146] In some embodiments, the flowchart interface data visualization method provided in this application may further include:
[0147] If a run operation command is detected for the current flowchart, and it is determined that the status of each process node in the current flowchart is normal, the current flowchart is controlled to enter the run state.
[0148] Based on the success or failure results output by each process node in the current flowchart, process nodes that output successful results and process nodes that output failure results are displayed with different display effects.
[0149] For example, when all process nodes in the flowchart are in a normal state, relevant personnel can control the flowchart to run by running operation commands.
[0150] Accordingly, when a run operation instruction for the current flowchart is detected, and it is determined that the node status of each process node in the current flowchart is normal, the current flowchart can be controlled to enter the running state.
[0151] In some embodiments, the flowchart interface data visualization method provided in this application may further include:
[0152] Determine the execution time of at least one process node in the flowchart;
[0153] Display the execution time of at least one process node in the visual flowchart interface.
[0154] For example, in order to help relevant personnel understand the running performance of process nodes in a flowchart, the running time of at least one process node can be determined and displayed in the visual flowchart interface, thereby helping relevant personnel identify performance bottlenecks and optimize flowchart configuration.
[0155] For example, the above-mentioned at least one process node may include all process nodes in the flowchart, or some process nodes, such as the process node selected by the user.
[0156] In one example, displaying the execution time of each process node in the visual flowchart interface can include:
[0157] For any process node in the visual flowchart interface, the execution time of that process node is displayed in the specified area associated with that process node.
[0158] For example, for any process node in the visual flowchart interface, the running time of the process node can be displayed in a designated area associated with the process node (such as below the display area of the process node in the visual flowchart interface), so that relevant personnel can intuitively determine the running time of the designated process node.
[0159] In one example, displaying the execution time of at least one process node in a visual flowchart interface could include:
[0160] Display the execution time of at least one process node in the flowchart in a designated area of the visual flowchart interface.
[0161] For example, the runtime information of all or part of the process nodes can be uniformly displayed in a designated area (such as the sidebar or bottom bar) of the visual flowchart interface, which is convenient for centralized viewing and comparison.
[0162] In one example, displaying the execution time of at least one process node in a visual flowchart interface can include:
[0163] If it is determined that the current time consumption information viewing mode is in progress, the execution time of at least one process node will be displayed in the visual flowchart interface.
[0164] For example, a dedicated time consumption information viewing mode can be set up to display the running time information of at least one process node.
[0165] For example, in the non-time-consuming information viewing mode, the running time-consuming information can be hidden or not displayed, thereby avoiding information overload on the interface and improving the flexibility of viewing time-consuming information.
[0166] As an example, the execution time of at least one process node is set to the default value before the flowchart starts running.
[0167] For example, the above default value can be 0, or other values used to indicate that the current flowchart has not started running, such as a preset invalid value.
[0168] In one example, the flowchart interface data visualization method provided in this application embodiment may further include:
[0169] If it is determined that the current error message viewing mode is in effect, the cause information of the abnormal state will be displayed in the visual flowchart interface for the process nodes in the abnormal state.
[0170] For example, a dedicated error message viewing mode can also be set up to display the cause information of the abnormal state of the process nodes in the flowchart.
[0171] For example, in non-error information viewing mode, the cause information of the abnormal state is not displayed or hidden, thereby avoiding information overload on the interface and improving the flexibility of viewing the cause information of the abnormal state.
[0172] For example, multiple viewing modes can be set, such as error message viewing mode and time consumption information viewing mode, displaying different types of information in different modes. For instance, error message viewing mode displays information about the cause of the abnormal status, while time consumption information viewing mode displays information about the running time, allowing relevant personnel to choose the appropriate information to view according to their actual needs.
[0173] As an example, the flowchart interface data visualization method provided in this application embodiment may further include:
[0174] In response to the detection of an operation command triggered in the visual flowchart interface, the view mode corresponding to the operation command is switched; the view mode is either the error message view mode or the time consumption view mode.
[0175] For example, a mode switching function can be provided in the visual flowchart interface, allowing relevant personnel to switch viewing modes by clicking the corresponding function buttons or entering corresponding operation commands. For instance, switching from error message viewing mode to time-consuming information viewing mode, or vice versa, allows for flexible viewing of different types of information.
[0176] For example, a function button for selecting "Error Message Viewing" mode or "Time Consumption Information Viewing" mode can be displayed in a designated location (such as a specific area in the upper left corner) of the visual flowchart interface. Relevant personnel can choose to enter the "Error Message Viewing" mode or "Time Consumption Information Viewing" mode according to their needs.
[0177] It should be noted that, in the embodiments of this application, the flowchart in the visual flowchart interface can be set to "error information viewing" mode by default, and relevant personnel can switch to "time consumption information viewing" mode as needed; or, the flowchart in the visual flowchart interface can be set to "time consumption information viewing" mode by default, and relevant personnel can switch to "error information viewing" mode as needed.
[0178] In one example, the display status of the execution time of at least one process node can be dynamically determined based on the real-time execution time sorting results of at least one process node in the visual flowchart interface.
[0179] The visual flowchart interface also displays the correspondence between the execution time of different display states and the ranking results of execution time.
[0180] For example, in order to better distinguish which process nodes take too long and which process nodes take less time, the runtime information can be specially processed and displayed.
[0181] For example, the execution time of different process nodes can be distinguished and displayed based on the sorting results of the execution time of different process nodes.
[0182] Furthermore, considering that the running time of each process node changes dynamically during the entire process, the real-time running time of each process node can be dynamically determined in order to display the running time of each process node more accurately.
[0183] Accordingly, the display status of the execution time of at least one process node can be dynamically determined based on the real-time execution time sorting results of at least one process node in the visual flowchart interface.
[0184] For example, in order to ensure that users can effectively identify the correspondence between different display states and the order of execution time, the visual flowchart display interface can also display the correspondence between the execution time of different display states and the order of execution time.
[0185] For example, suppose we use different colors to distinguish the running time of process nodes: blue can indicate the lowest running time, yellow can indicate a slightly lower running time, orange can indicate a slightly higher running time, and red can indicate the highest running time.
[0186] Accordingly, the real-time running time of each process node in the flowchart can be sorted, and the real-time running time of each process node can be divided into 4 groups according to the sorting results. The real-time running time is displayed in blue, yellow, orange and red in order from low to high.
[0187] To enable those skilled in the art to better understand the technical solutions provided in the embodiments of this application, the technical solutions provided in the embodiments of this application are described below in conjunction with specific application scenarios.
[0188] Please refer to Figure 3, which is a flowchart diagram of a flowchart construction and execution provided in an embodiment of this application. As shown in Figure 3, during the flowchart construction process, for each added process node, if a connection operation is detected for that process node, the configuration integrity can be checked and the node status of each process node can be displayed.
[0189] If a process node is in an abnormal state, it can be displayed as abnormal so that relevant personnel can view the abnormal process node and adjust its configuration.
[0190] If a configuration adjustment instruction is detected for a process node in an abnormal state, the configuration integrity check of that process node can be performed again.
[0191] When all process nodes in the flowchart are in a normal state and a run operation instruction for the current flowchart is detected, the current flowchart is controlled to enter the running state.
[0192] In the flowchart, each process node can be executed in the logical order of its construction.
[0193] For any process node, based on the input data of that process node, the algorithm contained in this process node is used to process the input data, and based on the comparison result of the processing result with the configuration value of this process node, a success result or a failure result is output.
[0194] For example, different display effects can be used for process nodes that output successful results and process nodes that output failed results.
[0195] The following section explains the relevant implementation details of the above process.
[0196] I. Configuration integrity check.
[0197] For example, process nodes can be divided into normal nodes (process nodes in normal state) and abnormal nodes (process nodes in abnormal state) based on the completeness of their configuration.
[0198] Among them, process nodes with complete and valid configuration parameters (i.e., normal nodes) are displayed as normal (without special processing effects); process nodes with incomplete configuration parameters or invalid parameters are displayed as abnormal.
[0199] For example, for abnormal nodes, the node can be highlighted as an abnormal state, and text explaining the main reason for the abnormality can be displayed below the node (e.g., the first abnormal state reason information mentioned above).
[0200] For example, as shown in Figure 4A, three process nodes have been added to the flowchart and formed logical connections. The three process nodes are fully configured and all three process nodes are displayed in a normal state (without any special processing effects).
[0201] As shown in Figure 4B, drag two new nodes (which can be named Node Name 3 and Node Name 4) into the process, and connect the new process nodes with existing process nodes to create logical relationships. When connecting the new nodes, the new nodes can automatically inherit some of the sequential data from the existing process according to the connection logic.
[0202] For example, suppose node name 2 is the node that outputs the image, and node name 3 and node name 4 are the nodes that need to input the image for image search, etc. When the connection relationship is created, the image output by node name 2 will be automatically associated with node name 3 and node name 4 (that is, node name 3 and node name 4 automatically subscribe to the output data of node name 2).
[0203] However, if the configuration of the newly added node is still incomplete after inheriting the data, the node will be displayed as an abnormal state.
[0204] For example, upon detecting an instruction to enable the information viewing function, the flowchart in the visual flowchart interface can be controlled to enter an information viewing mode.
[0205] When the information viewing mode is enabled, a "Error Message Viewing" or "Time Consumption Information Viewing" selection button will be displayed in a specific area in the upper left corner of the visual flowchart interface. Relevant personnel can select either mode based on their actual needs, as illustrated in Figure 5A.
[0206] For example, as shown in Figure 5A (Figure 5A takes the "Error Information Viewing" mode as an example), for abnormal nodes, on the one hand, the reason for the node's abnormality can be displayed below the abnormal node; on the other hand, a special area can be provided in the lower left corner of the interface to display the abnormal statistics list. Under normal circumstances (i.e., when it is not triggered), the abnormal statistics list will be hidden (i.e., it is in a hidden state).
[0207] As shown in Figure 5A, the anomaly statistics list is in a hidden state, and only the information of the first anomaly node can be displayed.
[0208] For example, as shown in Figure 5B, the exception statistics list can be fully displayed by triggering the display operation button on the interface. The fully displayed exception statistics list shows all exception nodes, their exception causes, and exception value codes.
[0209] II. Flowchart Operation.
[0210] When all process nodes in the flowchart are in a normal state, the "Execute Run" operation can be performed, that is, relevant personnel can trigger the flowchart to run through the "Execute Run" function button.
[0211] During the flowchart operation, each process node will process the received data using the algorithm contained in this process node, output the specified data, and pass it to the next related node (if it exists).
[0212] For any process node, the processing result of the input data of this process node can be compared with the configuration value of this process node, and the output result (OK or NG) can be determined based on the comparison result.
[0213] For example, process nodes whose processing results match the configured value (e.g., the configured value is within the threshold range and the processing result is within the threshold range) output an OK result; process nodes whose processing results do not match the configured value output an NG result.
[0214] For example, a process node that outputs an OK result can be displayed as a success status; a process node that outputs an NG result can be displayed as a failure status.
[0215] For example, when the flowchart is in "error information viewing" mode, for a failed process node, the error reason information that caused the node to be NG (also known as the reason for the node's NG result) can be displayed in the area below the display area of the process node, as shown in Figure 6.
[0216] For example, as shown in Figure 7, in this embodiment, the process for viewing process data information can be implemented as follows:
[0217] 1. The visual flowchart interface already has added process nodes, and these existing process nodes will display their corresponding status.
[0218] For example, when the flowchart is not running, the normal or abnormal state of the process node can be determined based on the configuration integrity status of the process node.
[0219] After the flowchart starts running, the process node can be determined as the process node that outputs an OK result or an NG result based on the success result (i.e., OK result) or failure result (i.e. NG result) output by the process node.
[0220] Nodes in different states can be displayed separately.
[0221] 2. Upon detecting an instruction to enable the information viewing function, control the flowchart in the visual flowchart interface to enter the information viewing mode.
[0222] 3. Based on the detected selection command for "Error Message Viewing" mode or "Time Consumption Information Viewing" mode, enter the "Error Message Viewing" mode or "Time Consumption Information Viewing" mode.
[0223] 4. In the "Error Message Viewing" mode, special processing is performed on the process nodes in the flowchart that are in an abnormal state (or process nodes that output NG results). The obtained reasons for the node abnormality or error are displayed near the corresponding abnormal node. The schematic diagram can be shown in Figure 8A.
[0224] 5. In the "Time Consumption Information Viewing" mode, all process nodes in the flowchart are displayed with special processing, and their corresponding running time data are displayed near all process nodes.
[0225] For example, the execution time of each process node can be a default value, such as 0, before the flowchart starts running.
[0226] After the flowchart starts running, the display status of the running time of each process node is dynamically determined based on the real-time running time sorting results of each process node in the visual flowchart interface.
[0227] For example, in order to ensure that users can effectively identify the correspondence between different display states and the order of execution time, the visual flowchart display interface can also display the correspondence between the execution time of different display states and the order of execution time, as shown in Figure 8B.
[0228] For example, suppose we use different colors to distinguish the running time of process nodes: blue can indicate the lowest running time, yellow can indicate a slightly lower running time, orange can indicate a slightly higher running time, and red can indicate the highest running time.
[0229] Accordingly, the real-time running time of each process node in the flowchart can be sorted, and the real-time running time of each process node can be divided into 4 groups according to the sorting results. The real-time running time is displayed in blue, yellow, orange and red in order from low to high.
[0230] III. Viewing Data Flow
[0231] As shown in Figure 9, in this embodiment, the implementation process for viewing the data flow of process nodes in the flowchart is as follows:
[0232] 1. Display all nodes and their configuration status in the visual flowchart interface.
[0233] 2. Upon detecting an instruction to enable the information viewing function, control the flowchart in the visual flowchart interface to enter the information viewing mode.
[0234] 3. When the flowchart is in information viewing mode, receive selection instructions for the target process node.
[0235] For example, when the flowchart is in the information viewing mode and a selection instruction for the target process node is received, it is determined that a data flow viewing request for the target process node has been received.
[0236] 4. Responding to received data flow viewing requests, the system differentiates between related nodes (also known as relevant nodes) and unrelated nodes (also known as irrelevant nodes) in the flowchart. It highlights related nodes that interact with the selected node and weakens the display of other unrelated nodes. Furthermore, an information viewing pop-up window is displayed next to the selected flow node (such as the target flow node mentioned above). This pop-up window displays all related nodes that interact with the selected node and their specific interaction data parameters, as illustrated in Figure 10.
[0237] As shown in Figure 10, assuming the target process node is "Node Name 8", the three nodes "Node Name 0", "Node Name 2" and "Node Name 9" (i.e., associated nodes) that have data flow interaction with it can be highlighted, while the display effect of the remaining nodes (i.e., non-associated nodes) can be weakened, and the corresponding information viewing floating window can be displayed on the right side of the display area of the target process node.
[0238] A detailed illustration of the information viewing floating window can be seen in Figure 2.
[0239] The information viewing pop-up window displays the name of this process node, the time taken for this process node to process data, the error / abnormal reason for this process node (if this process node outputs a failure result), and enumerates all the associated nodes (i.e., input nodes) to which input data is sent and the associated nodes (i.e., output nodes) to which output data is sent.
[0240] For example, for an input node, the name of the input node can be displayed and the specific parameter names of the input and the corresponding specific parameter names of the bound nodes in this process can be listed; for an output node, the name of the output node can be displayed and the specific parameter names of the output node in this process can be listed and the corresponding specific parameter names of the output nodes can be listed.
[0241] As shown in Figure 2, for process node 8, the input nodes may include process node 0 and process node 2, and the output node may include process node 9.
[0242] For process node 0, the input parameters include parameter value 1, parameter value 2, parameter value 3 and parameter value 4, and each parameter is input to parameter 1, parameter 2, parameter 3 and parameter 4 of process node 8 respectively.
[0243] For process node 2, the input parameters include parameter value 5, which is input to parameter 5 in process node 8.
[0244] For process node 9, the parameters output by this process node include parameter 6, which is the parameter 6 output to process node 9.
[0245] The information viewing pop-up window allows for a more convenient view of the data flow at each process node without opening the configuration panel.
[0246] For example, a diagram illustrating the information pop-up window in case of parameter errors can be found in Figure 11. As shown in Figure 11, for node name 3, its input nodes can include node name 1 and node name 2. The output node can include node name 4.
[0247] For node name 1, the parameter input to node name 3 is the output 1 of node name 1, and this parameter is output to the input 1 of node name 3. As shown in Figure 11, in this example, the parameter value is 6.0.
[0248] For node name 2, the parameter input to node name 3 is the output 3 of node name 2, and this parameter is output to the input 2 of node name 3. As shown in Figure 11, in this example, the parameter value is 11.0.
[0249] In this example, the normal parameter value range for input 2 of node name 3 is required to be no more than 5.0. Since the parameter value of output 3 of node name 3 is 11.0, and 11.0 > 5.0, an error occurs, and the error reason is "input parameter value is greater than 5.0".
[0250] For node name 4, the output of node name 3 to node name 4 is output 1, and this parameter is also output to the input 1 of node name 4. As shown in Figure 11, in this example, the parameter value is 1.0.
[0251] Based on the information floating window shown in Figure 11, relevant personnel can clearly and intuitively view the input and output parameters of the node, and clearly understand the reason for the parameter error if there is one.
[0252] For example, to more intuitively display abnormal parameters, normal parameters and error parameters can be displayed separately. This can be achieved by using different colors or other status indicators to differentiate between normal and error parameters.
[0253] In one example, abnormal parameters can be displayed in red, and normal parameters can be displayed in green.
[0254] As can be seen, the technical solution provided in this application embodiment can provide a comprehensive and intuitive display of data visualization information. The visualized flowchart interface displays more comprehensive data information, including the configuration integrity status of process nodes, the status of data anomalies, the cause of the anomalies, the running time, and the data flow direction. This effectively helps users quickly locate and identify key information when configuring and maintaining complex flowcharts, facilitating maintenance and adjustments.
[0255] In addition, the information viewing floating window effectively ensures that even if the process cannot display all nodes, all interaction node information and specific interaction data can still be viewed through the floating window, making it convenient for maintenance personnel to quickly switch nodes to troubleshoot process configurations.
[0256] Take a visual inspection workflow as an example. A typical visual inspection workflow in a project site usually involves more than 100 workflow nodes. After the workflow is built, it needs to be maintained and adjusted regularly. By intuitively locating abnormal nodes in the flowchart interface and based on the exposed causes of the problems, even if not all workflow nodes are displayed under a single workflow canvas, a floating window can be used to view the undisplayed related nodes and which specific parameter flow is problematic, allowing for quick configuration adjustments.
[0257] The method provided in this application has been described above. The apparatus provided in this application is described below:
[0258] Please refer to Figure 12, which is a schematic diagram of the structure of a flowchart interface data visualization display device provided in an embodiment of this application. As shown in Figure 12, the flowchart interface data visualization display device may include:
[0259] The receiving unit is used to receive a data flow viewing request for a target process node; wherein, the target process node is any process node in the flowchart displayed in the visual flowchart interface.
[0260] A determining unit is used to determine associated nodes and non-associated nodes in a flowchart; wherein, the associated nodes are the flowchart nodes that have data flow interaction with the target flowchart node; and the non-associated nodes are the remaining flowchart nodes other than the target flowchart node and the associated nodes.
[0261] An output unit is used to output information viewing interface elements; wherein the information viewing interface elements are used to display the identification information of the associated nodes, as well as the interaction data information between each associated node and the target process node.
[0262] In some embodiments, the receiving unit receives a data flow viewing request for a target process node, including:
[0263] A keyword search command matching the node name of the target process node was detected.
[0264] In some embodiments, before the receiving unit receives a data flow viewing request for a target process node, it further includes:
[0265] Upon detecting an instruction to enable the information viewing function, the flowchart in the visual flowchart interface is controlled to enter the information viewing mode.
[0266] The receiving unit receives a data flow viewing request for the target process node, including:
[0267] When the flowchart is in information viewing mode, a selection instruction for the target process node is received.
[0268] In some embodiments, the information viewing interface elements include an information viewing floating window;
[0269] The associated nodes displayed in the information viewing floating window include input nodes and / or output nodes. For any input node, the interactive data information includes the input parameter name and the parameter name of the corresponding bound target process node.
[0270] For any of the output nodes, the interactive data information includes the output parameter name and the parameter name of the corresponding output node.
[0271] In some embodiments, when the target process node is a process node that outputs a failure result during the execution of the flowchart...
[0272] The information viewing pop-up also displays the node error reasons that caused the target process node to fail to output a result; and / or,
[0273] The information viewing pop-up also indicates the data flow that caused the target process node to fail to output a result; and / or,
[0274] The information viewing pop-up also displays specific error information that caused the target process node to fail to output a result;
[0275] And / or,
[0276] When the flowchart is in running state, the information viewing pop-up window also displays the running time of the target process node.
[0277] In some embodiments, the flowchart interface data visualization display device further includes:
[0278] The display unit is used to display the associated nodes and the non-associated nodes with different display effects respectively.
[0279] In some embodiments, the display unit displays the associated nodes and the non-associated nodes with different display effects, including:
[0280] The associated nodes are highlighted, and / or the non-associated nodes are displayed in a less prominent manner.
[0281] In some embodiments, the determining unit is further configured to determine the node state of at least one process node in the flowchart;
[0282] The display unit is also used to display the cause information of the abnormal state in the visual flowchart interface for process nodes in abnormal states.
[0283] In some embodiments, the determining unit is further configured to determine the configuration integrity status of any process node added to the visual flowchart interface.
[0284] The display unit is further configured to display the node status of the process node in the visualization flowchart interface based on the configuration integrity status of the process node; wherein, the node status includes a normal status or an abnormal status, the node status corresponding to the process node with complete and valid configuration parameters is a normal status, and the node status corresponding to the process node with incomplete configuration parameters and / or invalid parameters is an abnormal status.
[0285] In some embodiments, for any process node added to the visual flowchart interface, the determining unit determines the configuration integrity status of the process node, including:
[0286] For any process node added in the visualization flowchart interface, based on the logical connection relationship between the process node and the existing process nodes in the flowchart interface, the data inherited by the process node from the corresponding existing process node is determined, and the configuration integrity status of the process node is determined based on the data inherited by the process node.
[0287] In some embodiments, the determining unit determines the node state of at least one process node in the flowchart, including:
[0288] After the flowchart starts running, the node status of the at least one process node in the flowchart is determined based on the success or failure result output by the at least one process node in the flowchart; wherein, the node status includes a normal state or an abnormal state, the node status corresponding to the process node that outputs a successful result is a normal state, and the node status corresponding to the process node that outputs a failure result is an abnormal state.
[0289] In some embodiments, during the execution of the current flowchart, for any process node, based on the input data of the process node, the algorithm contained in the process node is used to process the input data, and based on the comparison result of the processing result with the configuration value of the process node, a success result or a failure result is output, and if the process node is not a tail node, specified data is output to the next associated node.
[0290] In some embodiments, the display unit displays abnormal state cause information in a visual flowchart interface, including:
[0291] For any process node in an abnormal state, first abnormal state cause information is displayed in a designated area associated with the process node. The first abnormal state cause information is used to indicate the main reason for the abnormality of the process node. If the length of the first abnormal state cause information exceeds the display range of the designated area associated with the process node, and a selection command for the designated area is detected, the complete first abnormal state cause information is displayed.
[0292] And / or,
[0293] An anomaly statistics list is displayed in a designated area of the visualization flowchart interface; wherein, the anomaly statistics list is used to record anomaly process node information; the anomaly process node information includes the identifier information of the process node in an anomaly state, and the second anomaly state cause information of the process node in an anomaly state, the second anomaly state cause information including an anomaly value code, and / or, an anomaly cause information.
[0294] In some embodiments, the anomaly statistics list is hidden when not triggered, and the hidden anomaly statistics list displays at least some anomaly process node information.
[0295] In some embodiments, the determining unit is further configured to determine the running time of at least one process node in the flowchart;
[0296] The display unit is also used to display the running time of the at least one process node in the visual flowchart interface.
[0297] In some embodiments, the display unit displays the execution time of at least one process node in a visual flowchart interface, including:
[0298] For any process node in the visualization flowchart interface, the execution time of the process node is displayed in the specified area associated with the process node;
[0299] and / or
[0300] The execution time of at least one process node in the flowchart is displayed in a designated area of the visual flowchart interface.
[0301] In some embodiments, the display unit displays the execution time of at least one process node in a visual flowchart interface, including:
[0302] If it is determined that the current time consumption information viewing mode is in progress, the execution time of at least one process node is displayed in the visual flowchart interface.
[0303] In some embodiments, the display unit is further configured to, when determining that the current state is in error information viewing mode, display the cause information of the abnormal state in the visualization flowchart interface for the process node in the abnormal state of the flowchart.
[0304] In some embodiments, the display unit is further configured to switch the viewing mode corresponding to the operation instruction in response to detecting an operation instruction triggered on the visualization flowchart interface; the viewing mode is the error information viewing mode or the time consumption viewing mode.
[0305] In some embodiments, the execution time of the at least one process node is a default value before the flowchart begins to run.
[0306] In some embodiments, the display unit is further configured to dynamically determine the display status of the running time of at least one process node based on the real-time running time sorting result of at least one process node in the visualization flowchart interface.
[0307] The visual flowchart interface also displays the correspondence between the running time of different display states and the sorting results of the running time.
[0308] This application provides an electronic device, including a processor and a memory, wherein the memory stores machine-executable instructions that can be executed by the processor, and the processor executes the machine-executable instructions to implement the flowchart interface data visualization display method described above.
[0309] Please refer to Figure 13, which is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application. The electronic device may include a processor 1301 and a memory 1302 storing machine-executable instructions. The processor 1301 and the memory 1302 can communicate via a system bus 1303. Furthermore, by reading and executing the machine-executable instructions in the memory 1302 corresponding to the flowchart interface data visualization display logic, the processor 1301 can execute the flowchart interface data visualization display method described above.
[0310] The memory 1302 mentioned in this document can be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, etc. For example, machine-readable storage media can be: RAM (Random Access Memory), volatile memory, non-volatile memory, flash memory, storage drives (such as hard disk drives), solid-state drives, any type of storage disk (such as optical discs, DVDs, etc.), or similar storage media, or combinations thereof.
[0311] In some embodiments, a machine-readable storage medium is also provided, such as memory 1302 in FIG13. The machine-readable storage medium stores machine-executable instructions, which, when executed by a processor, implement the flowchart interface data visualization method described above. For example, the storage medium may be ROM, RAM, CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.
Claims
1. A method for visualizing data using a flowchart interface, characterized in that, include: Receive a request to view the data flow direction of a target process node; wherein, the target process node is any process node in the flowchart displayed in the visual flowchart interface; Identify the associated and non-associated nodes in the flowchart; wherein, the associated nodes are the flowchart nodes that have data flow interaction with the target flowchart node; the non-associated nodes are the remaining flowchart nodes other than the target flowchart node and the associated nodes; and, Output information viewing interface elements; wherein, the information viewing interface elements are used to display the identification information of the associated nodes, as well as the interaction data information between each associated node and the target process node.
2. The method according to claim 1, characterized in that, The receiving of a data flow viewing request for a target process node includes: A keyword search command matching the node name of the target process node was detected.
3. The method according to claim 1, characterized in that, Before receiving the data flow viewing request for the target process node, the method further includes: Upon detecting an instruction to enable the information viewing function, the flowchart in the visual flowchart interface is controlled to enter the information viewing mode. The receiving of a data flow viewing request for a target process node includes: When the flowchart is in information viewing mode, a selection instruction for the target process node is received.
4. The method according to claim 1, characterized in that, The information viewing interface elements include an information viewing floating window; The associated nodes displayed in the information viewing floating window include input nodes and / or output nodes. For any input node, the interactive data information includes the input parameter name and the parameter name of the corresponding bound target process node. For any of the output nodes, the interactive data information includes the output parameter name and the parameter name of the corresponding output node.
5. The method according to claim 4, characterized in that, When the target process node is a process node that outputs a failure result during the execution of the flowchart. The information viewing pop-up also displays the node error reasons that caused the target process node to fail to output a result; and / or, The information viewing pop-up also indicates the data flow that caused the target process node to fail to output a result; and / or, The information viewing pop-up also displays specific error information that caused the target process node to fail to output a result; And / or, When the flowchart is in running state, the information viewing pop-up window also displays the running time of the target process node.
6. The method according to claim 1, characterized in that, The method further includes: The associated nodes and the non-associated nodes are displayed with different display effects respectively.
7. The method according to claim 6, characterized in that, The step of displaying the associated nodes and the non-associated nodes with different display effects includes: The associated nodes are highlighted, and / or the non-associated nodes are displayed in a less prominent manner.
8. The method according to claim 1, characterized in that, The method further includes: Determine the node status of at least one process node in the flowchart; For process nodes in abnormal states, the cause information of the abnormal state is displayed in the visual flowchart interface.
9. The method according to claim 8, characterized in that, Determining the node state of at least one process node in the flowchart includes: For any process node added in the visualization flowchart interface, determine the configuration integrity status of the process node, and display the node status of the process node in the visualization flowchart interface based on the configuration integrity status of the process node; wherein, the node status includes normal status or abnormal status, the node status corresponding to the process node with complete and valid configuration parameters is normal status, and the node status corresponding to the process node with incomplete configuration parameters and / or invalid parameters is abnormal status.
10. The method according to claim 9, characterized in that, For any process node added in the visual flowchart interface, determine the configuration integrity status of that process node, including: For any process node added in the visualization flowchart interface, based on the logical connection relationship between the process node and the existing process nodes in the flowchart interface, the data inherited by the process node from the corresponding existing process node is determined, and the configuration integrity status of the process node is determined based on the data inherited by the process node.
11. The method according to claim 8, characterized in that, Determining the node state of at least one process node in the flowchart includes: After the flowchart starts running, the node status of the at least one process node in the flowchart is determined based on the success or failure result output by the at least one process node in the flowchart; wherein, the node status includes a normal state or an abnormal state, the node status corresponding to the process node that outputs a successful result is a normal state, and the node status corresponding to the process node that outputs a failure result is an abnormal state.
12. The method according to claim 11, characterized in that, During the operation of the flowchart, for any process node, the input data of the process node is processed using the algorithm contained in the process node, and a success result or failure result is output based on the comparison result between the processing result and the configuration value of the process node. In addition, if the process node is not the tail node, the specified data is output to the next associated node.
13. The method according to claim 8, characterized in that, The display of abnormal status reason information in the visual flowchart interface includes: For any process node in an abnormal state, first abnormal state cause information is displayed in a designated area associated with the process node. The first abnormal state cause information is used to indicate the main reason for the abnormality of the process node. If the length of the first abnormal state cause information exceeds the display range of the designated area associated with the process node, and a selection command for the designated area is detected, the complete first abnormal state cause information is displayed. And / or, An anomaly statistics list is displayed in a designated area of the visualization flowchart interface; wherein, the anomaly statistics list is used to record anomaly process node information; the anomaly process node information includes the identifier information of the process node in an anomaly state, and the second anomaly state cause information of the process node in an anomaly state, the second anomaly state cause information including an anomaly value code, and / or, an anomaly cause information.
14. The method according to claim 13, characterized in that, The anomaly statistics list is hidden when not triggered, and the hidden anomaly statistics list displays at least some anomaly process node information.
15. The method according to claim 1, characterized in that, The method further includes: Determine the execution time of at least one process node in the flowchart; The execution time of at least one process node is displayed in the visual flowchart interface.
16. The method according to claim 15, characterized in that, Displaying the execution time of at least one process node in the visual flowchart interface includes: For any process node in the visualization flowchart interface, the execution time of the process node is displayed in the specified area associated with the process node; and / or The execution time of at least one process node in the flowchart is displayed in a designated area of the visual flowchart interface.
17. The method according to claim 15, characterized in that, Displaying the execution time of at least one process node in the visual flowchart interface includes: If it is determined that the current time consumption information viewing mode is in progress, the execution time of at least one process node is displayed in the visual flowchart interface.
18. The method according to claim 17, characterized in that, The method further includes: If it is determined that the current state is in error information viewing mode, for the process nodes in the flowchart that are in an abnormal state, the reason information of the abnormal state will be displayed in the visual flowchart interface.
19. The method according to claim 18, characterized in that, The method further includes: In response to detecting an operation command triggered on the visualization flowchart interface, the view mode corresponding to the operation command is switched; the view mode is either the error message view mode or the time consumption view mode.
20. The method according to claim 15, characterized in that, Before the flowchart starts running, the running time of the at least one process node is the default value.
21. The method according to claim 15, characterized in that, The method further includes: Based on the real-time running time ranking results of at least one process node in the visualization flowchart interface, the display status of the running time of the at least one process node is dynamically determined. The visual flowchart interface also displays the correspondence between the running time of different display states and the sorting results of the running time.
22. A flowchart interface data visualization display device, characterized in that, include: The receiving unit is used to receive a data flow viewing request for a target process node; wherein, the target process node is any process node in the flowchart displayed in the visual flowchart interface. A determining unit is used to determine associated nodes and non-associated nodes in a flowchart; wherein, the associated nodes are the flowchart nodes that have data flow interaction with the target flowchart node; and the non-associated nodes are the remaining flowchart nodes other than the target flowchart node and the associated nodes. An output unit is used to output information viewing interface elements; wherein the information viewing interface elements are used to display the identification information of the associated nodes, as well as the interaction data information between each associated node and the target process node.
23. An electronic device, characterized in that, The method includes a processor and a memory, the memory storing machine-executable instructions that can be executed by the processor, the processor executing the machine-executable instructions to implement the method as described in any one of claims 1-21.
24. A machine-readable storage medium, characterized in that, The machine-readable storage medium stores machine-executable instructions, which, when executed by a processor, implement the method as described in any one of claims 1-21.
