Instructions to use Liyulingyue/PaddleOCR-VL-half-GGUF with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- llama-cpp-python
How to use Liyulingyue/PaddleOCR-VL-half-GGUF with llama-cpp-python:
# !pip install llama-cpp-python from llama_cpp import Llama llm = Llama.from_pretrained( repo_id="Liyulingyue/PaddleOCR-VL-half-GGUF", filename="llm_model.gguf", )
llm.create_chat_completion( messages = "No input example has been defined for this model task." )
- Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- llama.cpp
How to use Liyulingyue/PaddleOCR-VL-half-GGUF with llama.cpp:
Install (macOS, Linux)
curl -LsSf https://llama.app/install.sh | sh # Start a local OpenAI-compatible server with a web UI: llama serve -hf Liyulingyue/PaddleOCR-VL-half-GGUF:Q4_0 # Run inference directly in the terminal: llama cli -hf Liyulingyue/PaddleOCR-VL-half-GGUF:Q4_0
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf Liyulingyue/PaddleOCR-VL-half-GGUF:Q4_0 # Run inference directly in the terminal: llama cli -hf Liyulingyue/PaddleOCR-VL-half-GGUF:Q4_0
Use pre-built binary
# Download pre-built binary from: # https://github.com/ggerganov/llama.cpp/releases # Start a local OpenAI-compatible server with a web UI: ./llama-server -hf Liyulingyue/PaddleOCR-VL-half-GGUF:Q4_0 # Run inference directly in the terminal: ./llama-cli -hf Liyulingyue/PaddleOCR-VL-half-GGUF:Q4_0
Build from source code
git clone https://github.com/ggerganov/llama.cpp.git cd llama.cpp cmake -B build cmake --build build -j --target llama-server llama-cli # Start a local OpenAI-compatible server with a web UI: ./build/bin/llama-server -hf Liyulingyue/PaddleOCR-VL-half-GGUF:Q4_0 # Run inference directly in the terminal: ./build/bin/llama-cli -hf Liyulingyue/PaddleOCR-VL-half-GGUF:Q4_0
Use Docker
docker model run hf.co/Liyulingyue/PaddleOCR-VL-half-GGUF:Q4_0
- LM Studio
- Jan
- Ollama
How to use Liyulingyue/PaddleOCR-VL-half-GGUF with Ollama:
ollama run hf.co/Liyulingyue/PaddleOCR-VL-half-GGUF:Q4_0
- Unsloth Studio
How to use Liyulingyue/PaddleOCR-VL-half-GGUF with Unsloth Studio:
Install Unsloth Studio (macOS, Linux, WSL)
curl -fsSL https://unsloth.ai/install.sh | sh # Run unsloth studio unsloth studio -H 0.0.0.0 -p 8888 # Then open http://localhost:8888 in your browser # Search for Liyulingyue/PaddleOCR-VL-half-GGUF to start chatting
Install Unsloth Studio (Windows)
irm https://unsloth.ai/install.ps1 | iex # Run unsloth studio unsloth studio -H 0.0.0.0 -p 8888 # Then open http://localhost:8888 in your browser # Search for Liyulingyue/PaddleOCR-VL-half-GGUF to start chatting
Using HuggingFace Spaces for Unsloth
# No setup required # Open https://huggingface.co/spaces/unsloth/studio in your browser # Search for Liyulingyue/PaddleOCR-VL-half-GGUF to start chatting
- Atomic Chat new
- Docker Model Runner
How to use Liyulingyue/PaddleOCR-VL-half-GGUF with Docker Model Runner:
docker model run hf.co/Liyulingyue/PaddleOCR-VL-half-GGUF:Q4_0
- Lemonade
How to use Liyulingyue/PaddleOCR-VL-half-GGUF with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull Liyulingyue/PaddleOCR-VL-half-GGUF:Q4_0
Run and chat with the model
lemonade run user.PaddleOCR-VL-half-GGUF-Q4_0
List all available models
lemonade list
PaddleOCR-VL GGUF models hallucinate on large blocks of text
When I input an image containing a block of text to the PaddleOCR-VL GGUF, the output contains a lot of hallucinations.
For example, I tried with using this as input
And the output is this:
One advantage of parameterizing policies according to the soft-max action preferences is that the action-value and the?? are the same as the??.
This does not happen with the vllm example found here: https://docs.vllm.ai/projects/recipes/en/latest/PaddlePaddle/PaddleOCR-VL.html#installing-vllm
I get this issue even when using the Q8 and Q16 GGUF models. Does anyone know how to address this issue?
I only run it on my edge devices(just for some simple text recognition) and haven't tried processing such large amounts of text.
It might have caused some destructive accuracy interference when decoupling the original process...