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

Compatibility tests - sensors data publishers #44

Open
2 tasks
WJaworskiRobotec opened this issue Jul 20, 2022 · 23 comments
Open
2 tasks

Compatibility tests - sensors data publishers #44

WJaworskiRobotec opened this issue Jul 20, 2022 · 23 comments
Assignees
Labels

Comments

@WJaworskiRobotec
Copy link

WJaworskiRobotec commented Jul 20, 2022

Description

Preparation of second batch of tests related to publication of sensor data by the simulator. Important to have a definition of topics, message types in the configuration file to easily change the number of published lidars/cameras

Purpose

To evaluate the sensor data published by the simulators

Definition of Done

  • PR created
  • Tests verified in AWSIM and MORAI SIM
@SoohyeokPark-MORAI
Copy link

I am planning to start this Friday.
I made a sample configuration file that includes sensor-related publishers and publishers and subscribers just in case.
sample configuration file link

@WJaworskiRobotec WJaworskiRobotec moved this from Todo to In Progress in Simulation Working Group Aug 3, 2022
@SoohyeokPark-MORAI
Copy link

SoohyeokPark-MORAI commented Aug 17, 2022

camera, gps (gnss pose, pose with covariance), imu are under tests with MORAI SIM.

@WJaworskiRobotec
Copy link
Author

@SoohyeokPark-MORAI Is the PR for these tests ready ?

@SoohyeokPark-MORAI
Copy link

@WJaworskiRobotec Here I share the link PR link

@WJaworskiRobotec
Copy link
Author

@SoohyeokPark-MORAI thanks a lot, Have you tested it with AWSIM ?

@SoohyeokPark-MORAI
Copy link

@WJaworskiRobotec I tried it with AWSIM but found an issue related to LIDAR whose data is not received.

@WJaworskiRobotec
Copy link
Author

OK I will check it with AWSIM with modified QoS

@WJaworskiRobotec
Copy link
Author

I have managed to make it work with AWSIM with some changes that I will push to the repo.

Image

*4 failed tests for lidars are related to left and right sensors not included in the binary that I've tested

@WJaworskiRobotec WJaworskiRobotec moved this from In Progress to In Review in Simulation Working Group Sep 28, 2022
@Hyeongseok-Jeon
Copy link

MORAI update

  • I started to look the compatibility test code from @SoohyeokPark-MORAI
  • I could not specify the sensor configuration file yet

@WJaworskiRobotec WJaworskiRobotec moved this from In Review to In Progress in Simulation Working Group Nov 23, 2022
@WJaworskiRobotec
Copy link
Author

@Hyeongseok-Jeon any progress in this task ?

@Hyeongseok-Jeon
Copy link

@WJaworskiRobotec There is no prograss on this task in terms of importing the sensor configuration file in compatibility test code. Sorry for delaying and we will work on this issue from next week (after finishing regular version update of our product)

@Hyeongseok-Jeon
Copy link

Hyeongseok-Jeon commented Dec 2, 2022

@WJaworskiRobotec @SoohyeokPark-MORAI

How about build configuration file with the sensor category and corresponding topics?
Sample for the config file will be below

{
  "Target_sim": [
    "AWSIM"
  ],
  "Camera_list": [
    "/sensing/camera/traffic_light/image_raw",
	"/sensing/camera/traffic_light/camera_info"
  ],
  "GPS_list": [
	 "/sensing/gnss/pose",
	 "/sensing/gnss/pose_with_covariance"
  ],
  "Lidar_list": [
        "/sensing/lidar/left/pointcloud_raw",
	"/sensing/lidar/left/pointcloud_raw_ex",
	"/sensing/lidar/right/pointcloud_raw",
	"/sensing/lidar/right/pointcloud_raw_ex",
	"/sensing/lidar/top/pointcloud_raw",
	"/sensing/lidar/top/pointcloud_raw_ex"
  ]
}

Based on this structure, compatibility test will be processed only for the topic in the above configuration file on the Target simulator.
Please let me know your opinion.

@WJaworskiRobotec
Copy link
Author

@Hyeongseok-Jeon
In general looks fine, but I think we should add msg type to each topic, right ?
For example "/sensing/gnss/pose" and
"/sensing/gnss/pose_with_covariance" have different message types, the same for image_raw and camera_info.

How about the structure like that:


{
    "Target_sim": [
      "AWSIM"
    ],
    "Camera_list": [
      {
        "topic":"/sensing/camera/traffic_light/image_raw",
        "msg": "..."
      },
      {
        "topic":"/sensing/camera/traffic_light/camera_info",
        "msg": "..."
      }
    ],
...
}

@Hyeongseok-Jeon
Copy link

Hyeongseok-Jeon commented Dec 20, 2022

MORAI started developing the compatibility test tool which will be done before Jan 18th.

@WJaworskiRobotec
Copy link
Author

WJaworskiRobotec commented Jan 16, 2023

@SoohyeokPark-MORAI
I see you started to push some commits, let me know when It's ready for initial testing :)

@Soohyeok-Park
Copy link

@WJaworskiRobotec @Hyeongseok-Jeon
There have been some bug fixes and It's ready to be tested.
I have tested with the MORAI SIM.

@WJaworskiRobotec
Copy link
Author

@SoohyeokPark-MORAI

Should I use humble or galactic ?

btw. Have you added some documentation of how to run the tests ? If not , it might be a good idea to add it a a separate page here : https://autowarefoundation.github.io/autoware-documentation/main/tutorials/ under Digital Twin Simulations

@Hyeongseok-Jeon
Copy link

@WJaworskiRobotec @Soohyeok-Park

  1. We test compatiblity testing tool based on humble
  2. To run the test, please refer the followings
cd ~/${autoware installed directory}
source /opt/ros/humble/setup.bash
source install/setup.bash

cd ~/${autoware installed directory}/src/universe/autoware.universe/tools/simulator_test/simulator_compatibility_test/test_sim_common_manual_testing/
python3 -m pytest .
  1. I will make PR for the compatilibty test manual soon.

@Hyeongseok-Jeon
Copy link

@WJaworskiRobotec @SoohyeokPark-MORAI

I created PR in the link
Sorry for delaying and please let me know if you have any comment on the PR

@stale
Copy link

stale bot commented May 28, 2023

This pull request has been automatically marked as stale because it has not had recent activity.

@stale stale bot added the stale label May 28, 2023
@Hyeongseok-Jeon
Copy link

@WJaworskiRobotec

Does it have to be higher priority? Since Soohyeok is decided to leave MORAI, there will be some delay before hiring new developer.

@stale stale bot removed the stale label Jun 29, 2023
@WJaworskiRobotec
Copy link
Author

Sure, no problem. It's definitely not the highest priority

@WJaworskiRobotec WJaworskiRobotec moved this from In Progress to Blocked in Simulation Working Group Jul 18, 2023
@stale
Copy link

stale bot commented Sep 3, 2023

This pull request has been automatically marked as stale because it has not had recent activity.

@stale stale bot added the stale label Sep 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

5 participants