Files
comfyui-workflows/optimized/T2I/flux3image/README.md
T

53 lines
2.5 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# FLUX 3 Image
This directory contains the first controlled workflow and test plan for the
server's locally installed FLUX 3 Image Klein model. The workflow does not use
the remote `Flux3ImageNode` API.
## Workflow
- `workflow.json` — API-format prompt for `/prompt` automation.
- `prompt.txt` — fixed baseline prompt.
- `variables.json` — fixed values and allowed test variables.
- `results/` — output images and matching metadata records.
The local graph uses `flux3-image-klein-int8-convrot.safetensors`,
`qwen3vl_4b_int8_convrot.safetensors` with `type=flux3`, `flux2-vae.safetensors`,
Flux guidance, Euler sampling, and the native ComfyUI sampler chain. The
remote API node is not used because it requires a separate Comfy API login.
## Test matrix
The first pass changes one variable at a time. The prompt, aspect ratio,
grounding state, safety tolerance, and reference count remain fixed unless a
row explicitly changes them.
| ID | Purpose | Resolution | References | Grounding | Seed | Status | Runtime (s) | Verdict |
|---|---|---:|---:|---|---:|---|---:|---|
| F3I-T2I-01 | Baseline local text-to-image | 1K | 0 | Off | 310001 | **Passed** | 1.2 | 1024×1024 output generated |
| F3I-T2I-02 | Lower-cost output comparison | 0.75K | 0 | Off | 310002 | Planned | — | — |
| F3I-T2I-03 | Detail/quality comparison | 1.5K | 0 | Off | 310003 | Planned | — | — |
| F3I-T2I-04 | Higher-resolution feasibility | 2K | 0 | Off | 310004 | Planned | — | — |
| F3I-T2I-05 | Grounded prompt comparison | 1K | 0 | On | 310005 | Planned | — | — |
| F3I-I2I-01 | Single-reference edit | 1K | 1 | Off | 310006 | Planned | — | — |
## Evaluation
Record the exact prompt, seed, resolution, reference filename/hash, runtime,
output dimensions, success/failure, and visual notes in `results/<test-id>.json`.
Keep the first successful baseline as the comparison target. Do not promote a
larger resolution solely because it is larger; judge detail, composition,
prompt adherence, artifacts, and cost/runtime together.
The API node's seed controls rerun identity but the service may remain
nondeterministic. That is recorded as a property of the test, not treated as a
failure.
## Initial run
The earlier API-node probe is retained as `results/F3I-T2I-01-remote-api.json`
as an environment diagnostic: it returned `Unauthorized` before generation.
The local workflow was then corrected to use the Flux 3-compatible
Qwen3-VL 4B encoder and 128-channel `flux2-vae.safetensors`; that run passed
and is recorded in `results/F3I-T2I-01.json`.