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

Some problems about ZeroDivisionError #138

Open
Ethan0207 opened this issue Apr 24, 2024 · 1 comment
Open

Some problems about ZeroDivisionError #138

Ethan0207 opened this issue Apr 24, 2024 · 1 comment

Comments

@Ethan0207
Copy link

Hi,
I have a question I'd like to consult about. When I changed the LiDAR, I encountered the following error during the training process. So, when using the Velodyne LiDAR, why do you not need to consider this division by zero error? And How can you ensure that mag1 * mag2 does not equal zero?
4 24-1
4 24-2

@reiniscimurs
Copy link
Owner

Division by 0 can only happen if both data[i][0] and data[i][1] are 0. This is unrealistic as it means that the returned point value is at x=0 and y=0. This does not happen for the velodyne Puck as those are not real values that it could encounter.

My only guess is that the lidar you are using is either not set up properly, is returning faulty data or sets inf values as 0. You shoyld check how data is represented differently between the velodyne lidar and the lidar you are using.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants