dimensionalOS / dimensionalOS/dimos
Measure tf latency
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
This is is important if we want to rely on tf instead of odom values between modules.
For example, ray tracer needs up to date and synchronized lidar origins and point clouds.
Synced from DIM-1377 by andrew
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 tf and odom transform path, then trace how lidar origins and point clouds reach the ray tracer; done means reporting tf latency and showing whether the values are synchronized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, robotics
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100