nodes/DumiFlex-ComfyUI-Wildcard-Pipeline

Files

T

Claude 68326e855a feat(model-info): keep the model variables out of the assembler unless shown

Each Detected row gets the Injector's globe. All three start internal:
later rules read them, the Assembler and its chips leave them out until
the globe is clicked. The canvas walkers and preview chain follow the
same flags.

2026-10-06 05:31:17 +00:00

3.0 KiB

Raw Blame History

WP Model Info

Names the loaded checkpoint so your rules can branch on it. Writes three variables into the Context:

$model_family: the architecture, read from the model itself (sd15, sdxl, flux, sd3, …).
$model_variant: the fine-tune line, read from the file name by the variant rules (pony, illustrious, noobai, animagine, or empty when nothing matches).
$model_name: the file name without folders or extension.

Pony and Illustrious are both SDXL underneath, so only the file name can tell them apart.

Inputs

upstream (optional): an existing Context to extend. Only nodes after Model Info see its variables, so put it first in the chain.
model (optional): the MODEL from your checkpoint loader. Gives the family, and the node follows the wire back to the loader to read its file name (through LoRA loaders and other model patches).

Detected shows the three values and where each comes from. The variant and name update as soon as you change the loader's checkpoint; the family needs the loaded model, so it shows after the first run.
The globe on a row decides whether the Assembler can use that variable. All three start internal: later rules read them, but the Assembler leaves them out of the prompt and its variable chips. Click the globe to use one in the Assembler, for example $model_variant in a file-name prefix.
Click the pin on a row to use your own value instead, for example a file name when no model is wired, or a variant to try your Pony rules without switching checkpoint. Click it again to go back to detection.
Variant rules are variant + pattern rows. The first pattern found in the file name sets $model_variant, and its row lights up. Case-insensitive, | separates alternatives. A broken row is outlined in red and skipped (WP Debug says why). Reset puts the shipped rules back.

Output

context: the upstream Context plus the three variables. To use a value outside the pipeline, turn its globe off and put it in an Assembler template.

How to use

Wire Load Checkpoint → MODEL into model, and Model Info's context into your first WP Context.
Branch on $model_variant in a derivation. The derivation editor's LoRA by model button adds a ready-made rule that sets $loras per variant; put $loras in your Assembler template.
To drive a constraint from the model, make a wildcard (say "Model") with options pony and illustrious, and in its node settings set Match variable to model_variant. It then picks the option equal to the detected variant, and any constraint can use it as its source.

Tips

If a node that loads LoRAs from the prompt sits on the model, take MODEL from before it, or the graph loops.
A wildcard set to Match variable uses its fallback option when no option matches; without one it rolls as usual and WP Debug says why.
WP Debug's trace shows each value and where it came from (model, loader, rules or pinned).

3.0 KiB Raw Blame History