[Other issue]: Does Negotiation proposed itinerary only cover the current task?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 438
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
Before proceeding, is there an existing issue or discussion for this?
- I have done a search for similar issues and discussions.
Description
Hi team, a quick question regarding the negotiation proposals made by the fleet adapter: Does it only include the timed-waypoints for the robot's current task, or does it take into account the remaining tasks in the queue as well?
For example, if a robot is running a delivery task, and have a parking task afterwards as a "finishing task", when proposing an itinerary for this robot, will the finishing waypoint for that itinerary be the dropoff waypoint (from the delivery task), or will it be the parking spot (from the parking task)?
I tried to look into Negotiate service implementation, and the respond(~) function in GoToPlace.cpp, but not able to figure this out. Many thanks in advance!
Contributor guide
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 with the Negotiate service implementation and the respond(~) function in GoToPlace.cpp, which the issue identifies as relevant entry points. Trace whether proposals use only the current task or include remaining queued and finishing tasks, then document the behavior using the delivery-and-parking example from the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- robotics
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100