You can deploy this model and start earning money today!

groxaxo/
Qwen3.5-24.5B-Reapped-v1-GPTQ-Pro-4bit-g128

Name: Qwen3.5-24.5B-Reapped-v1-GPTQ-Pro-4bit-g128
Availability: InStock

Views

No views yet

Qwen3.5-24.5B-Reapped-v1-GPTQ-Pro-4bit-g128

Overview

Qwen3.5-24.5B-Reapped-v1-GPTQ-Pro-4bit-g128 is a GPTQ-quantized checkpoint intended for efficient GPU inference, published by groxaxo. It is intended for open-source evaluation, reproducible experimentation, and compatible local or hosted inference workflows. The wording below is deliberately limited to what can be verified from this repository's metadata and artifacts.

At a glance

Field	Details
Format	GPTQ
Source / base	the source checkpoint identified in the repository metadata
Intended task	`text-generation`
License	the license declared in the repository files

What is included

*.safetensors (4 files)
config.json
generation_config.json
tokenizer.json
tokenizer_config.json
chat_template.jinja
quantize_config.json
Additional configuration, tokenizer, processor, or shard files (11 visible artifacts total)

Quick start

vLLM (documented configuration)

bash

vllm serve groxaxo/Qwen3.5-24.5B-Reapped-v1-GPTQ-Pro-4bit-g128 \
  --quantization gptq_marlin \
  --dtype float16 \
  --trust-remote-code

This command is taken from the repository documentation. Adjust tensor parallelism, context length, and cache settings to match your hardware and vLLM version.

Compatibility and responsible use

Use a runtime that explicitly supports this format, architecture, and modality.
Keep configuration, tokenizer, processor, projection, and weight files from the same revision together.
Review the source model card and license before redistribution or deployment.
Hardware needs depend on parameter count, context length, cache precision, quantization, and concurrency.
Report reproducible issues with the runtime version, hardware, launch command, and a minimal example.

Quantization or conversion changes numerical behavior, memory use, and throughput relative to the source checkpoint; validate quality on your own workload.

Generated outputs may be inaccurate or unsuitable for a given use case. Users are responsible for testing behavior, applying appropriate safeguards, and complying with applicable licenses and laws.