Downloads · 30 days
41
13% of all-time downloads
Justbackup/Qwen3.8-27B-ARA-abliterated-NVFP4-MTP
Qwen3.8-27B-ARA-abliterated-NVFP4-MTP is a image-text-to-text model from Justbackup. Use it for the image-text-to-text task on the model card, and read the license before you ship it in a product. The card lists the license as apache-2.0.
This is a multimodal, refusal-ablated (commonly described as "uncensored") W4A4 NVFP4 derivative of the reproducible trohrbaugh/Qwen3.8-27B-heretic-ara BF16 checkpoint. It is intended for native Blackwell NVFP4 infere…
Downloads · 30 days
41
13% of all-time downloads
All-time downloads
320
Public
Parameters
16.7B
20.6 GB on disk
Likes
0
Public
Click a slice to open those files.
.safetensors20.6 GB · 100%
How the weights are stored.
U824.4B · 88%
From the Hugging Face model README
This is a multimodal, refusal-ablated (commonly described as "uncensored") W4A4
NVFP4 derivative of the reproducible
trohrbaugh/Qwen3.8-27B-heretic-ara
BF16 checkpoint. It is intended for native Blackwell NVFP4 inference.
This artifact passed its text-capability, image-vision, benign refusal-surface,
native MTP-acceptance, integrity, and clean-load gates on vLLM 0.23. See
BUILD_MANIFEST.json, VALIDATION_REPORT.json, and SHA256SUMS for exact
provenance and results. Video tensors/processors are preserved, but video input
was not part of the live runtime gate.
The live gate used Qwen3_5ForConditionalGeneration, native three-token MTP,
the FlashInfer CUTLASS NVFP4 kernel, an 8,192-token context, and an RTX PRO 6000
Blackwell GPU. Loaded model memory was approximately 19.53 GiB.
vllm serve aday777/Qwen3.8-27B-ARA-abliterated-NVFP4-MTP \
--served-model-name Qwen3.8-27B-ARA-NVFP4-MTP \
--max-model-len 8192 \
--speculative-config '{"method":"mtp","num_speculative_tokens":3}'
Use a recent vLLM build with Qwen3.5 multimodal and compressed-tensors NVFP4 support. Native NVFP4 execution requires compatible Blackwell hardware and CUDA runtime support.
"Abliterated" or "uncensored" describes the source checkpoint's refusal-ablation process; it is not a guarantee that every prompt will receive a particular answer. Users remain responsible for evaluating outputs and applying safeguards appropriate to their deployment.