license: apache-2.0 thumbnail: https://cdn-uploads.huggingface.co/production/uploads/6625f4a8a8d1362ebcc3851a/hIZ2ZcaDyfYLT9Yd4pfOs.jpeg language:

• en base_model:
• Qwen/QwQ-32B library_name: transformers pipeline_tag: text-generation

QwQ-32B-ArliAI-RpR-v4 GGUF Models

Model Generation Details

This model was generated using llama.cpp at commit f5cd27b7.

Ultra-Low-Bit Quantization with IQ-DynamicGate (1-2 bit)

Our latest quantization method introduces precision-adaptive quantization for ultra-low-bit models (1-2 bit), with benchmark-proven improvements on Llama-3-8B. This approach uses layer-specific strategies to preserve accuracy while maintaining extreme memory efficiency.

Benchmark Context

All tests conducted on Llama-3-8B-Instruct using:

• Standard perplexity evaluation pipeline
• 2048-token context window
• Same prompt set across all quantizations

Method

• Dynamic Precision Allocation:
  • First/Last 25% of layers ‚Üí IQ4_XS (selected layers)
  • Middle 50% ‚Üí IQ2_XXS/IQ3_S (increase efficiency)
• Critical Component Protection:
  • Embeddings/output layers use Q5_K
  • Reduces error propagation by 38% vs standard 1-2bit

Quantization Performance Comparison (Llama-3-8B)

Key:

• PPL = Perplexity (lower is better)
• Œî PPL = Percentage change from standard to DynamicGate
• Speed = Inference time (CPU avx2, 2048 token context)
• Size differences reflect mixed quantization overhead

Key Improvements:

• üî• IQ1_M shows massive 43.9% perplexity reduction (27.46 ‚Üí 15.41)
• üöÄ IQ2_S cuts perplexity by 36.9% while adding only 0.2GB
• ‚ö° IQ1_S maintains 39.7% better accuracy despite 1-bit quantization

Tradeoffs:

• All variants have modest size increases (0.1-0.3GB)
• Inference speeds remain comparable (<5% difference)

When to Use These Models

üìå Fitting models into GPU VRAM

‚úî Memory-constrained deployments

‚úî Cpu and Edge Devices where 1-2bit errors can be tolerated

‚úî Research into ultra-low-bit quantization

Choosing the Right Model Format

Selecting the correct model format depends on your hardware capabilities and memory constraints.

BF16 (Brain Float 16) – Use if BF16 acceleration is available

