CN116382877B - Task execution method and device, storage medium and electronic equipment - Google Patents
Task execution method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN116382877B CN116382877B CN202310598325.3A CN202310598325A CN116382877B CN 116382877 B CN116382877 B CN 116382877B CN 202310598325 A CN202310598325 A CN 202310598325A CN 116382877 B CN116382877 B CN 116382877B
- Authority
- CN
- China
- Prior art keywords
- task
- workflow
- user
- task node
- subtask
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 83
- 230000006978 adaptation Effects 0.000 claims abstract description 80
- 230000004044 response Effects 0.000 claims description 38
- 238000004590 computer program Methods 0.000 claims description 16
- 238000004806 packaging method and process Methods 0.000 claims description 8
- 238000010276 construction Methods 0.000 claims description 2
- 238000013461 design Methods 0.000 abstract description 5
- 238000010586 diagram Methods 0.000 description 15
- 230000006870 function Effects 0.000 description 9
- 230000006872 improvement Effects 0.000 description 8
- 230000008569 process Effects 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 6
- 238000012545 processing Methods 0.000 description 6
- 238000004364 calculation method Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012549 training Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 229920001296 polysiloxane Polymers 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 239000010979 ruby Substances 0.000 description 1
- 229910001750 ruby Inorganic materials 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/30—Arrangements for executing machine instructions, e.g. instruction decode
- G06F9/30003—Arrangements for executing specific machine instructions
- G06F9/3005—Arrangements for executing specific machine instructions to perform operations for flow control
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Stored Programmes (AREA)
Abstract
The specification discloses a task execution method, a device, a storage medium and electronic equipment, wherein each subtask of a computing task is determined, an adaptation unit of input data of each subtask is determined, and each subtask and the adaptation unit corresponding to each subtask are packaged into each task node. And determining the task nodes selected by the user and the connection relation between the task nodes, constructing and obtaining a workflow, compiling and executing the workflow. The method does not need a user to design the adaptation relation of data among the subtasks, but directly selects the subtasks in the client and establishes the connection relation among the subtasks, and then the client can construct a workflow according to the subtasks selected by the user and the connection relation among the subtasks and compile and execute the workflow to obtain an execution result of the workflow. The method enables the adaptation of data between subtasks in the computing task to be completely transparent to the user, and reduces the complexity of constructing the workflow.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and apparatus for executing a task, a storage medium, and an electronic device.
Background
With the development of technology, intelligent computing is also rapidly developing. Generally, for some computation tasks with high space and time complexity (such as computation tasks in astronomy, materials, pharmacy and other fields), a workflow is designed to execute the computation of the task. In the process of designing the workflow, the connection relation of all the subtasks in the computing task is determined so as to ensure the completion of the computing task.
In general, a workflow requires a user to design himself, and in the process of designing the workflow, since the types of data that can be received by each subtask are different, an adaptation method of data between the subtasks is determined, so that one subtask can receive data output by other subtasks. However, this is extremely difficult for the user.
Based on the above, the specification of the application provides a task execution method.
Disclosure of Invention
The present disclosure provides a method, an apparatus, a storage medium, and an electronic device for performing tasks, so as to at least partially solve the foregoing problems in the prior art.
The technical scheme adopted in the specification is as follows:
the specification provides a method for executing a task, the method comprising:
Determining each subtask in the computing task;
for each sub-task, determining an adaptation unit for adapting input data of the sub-task; wherein, at least, the adaptation unit includes: an adaptation method for converting the format of the input data of the subtask into the data format supported by the subtask;
packaging the subtasks and the adaptation unit as task nodes;
responding to the operation of a user on the task nodes, and determining the connection relationship between the task nodes selected by the user and the task nodes selected by the user;
constructing a workflow according to the determined task nodes selected by the user and the connection relation;
compiling and executing each task node in the workflow.
Optionally, determining an adapting unit for adapting the input data of the subtask specifically includes:
carrying out structural description on the input data of the subtasks; wherein the structured description comprises at least: determining the type, the identification and the default value of the input data of the subtask;
and determining an adaptation unit for adapting the input data of the subtask after the structural description according to the structural description of the input data of the subtask.
Optionally, in response to the operation of the user on the task node, determining the task node selected by the user specifically includes:
displaying the list and canvas; wherein the list at least comprises task nodes;
responsive to a user dragging at least one task node from the list into the canvas, displaying the user-dragged at least one task node in the canvas as the user-selected task node.
Optionally, in response to the operation of the user on the task node, determining the connection relationship between the task node selected by the user and the task node selected by the user specifically includes:
displaying the list and canvas; wherein the list at least comprises a workflow template; the workflow template comprises a plurality of task nodes and connection relations among the plurality of task nodes;
in response to a user dragging at least one workflow template from the list into the canvas, displaying the user-dragged at least one workflow template in the canvas, taking a plurality of task nodes in the user-dragged at least one workflow template as the user-selected task nodes, and taking connection relations among the plurality of task nodes in the user-dragged at least one workflow template as connection relations among the user-selected task nodes.
Optionally, determining the connection relationship between the task nodes selected by the user specifically includes:
responding to the connection operation of the user on the task nodes in the canvas, determining a previous task node and a next task node in the connection operation aiming at each connection operation, and judging whether a method for adapting the output data of the previous task node exists in an adapting unit of the next task node;
if yes, executing the connection operation, and displaying the connection between the task nodes corresponding to the connection operation;
if not, refusing to execute the connection operation.
Optionally, before compiling and executing each task node in the workflow, the method further comprises:
determining the resource parameters of the task node in response to the resource parameter setting operation of the user on the task node; wherein the resource parameters at least include: the number of computing devices, the memory parameters of each computing device, and the graphics processor core number of each computing device;
executing each task node in the workflow, specifically including:
and executing the subtasks corresponding to the task nodes in the workflow by using the computing equipment corresponding to the resource parameters according to the resource parameters of the task nodes in the workflow.
Optionally, before compiling and executing each task node in the workflow, the method further comprises:
receiving an operation parameter input into the task node by a user;
compiling and executing each task node in the workflow, and specifically comprising the following steps:
and compiling and executing the task node according to the operation parameters input into the task node by the user.
Optionally, compiling each task node in the workflow specifically includes:
judging whether the connection relation between all task nodes in the workflow meets the specified condition or not;
if yes, generating a compiling result of the workflow;
if not, compiling the workflow is not passed.
Optionally, the method further comprises:
when each task node in the workflow is compiled and executed successfully;
removing operation parameters and resource parameters of each task node in the workflow to obtain a workflow template corresponding to the workflow;
and storing the workflow template.
The specification provides a task execution device, which comprises:
the determining module is used for determining each subtask in the computing task;
the adaptation module is used for determining an adaptation unit for adapting the input data of each subtask according to each subtask; wherein, at least, the adaptation unit includes: an adaptation method for converting the format of the input data of the subtask into the data format supported by the subtask;
The packaging module is used for packaging the subtasks and the adaptation unit into task nodes;
the response module is used for responding to the operation of the user on the task nodes and determining the task nodes selected by the user and the connection relation between the task nodes selected by the user;
the construction module is used for constructing a workflow according to the determined task nodes selected by the user and the connection relation;
and the execution module is used for compiling and executing each task node in the workflow.
Optionally, the adaptation module is specifically configured to perform structural description on input data of the subtask; wherein the structured description comprises at least: determining the type, the identification and the default value of the input data of the subtask; and determining an adaptation unit for adapting the input data of the subtask after the structural description according to the structural description of the input data of the subtask.
Optionally, the response module is specifically configured to display a list and a canvas; wherein the list at least comprises task nodes; responsive to a user dragging at least one task node from the list into the canvas, displaying the user-dragged at least one task node in the canvas as the user-selected task node.
Optionally, the response module is specifically configured to display a list and a canvas; wherein the list at least comprises a workflow template; the workflow template comprises a plurality of task nodes and connection relations among the plurality of task nodes; in response to a user dragging at least one workflow template from the list into the canvas, displaying the user-dragged at least one workflow template in the canvas, taking a plurality of task nodes in the user-dragged at least one workflow template as the user-selected task nodes, and taking connection relations among the plurality of task nodes in the user-dragged at least one workflow template as connection relations among the user-selected task nodes.
Optionally, the response module is specifically configured to, in response to a connection operation between task nodes in the canvas by the user, determine, for each connection operation, a previous task node and a next task node in the connection operation, and determine whether a method for adapting output data of the previous task node exists in an adapting unit of the next task node; if yes, executing the connection operation, and displaying the connection between the task nodes corresponding to the connection operation; if not, refusing to execute the connection operation.
Optionally, the response module is further configured to determine a resource parameter of the task node in response to a user setting operation on the resource parameter of the task node; wherein the resource parameters at least include: the number of computing devices, the memory parameters of each computing device, and the graphics processor core number of each computing device;
the execution module is specifically configured to execute subtasks corresponding to each task node in the workflow by using a computing device corresponding to the resource parameter according to the resource parameter of each task node in the workflow.
Optionally, the response module is further configured to receive an operation parameter input into the task node by a user;
the execution module is specifically configured to compile and execute the task node according to the operation parameter input into the task node by the user.
Optionally, the execution module is specifically configured to determine whether a connection relationship between task nodes in the workflow meets a specified condition; if yes, generating a compiling result of the workflow; if not, compiling the workflow is not passed.
Optionally, the execution module is further configured to, when each task node in the workflow is compiled and executed successfully; removing operation parameters and resource parameters of each task node in the workflow to obtain a workflow template corresponding to the workflow; and storing the workflow template.
The present specification provides a computer-readable storage medium storing a computer program which, when executed by a processor, implements the execution method of the above tasks.
The present specification provides an electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing a method of performing the above tasks when executing the program.
The above-mentioned at least one technical scheme that this specification adopted can reach following beneficial effect:
in the task execution method provided by the specification, an adaptation unit of input data of a subtask is constructed, the subtask and the adaptation unit corresponding to the subtask are packaged into task nodes, and when the fact that a user drags the task nodes and connection relations among all the task nodes are established is detected, a workflow can be constructed, compiled and executed. According to the method, the user does not need to design the adaptation relation of the data among the subtasks, but directly selects the subtasks and determines the connection relation among the selected subtasks to obtain the workflow, so that the complexity of constructing the workflow is reduced.
Drawings
The accompanying drawings, which are included to provide a further understanding of the specification, illustrate and explain the exemplary embodiments of the present specification and their description, are not intended to limit the specification unduly. In the drawings:
FIG. 1 is a flow chart of a task execution method in the present specification;
FIG. 2a is a schematic diagram of a task node provided in the present specification;
FIG. 2b is a schematic diagram of a task node provided in the present specification;
FIG. 3a is a schematic illustration of the list provided in this specification;
FIG. 3b is a schematic illustration of the list provided in this specification;
FIG. 4 is a schematic diagram of a task execution device provided in the present specification;
fig. 5 is a schematic view of the electronic device corresponding to fig. 1 provided in the present specification.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the present specification more apparent, the technical solutions of the present specification will be clearly and completely described below with reference to specific embodiments of the present specification and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, of the embodiments of the present specification. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are intended to be within the scope of the present disclosure.
The following describes in detail the technical solutions provided by the embodiments of the present specification with reference to the accompanying drawings.
Fig. 1 is a flow chart of a task execution method provided in the present specification, which specifically includes the following steps:
s100: each sub-task in the computing task is determined.
The execution body for executing the embodiments of the present specification may be any computing device (e.g., terminal, server) with computing capability. The description will now be made with the client as an execution subject.
In one or more embodiments of the present description, a display window may be included in the client when performing workflow design of a computing task, a user may perform different operations in the display window, and the client may display data and/or graphics corresponding to the user's operations in the display window in response to the user's operations.
The client may first determine each sub-task in the computing task. The computing task may be a pre-designed computing task, and the pre-designed computing task may be divided to obtain sub-tasks.
For example: the computing task may be a model training task, and each subtask in the model training task may be a forward propagation task, a backward propagation task, a model parameter adjustment task, and so on in the model.
It should be noted that the method used in splitting different subtasks from a computing task is not limited in this specification.
S102: for each sub-task, determining an adaptation unit for adapting input data of the sub-task; wherein, at least, the adaptation unit includes: an adaptation method for converting the format of input data of a subtask into a data format supported by the subtask.
Because the types of data which can be received by each subtask in the computing task are different and the associated relation exists among the subtasks, the adaptation method of the data among the subtasks is determined so that one subtask can receive the output data of other subtasks. The client may determine, for each sub-task, an adaptation unit for adapting the input data of that sub-task. The adaptation unit comprises an adaptation method for converting the format of the input data of the subtask into the data format supported by the subtask.
That is, each subtask has a corresponding adapting unit for adapting its own input data. The adaptation unit may convert data of different formats input to the subtask into data of a format that the subtask can directly receive.
The input data of the subtasks may be input data of the subtasks of the pre-designed calculation tasks.
S104: and packaging the subtasks and the adaptation unit into task nodes.
After obtaining each subtask and the adaptation unit corresponding to each subtask, the client may package the subtask and the adaptation unit corresponding to the subtask as a task node.
Each task node at least comprises a subtask and an adaptation unit corresponding to the subtask.
In one or more embodiments of the present description, a list is provided in a display window of a client, and the client may store the packaged task nodes in the list, so that a user may select each task node in the list.
S106: and responding to the operation of the user on the task nodes, and determining the connection relationship between the task nodes selected by the user and the task nodes selected by the user.
After executing steps S100-S104, the client has already encapsulated task nodes, and the user may directly select the task nodes in the client according to the computing task to be executed, so as to obtain a workflow corresponding to the computing task to be executed.
The client may determine a relationship between the user-selected task node and the user-selected task node in response to a user operation. In one or more embodiments of the present description, a canvas may be included in the client. The client may display the list and the canvas in the display window and then, when an operation is detected in which the user drags at least one task node from the list into the canvas, the client may display the at least one task node dragged by the user in the canvas in response to the drag operation.
And when the client detects that the user performs the connection operation on the task nodes in the canvas, the client can respond to the connection operation, determine the previous task node and the next task node or the previous task node and the next task node in the connection operation for each connection operation, and judge whether a method for adapting the output data of the previous task node exists in an adapting unit of the next task node. If the task node exists, the connection operation is executed, and the connection between the task nodes corresponding to the connection operation is displayed in the canvas. If not, refusing to execute the connection operation.
That is, for each connection operation, it is determined whether the format of the output data of the previous task node is in an adaptation list of the adaptation units of the next task node, wherein different adaptation methods are stored in the adaptation list. For example: as shown in fig. 2a, as shown in the schematic diagram of the task node provided in the present specification, it can be seen that the output data of the task node a is input to the task node B, the output data of the task node a is in a format a, the output data of the task node B is in a format B, and an adaptation method for converting the format a into the format B, converting the format c into the format B, and converting the format d into the format B is stored in the adaptation unit B of the task node B, so that it can be determined that the task node B can receive the output data of the task node a, that is, a connection can be performed between the task node a and the task node B.
In one or more embodiments of the present description, a schematic diagram of a task node is additionally provided. As shown in fig. 2b, a schematic diagram of a task node is provided in the present specification. As can be seen in fig. 2b, there is a subtask 1 in the task node 1, the output data of the subtask 1 includes data in two formats corresponding to m and n, and there is a subtask 2 in the task node 2, where the subtask can receive data in three formats corresponding to p, q and f. And the output data of the subtask 1 is to be input into the subtask 2, the output data m of the subtask 1 is to be converted into data p receivable by the subtask 2 by an adaptation unit in the task node 2 and the data p is to be input into the subtask 2, and the output data n of the subtask 1 is to be converted into data q receivable by the subtask 2 and the data q is to be input into the subtask 2. The subtask may also be data f input by an external device.
In one or more embodiments of the present disclosure, after determining each task node and an adaptation unit corresponding to each task node, for each task node, an adaptation result receiving unit of the task node may be determined according to the adaptation unit of the task node, where an adaptation list is stored in the adaptation result receiving unit, where different adaptation methods are stored in the adaptation list, or where a data format supported by the task node that converts data in different formats may also be stored in the adaptation list. Therefore, when the connection relation between the task nodes is determined, the previous task node and the next task node which can be connected with the task node corresponding to the adaptation unit can be determined according to the adaptation method or the data format stored in the adaptation list, so that whether the connection relation between the task nodes is legal or not can be determined more quickly.
The subtasks, the adaptation unit and the adaptation result receiving unit may be packaged as task nodes in step S104 described above.
S108: and constructing a workflow according to the determined task nodes selected by the user and the connection relation.
S110: compiling and executing each task node in the workflow.
After determining the task nodes selected by the user and the connection relations between the task nodes, the connection relations between the task nodes selected by the user and the task nodes can be displayed in a display window of the client to obtain the workflow.
Further, in one or more embodiments of the present description, a node setting panel is also included in the client. After the user drags at least one task node into the canvas, before compiling and executing each task node in the workflow, the resource parameter of the task node can be set in the node setting panel corresponding to the task node, and then the client can respond to the setting operation of the user on the resource parameter of the task node to determine the resource parameter of the task node. And when the subtasks corresponding to the task nodes are executed in the subsequent steps, the subtasks corresponding to the task nodes can be executed by using the computing equipment corresponding to the resource parameters of the task nodes.
The resource parameters at least comprise the number of computing devices, the memory parameters of the computing devices and the graphics processor core number of the computing devices.
Further, after the user drags at least one task node into the canvas, the client may receive the operation parameters input into the task node by the user and compile and execute the task node according to the operation parameters input into the task node by the user before compiling and executing each task node in the workflow.
And executing the subtasks corresponding to the task nodes in the workflow by using the computing equipment corresponding to the resource parameters according to the determined resource parameters.
In the method for executing the task provided in the present specification and shown in fig. 1, each subtask of the computing task is determined, an adaptation unit of input data of each subtask is determined, and each subtask and the adaptation unit corresponding to each subtask are packaged as each task node. And when the task node selected by the user and the connection relation between the task nodes are determined, a workflow can be constructed, compiled and executed. The method does not need a user to determine the adaptation relation of data among the subtasks, namely, the user does not need to consider how the subtasks in the calculation tasks to be executed can receive the output data of other subtasks connected with the subtasks, but only needs to directly select the subtasks in a client and establish the connection relation among the subtasks, and the client can construct the workflow of the calculation tasks to be executed according to the subtasks selected by the user and the connection relation among the subtasks, compile and execute the workflow to obtain the execution result of the calculation tasks to be executed. The method can enable the adaptation of the data between the subtasks in the computing task to be completely transparent to the user, and reduces the complexity of constructing the workflow.
In addition, in one or more embodiments of the present specification, in the step S102, the client may perform a structural description on the input data of the subtask when determining an adaptation unit for adapting the input data of the subtask.
Wherein the structured description comprises at least: the type, the identification and the default value of the input data of the subtask are determined.
An adaptation unit for adapting the input data of the subtask after the structured description may then be determined from the structured description of the input data of the subtask.
In addition, in one or more embodiments of the present disclosure, in the foregoing step S110, in the process of compiling the workflow, it may be determined whether the connection relationship between the task nodes in the workflow satisfies a specified condition, if so, a result of compiling the workflow may be generated, and if not, the workflow may not be compiled.
Wherein, the specified conditions can be: the workflow is not ring-shaped and each task node in the workflow is wired to at least one other task node.
Of course, when the workflow is compiled and executed, each task node in the workflow is required to complete the setting of the resource parameters and the running parameters.
Further, by adopting the method shown in fig. 1, different workflows can be constructed and compiled and executed. The client can determine the workflow which is successfully executed in each workflow which is successfully executed, remove the operation parameters and the resource parameters of each task node in the workflow which is successfully executed, obtain the workflow template corresponding to the workflow, and store the workflow template. When other computing tasks comprise a computing task corresponding to a workflow which is successfully executed, a workflow template corresponding to the workflow which is successfully executed can be directly used, so that the reusability of the workflow is improved, and the implementation efficiency of the computing task is improved.
In one or more embodiments of the present specification, the client may display the workflow template in a list, and in step S106 described above, the client may display the list and canvas in a display window, with at least the workflow template included in the list. Because the workflow templates comprise a plurality of task nodes and connection relations among the task nodes, the client can respond to the operation that a user drags at least one workflow template from the list to the canvas, display the at least one workflow template dragged by the user in the canvas, take the task nodes and the connection relations among the task nodes in the at least one workflow template dragged by the user as the task nodes selected by the user, and display the workflow template in the canvas.
As shown in fig. 3a, for the schematic view of the list provided in this specification, it is visible that there are task nodes and workflow templates in the list, and of course, there may be only task nodes and workflow templates in the list.
In one or more embodiments of the present disclosure, the list may include a node list and a template list, where task nodes are in the node list, and workflow templates are in the template list, and the task nodes and the workflow templates are placed in different lists, so as to facilitate the searching and use of the user. As shown in fig. 3b, a schematic diagram of the list provided in this specification is provided. The list of the client can be seen to comprise a template list and a node list, wherein task nodes are arranged in the node list, and workflow templates are arranged in the template list.
Furthermore, in one or more embodiments of the present specification, each task node may further include a subtask result receiving unit for storing an execution result of the subtask. The subtask result receiving unit may then be encapsulated into the task node when encapsulating the task node.
Further, the client may also include a workflow executor and a message listener.
The workflow executor at least comprises: the system comprises a starting component, a task execution component, a waiting task execution result component and an ending component, wherein the execution of all workflows starts with the starting component and ends with the ending component.
The client may submit the workflow to the workflow executor to perform the corresponding subtasks in the workflow in step S110 described above.
Specifically, first, the workflow executor may assign a unique workflow identifier to each workflow, and a unique node identifier to each task node in the workflow.
Then, for each task node in the workflow, the input data of the task node may be converted into a data format supported by the task node according to an adaptation list in an adaptation unit of the task node.
And the client can store the data converted from the input data of the task node, the flow identifier corresponding to the task node and the identifier of the task node in a file.
Then, the workflow executor may submit the file corresponding to the task node to the computing device corresponding to the resource parameter of the task node, so as to obtain the execution result corresponding to the task node.
Finally, the message monitor may monitor a message sent by the external computing device, where the message sent by the external computing device includes at least a workflow identifier, a node identifier, an execution result, and a status of the execution result. If the state of the execution result of the task node, which is obtained by the computing device corresponding to the resource parameter of the task node, is successful, the node identifier corresponding to the task node can be marked as a successful operation state, and the execution result is sent to the corresponding subtask result receiving unit. When the workflow executor receives the state of the execution result and the execution result, and when the state of the execution result is determined to be successful, the next task node of the task node corresponding to the node identification can be determined, and the subtask corresponding to the next task node of the task node can be continuously executed. If the state of the execution result of the task node, which is obtained by the computing device corresponding to the resource parameter of the task node, is failure, the node identifier corresponding to the task node can be marked as an operation failure state and returned to the workflow executor, and the execution of the workflow is ended.
And the client can also be provided with an operation monitor so that a user can know the execution condition of each task node in the workflow in a visual mode.
The running monitor of the client can display basic information such as running start time, running end time, resource utilization rate, running duration and the like of each task node, can generate a running log, and can update the running log in real time.
A results viewer may also be present in the client to allow the user to view the results of the execution of the workflow. Specifically, the client may store path information of the execution result of each task node in the workflow, traverse the file where the execution result of each task node is located according to the path information of the execution result of each task node, and display basic information such as format, size, generation time and the like of the file.
Based on the task execution method described above, the embodiment of the present disclosure further provides a schematic device for task execution, as shown in fig. 4.
Fig. 4 is a schematic diagram of an execution apparatus for tasks according to an embodiment of the present disclosure, where the apparatus includes:
a determining module 400, configured to determine each subtask in the computing task;
An adaptation module 402, configured to determine, for each subtask, an adaptation unit for adapting input data of the subtask; wherein, at least, the adaptation unit includes: an adaptation method for converting the format of the input data of the subtask into the data format supported by the subtask;
a packaging module 404, configured to package the subtasks and the adaptation unit into task nodes;
a response module 406, configured to determine, in response to a user operation on the task node, a connection relationship between the task node selected by the user and the task node selected by the user;
a building module 408, configured to build a workflow according to the determined task node selected by the user and the connection relationship;
and the execution module 410 is used for compiling and executing each task node in the workflow.
Optionally, the adapting module 402 is specifically configured to perform a structural description on the input data of the subtask; wherein the structured description comprises at least: determining the type, the identification and the default value of the input data of the subtask; and determining an adaptation unit for adapting the input data of the subtask after the structural description according to the structural description of the input data of the subtask.
Optionally, the response module 406 is specifically configured to display a list and a canvas; wherein the list at least comprises task nodes; responsive to a user dragging at least one task node from the list into the canvas, displaying the user-dragged at least one task node in the canvas as the user-selected task node.
Optionally, the response module 406 is specifically configured to display a list and a canvas; wherein the list at least comprises a workflow template; the workflow template comprises a plurality of task nodes and connection relations among the plurality of task nodes; in response to a user dragging at least one workflow template from the list into the canvas, displaying the user-dragged at least one workflow template in the canvas, taking a plurality of task nodes in the user-dragged at least one workflow template as the user-selected task nodes, and taking connection relations among the plurality of task nodes in the user-dragged at least one workflow template as connection relations among the user-selected task nodes.
Optionally, the response module 406 is specifically configured to, in response to a connection operation between task nodes in the canvas by the user, determine, for each connection operation, a previous task node and a next task node in the connection operation, and determine whether a method for adapting output data of the previous task node exists in an adapting unit of the next task node; if yes, executing the connection operation, and displaying the connection between the task nodes corresponding to the connection operation; if not, refusing to execute the connection operation.
Optionally, the response module 406 is further configured to determine a resource parameter of the task node in response to a user setting operation on the resource parameter of the task node; wherein the resource parameters at least include: the number of computing devices, the memory parameters of each computing device, and the graphics processor core number of each computing device;
the execution module 410 is specifically configured to execute, according to a resource parameter of each task node in the workflow, a subtask corresponding to each task node in the workflow by using a computing device corresponding to the resource parameter.
Optionally, the response module 406 is further configured to receive an operation parameter input into the task node by a user;
the execution module 410 is specifically configured to compile and execute the task node according to the operation parameter input by the user into the task node.
Optionally, the execution module 410 is specifically configured to determine whether a connection relationship between task nodes in the workflow meets a specified condition; if yes, generating a compiling result of the workflow; if not, compiling the workflow is not passed.
Optionally, the execution module 410 is further configured to, when each task node in the workflow compiles and executes successfully; removing operation parameters and resource parameters of each task node in the workflow to obtain a workflow template corresponding to the workflow; and storing the workflow template.
The embodiments of the present specification also provide a computer-readable storage medium storing a computer program usable for executing the execution method of the tasks described above.
Based on the task execution method described above, the embodiment of the present disclosure further proposes a schematic block diagram of the electronic device shown in fig. 5. At the hardware level, as in fig. 5, the electronic device includes a processor, an internal bus, a network interface, a memory, and a non-volatile storage, although it may include hardware required for other services. The processor reads the corresponding computer program from the nonvolatile memory into the memory and then runs the computer program to realize the task execution method.
Of course, other implementations, such as logic devices or combinations of hardware and software, are not excluded from the present description, that is, the execution subject of the following processing flows is not limited to each logic unit, but may be hardware or logic devices.
In the 90 s of the 20 th century, improvements to one technology could clearly be distinguished as improvements in hardware (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) or software (improvements to the process flow). However, with the development of technology, many improvements of the current method flows can be regarded as direct improvements of hardware circuit structures. Designers almost always obtain corresponding hardware circuit structures by programming improved method flows into hardware circuits. Therefore, an improvement of a method flow cannot be said to be realized by a hardware entity module. For example, a programmable logic device (Programmable Logic Device, PLD) (e.g., field programmable gate array (Field Programmable Gate Array, FPGA)) is an integrated circuit whose logic function is determined by the programming of the device by a user. A designer programs to "integrate" a digital system onto a PLD without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, such programming is mostly implemented by using "logic compiler" software, which is similar to the software compiler used in program development and writing, and the original code before the compiling is also written in a specific programming language, which is called hardware description language (Hardware Description Language, HDL), but not just one of the hdds, but a plurality of kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), lava, lola, myHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog are currently most commonly used. It will also be apparent to those skilled in the art that a hardware circuit implementing the logic method flow can be readily obtained by merely slightly programming the method flow into an integrated circuit using several of the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic controllers, and embedded microcontrollers, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, atmel AT91SAM, microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic of the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller in a pure computer readable program code, it is well possible to implement the same functionality by logically programming the method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. Such a controller may thus be regarded as a kind of hardware component, and means for performing various functions included therein may also be regarded as structures within the hardware component. Or even means for achieving the various functions may be regarded as either software modules implementing the methods or structures within hardware components.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. One typical implementation is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each element may be implemented in one or more software and/or hardware elements when implemented in the present specification.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
It will be appreciated by those skilled in the art that embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the present specification may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present description can take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
The description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.
The foregoing is merely exemplary of the present disclosure and is not intended to limit the disclosure. Various modifications and alterations to this specification will become apparent to those skilled in the art. Any modifications, equivalent substitutions, improvements, or the like, which are within the spirit and principles of the present description, are intended to be included within the scope of the claims of the present application.
Claims (14)
1. A method of performing a task, the method comprising:
determining each subtask in the computing task;
for each sub-task, determining an adaptation unit for adapting input data of the sub-task; each subtask is correspondingly provided with an adapting unit for adapting the input data of the subtask, and the adapting unit is used for converting the data of different formats input to the subtask into the data of formats which can be directly received by the subtask; wherein, at least, the adaptation unit includes: an adaptation method for converting the format of the input data of the subtask into the data format supported by the subtask;
packaging the subtasks and the adaptation unit as task nodes;
responding to the operation of a user on the task nodes, and determining the connection relationship between the task nodes selected by the user and the task nodes selected by the user;
constructing a workflow according to the determined task nodes selected by the user and the connection relation;
compiling and executing each task node in the workflow;
compiling each task node in the workflow, specifically including: judging whether the connection relation among all task nodes in the workflow meets the specified conditions, wherein the specified conditions can be as follows: the workflow is not annular, and each task node in the workflow is connected with at least one other task node; if yes, generating a compiling result of the workflow; if not, compiling the workflow without passing;
The determining, in response to the operation of the user on the task node, a connection relationship between the task node selected by the user and the task node selected by the user specifically includes:
displaying the list and canvas; wherein the list at least comprises task nodes; responsive to a user dragging at least one task node from the list into the canvas, displaying the user-dragged at least one task node in the canvas as the user-selected task node;
the determining the connection relationship between the task node selected by the user and the task node selected by the user specifically includes:
responding to the connection operation of the user on the task nodes in the canvas, determining a previous task node and a next task node in the connection operation aiming at each connection operation, and judging whether a method for adapting the output data of the previous task node exists in an adapting unit of the next task node; if yes, executing the connection operation, and displaying the connection between the task nodes corresponding to the connection operation; if not, refusing to execute the connection operation.
2. The method according to claim 1, wherein determining an adaptation unit for adapting the input data of the subtask, in particular comprises:
carrying out structural description on the input data of the subtasks; wherein the structured description comprises at least: determining the type, the identification and the default value of the input data of the subtask;
and determining an adaptation unit for adapting the input data of the subtask after the structural description according to the structural description of the input data of the subtask.
3. The method according to claim 1, wherein determining the connection relationship between the user-selected task node and the user-selected task node in response to a user operation on the task node, comprises:
displaying the list and canvas; wherein the list at least comprises a workflow template; the workflow template comprises a plurality of task nodes and connection relations among the plurality of task nodes;
in response to a user dragging at least one workflow template from the list into the canvas, displaying the user-dragged at least one workflow template in the canvas, taking a plurality of task nodes in the user-dragged at least one workflow template as the user-selected task nodes, and taking connection relations among the plurality of task nodes in the user-dragged at least one workflow template as connection relations among the user-selected task nodes.
4. The method of claim 1, wherein prior to compiling and executing each task node in the workflow, the method further comprises:
determining the resource parameters of the task node in response to the resource parameter setting operation of the user on the task node; wherein the resource parameters at least include: the number of computing devices, the memory parameters of each computing device, and the graphics processor core number of each computing device;
executing each task node in the workflow, specifically including:
and executing the subtasks corresponding to the task nodes in the workflow by using the computing equipment corresponding to the resource parameters according to the resource parameters of the task nodes in the workflow.
5. The method of claim 1, wherein prior to compiling and executing each task node in the workflow, the method further comprises:
receiving an operation parameter input into the task node by a user;
compiling and executing each task node in the workflow, and specifically comprising the following steps:
and compiling and executing the task node according to the operation parameters input into the task node by the user.
6. The method of claim 1, wherein the method further comprises:
when each task node in the workflow is compiled and executed successfully;
removing operation parameters and resource parameters of each task node in the workflow to obtain a workflow template corresponding to the workflow;
and storing the workflow template.
7. A device for executing a task, the device comprising:
the determining module is used for determining each subtask in the computing task;
the adaptation module is used for determining an adaptation unit for adapting the input data of each subtask according to each subtask; each subtask is correspondingly provided with an adapting unit for adapting the input data of the subtask, and the adapting unit is used for converting the data of different formats input to the subtask into the data of formats which can be directly received by the subtask; wherein, at least, the adaptation unit includes: an adaptation method for converting the format of the input data of the subtask into the data format supported by the subtask;
the packaging module is used for packaging the subtasks and the adaptation unit into task nodes;
the response module is used for responding to the operation of the user on the task nodes and determining the task nodes selected by the user and the connection relation between the task nodes selected by the user;
The construction module is used for constructing a workflow according to the determined task nodes selected by the user and the connection relation;
the execution module is used for compiling and executing each task node in the workflow, and compiling each task node in the workflow, and specifically comprises the following steps: judging whether the connection relation among all task nodes in the workflow meets the specified conditions, wherein the specified conditions can be as follows: the workflow is not annular, and each task node in the workflow is connected with at least one other task node; if yes, generating a compiling result of the workflow; if not, compiling the workflow without passing;
the response module is specifically used for displaying a list and canvas; wherein the list at least comprises task nodes; responsive to a user dragging at least one task node from the list into the canvas, displaying the user-dragged at least one task node in the canvas as the user-selected task node;
the response module is specifically configured to respond to a connection operation between task nodes in the canvas by the user, determine, for each connection operation, a previous task node and a next task node in the connection operation, and determine whether a method for adapting output data of the previous task node exists in an adaptation unit of the next task node; if yes, executing the connection operation, and displaying the connection between the task nodes corresponding to the connection operation; if not, refusing to execute the connection operation.
8. The apparatus of claim 7, wherein the adaptation module is specifically configured to structurally describe input data of the subtask; wherein the structured description comprises at least: determining the type, the identification and the default value of the input data of the subtask; and determining an adaptation unit for adapting the input data of the subtask after the structural description according to the structural description of the input data of the subtask.
9. The apparatus of claim 7, wherein the response module is specifically to display a list and a canvas; wherein the list at least comprises a workflow template; the workflow template comprises a plurality of task nodes and connection relations among the plurality of task nodes; in response to a user dragging at least one workflow template from the list into the canvas, displaying the user-dragged at least one workflow template in the canvas, taking a plurality of task nodes in the user-dragged at least one workflow template as the user-selected task nodes, and taking connection relations among the plurality of task nodes in the user-dragged at least one workflow template as connection relations among the user-selected task nodes.
10. The apparatus of claim 7, wherein the response module is further configured to determine the resource parameter of the task node in response to a user's resource parameter setting operation on the task node; wherein the resource parameters at least include: the number of computing devices, the memory parameters of each computing device, and the graphics processor core number of each computing device;
the execution module is specifically configured to execute subtasks corresponding to each task node in the workflow by using a computing device corresponding to the resource parameter according to the resource parameter of each task node in the workflow.
11. The apparatus of claim 7, wherein the response module is further for receiving an operational parameter entered by a user into the task node;
the execution module is specifically configured to compile and execute the task node according to the operation parameter input into the task node by the user.
12. The apparatus of claim 7, wherein the execution module is further to, when each task node in the workflow compiles and executes successfully; removing operation parameters and resource parameters of each task node in the workflow which is successfully executed to obtain a workflow template corresponding to the workflow; and storing the workflow template.
13. A computer readable storage medium, characterized in that the storage medium stores a computer program which, when executed by a processor, implements the method of any of the preceding claims 1-6.
14. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method of any of the preceding claims 1-6 when executing the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310598325.3A CN116382877B (en) | 2023-05-25 | 2023-05-25 | Task execution method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310598325.3A CN116382877B (en) | 2023-05-25 | 2023-05-25 | Task execution method and device, storage medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116382877A CN116382877A (en) | 2023-07-04 |
| CN116382877B true CN116382877B (en) | 2023-09-05 |
Family
ID=86978992
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310598325.3A Active CN116382877B (en) | 2023-05-25 | 2023-05-25 | Task execution method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116382877B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110750308A (en) * | 2019-09-11 | 2020-02-04 | 东软集团股份有限公司 | Task processing method and device, storage medium and electronic equipment |
| CN113326113A (en) * | 2021-05-25 | 2021-08-31 | 北京市商汤科技开发有限公司 | Task processing method and device, electronic equipment and storage medium |
| CN113448547A (en) * | 2021-06-25 | 2021-09-28 | 未鲲(上海)科技服务有限公司 | Visual task arrangement method, equipment and storage medium |
| CN115016909A (en) * | 2022-05-27 | 2022-09-06 | 北京思特奇信息技术股份有限公司 | Task flow concurrent scheduling method and system based on parameter dependence inference execution flow |
| CN115480746A (en) * | 2022-09-21 | 2022-12-16 | 北京沃东天骏信息技术有限公司 | Method, device, equipment and medium for generating execution file of data processing task |
| CN115793914A (en) * | 2023-02-08 | 2023-03-14 | 广州市玄武无线科技股份有限公司 | Multi-round scene interaction flow chart generation method, electronic equipment and storage medium thereof |
| CN115794064A (en) * | 2022-10-25 | 2023-03-14 | 中电金信软件有限公司 | Configuration method and device of task processing flow, electronic equipment and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070044071A1 (en) * | 2005-08-16 | 2007-02-22 | Hayles Timothy J | Efficient Configuration of Hardware Devices in a Graphical Dataflow Programming Environment |
-
2023
- 2023-05-25 CN CN202310598325.3A patent/CN116382877B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110750308A (en) * | 2019-09-11 | 2020-02-04 | 东软集团股份有限公司 | Task processing method and device, storage medium and electronic equipment |
| CN113326113A (en) * | 2021-05-25 | 2021-08-31 | 北京市商汤科技开发有限公司 | Task processing method and device, electronic equipment and storage medium |
| CN113448547A (en) * | 2021-06-25 | 2021-09-28 | 未鲲(上海)科技服务有限公司 | Visual task arrangement method, equipment and storage medium |
| CN115016909A (en) * | 2022-05-27 | 2022-09-06 | 北京思特奇信息技术股份有限公司 | Task flow concurrent scheduling method and system based on parameter dependence inference execution flow |
| CN115480746A (en) * | 2022-09-21 | 2022-12-16 | 北京沃东天骏信息技术有限公司 | Method, device, equipment and medium for generating execution file of data processing task |
| CN115794064A (en) * | 2022-10-25 | 2023-03-14 | 中电金信软件有限公司 | Configuration method and device of task processing flow, electronic equipment and storage medium |
| CN115793914A (en) * | 2023-02-08 | 2023-03-14 | 广州市玄武无线科技股份有限公司 | Multi-round scene interaction flow chart generation method, electronic equipment and storage medium thereof |
Non-Patent Citations (1)
| Title |
|---|
| Automated Design Workflow for Structural Nodes of Space Frame Structures;Patrick Beutler;Procedia CIRP;第109卷;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116382877A (en) | 2023-07-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110401700A (en) | Model loading method and system, control node and execution node | |
| CN117093352B (en) | Template-based computing cluster job scheduling system, method and device | |
| CN117075930B (en) | Computing framework management system | |
| CN116225669B (en) | Task execution method and device, storage medium and electronic equipment | |
| CN111026494A (en) | Business process processing method, device and equipment | |
| CN111861454B (en) | Method and device for displaying unique identifier of digital object | |
| CN110633959A (en) | Method, device, equipment and medium for creating approval task based on graph structure | |
| CN116932175B (en) | Heterogeneous chip task scheduling method and device based on sequence generation | |
| CN111782409B (en) | Task processing method, device and electronic equipment, and risk identification task processing method and device | |
| CN116382877B (en) | Task execution method and device, storage medium and electronic equipment | |
| CN111459573B (en) | Method and device for starting intelligent contract execution environment | |
| CN108804088B (en) | Protocol processing method and device | |
| EP3779697A1 (en) | Data processing method, device and apparatus | |
| CN116842715A (en) | Simulation data structuring processing system | |
| CN117406982B (en) | Integrated storage and calculation application generation system and method, storage medium and equipment | |
| CN114968457B (en) | Form processing method and device applied to subprogram | |
| CN117519912B (en) | Mirror image warehouse deployment method, device, storage medium and equipment | |
| CN117170669A (en) | Page display method based on front-end high-low code fusion | |
| CN111966479B (en) | Service processing and risk identification service processing method and device and electronic equipment | |
| CN116167437B (en) | Chip management system, method, device and storage medium | |
| CN113411219B (en) | Front-end service publishing method, device and equipment | |
| CN116341642B (en) | Data processing method and device, storage medium and electronic equipment | |
| CN117348999B (en) | Service execution system and service execution method | |
| CN116384472A (en) | Data processing system, method, equipment and storage medium | |
| CN117573359A (en) | Heterogeneous cluster-based computing framework management system and method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |