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

The PCD obtained by velodyne16 does not seem to yield good voxels #23

Open
af-doom opened this issue Jul 11, 2023 · 15 comments
Open

The PCD obtained by velodyne16 does not seem to yield good voxels #23

af-doom opened this issue Jul 11, 2023 · 15 comments

Comments

@af-doom
Copy link

af-doom commented Jul 11, 2023

2023-07-11 19-42-32 的屏幕截图

@samsdolphin
Copy link
Collaborator

Hi @af-doom, I apologize for my late reply. Have you solved this issue? Can you share the point cloud, image, and rosbag so I can help you to debug it?

@af-doom
Copy link
Author

af-doom commented Sep 12, 2023 via email

@samsdolphin
Copy link
Collaborator

Thank you very much for your reply. The image, bag, and PCD data are attached. Thank you very much test_data.zip

------------------ 原始邮件 ------------------ 发件人: "hku-mars/mlcc" @.>; 发送时间: 2023年9月11日(星期一) 晚上11:54 @.>; @.@.>; 主题: Re: [hku-mars/mlcc] The PCD obtained by velodyne16 does not seem to yield good voxels (Issue #23) Hi @af-doom, I apologize for my late reply. Have you solved this issue? Can you share the point cloud, image, and rosbag so I can help you to debug it? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

Hi @af-doom, I can't find your attached files here. Can you double-check?

@af-doom
Copy link
Author

af-doom commented Sep 15, 2023 via email

@lsangreg
Copy link

Hi, how did you resolve?

@Chatoyant19
Copy link

I also have this problem.Did you solve it?

@lsangreg
Copy link

@Chatoyant19 tbh i wasn't able to reproduce their results with their data, what about you?

@Chatoyant19
Copy link

@Chatoyant19 tbh i wasn't able to reproduce their results with their data, what about you?

I can get a good result with their data.I think it is necessary to adjust some parameters, when using myself datas. Because after I changed 'voxel_size' and 'eigen_ratio', I can extract more useful planes.But it is not enough, for example, the same wall cannot be extracted completely when the plane is extracted.

@lsangreg
Copy link

lsangreg commented Jan 26, 2024

@Chatoyant19 tbh i wasn't able to reproduce their results with their data, what about you?

I can get a good result with their data.I think it is necessary to adjust some parameters, when using myself datas. Because after I changed 'voxel_size' and 'eigen_ratio', I can extract more useful planes.But it is not enough, for example, the same wall cannot be extracted completely when the plane is extracted.

I think at least it is important to reproduce what they say " the average translation and rotation errors down to 6mm and 0.09 degrees for LiDAR-camera" , which for me is more or less angular error 0.067 degree baseline error 0.025 m ( should be 0.006).

With this being said I will also try to investigate more eigen and voxel size... I was working more on the edge detection intensity as my data are synthetic and highly defined...

Can I ask you which error did you introduce to your initial extrinsics?
I tried max 0.1 in translation and 2/3 degrees in rotation per axes, as with 5 degrees - as written in the paper - the algorithm goes completely wrong

@lsangreg
Copy link

@Chatoyant19 did you obtain better results?

@Chatoyant19
Copy link

@Chatoyant19 did you obtain better results?

No, I didn't. I know that my problem lies in extracting planar features from the LiDAR point clouds. I 'm unable to extract enough and high-quality planar features.Maybe use PCA to extract planar features is closely related to the quality of point cloud mapping? My LiDAR model is the Hesai FT120, which has relatively poor ranging accuracy.

@af-doom
Copy link
Author

af-doom commented Aug 6, 2024

@Chatoyant19 did you obtain better results?

No, I didn't. I know that my problem lies in extracting planar features from the LiDAR point clouds. I 'm unable to extract enough and high-quality planar features.Maybe use PCA to extract planar features is closely related to the quality of point cloud mapping? My LiDAR model is the Hesai FT120, which has relatively poor ranging accuracy.

Hello, do you have data about FT120 and camera? Can you share it with me for testing?

@Chatoyant19
Copy link

@Chatoyant19 did you obtain better results?

No, I didn't. I know that my problem lies in extracting planar features from the LiDAR point clouds. I 'm unable to extract enough and high-quality planar features.Maybe use PCA to extract planar features is closely related to the quality of point cloud mapping? My LiDAR model is the Hesai FT120, which has relatively poor ranging accuracy.

Hello, do you have data about FT120 and camera? Can you share it with me for testing?

Of course, can I have your email address? I'll send you the relevant data.

@af-doom
Copy link
Author

af-doom commented Aug 7, 2024 via email

@Chatoyant19
Copy link

@.*** This is my email address, thank you

---Original--- From: @.> Date: Wed, Aug 7, 2024 14:33 PM To: @.>; Cc: @.@.>; Subject: Re: [hku-mars/mlcc] The PCD obtained by velodyne16 does not seem toyield good voxels (Issue #23) @Chatoyant19 did you obtain better results? No, I didn't. I know that my problem lies in extracting planar features from the LiDAR point clouds. I 'm unable to extract enough and high-quality planar features.Maybe use PCA to extract planar features is closely related to the quality of point cloud mapping? My LiDAR model is the Hesai FT120, which has relatively poor ranging accuracy. Hello, do you have data about FT120 and camera? Can you share it with me for testing? Of course, can I have your email address? I'll send you the relevant data. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

Sorry, the email information has been encrypted, I cannot access it.

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

4 participants