• A 16-bit floating-point format designed for faster computation while retaining good precision.
• Provides similar dynamic range as FP32 but with lower memory usage.
• Recommended if your hardware supports BF16 acceleration (check your device's specs).
• Ideal for high-performance inference with reduced memory footprint compared to FP32.

üìå Use BF16 if:
‚úî Your hardware has native BF16 support (e.g., newer GPUs, TPUs).
‚úî You want higher precision while saving memory.
‚úî You plan to requantize the model into another format.

üìå Avoid BF16 if:
‚ùå Your hardware does not support BF16 (it may fall back to FP32 and run slower).
‚ùå You need compatibility with older devices that lack BF16 optimization.

F16 (Float 16) – More widely supported than BF16

• A 16-bit floating-point high precision but with less of range of values than BF16.
• Works on most devices with FP16 acceleration support (including many GPUs and some CPUs).
• Slightly lower numerical precision than BF16 but generally sufficient for inference.

üìå Use F16 if:
‚úî Your hardware supports FP16 but not BF16.
‚úî You need a balance between speed, memory usage, and accuracy.
‚úî You are running on a GPU or another device optimized for FP16 computations.

üìå Avoid F16 if:
‚ùå Your device lacks native FP16 support (it may run slower than expected).
‚ùå You have memory limitations.

Quantized Models (Q4_K, Q6_K, Q8, etc.) – For CPU & Low-VRAM Inference

Quantization reduces model size and memory usage while maintaining as much accuracy as possible.

• Lower-bit models (Q4_K) ‚Üí Best for minimal memory usage, may have lower precision.
• Higher-bit models (Q6_K, Q8_0) ‚Üí Better accuracy, requires more memory.

üìå Use Quantized Models if:
‚úî You are running inference on a CPU and need an optimized model.
‚úî Your device has low VRAM and cannot load full-precision models.
‚úî You want to reduce memory footprint while keeping reasonable accuracy.

üìå Avoid Quantized Models if:
‚ùå You need maximum accuracy (full-precision models are better for this).
‚ùå Your hardware has enough VRAM for higher-precision formats (BF16/F16).

Very Low-Bit Quantization (IQ3_XS, IQ3_S, IQ3_M, Q4_K, Q4_0)

These models are optimized for extreme memory efficiency, making them ideal for low-power devices or large-scale deployments where memory is a critical constraint.

• IQ3_XS: Ultra-low-bit quantization (3-bit) with extreme memory efficiency.

  • Use case: Best for ultra-low-memory devices where even Q4_K is too large.
  • Trade-off: Lower accuracy compared to higher-bit quantizations.

• IQ3_S: Small block size for maximum memory efficiency.

  • Use case: Best for low-memory devices where IQ3_XS is too aggressive.

• IQ3_M: Medium block size for better accuracy than IQ3_S.

  • Use case: Suitable for low-memory devices where IQ3_S is too limiting.

• Q4_K: 4-bit quantization with block-wise optimization for better accuracy.

  • Use case: Best for low-memory devices where Q6_K is too large.

• Q4_0: Pure 4-bit quantization, optimized for ARM devices.

  • Use case: Best for ARM-based devices or low-memory environments.

Summary Table: Model Format Selection

Included Files & Details

QwQ-32B-ArliAI-RpR-v4-bf16.gguf

• Model weights preserved in BF16.
• Use this if you want to requantize the model into a different format.
• Best if your device supports BF16 acceleration.

QwQ-32B-ArliAI-RpR-v4-f16.gguf

• Model weights stored in F16.
• Use if your device supports FP16, especially if BF16 is not available.

QwQ-32B-ArliAI-RpR-v4-bf16-q8_0.gguf

• Output & embeddings remain in BF16.
• All other layers quantized to Q8_0.
• Use if your device supports BF16 and you want a quantized version.

QwQ-32B-ArliAI-RpR-v4-f16-q8_0.gguf

• Output & embeddings remain in F16.
• All other layers quantized to Q8_0.

QwQ-32B-ArliAI-RpR-v4-q4_k.gguf

• Output & embeddings quantized to Q8_0.
• All other layers quantized to Q4_K.
• Good for CPU inference with limited memory.

QwQ-32B-ArliAI-RpR-v4-q4_k_s.gguf

• Smallest Q4_K variant, using less memory at the cost of accuracy.
• Best for very low-memory setups.

QwQ-32B-ArliAI-RpR-v4-q6_k.gguf

• Output & embeddings quantized to Q8_0.
• All other layers quantized to Q6_K .

QwQ-32B-ArliAI-RpR-v4-q8_0.gguf

• Fully Q8 quantized model for better accuracy.
• Requires more memory but offers higher precision.

QwQ-32B-ArliAI-RpR-v4-iq3_xs.gguf

• IQ3_XS quantization, optimized for extreme memory efficiency.
• Best for ultra-low-memory devices.

QwQ-32B-ArliAI-RpR-v4-iq3_m.gguf

• IQ3_M quantization, offering a medium block size for better accuracy.
• Suitable for low-memory devices.

QwQ-32B-ArliAI-RpR-v4-q4_0.gguf

• Pure Q4_0 quantization, optimized for ARM devices.
• Best for low-memory environments.
• Prefer IQ4_NL for better accuracy.

üöÄ If you find these models useful

‚ù§ Please click "Like" if you find this useful!
Help me test my AI-Powered Network Monitor Assistant with quantum-ready security checks:
üëâ Free Network Monitor

💬 How to test:
Choose an AI assistant type:

• TurboLLM (GPT-4o-mini)
• HugLLM (Hugginface Open-source)
• TestLLM (Experimental CPU-only)

What I’m Testing

I’m pushing the limits of small open-source models for AI network monitoring, specifically:

• Function calling against live network services
• How small can a model go while still handling:
  • Automated Nmap scans
  • Quantum-readiness checks
  • Network Monitoring tasks

🟡 TestLLM – Current experimental model (llama.cpp on 2 CPU threads):

• ‚úÖ Zero-configuration setup
• ‚è≥ 30s load time (slow inference but no API costs)
• üîß Help wanted! If you‚Äôre into edge-device AI, let‚Äôs collaborate!

Other Assistants

🟢 TurboLLM – Uses gpt-4o-mini for:

• Create custom cmd processors to run .net code on Free Network Monitor Agents
• Real-time network diagnostics and monitoring
• Security Audits
• Penetration testing (Nmap/Metasploit)
• üîë Get more tokens by logging in or downloading our Free Network Monitor Agent with integrated AI Assistant

🔵 HugLLM – Latest Open-source models:

• üåê Runs on Hugging Face Inference API

üí° Example commands to you could test:

1. "Give me info on my websites SSL certificate"
2. "Check if my server is using quantum safe encyption for communication"
3. "Run a comprehensive security audit on my server"
4. '"Create a cmd processor to .. (what ever you want)" Note you need to install a Free Network Monitor Agent to run the .net code from. This is a very flexible and powerful feature. Use with caution!

QwQ-32B-ArliAI-RpR-v4

Image generated using Arli AI Image Generation https://www.arliai.com/image-generation

RpR v4 Changes:

The best RP/creative model from ArliAI yet again.

• Reduced repetitions and impersonation

  To add to the creativity and out of the box thinking of RpR v3, a more advanced filtering method was used in order to remove examples where the LLM repeated similar phrases or talked for the user. Any repetition or impersonation cases that happens will be due to how the base QwQ model was trained, and not because of the RpR dataset.

• Increased training sequence length

  The training sequence length was increased to 16K in order to help awareness and memory even on longer chats.

RpR Series Overview: Building on RPMax with Reasoning

RpR (RolePlay with Reasoning) is a new series of models from ArliAI. This series builds directly upon the successful dataset curation methodology and training methods developed for the RPMax series.

RpR models use the same curated, deduplicated RP and creative writing dataset used for RPMax, with a focus on variety to ensure high creativity and minimize cross-context repetition. Users familiar with RPMax will recognize the unique, non-repetitive writing style unlike other finetuned-for-RP models.

With the release of QwQ as the first high performing open-source reasoning model that can be easily trained, it was clear that the available instruct and creative writing reasoning datasets contains only one response per example. This is type of single response dataset used for training reasoning models causes degraded output quality in long multi-turn chats. Which is why Arli AI decided to create a real RP model capable of long multi-turn chat with reasoning.

In order to create RpR, we first had to actually create the reasoning RP dataset by re-processing our existing known-good RPMax dataset into a reasoning dataset. This was possible by using the base QwQ Instruct model itself to create the reasoning process for every turn in the RPMax dataset conversation examples, which is then further refined in order to make sure the reasoning is in-line with the actual response examples from the dataset.

Another important thing to get right is to make sure the model is trained on examples that present reasoning blocks in the same way as it encounters it during inference. Which is, never seeing the reasoning blocks in it's context. In order to do this, the training run was completed using axolotl with manual template-free segments dataset in order to make sure that the model is never trained to see the reasoning block in the context. Just like how the model will be used during inference time.

The result of training QwQ on this dataset with this method are consistently coherent and interesting outputs even in long multi-turn RP chats. This is as far as we know the first true correctly-trained reasoning model trained for RP and creative writing.

You can access the model at https://arliai.com and we also have a models ranking page at https://www.arliai.com/models-ranking

Ask questions in our new Discord Server https://discord.com/invite/t75KbPgwhk or on our subreddit https://www.reddit.com/r/ArliAI/

Model Description

QwQ-32B-ArliAI-RpR-v4 is the third release in the RpR series. It is a 32-billion parameter model fine-tuned using the RpR dataset based on the curated RPMax dataset combined with techniques to maintain reasoning abilities in long multi-turn chats.

Recommended Samplers

• RpR models does not work well with repetition penalty type of samplers, even more advanced ones such as XTC or DRY.
• It works best with simple sampler settings and also being allowed to reason for a long time (high max tokens).
• You can download the ST master export uploaded in the files section of this repo as well.

Recommended to first start with:

• Temperature: 1.0
• MinP: 0.02
• TopK: 40
• Response Tokens: 2048+

Specs

• Base Model: QwQ-32B
• Max Context Length: Max 128K with Yarn (Same as base QwQ it is Natively 32K)
• Parameters: 32B
• Reasoning Model: Yes

Training Details

• Sequence Length: 16384
• Epochs: 1 epoch training (Inherited from RPMax methods)
• Fine-tuning Method: RS-QLORA+ (Rank-Stabilized LoRA + LoRA Plus 8x)
• Rank/Alpha: 128-rank 128-alpha
• Learning Rate: 0.00001
• Scheduler: Rex
• Gradient accumulation: 32

Very Nice Training graphs :)

