-
Notifications
You must be signed in to change notification settings - Fork 19
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
Handling empty data #21
Comments
Minimal steps to reproduce
Result The
The Expected Result The |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
stop_reconstruction
service returns a boolean for whether or not it was successfully able to construct a mesh. The current implementation only returns false if thestart_reconstruction
service had not yet been called (actually, looking at the code, I don't think the internal state is ever reset -- it looks like calling start followed by multiple stops might not be detected, though I haven't tried it to verify).Except for that particular case of not calling the start service, the stop service is assumed to succeed and always returns true. However, there are cases where the mesh generation can fail -- in particular, if no data is received from the camera or there is an issue converting camera data to the correct frame, the industrial reconstruction node will crash with numpy complaining about attempting to take the minimum of an empty array.
The industrial reconstruction node should be robust against issues like this, and should gracefully handle any errors by returning false to indicate that the mesh generation failed.
The text was updated successfully, but these errors were encountered: