Skip to content

Latest commit

 

History

History
101 lines (79 loc) · 6.1 KB

README.md

File metadata and controls

101 lines (79 loc) · 6.1 KB
Raw

minigpt4

CONTAINERS IMAGES RUN BUILD

To start the MiniGPT4 container and webserver with the recommended models, run this command:

./run.sh $(./autotag minigpt4) /bin/bash -c 'cd /opt/minigpt4.cpp/minigpt4 && python3 webui.py \
  $(huggingface-downloader --type=dataset maknee/minigpt4-13b-ggml/minigpt4-13B-f16.bin) \
  $(huggingface-downloader --type=dataset maknee/ggml-vicuna-v0-quantized/ggml-vicuna-13B-v0-q5_k.bin)'

Then navigate your browser to http://HOSTNAME:7860

Inference Benchmark

./run.sh --workdir=/opt/minigpt4.cpp/minigpt4/ $(./autotag minigpt4) /bin/bash -c \
  'python3 benchmark.py \
    $(huggingface-downloader --type=dataset maknee/minigpt4-13b-ggml/minigpt4-13B-f16.bin) \
    $(huggingface-downloader --type=dataset maknee/ggml-vicuna-v0-quantized/ggml-vicuna-13B-v0-q5_k.bin) \
    --prompt "What does the sign say?" --prompt "How far is the exit?" --prompt "What would happen next?" \
    --image /data/images/hoover.jpg \
    --run 3 \
    --save /data/minigpt4.csv'
CONTAINERS
minigpt4
   Builds minigpt4_jp51 minigpt4_jp60
   Requires L4T ['>=34.1.0']
   Dependencies build-essential cuda cudnn python numpy cmake onnx pytorch:2.2 torchvision huggingface_hub
   Dockerfile Dockerfile
   Images dustynv/minigpt4:r35.2.1 (2023-12-11, 5.9GB)
dustynv/minigpt4:r35.3.1 (2023-12-15, 5.9GB)
dustynv/minigpt4:r35.4.1 (2023-12-14, 5.9GB)
dustynv/minigpt4:r36.2.0 (2023-12-15, 7.6GB)
CONTAINER IMAGES
Repository/Tag Date Arch Size
  dustynv/minigpt4:r35.2.1 2023-12-11 arm64 5.9GB
  dustynv/minigpt4:r35.3.1 2023-12-15 arm64 5.9GB
  dustynv/minigpt4:r35.4.1 2023-12-14 arm64 5.9GB
  dustynv/minigpt4:r36.2.0 2023-12-15 arm64 7.6GB

Container images are compatible with other minor versions of JetPack/L4T:
    • L4T R32.7 containers can run on other versions of L4T R32.7 (JetPack 4.6+)
    • L4T R35.x containers can run on other versions of L4T R35.x (JetPack 5.1+)

RUN CONTAINER

To start the container, you can use jetson-containers run and autotag, or manually put together a docker run command:

# automatically pull or build a compatible container image
jetson-containers run $(autotag minigpt4)

# or explicitly specify one of the container images above
jetson-containers run dustynv/minigpt4:r35.3.1

# or if using 'docker run' (specify image and mounts/ect)
sudo docker run --runtime nvidia -it --rm --network=host dustynv/minigpt4:r35.3.1

jetson-containers run forwards arguments to docker run with some defaults added (like --runtime nvidia, mounts a /data cache, and detects devices)
autotag finds a container image that's compatible with your version of JetPack/L4T - either locally, pulled from a registry, or by building it.

To mount your own directories into the container, use the -v or --volume flags:

jetson-containers run -v /path/on/host:/path/in/container $(autotag minigpt4)

To launch the container running a command, as opposed to an interactive shell:

jetson-containers run $(autotag minigpt4) my_app --abc xyz

You can pass any options to it that you would to docker run, and it'll print out the full command that it constructs before executing it.

BUILD CONTAINER

If you use autotag as shown above, it'll ask to build the container for you if needed. To manually build it, first do the system setup, then run:

jetson-containers build minigpt4

The dependencies from above will be built into the container, and it'll be tested during. Run it with --help for build options.