Quantization

• BF16: https://huggingface.co/ArliAI/QwQ-32B-ArliAI-RpR-v4
• GGUF: https://huggingface.co/ArliAI/QwQ-32B-ArliAI-RpR-v4-GGUF

How to use reasoning models correctly in ST

For any reasoning models in general, you need to make sure to set:

• Prefix is set to ONLY <think> and the suffix is set to ONLY </think> without any spaces or newlines (enter)

• Reply starts with <think>

• Always add character names is unchecked

• Include names is set to never

• As always the chat template should also conform to the model being used

Note: Reasoning models work properly only if include names is set to never, since they always expect the eos token of the user turn followed by the <think> token in order to start reasoning before outputting their response. If you set include names to enabled, then it will always append the character name at the end like "Seraphina:<eos_token>" which confuses the model on whether it should respond or reason first.

The rest of your sampler parameters can be set as you wish as usual.

If you don't see the reasoning wrapped inside the thinking block, then either your settings is still wrong and doesn't follow my example or that your ST version is too old without reasoning block auto parsing.

If you see the whole response is in the reasoning block, then your <think> and </think> reasoning token suffix and prefix might have an extra space or newline. Or the model just isn't a reasoning model that is smart enough to always put reasoning in between those tokens.

If you set everything up correctly, it should look like this:

Try It Out!

Model preference is subjective, so please do try QwQ-32B-ArliAI-RpR-v4 for yourself. Your feedback both good and bad is always valueable and will help us improve the future RPMax and RpR models.