PRX pixel pipeline#6
Open
DavidBert wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PRX-Pixel in 🧨 diffusers
Quick note for running a trained PRX-Pixel checkpoint (7B, pixel-space RGB, no VAE, Qwen3-VL
text tower) through
PRXPixelPipeline. Three steps: convert → load → predict.Checkpoints
The research checkpoints live on the other cluster (point
--checkpoint_pathat one of these):/mnt/data/users/davidb/checkpoints/PRX7B-ckpt/SFT/mnt/data/users/davidb/checkpoints/PRX7B-ckpt/FDFO_forensic_omniaid1. Setup
PRX-Pixel needs the Qwen3-VL text tower →
transformers >= 4.57(pin< 5, 5.x breaks torchvision).2. Convert the checkpoint
Reads the research checkpoint (a DCP dir
*.distcpor a.ptfile) and writes a diffusers folder.Look for
✓ All parameters loaded successfully (0 missing, 0 unexpected)!. This also downloads theQwen3-VL text encoder + tokenizer into the output folder.
3. Load + predict
The pipeline already handles the PRX-Pixel specifics (x0-prediction,
noise_scale=2, 256-tokenbudget, full-res RGB). Good defaults: 50 steps, CFG 1, scheduler shift ≈ 3.