Gemma4 Prometheus workflow
Reproduction scripts and config for the Gemma4 Prometheus run that led to the exported merged model and GPTQ output.
What is included
gemma4_prometheus.tomlexport_prometheus_merged.pyquantize_gemma4_prometheus.pycheckpoints/with the Prometheus journal file
Related repos
- Fixes used to make the pipeline work:
groxaxo/gemma4-prometheus-fixes - Merged model:
groxaxo/gemma4-prometheus-merged - GPTQ model:
groxaxo/gemma4-prometheus-gptq-4bit - Upstream source model:
google/gemma-4-31B-it
Run
conda activate gemma4-prometheus-ready
export CUDA_VISIBLE_DEVICES=GPU-828df6fd-3fd0-ed25-0b2b-2b6d9d8dca47,GPU-78996a05-18c5-e153-b621-096273299d41,GPU-89c6bfdc-6f42-d312-de77-a9fb1ae370d8
export PM_CONFIG=./gemma4_prometheus.toml
prometheus --config ./gemma4_prometheus.toml --non-interactive --overwrite-checkpoint
python export_prometheus_merged.py --config ./gemma4_prometheus.toml --output-dir ./merged-model
python quantize_gemma4_prometheus.py --config ./gemma4_prometheus.toml --model-dir ./merged-model --output-dir ./gptq-4bit --offload-dir ./gptq-offload --prompts-per-dataset 16
Notes
- The workflow assumes the local Prometheus and GPTQModel fixes described in the fixes repo.
- The GPTQ step uses
gptqmodel==5.8.0plus the Gemma4-specific patch set. - The checkpoint journal is included so the exported merged model can be traced back to the exact Prometheus trial.
Inference Providers NEW
This model isn't deployed by any Inference Provider. 🙋 Ask for provider support