dimensionalOS / dimensionalOS/dimos
PimSim: maintained robot coverage through profiles and control families
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
Add robots through reusable profiles and control-family adapters after the flagship workflow is stable.
Acceptance
- No robot-specific PimSim application stacks
- Ordinary DimOS blueprints remain the public surface
- Each supported robot records assets, controls, sensors, fidelity, and evidence
- New embodiments are accepted only against a named task or product need
G1, Go2, and xArm7 are the current foundation. Broad coverage is deliberately deferred.
Synced from DIM-1375 by pim
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 by reviewing the flagship workflow and the current G1, Go2, and xArm7 foundation. Define how reusable profiles and control-family adapters meet the acceptance criteria, including assets, controls, sensors, fidelity, evidence, and named task or product need; done means no robot-specific PimSim application stacks and ordinary DimOS blueprints remain the public surface.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100