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

bug: Stopping the first launch of openset.launch.py causes model loading failure in subsequent launches #432

Open
maciejmajek opened this issue Feb 24, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@maciejmajek
Copy link
Member

Describe the bug
Stopping the first launch of openset.launch.py causes model laoding failure in subsequent launches due to existing (corrupted) model files.

Relevant code

try:
weight_path = self.get_parameter("weights_path").value
assert isinstance(weight_path, str)
if self.get_parameter("weights_path").value == "":
weight_path = self._init_weight_path()
self.segmenter = GDSegmenter(weight_path)
except Exception:
self.get_logger().error("Could not load model")
raise Exception("Could not load model")

To Reproduce
Steps to reproduce the behavior:
setup RAI

  1. run timeout 10 ros2 launch rai_bringup openset.launch.py to simulate ctrl+c during initialization
  2. run ros2 launch rai_bringup openset.launch.py
  3. See error

Expected behavior
Should either redownload the files or instruct the user to remove existing corrupted files

Screenshots
N/A

Platform

  • OS: Ubuntu 24.04
  • ROS 2 Version: Jazzy
@maciejmajek maciejmajek added the bug Something isn't working label Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant