petercorke / petercorke/robotics-toolbox-python
[Feature Proposal]: Composite Trajectories
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 3.5k
- Forks
- 624
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 53
Description
Hello,
Recently I was working on a project using the robotics-toolbox-python package and found there was no native support for combining trajectories. In my case, I found myself wanting to demo certain poses for a robot and so I created trajectories from each pose to the next and had to implement my own logic to concatenate the lists from both trajectories and add the last time value onto the second trajectory manually.
I think this is something that may be useful to others for constructing different trajectories and could potentially be implemented as the add method with checks for the final position / velocity matching the beginning of the second one.
I am happy to implement this if it is something that the maintainers think is worth while.
Let me know your thoughts :)
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
No source file, test, or entry point is named. Start by locating the trajectory classes and their existing construction and combination behavior, then clarify the API and continuity checks for joining trajectories. Done means the supported composite-trajectory behavior and its handling of incompatible joins are defined and tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- robotics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100