hamo score 0.6b needs about 2.1 GB of memory at its main file (a 0.6 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 4 quants, from 0.6 GB to 0.6 GB. Longer context needs more: at 32K tokens the KV cache alone adds about 3.8 GB.
A 0.6B Qwen3 model for scoring wellness messages
hamo-score-0.6b is a 0.6B parameter model based on Qwen3. It reads a single wellness conversation message and outputs five scores in a JSON object. The model is lightweight and designed for local CPU inference.
Good at
- Fast inference on CPU
- Low memory footprint
- Deterministic scoring
Limits
- No vision support
- No conversation generation
- Requires prompt trimming for speed
Best for
- Live wellness scoring
- Embedded scoring in apps
- Batch score processing
Who it’s for. Developers building wellness or mental‑health tools that need quick, local scoring of user messages. The model is suitable for server or edge deployments where privacy and speed are priorities.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 0.6 GB | 2.1 GB | Fits | Get file → | |
| — | 0.6 GB | 2.1 GB | Fits | Get file → | |
| — | 0.6 GB | 2.1 GB | Fits | Get file → | |
| — | 0.6 GB | 2.1 GB | Fits | Get file → |
The available GGUF file is 0.64 GB. It requires approximately 2.1 GB of VRAM at 8 k context. For systems with 8 GB VRAM, the model runs comfortably. If VRAM is limited to 4 GB, consider using a lower‑precision quantization if available, but no such quant is listed.
What GPU do you need for hamo score 0.6b?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: the best quant that fits is the main file (0.6 GB file, about 2.1 GB in use).
Which hamo score 0.6b quant should you choose?
If memory is tight, the smallest file is the first one in the table at 0.6 GB, with the quality trade-offs that come with fewer bits.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about hamo score 0.6b
How much VRAM does hamo score 0.6b need?
About 2.1 GB at its main file with an 8K context window. That is the 0.6 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run hamo score 0.6b on an 8 GB GPU?
Yes, with the smaller files: the 0.6 GB file needs about 2.1 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of hamo score 0.6b GGUF?
It depends on the quant: file is 0.6 GB, file is 0.6 GB, file is 0.6 GB, file is 0.6 GB.
What context length does hamo score 0.6b support?
The GGUF header lists a trained context length of 40,960 tokens (40K). The KV cache grows with the context you use: about 0.9 GB at 8K and 3.8 GB at 32K.
Where can I download hamo score 0.6b GGUF?
The files are on Hugging Face in the HamoAI/hamo-score-0.6b repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does hamo score 0.6b use?
Hugging Face lists the license as other. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.
Can I run hamo-score-0.6b on 8 GB VRAM?
Yes, the model requires about 2.1 GB of VRAM at 8 k context, so 8 GB is more than sufficient.
Does the model generate text?
No, it only outputs five numeric scores in JSON.
Is the model free for commercial use?
Yes, it is released under HAMO‑RAIL‑S 1.0, which allows commercial use with restrictions.