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

About the usage of the dataset. #5

Closed
daleigehhh opened this issue Jul 2, 2024 · 6 comments
Closed

About the usage of the dataset. #5

daleigehhh opened this issue Jul 2, 2024 · 6 comments

Comments

@daleigehhh
Copy link

Hi, @zzuxzt!
Great work, thanks for sharinig it with the community! I am now working on Social-Nav and I am interested in occupancy grid prediction and planning. I noticed your dataset comes from the SCAND dataset but I am little confusing about how to use the npy files provided by you especially the "scan" part. Did you capture the ranges in the ROS bag files directly into your npy files? And I guess the max range is 30 meter?
Thank you

@zzuxzt
Copy link
Member

zzuxzt commented Jul 4, 2024

Thanks for your interest in our work. The lidar scan .npy file is a numpy array of scan range values. You can directly use python np.load() to read the npy file and obtain the scanning range values, and you can find the scanning bearing values (the angle range and resolution) based on the specific lidar sensor installed on the robot. The maximum range is also based on the specific lidar sensor, but I manually cut it off to 30 meters when I used it.

@daleigehhh
Copy link
Author

@zzuxzt
Hi, thanks for your reply, in your settings described in your paper, the size of the local map is (0,6.4)m on x axis and (-3.2, 3.2)m on y axis. But I see that in your code to validate a scan is in the local discrete coordinate or not, you write:
flag_v = (x_r < self.x_max) & (y_c < self.y_max) & (x_r >= 0) & (y_c >= 0) in a member function of GridMap. Hrere (y_c > 0), why not (y_c >= -3.2), -3.2 is the y_lim fo the GridMap.

@zzuxzt
Copy link
Member

zzuxzt commented Jul 31, 2024

Note that x_r and y_c are the grid indices of the OGM (x_row, y_column) rather than the physical coordinates. The range of x_r and y_c is [0, 64] in our paper.

@daleigehhh
Copy link
Author

@zzuxzt
Ok, my bad. I still have a problem understanding your code.
In the motion compensation, when calculating the coord transformation of past seq_len frames pos relative to the predicted frame pos_origin, why the inverse rotation matrix are all the same?
Uploading robot_transform_coor.png…

@zzuxzt
Copy link
Member

zzuxzt commented Aug 6, 2024

This is because we use the predicted coordinate frame as the reference frame and need to transfer the coordinates of all the past lidar sequences to the predicted coordinate frame. The predicted coordinate frame (future pose of the robot) is the same for all the past lidar sequences.

@daleigehhh
Copy link
Author

Thank you for answering my questions.

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

No branches or pull requests

2 participants