poor result on the kitti dataset
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 243
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Thank you for your excellent work. However, when I ran the kitti dataset under the run_kitti_gs.yaml parameter you provided, I found that the SLAM localization(ATE...) accuracy was poor. May I ask what the reason is? Compared with the outstanding performance of PIN-SLAM, why does PINGS perform much worse on the kitti dataset?
Looking forward to your reply!
Contributor guide
No contributing guide indexed for this repository
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 reproducing the KITTI run with the provided run_kitti_gs.yaml parameters and checking the ATE localization result. Compare the configuration and evaluation output with the reported PIN-SLAM performance; the work is done when the cause of the discrepancy is identified and documented or a verified correction is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision, performance, robotics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100