Can Rmader replan trajectories when drones are lagging behind the target waypoints?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 127
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I have encountered some challenges when deploying R-mader on real drones. Specifically, I wonder whether R-mader can detect the deviations of the drones from their target waypoints and subsequently adjust the plans.
In my current environment, the drones publish their positions via the rostopic /SQxxs/state, and receive position commands from R-mader through /SQxxs/goal. To eliminate interference from the simulator, I have disabled perfect_controller.
However, the drones sometimes fly slower than R-mader expects and therefore lag behind the target waypoints. In such cases, R-mader seems to disregard the actual drone positions and continues planning trajectories based on its previous commands.
I've attached an image illustrating this issue. In this scenario, three drones are supposed to be flying forward, but the drone in the middle remains stationary at the origin. R-mader, though, supposes all trajectories are completed and continues to plan forward.
What might be wrong in my setup? Any assistance would be greatly appreciated.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how R-mader consumes positions from /SQxxs/state and sends commands through /SQxxs/goal, with perfect_controller disabled. Compare the reported state with the planner's completion condition and determine what evidence would show that lagging drones are replanned from their actual positions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- robotics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100