Unable to locate package ros-humble-isaac-ros-unet

NVIDIA-ISAAC-ROS / isaac_ros_image_segmentation

NVIDIA-accelerated, deep learned semantic image segmentation

Apache License 2.0

72 stars 7 forks source link

Unable to locate package ros-humble-isaac-ros-unet #24

Closed magic-Alex closed 11 months ago

magic-Alex commented 12 months ago

I tried to run the demo but I can't find package 'ros-humble-isaac-ros-unet' when installing at step 5 of the Quickstart, do you have any suggestions

magic-Alex commented 12 months ago

with docker

kajananchinniahNV commented 11 months ago

Hi,

Could you confirm that everything that you're running is on the latest version? Could you also provide further details about what platform you're running on?

Could you please run this command inside the container and let us know what the output is:

sudo apt policy ros-humble-isaac-ros-unet

The expected output is something like this:

  Installed: (none)
  Candidate: 2.1.0-0focal
  Version table:
     2.1.0-0focal 500
        500 https://isaac.download.nvidia.com/isaac-ros/ubuntu/main focal/main amd64 Packages

magic-Alex commented 11 months ago

Hi,

Could you confirm that everything that you're running is on the latest version? Could you also provide further details about what platform you're running on?

Could you please run this command inside the container and let us know what the output is:
sudo apt policy ros-humble-isaac-ros-unet
The expected output is something like this:
  Installed: (none)
  Candidate: 2.1.0-0focal
  Version table:
     2.1.0-0focal 500
        500 https://isaac.download.nvidia.com/isaac-ros/ubuntu/main focal/main amd64 Packages

Thinks,I found out that the package and doc had been updated a few days ago, but my package was previously cloned.I solved the problem by deleting docker images and running the new 'run_dev.sh'. Then I have a new question, do I need to build a new image every update.

hemalshahNV commented 11 months ago

You should only need to exit the container and run 'run_dev.sh' again which will download any new Docker image needed and launch a fresh container against it.

magic-Alex commented 11 months ago

You should only need to exit the container and run 'run_dev.sh' again which will download any new Docker image needed and launch a fresh container against it. I get it,thinks.

magic-Alex commented 11 months ago

Sorry for reopening this issue，I used a new computer and everything worked according to quickStart, but this problem reappeared. I dont understand.

yrqs commented 11 months ago

Sorry for reopening this issue，I used a new computer and everything worked according to quickStart, but this problem reappeared. I dont understand.

Have you executed sudo apt update before?

magic-Alex commented 11 months ago

Sorry for reopening this issue，I used a new computer and everything worked according to quickStart, but this problem reappeared. I dont understand.

Have you executed sudo apt update before?

No,I think it's not necessary,maybe. Because I tried to run run_dev.sh today,everything worked normally. So weird,To ensure success each time, what should I pay attention to?

hemalshahNV commented 11 months ago

This is very strange indeed. Let us check whether that package itself is being appeared/disappeared from the manifest on the debian repository somehow. That seems suspect.