-
|
Hello, RMF transactions send task messages to robots. When I send it as 5 different tasks in a row, each task queue structure is integrated and it seems like it will be searched until this part. However, when the 2nd task is finished and the 3rd task is started, when a new task message arrives, the 4th and 5th message in the queue is skipped and the system starts working by receiving the last task message. The son of the 4th and 5th personnel is being processed after duty. Can you help me understand which section is defined within the queue structure system and whether such a situation is natural or not? No such explanation or solution was found during my research. Note: Numbers are given as examples. The same situation occurs again after 2 mission messages. It does not depend specifically on the numbers above. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
When you use task dispatching, the tasks can be reordered to minimize the overall time spent across all the tasks. This is known as Pareto optimal. If you want the tasks to be run in a specific order then you can use the direct robot task request API instead. |
Beta Was this translation helpful? Give feedback.
-
|
I will try this. When I have a question about this subject again, I will write in this section. Thanks. |
Beta Was this translation helpful? Give feedback.
When you use task dispatching, the tasks can be reordered to minimize the overall time spent across all the tasks. This is known as Pareto optimal.
If you want the tasks to be run in a specific order then you can use the direct robot task request API instead.