EmAySee Greater Than (Float)

ComfyUI is a dataflow graph, which means "if this, do that" is not a language feature - it's something you assemble from comparison nodes, switches, and a pile of wires. This node is the comparison: it takes two floats, A and B, and outputs 1 if A > B, otherwise 0. That integer is the raw material for every conditional branch in your graph. Feed it into a switch or a selector node and you've got an if-statement.

How it works

The logic is one comparison - return (1,) if A > B else (0,). Strictly greater than, no equality case: if A == B, you get 0. The output is an INT (not a boolean - ComfyUI's switch/selector nodes tend to consume INTs, and 1/0 is the common convention in this ecosystem), which is exactly why the author chose it. There's no hidden threshold, no hysteresis, no edge handling beyond the strict comparison.

Inputs and outputs

• A (FLOAT, default 0, -10000 to 10000, step 0.01)
• B (FLOAT, default 0, -10000 to 10000, step 0.01)

Output: RESULT (INT) - 1 when A > B, else 0.

Wire RESULT into a switch, a conditional string selector, or multiply it against another value to scale a parameter by the comparison result. The classic build: "if my CFG/denoise/counter is above a threshold, use prompt A, else prompt B."

Where it fits in the pack

This node is the logic muscle behind the pack's automation nodes. Pair it with EmAySee_DynamicRangeSlider (which gives you a value in a range) and EmAySee_DynamicStringSelectorNode (which picks a string by index) and you have a complete "is the animated value past the halfway point? then switch prompts" branch. Also handy as a guard: gate an expensive operation on is_up from EmAySee_HostPinger or on any counter crossing a line.

Install

Part of ComfyUI_EmAySee_CustomNodes. ComfyUI Manager → search "EmAySee" → install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/EmAySee/ComfyUI_EmAySee_CustomNodes

No dependencies, no models - it's a single Python comparison. Restart and you'll see the pack's "SPECTRE v5.0" banner in the console.

The honest take

It's a one-line comparison wearing a node costume, and for a float comparison that's fine - ComfyUI's built-in logic handling is famously thin, so pack authors keep reinventing this exact wheel. The only thing that would stop me reaching for it is if you're already deep into a switch-pack ecosystem that ships its own comparison nodes (rgthree's logic set, or Impact's), because then you're mixing two conventions of INT vs boolean outputs. If you're not already committed elsewhere, this one is as clean as any. Just remember: strict >, so equality falls to 0.