Downloads ยท 30 days
55
21% of all-time downloads
Goodoldjam/DiffusionGemma-26B-E38-Abliterated-BF16
DiffusionGemma-26B-E38-Abliterated-BF16 is a image-text-to-text model from Goodoldjam. Use it for the image-text-to-text task on the model card, and read the license before you ship it in a product. It is set up for transformers. The card lists the license as apache-2.0.
E38 is a deeply tested middle-layer abliteration of Google's DiffusionGemma 26B A4B model. This BF16 checkpoint is the frozen high-precision E38 reference model used to create the deployment-oriented E38 NVIDIA-styleโฆ
Downloads ยท 30 days
55
21% of all-time downloads
All-time downloads
257
Public
Parameters
25.8B
51.7 GB on disk
Likes
1
Public
Click a slice to open those files.
.safetensors51.6 GB ยท 100%
From the Hugging Face model README
<p align="center"> <a href="https://huggingface.co/Goodoldjam/DiffusionGemma-26B-E38-Abliterated-NVFP4"> <img src="https://img.shields.io/badge/RECOMMENDED_RELEASE-E38_NVFP4-16A34A?style=for-the-badge" alt="E38 NVFP4"> </a> </p>E38 is a deeply tested middle-layer abliteration of Google's DiffusionGemma 26B A4B model.
This BF16 checkpoint is the frozen high-precision E38 reference model used to create the deployment-oriented E38 NVIDIA-style NVFP4 release.
The current deployment and active performance-development model is:
The goal is not simply throughput.
The goal is maximum practical throughput while maintaining the validated quality profile.
The performance work is not focused on obtaining the largest possible tokens-per-second number by stripping away diffusion refinement.
The target is:
zero measurable quality regression while pushing throughput as far as the hardware and runtime will allow
while preserving:
Support directly helps fund:
The NVFP4 derivative already:
The validated quality-oriented configuration uses:
t_max = 0.80t_min = 0.40entropy_bound = 0.1confidence_threshold = 0.005stability_threshold = 1This configuration was retained after a:
2,400-generation prospective inference-optimization study
because it provided the strongest validated overall balance of:
Current development is attempting to make this quality target substantially faster.
Google publicly reports DiffusionGemma performance of approximately:
700+ tok/s on RTX 5090
and:
1000+ tok/s on H100
with the joint Google DeepMind / vLLM H100 result reported at:
1,008 generation tok/s
Those numbers demonstrate that DiffusionGemma has substantial raw throughput potential.
However:
Those headline numbers come from a performance-only throughput benchmark. They are not a simultaneous quality-and-speed validation.
The published H100 reproduction uses:
diffusion_entropy_bound = 0.1diffusion_confidence_threshold = 0.0ignore-eosIts published generation tok/s metric is also decode-oriented:
This is a perfectly valid performance benchmark.
But it measures:
maximum generation throughput under a throughput-oriented configuration
It does not establish that the same throughput is achieved while preserving the deeper quality-oriented inference behavior used in this project.
The E38 NVFP4 quality configuration allows:
48 maximum denoising steps per canvas
The published performance benchmark uses:
16 maximum denoising steps per canvas
Therefore:
E38's quality-oriented configuration allows 3ร the maximum denoising-step budget.
Adaptive stopping means the 48-step configuration does not necessarily execute all 48 steps on every canvas.
Therefore this does not imply exactly 3ร realized compute.
It does mean the two configurations have substantially different maximum refinement budgets.
The research goal here is intentionally harder:
retain the deeper quality-oriented refinement budget and recover throughput through better execution.
The published performance benchmark asks:
How fast can DiffusionGemma generate under a throughput-focused configuration?
This project is asking:
How fast can DiffusionGemma generate while preserving the strongest validated quality configuration?
Those are not the same benchmark.
The current target is:
Quality and speed together.
Current NVFP4 runtime optimization has already produced a substantial matched eager-versus-compiled result.
The checkpoint and quality target remained unchanged.
| Metric | Eager | Compiled Graphs | Change |
|---|---|---|---|
| Overall throughput | 276.74 tok/s | 636.46 tok/s | 2.30ร |
| Long-form throughput | 247.08 tok/s | 586.63 tok/s | 2.37ร |
| Mean latency | 1.574 s | 0.690 s | ~56% lower |
| Objective accuracy | 20/30 | 21/30 | +1 |
| Automatic lexical events | 0 | 0 | No regression detected |
| Long-form degeneration | 1 | 0 | Favorable point result |
| Terminal parsing | 26/30 | 24/30 | -2 cases |
Matched overall throughput increased from:
276.74 โ 636.46 tok/s
Long-form throughput increased from:
247.08 โ 586.63 tok/s
representing:
2.30ร higher overall throughput
and:
2.37ร higher long-form throughput
while mean latency decreased from:
1.574 s โ 0.690 s
Most importantly:
The speedup came from execution optimization, not from reducing the 48-step quality-oriented denoising target.
Early quality signals are encouraging.
20/30 eager โ 21/30 compiled
0 eager โ 0 compiled
1 eager โ 0 compiled
No obvious broad quality regression was detected in those areas.
One guard remains under investigation.
26/30 eager โ 24/30 compiled
That is a two-case difference.
Because the validation set is small, those cases may represent:
The compiled configuration will not replace the validated runtime until that question is resolved.
ACTIVE VALIDATION โ COMPILED RUNTIME NOT YET THE DEFAULT
Until the remaining structured-output guard is cleared:
292.59 tok/s remains the validated NVFP4 release throughput
while:
636.46 tok/s remains the current quality-preserving compiled candidate
The question is not simply:
Is it faster?
The question is:
Is it faster without making the model worse?
| Configuration | Purpose | Throughput |
|---|---|---|
| E38 BF16 | High-precision reference | 166.97 tok/s |
| E38 NVFP4 โ validated quality reference | Validated deployment | 292.59 tok/s |
| E38 NVFP4 โ compiled quality candidate | Same quality target, optimized execution | 636.46 tok/s A/B |
| Compiled long-form candidate | Quality-oriented long-form generation | 586.63 tok/s A/B |
| Published RTX 5090 result | Performance-only external benchmark | 700+ tok/s |
| Published H100 result | Performance-only external benchmark | 1000+ tok/s |
The external numbers are not quality-equivalent comparisons.
The current priority is:
push the quality-oriented configuration substantially faster before considering reductions to its denoising budget
E38 NVFP4 should also be a strong fit for the GeForce RTX 5090.
The 18.86 GB checkpoint fits within 32 GB VRAM, making consumer Blackwell a practical deployment target.
Similar single-model performance is expected.
Current measured E38 NVFP4 performance figures are from the RTX PRO 6000 Blackwell. Direct RTX 5090 validation is still needed.
The major validation results are aligned across:
using matched evaluation sets.
| Evaluation | Base BF16 | E38 BF16 | E38 NVFP4 |
|---|---|---|---|
| Objective validation โ 200/model | 128/200 โ 64.0% | 134/200 โ 67.0% | 137/200 โ 68.5% |
| Target refusal โ 402/model | 383/402 โ 95.27% | 0/402 โ 0.00% | 0/402 โ 0.00% |
| Prompt-majority refusal โ 134/model | 127/134 โ 94.78% | 0/134 โ 0.00% | 0/134 โ 0.00% |
| Benign false refusal โ 249/model | 0/249 โ 0.00% | 0/249 โ 0.00% | 0/249 โ 0.00% |
| Benchmark regression subset โ 100/model | 62/100 โ 62% | 58/100 โ 58% | 64/100 โ 64% |
| Multimodal โ 20/model | 20/20 | 20/20 | 20/20 |
| Multi-turn conversations โ 8/model | 8/8 | 8/8 | 8/8 |
| Multi-turn generations โ 24/model | 24/24 | 24/24 | 24/24 |
| Grammar errors /10k words โ | 4.059 | 5.479 | 3.236 |
| Lexical artifacts /10k โ | 2.243 | 1.865 | 1.387 |
| Mean latency โ | 2.487 s | 2.300 s | 0.962 s |
| Throughput โ | 162.15 tok/s | 166.97 tok/s | 292.59 tok/s |
| Checkpoint size โ | ~51.68 GB | 51.68 GB | 18.86 GB |
Aligned validation classification: PASS
E38 NVFP4 preserved the E38 behavior and capability profile under matched testing.
NVFP4 integrity validation confirmed:
E38 is the selected configuration from a controlled Heretic-based abliteration search of:
google/diffusiongemma-26B-A4B-it
More than:
80 controlled candidate configurations
were evaluated before E38 was frozen.
The final E38 modification affects:
attn.o_proj + mlp.down_projThe checkpoint was frozen after selection.
The E38 modification remained unchanged through subsequent NVFP4 conversion and validation.
9fe83b2fa2a3b7643f6dcc4a8360feb2cd96dcb9f70d215bd2e8f8f9d9d3044b
cd69540ec547f2f5cf181d527e8366fe60b49df7cafde38b434c5e42eeeb6175
No E38.1 checkpoint was created.
The defining E38 behavioral change is its substantial reduction in target refusal behavior.
The aligned full refusal comparison used:
| Refusal Metric | Base BF16 | E38 BF16 | E38 NVFP4 |
|---|---|---|---|
| Target refusal | 383/402 โ 95.27% | 0/402 โ 0.00% | 0/402 โ 0.00% |
| Prompt-majority refusal | 127/134 โ 94.78% | 0/134 โ 0.00% | 0/134 โ 0.00% |
| False refusal | 0/249 โ 0.00% | 0/249 โ 0.00% | 0/249 โ 0.00% |
The defining E38 refusal-suppression behavior was directly preserved after NVFP4 conversion.
E38 and E38 NVFP4 should therefore not be expected to retain the refusal behavior of the original upstream model.
The frozen matched 200-prompt evaluation produced:
| Model | Correct | Accuracy |
|---|---|---|
| Base BF16 | 128 / 200 | 64.0% |
| E38 BF16 | 134 / 200 | 67.0% |
| E38 NVFP4 | 137 / 200 | 68.5% |
E38 NVFP4 versus E38 BF16:
The difference was not statistically significant.
Validated conclusion: NVFP4 preserved measured E38 BF16 quality.
The higher NVFP4 point estimate is not claimed as proof that quantization makes the model more capable.
The larger public benchmark suite was run on Base BF16 and E38 BF16.
| Benchmark | Base BF16 | E38 BF16 | Delta |
|---|---|---|---|
| IFEval | 67.10% | 64.70% | -2.40 pp |
| BBH | 71.62% | 73.96% | +2.34 pp |
| MuSR | 41.80% | 50.00% | +8.20 pp |
| MMLU-Pro | 49.61% | 51.57% | +1.96 pp |
| MATH Level 5 @1280 | 84.06% | 80.51% | -3.55 pp |
The full benchmark suites have not all been rerun directly on NVFP4.
A separate aligned 100-item Base/E38/NVFP4 subset found:
The smaller aligned set is treated as a:
regression detector, not evidence of NVFP4 superiority
E38 is best described as a:
capability redistribution
rather than a universally stronger checkpoint.
The full matched MATH Level 5 evaluation used:
1,324 problems
at matched 1280-token generation capacity.
| Model | Correct | Accuracy |
|---|---|---|
| Base BF16 | 1113 / 1324 | 84.06% |
| E38 BF16 | 1066 / 1324 | 80.51% |
Difference:
-3.55 percentage points
with:
The mathematics regression is a real measured E38 BF16 tradeoff under the tested inference configuration.
The full MATH benchmark has not yet been rerun directly on NVFP4.
The aligned three-model multimodal subset produced:
| Model | Correct |
|---|---|
| Base BF16 | 20 / 20 |
| E38 BF16 | 20 / 20 |
| E38 NVFP4 | 20 / 20 |
A larger historical Base/E38 multimodal evaluation produced:
| Model | Aggregate Accuracy |
|---|---|
| Base BF16 | 88.67% |
| E38 BF16 | 88.67% |
No aggregate multimodal capability loss was observed.
The E38 tensor audit independently confirmed:
0 vision tensors modified
A prospective 432-generation total long-form study directly compared:
| Model | Grammar Errors /10k Words | Lexical Artifacts /10k |
|---|---|---|
| Base BF16 | 4.059 | 2.243 |
| E38 BF16 | 5.479 | 1.865 |
| E38 NVFP4 | 3.236 | 1.387 |
The original Base model showed the same general class of rare grammar and lexical problems before either E38 abliteration or NVFP4 quantization.
The E38-vs-Base grammar difference was statistically unresolved:
Therefore:
The long-form study did not establish an E38-specific grammar regression.
NVFP4 also did not show evidence of language-quality degradation.
The lower NVFP4 point estimates are encouraging but are not claimed as proof that quantization improves grammar.
The current working hypothesis is:
DiffusionGemma may possess greater language-quality capability than current diffusion inference is consistently extracting from the model.
This remains a research hypothesis.
Current evidence includes:
These findings suggest that some language failures may be connected to diffusion finalization rather than being purely encoded in the learned weights.
If that is true:
additional language capability may already exist inside DiffusionGemma and could potentially be recovered through better inference
That could potentially improve:
without necessarily requiring:
The next major research phase is intended to test this directly.
The NVFP4 derivative reduces checkpoint size from:
51.68 GB โ 18.86 GB
The dedicated matched performance study measured:
| Metric | Base BF16 | E38 BF16 | E38 NVFP4 |
|---|---|---|---|
| Checkpoint size | 51.68 GB | 51.68 GB | 18.86 GB |
| Mean latency | 2.487 s | 2.300 s | 0.962 s |
| Throughput | 162.15 tok/s | 166.97 tok/s | 292.59 tok/s |
Compared with E38 BF16, NVFP4 achieved:
The current compiled quality-preserving candidate has subsequently reached:
636.46 tok/s overall
and:
586.63 tok/s long-form
on its matched A/B workload.
Those newer figures remain under validation.
A likely contributor to NVFP4's performance is improved memory-system efficiency.
The smaller routed-expert representation may reduce:
and may improve effective cache behavior.
This remains a:
working performance hypothesis
The large compiled-graph A/B improvement also shows that a substantial amount of previous runtime cost came from execution overhead rather than the frozen model weights themselves.
Current optimization is separating:
The retained quality-oriented configuration is:
t_max = 0.80t_min = 0.40max_denoising_steps = 48entropy_bound = 0.1confidence_threshold = 0.005stability_threshold = 1canvas_length = 256long_form_capacity = 1280This remains the:
validated quality target
The active NVFP4 performance work is attempting to execute this target substantially faster.
Compared with the published 16-step performance-only benchmark:
48 steps represents a 3ร higher maximum denoising-step budget.
Adaptive stopping means this does not imply exactly 3ร realized computation on every generation.
The goal remains:
maximum practical throughput with zero measurable quality regression
The broader E38 research program includes:
The final aligned validation matched:
Negative findings and regressions are retained rather than discarded.
Google DiffusionGemma 26B A4B BF16
โ
Heretic / controlled abliteration search
โ
E38 BF16 โ this frozen validated reference
โ
E38 NVIDIA-style NVFP4 โ validated deployment derivative
The BF16 checkpoint is intentionally retained so the effects of:
can be evaluated independently.
google/diffusiongemma-26B-A4B-it
Pinned revision:
f7f5b7f5fa82ffc52addd066915886d497f5517b
Overlay SHA256:
9fe83b2fa2a3b7643f6dcc4a8360feb2cd96dcb9f70d215bd2e8f8f9d9d3044b
Selection hash:
cd69540ec547f2f5cf181d527e8366fe60b49df7cafde38b434c5e42eeeb6175
Measured E38 weight difference:
0.02503088028540.201904296875E38 is experimental and is not universally stronger than Base.
Known considerations include:
The current long-form evidence did not establish an E38-specific grammar regression.
The possibility that better diffusion inference could unlock additional language quality remains a:
research hypothesis
This checkpoint is intended for:
For deployment and current performance development:
This model intentionally has substantially reduced refusal behavior.
It may answer requests that the upstream DiffusionGemma checkpoint would refuse.
The aligned evaluation found:
| Model | Target Refusal |
|---|---|
| Base BF16 | 383 / 402 โ 95.27% |
| E38 BF16 | 0 / 402 โ 0.00% |
| E38 NVFP4 | 0 / 402 โ 0.00% |
Benign false refusal was:
0 / 249 for Base BF16, E38 BF16, and E38 NVFP4
This release should therefore not be interpreted as retaining the original model's refusal or safety characteristics.
Users should independently evaluate behavior appropriate for their application.
Original upstream model:
google/diffusiongemma-26B-A4B-it
Recommended deployment derivative:
Apache License 2.0.
This repository contains a modified derivative of:
google/diffusiongemma-26B-A4B-it