IndustrialCoder Thinking needs about 22.0 GB of memory at Q4_K_M (a 19.3 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 24 quants, from 0.0 GB to 26.2 GB (Q6_K). Longer context needs more: at 32K tokens the KV cache alone adds about 8.6 GB.
IndustrialCoder Thinking – 32B code model with chain‑of‑thought reasoning
IndustrialCoder Thinking is a 32B llama‑based model trained for industrial code generation. It adds a reasoning trace inside ` ... ` tags to decompose complex tasks before writing code. The model is tuned for debugging RTL, optimizing GPU kernels, and diagnosing embedded firmware.
Good at
- Multi‑step code reasoning
- Industrial code debugging
- Hardware‑centric code generation
Limits
- Requires large VRAM for full context
- No vision support
- License is Apache‑2.0
Best for
- Debugging RTL modules
- Optimizing GPU kernels
- Diagnosing embedded firmware
Who it’s for. Engineers and developers working on low‑level hardware or performance‑critical code. The model is useful when step‑by‑step reasoning is needed before code output.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 0.0 GB | 2.7 GB | Fits | Get file → | |
| IQ1_S | 6.9 GB | 9.5 GB | Too big | Get file → | |
| IQ1_M | 7.5 GB | 10.2 GB | Too big | Get file → | |
| IQ2_XXS | 8.6 GB | 11.3 GB | Too big | Get file → | |
| IQ2_XS | 9.6 GB | 12.2 GB | Too big | Get file → | |
| IQ2_S | 10.0 GB | 12.6 GB | Too big | Get file → | |
| IQ2_M | 10.8 GB | 13.5 GB | Too big | Get file → | |
| Q2_K_S | 11.0 GB | 13.7 GB | Too big | Get file → | |
| Q2_K | 11.9 GB | 14.5 GB | Too big | Get file → | |
| IQ3_XXS | 12.4 GB | 15.1 GB | Too big | Get file → | |
| IQ3_XS | 13.2 GB | 15.9 GB | Too big | Get file → | |
| Q3_K_S | 13.9 GB | 16.6 GB | Too big | Get file → | |
| IQ3_S | 13.9 GB | 16.6 GB | Too big | Get file → | |
| IQ3_M | 14.3 GB | 17.0 GB | Too big | Get file → | |
| Q3_K_M | 15.4 GB | 18.1 GB | Too big | Get file → | |
| Q3_K_L | 16.8 GB | 19.4 GB | Too big | Get file → | |
| IQ4_XS | 17.2 GB | 19.8 GB | Too big | Get file → | |
| Q4_0 | 18.2 GB | 20.8 GB | Too big | Get file → | |
| Q4_K_S | 18.2 GB | 20.9 GB | Too big | Get file → | |
| Q4_K_M | 19.3 GB | 22.0 GB | Too big | Get file → | |
| Q4_1 | 20.1 GB | 22.7 GB | Too big | Get file → | |
| Q5_K_S | 22.1 GB | 24.7 GB | Too big | Get file → | |
| Q5_K_M | 22.7 GB | 25.3 GB | Too big | Get file → | |
| Q6_K | 26.2 GB | 28.9 GB | Too big | Get file → |
For 8 GB VRAM, use IQ1_S (6.88 GB, 9.5 GB memory at 8 k context). For 12 GB VRAM, IQ2_S (9.95 GB, 12.6 GB memory). For 16 GB VRAM, Q3_K_S (13.9 GB, 16.6 GB memory). Estimates are approximate.
What GPU do you need for IndustrialCoder Thinking?
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.0 GB file, about 2.7 GB in use).
- 6 GB VRAM: the best quant that fits is the main file (0.0 GB file, about 2.7 GB in use).
- 8 GB VRAM: the best quant that fits is the main file (0.0 GB file, about 2.7 GB in use).
- 12 GB VRAM: the best quant that fits is IQ2_XXS (8.6 GB file, about 11.3 GB in use).
- 16 GB VRAM: the best quant that fits is IQ3_XS (13.2 GB file, about 15.9 GB in use).
- 24 GB VRAM: the best quant that fits is Q4_1 (20.1 GB file, about 22.7 GB in use).
- 32 GB VRAM: the best quant that fits is Q6_K (26.2 GB file, about 28.9 GB in use).
Which IndustrialCoder Thinking quant should you choose?
Q4_K_M is the usual starting point for IndustrialCoder Thinking: it balances file size and quality well. Here it is a 19.3 GB file.
If memory is tight, the smallest file is the first one in the table at 0.0 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 IndustrialCoder Thinking
How much VRAM does IndustrialCoder Thinking need?
About 22.0 GB at Q4_K_M with an 8K context window. That is the 19.3 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 IndustrialCoder Thinking on an 8 GB GPU?
Yes, with the smaller files: the 0.0 GB file needs about 2.7 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of IndustrialCoder Thinking GGUF?
It depends on the quant: file is 0.0 GB, IQ1_S is 6.9 GB, IQ1_M is 7.5 GB, IQ2_XXS is 8.6 GB, IQ2_XS is 9.6 GB, IQ2_S is 10.0 GB and 18 more.
What context length does IndustrialCoder Thinking support?
The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 2.1 GB at 8K and 8.6 GB at 32K.
Where can I download IndustrialCoder Thinking GGUF?
The files are on Hugging Face in the mradermacher/IndustrialCoder-Thinking-i1-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 IndustrialCoder Thinking 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 IndustrialCoder Thinking on 8 GB VRAM?
Use the IQ1_S quant, which is 6.88 GB and requires about 9.5 GB of VRAM at 8 k context.
Does the model support vision tasks?
No, the model is purely text‑based and has no vision capabilities.
What license applies to this model?
The model is released under the Apache‑2.0 license.