tickwave tick 1.5b needs about 1.7 GB of memory at Q4_K_M (a 1.0 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 2 quants, from 1.0 GB (Q4_K_M) to 1.0 GB (Q4_K_M). Longer context needs more: at 32K tokens the KV cache alone adds about 0.9 GB.
Tickwave Tick 1.5B – a Qwen2.5-Coder fine‑tuned for Verilog and SystemVerilog.
Tickwave Tick 1.5B is a 1.54B parameter model derived from Qwen2.5-Coder-1.5B-Instruct. It is instruction‑tuned to fix, explain, and suggest changes to small Verilog and SystemVerilog designs. The model is available in Q4_K_M quantization and runs on a CPU.
Good at
- Verilog code fixing
- Verilog code explanation
- SystemVerilog design suggestions
Limits
- No vision support
- Full context length 32,768 tokens
- Requires Apache‑2.0 license
Best for
- Embedded hardware design assistance
- Verilog debugging
- SystemVerilog code review
Who it’s for. Developers and engineers working with Verilog or SystemVerilog who need an offline assistant for code correction and explanation. The model is suitable for use within the Tickwave desktop application or any local LLM deployment.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 1.0 GB | 1.7 GB | Fits | Get file → | |
| Q4_K_M | 1.0 GB | 1.7 GB | Fits | Get file → |
The Q4_K_M quantization file is 0.99 GB and requires approximately 1.7 GB of VRAM at 8 k context. This is suitable for systems with 2 GB or more of VRAM. For lower memory budgets, no other quantizations are available in the provided file list.
What GPU do you need for tickwave tick 1.5b?
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 Q4_K_M (1.0 GB file, about 1.7 GB in use).
Which tickwave tick 1.5b quant should you choose?
Q4_K_M is the usual starting point for tickwave tick 1.5b: it balances file size and quality well. Here it is a 1.0 GB file.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about tickwave tick 1.5b
How much VRAM does tickwave tick 1.5b need?
About 1.7 GB at Q4_K_M with an 8K context window. That is the 1.0 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 tickwave tick 1.5b on an 8 GB GPU?
Yes, with Q4_K_M: the 1.0 GB file needs about 1.7 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of tickwave tick 1.5b GGUF?
It depends on the quant: Q4_K_M is 1.0 GB, Q4_K_M is 1.0 GB.
What context length does tickwave tick 1.5b support?
The GGUF header lists a trained context length of 32,768 tokens (32K). The KV cache grows with the context you use: about 0.2 GB at 8K and 0.9 GB at 32K.
Where can I download tickwave tick 1.5b GGUF?
The files are on Hugging Face in the Vigneshbscs/tickwave-tick-1.5b-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does tickwave tick 1.5b use?
Hugging Face lists the license as apache-2.0. 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 Tickwave Tick 1.5B on 8 GB VRAM?
Yes, the Q4_K_M quantized model requires about 1.7 GB of VRAM at 8 k context, well within an 8 GB budget.
Does this model support image input?
No, the model does not have vision capabilities.
What license applies to this model?
The model is released under the Apache‑2.0 license.