autoware.universe
autoware.universe copied to clipboard
collect rosbag of sensor data for camera
Checklist
- [X] I've read the contribution guidelines.
- [X] I've searched other issues and no duplicate issues were found.
- [X] I've agreed with the maintainers that I can plan this task.
Description
Part of #680
Purpose
Possible approaches
Definition of done
- [ ] Decide the datasets we need with reasons (@xmfcx create a discussion, https://docs.nvidia.com/drive/archive/driveworks-3.0/signnet_US_v1_0.html )
- [ ] Define the requirements for the data like fps, resolution, compression (@goktugyildirim create a discussion, probably follow how other datasets are doing)
- [ ] Have a meeting with TCS
- [ ] Look for alternative data annotator companies to help
- [ ] Talk to ITRI, ADASTEC for camera data
For each data collector,
- [ ] Decide & agree upon what kind of data to collect
- [ ] Obtain rosbag2 files
- [ ] Convert rosbag2 files to image seqs
- [ ] Provide data to TCS
I have talked with ADASTEC today, and they might be able to provide us the data (lidar+camera+tf).
(cc. @yucedagonurcan)
LeoDrive has already started testing image perception with real hardware. https://github.com/autowarefoundation/autoware.universe/issues/1228
This pull request has been automatically marked as stale because it has not had recent activity.
The data we shared has some camera data too.
https://github.com/autowarefoundation/autoware-documentation/pull/200
Although it is not labeled nor can be used to train, it can be used to visually test maybe.
I will close this issue until we create more concrete plans to collect an image dataset.