Ideally, we should be able to specify that the system assumes a given action should be running only once, possibly "narrowing" on a subset of the arguments.
I've seen a bunch of use cases for this over time, but the latest is the following:
We have to control the position of some objects in a Gazebo scene. There's an action for that, and obviously we should have only one item of this action running. We could do some job tracking in the UI, but then it defeats the main goal of having only Roby do state tracking. However, having the "perfect" logic to keep the action unique is a bit involved (requires some knowledge about Roby patterns).
Ideally, we should be able to specify that the system assumes a given action should be running only once, possibly "narrowing" on a subset of the arguments.
I've seen a bunch of use cases for this over time, but the latest is the following:
We have to control the position of some objects in a Gazebo scene. There's an action for that, and obviously we should have only one item of this action running. We could do some job tracking in the UI, but then it defeats the main goal of having only Roby do state tracking. However, having the "perfect" logic to keep the action unique is a bit involved (requires some knowledge about Roby patterns).
Proposed API: