dimensionalOS / dimensionalOS/dimos
Testing Trajectory controller for statistical analysis
Open
Nobody has claimed this yet.
this week
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
-
5 sets of runs at each speed
-
For each controller (P-controller, paul , holonmic controller , dan controller)
Testing Trajectory controller for statistical analysis · Issue #3098 · dimensionalOS/dimos
Synced from DIM-1305 by mustafa
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 files, tests, or entry points are named. Start by locating the trajectory controller entry points and the implementations for the P-controller, paul, holonmic controller, and dan controller; then determine how speeds are configured. Done means completing five runs at each speed for every controller and producing statistical results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, robotics, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100