-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[✨FEAT✨]: Cone mapping #27
Comments
Plan: |
For the plan I would like somthing more spesific and a plan of actions an example might be : We are going to first make 3 test data set by hand then we will try to see if x algo will be effective and then compare it to y, we are going to do this by making a node called z that is in package a yada yada this is a good basic outline but a plan should be a plan of action so that the team and you guys know what are the steps you have to do in order to compleate this |
1: Use python script to generate test data, use publisher to simulate cone detection output and use subscriber to receive output 2: Create a map of the track using a mapping algorithm such as occupancy grid mapping or SLAM. 3: Use the 3D world coordinates of the cone to determine its position in relation to the robot's current pose and output a ROS PoseWithCovariance message with the cone's position and orientation. 4: Continuously update the map with new cone detections and publish the updated map to a separate topic. 5: Attach the color (int) of the cone to the ROS message. 6: Publish the ROS message to a designated topic. 7: Test the algorithm on a real-world scenario to ensure it is robust and accurate enough for deployment. Monitor the performance of the algorithm, tweak parameters as necessary, add filtering method for noises, and optimize for speed and accuracy (Iterative process). Next possible iteration might be:
|
Merged Kalman filter cone mapping version, now exploring particle filter version |
Is there an existing enhancement request for this?
Description
Map of all cones detected
Additional Information
No response
The text was updated successfully, but these errors were encountered: