Instructions to use litert-community/clef-flash-LiteRT with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- LiteRT
How to use litert-community/clef-flash-LiteRT with LiteRT:
# No code snippets available yet for this library. # To use this model, check the repository files and the library's documentation. # Want to help? PRs adding snippets are welcome at: # https://github.com/huggingface/huggingface.js
- Notebooks
- Google Colab
- Kaggle
|
Download examples/README.md from litert-community/clef-flash-LiteRT: direct link, hf CLI and curl.
- Browser
- Download file 1.4 kB
-
https://huggingface.co/litert-community/clef-flash-LiteRT/resolve/main/examples/README.md
- Command line
-
hf download hf://litert-community/clef-flash-LiteRT/examples/README.md
-
curl -L -o README.md https://huggingface.co/litert-community/clef-flash-LiteRT/resolve/main/examples/README.md
1.4 kB
Running the example
From the root of this repository, on a Mac (the commands were run on macOS 27.0 with Python 3.14.6):
python3 -m venv .venv
.venv/bin/pip install -r host/requirements-host.txt
.venv/bin/python examples/run_example.py --check
.venv/bin/python examples/run_example.py --check --accelerator cpu
.venv/bin/python examples/run_example.py --request examples/request.json --image fixtures/images/clock_3oclock_256x240.png --tile 256
--checkanswers four public fixture requests (a SemIf record, a support ticket, a JSON order and a drawn picture) on the GPU at float32 precision (Metal on a Mac), compares them with the provider's own code in float32 on the CPU (run_example.expected.json), sends twelve requests the host refuses, and prints one line,PASSorFAIL.--accelerator cpudoes the same on the CPU (XNNPACK, 8 threads).--requestanswers your own request (a JSON file of the SystemOne-compatible request shape) and prints the response;--imageadds one picture, read at a 448 px square tile (--tile 448, the default) or a 256 px one.- A graph is compiled the first time a request needs it: on the GPU that takes one to three minutes per row graph. One process keeps one row graph at a time; a request of another length closes it and compiles the next.
- A request the host refuses prints
refused: <error>: <message>and exits with code 3.