Skip to content
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

LiDAR Detection (Issue #368) #417

Merged
merged 11 commits into from
May 7, 2024
Merged

LiDAR Detection (Issue #368) #417

merged 11 commits into from
May 7, 2024

Conversation

MtGuerenS
Copy link

@MtGuerenS MtGuerenS commented Apr 15, 2024

Description

Implemented a lidar detection node that combines the MMDetection3D and the ComplexYOLOv4 models for the Object classification (Lidar) Issue.

Usage

To test the new feature do the following:

  1. Click here and download the complex_yolov4_mse_loss.pth file
  2. Move complex_yolov4_mse_loss.pth into the directory navigator/data/perception/checkpoints/complex_yolov4_mse_loss.pth
  3. cd into /navigator
  4. uncomment # *object3d_launch_entities, in launches/launch.perception.py
  5. run docker compose run navigator_carla
  6. run colcon build --symlink-install --packages-select lidar_detection && source install/setup.bash
  7. run ros2 launch launches/launch.vehicle.py
  8. open new ternminal with pwd in /navigator
  9. run docker compose run navigator_carla
  10. run ros2 bag play /bags/2024/bag_2024-02-09_Demo/ or other bag

@MtGuerenS MtGuerenS requested a review from danielv012 April 15, 2024 22:51
@MtGuerenS MtGuerenS marked this pull request as draft April 15, 2024 23:16
@MtGuerenS MtGuerenS marked this pull request as ready for review April 15, 2024 23:38
Copy link
Contributor

@danielv012 danielv012 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything looks awesome. Just a few comments I left

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's with all the changes to the default rviz config?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was this a rebase?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added a group for object detection/tracking, and the rest of the changes are just the position I had the camera at. Here is the most important part of the changes:

- Class: rviz_common/Group
      Displays:
        - Class: rviz_default_plugins/MarkerArray
          Enabled: true
          Name: Detected
          Namespaces:
            object_bounding_box: true
            object_tag: true
          Topic:
            Depth: 5
            Durability Policy: Volatile
            History Policy: Keep Last
            Reliability Policy: Reliable
            Value: /viz/detected/objects3d
          Value: true
        - Class: rviz_default_plugins/MarkerArray
          Enabled: false
          Name: Tracked
          Namespaces:
            {}
          Topic:
            Depth: 5
            Durability Policy: Volatile
            History Policy: Keep Last
            Reliability Policy: Reliable
            Value: /viz/tracked/objects3d
          Value: false
      Enabled: true
      Name: 3D Objects

docs/Perception/static_occupancy_node.md Outdated Show resolved Hide resolved
launches/launch.object3d.py Show resolved Hide resolved
@ragibarnab
Copy link
Contributor

Hi Gueren. Please don't hardcode the paths to model configs/weights, change it so they pass them through ros params. There's a reason I used MMDetection. That is, you can take any state-of-the-art model (a lot of them better than ComplexYOLO) from MMDetection package and use it for inference. By hardcoding the configs/weights the key functionality of my package is lost.

Thanks,
Rae

P.S. in the future just communicate with others if you are going to edit and remove their code. Communication is key, y'know? I'm a nice guy, I promise, just reach me out on teams. Like really, our packages should've been split instead of combined the way it is to prevent any issues.

MtGuerenS and others added 2 commits April 29, 2024 12:25
- Added checkpoint_path and config_path to the params of LidarDetectionNode
- Fixed MMDetection3DModel class to take checkpoint and config arguements
@danielv012 danielv012 merged commit ba3caa8 into dev May 7, 2024
1 check failed
@danielv012 danielv012 deleted the feature/yolo_detection_3d branch May 7, 2024 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants