NVIDIA Jetson AI Lab tutorial not running on Jetson Orin NX

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
1

Hello All,

I was trying to run some tutorial models such as EfficientViT and NanoSam on my Jetson Orin NX with the supplied Tutorial : EfficientViT - NVIDIA Jetson AI Lab

I am having a hard time following since the container that started once did not have the same file structure. I wasn’t able to find anything related to those models above.

The following are the steps that I have followed :
git clone GitHub - dusty-nv/jetson-containers: Machine Learning Containers for NVIDIA Jetson and JetPack-L4T
bash jetson-containers/install.sh
jetson-containers run $(autotag efficientvit)

once container started running:

root@jetson-desktop:/data# mkdir -p /data/models/efficientvit/sam/
cd /data/models/efficientvit/sam/
wget https://huggingface.co/han-cai/efficientvit-sam/resolve/main/l2.pt
–2024-10-23 13:01:25-- https://huggingface.co/han-cai/efficientvit-sam/resolve/main/l2.pt
Resolving huggingface.co (huggingface.co)… 2600:9000:2831:3a00:17:b174:6d00:93a1, 2600:9000:2831:b800:17:b174:6d00:93a1, 2600:9000:2831:c00:17:b174:6d00:93a1, …
Connecting to huggingface.co (huggingface.co)|2600:9000:2831:3a00:17:b174:6d00:93a1|:443… connected.
HTTP request sent, awaiting response… 307 Temporary Redirect
Location: /mit-han-lab/efficientvit-sam/resolve/main/l2.pt [following]
–2024-10-23 13:01:26-- https://huggingface.co/mit-han-lab/efficientvit-sam/resolve/main/l2.pt
Reusing existing connection to [huggingface.co]:443.
HTTP request sent, awaiting response… 404 Not Found
2024-10-23 13:01:26 ERROR 404: Not Found.

root@jetson-desktop:/data/models/efficientvit/sam#

and in the /opt directory:

root@jetson-desktop:/data/models/efficientvit/sam# cd /opt
root@jetson-desktop:/opt# ls
nvidia torchvision-0.19.1a0+6194369-cp310-cp310-linux_aarch64.whl

Could someone please point out to what I am doing wrong?

Thank you!!

3

Hi @vickhung, it would appear that model repo was reorganized, and the checkpoint location is now here:

4

Hello dusty_nv,

Thank you for the reply. I was confused as to why the ‘jetson-container run nanosam’ command did not generate a folder under /opt? and it kept on trying to build one locally. is there not a rebuild docker for r36.4 yet?

5

Hi @vickhung, seeing as the nanosam Dockerfile still installs under /opt, my guess is that what you are seeing is from a container from a previous build stage (and not the final nanosam container)

IIRC I had not yet built/pushed nanosam:r36.4.0 container - I will add it to the list to do 👍

6

Hello dusty_nv,

Thank you for getting back to me with this! I will try again in the future.

8

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.