DOGMA MASTER SWITCH — Test / Full
One boolean to flip a whole workflow between test and full run
- mode
A 4K restoration graph with six semantic categories, six crop passes and a tiled inpaint is not something you iterate on at full size. You debug on a small tile, and when the tile looks right you run the whole thing. DOGMA MASTER SWITCH - class DOGMARunModeMasterV353 - is the node that makes that a one-click decision instead of a re-wiring session.
What it is
A single boolean, full_run, with the widget labels set to FULL RUN (on) and 2x2 TEST (off), and one output: mode, a string that reads either FULL WORKFLOW or 2x2 TILE TEST. Default is off, i.e. test mode - which is the right default for a graph that costs real GPU time.
That's it. It computes a string from a bool.
Why you want it anyway
Because a boolean can't be wired into a text field, and a lot of run-control plumbing is text-based. ComfyUI's switch-and-gate layer - the kind of thing rgthree and the Impact Pack populate - routes on typed values, and string-compare switches are the classic pattern for multi-branch graphs: compare the incoming mode string against a literal and let the matching branch through. This node produces the string those comparisons want, from a bool you can also feed to boolean gates. One source, two dialects.
The second reason is legibility. In a graph with forty nodes, a node labelled "MASTER SWITCH" with an obvious on/off is documentation. You hand the workflow to a colleague, they see where the expensive/fast fork is controlled, and they don't have to trace a boolean through six "convert widget to input" hops to find out what it means.
And it is honest about what the two modes are: the strings name the two phases the author's pipeline actually has - a 2x2 tiled test, and the full workflow.
Inputs and outputs that matter
full_run (BOOLEAN, default false). mode (STRING). Wire mode into whatever compares strings in your graph, and full_run into boolean gates if you have them. Do not wire mode into a prompt - it's a control string, not text for a model. Half the fun of debugging a shared workflow is finding someone did exactly that and their prompts now start with "FULL WORKFLOW".
Install
Manager → search DOGMA Nodes → install → restart. Manual:
cd ComfyUI/custom_nodes
git clone https://github.com/axior/ComfyUI-DOGMA-Nodes
No dependencies, no models (requirements.txt is a comment saying "No external dependencies"), nothing to configure. It registers under DOGMA/Run Control, the only node in that category - if you search for "switch" and find nothing, search "DOGMA" instead.
For context on why a studio bothered writing this: DOGMA Nodes is by axior, the studio arm of a Milan production team doing commercial AI-work with heavy ComfyUI inpaint chains. A master switch is a production artifact - it's what you build after the tenth time you re-enabled eleven bypassed nodes by hand.
Two practical notes
It doesn't bypass anything on its own. A boolean output is a value; whether your graph acts on it depends on gates and switches downstream. If flipping it changes nothing, you haven't finished wiring the fork.
Check the seed interaction. Test mode is where you will spend most of your time, and it's also where a randomizing seed will hide whether an improvement is real. Lock the seed while you iterate the tile, flip to full run once, then unlock.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| full_run | BOOLEAN | false | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| mode | STRING | — |