Number PI

This is about as low-drama as a node gets: Number PI has no inputs and one job - it outputs the mathematical constant π (3.14159265...) as a WAS NUMBER. That's it. No settings to configure, nothing to get wrong, nothing to troubleshoot beyond making sure the pack loaded at all.

Why it exists

WAS's number family runs on a generic NUMBER type that different downstream nodes read as an int or a float depending on what they need - the same family that gives you Constant Number (a value you type in yourself), Number Operation (arithmetic between two numbers), and the Number-to-X converters. Number PI is a convenience sitting next to Constant Number: instead of a blank slot where you type your own value, it's pre-loaded with one specific, extremely common constant that's annoying to type correctly by hand and easy to fat-finger if you do (miss a digit of 3.14159265358979 and every downstream calculation is subtly, silently wrong).

Where you'd actually use it

Honestly, most people building ComfyUI graphs will never touch this node - image generation workflows rarely need trigonometry. It earns its place for the minority of cases that do: computing an angle-driven offset, working out a circumference or arc length as part of a procedural effect, or feeding a formula in a Number Operation chain that needs π as one of its terms - a sine-wave-driven parameter sweep across a batch, say, or math behind a custom rotation. If you're not already building that kind of formula in-graph with Number Operation, you don't need this node.

What it takes and gives back

No inputs - it's a pure source node. One NUMBER output, fixed at π. Wire it straight into a Number Operation node as one of the operands, or into any other node in WAS's number family that accepts a NUMBER.

Installing it

ComfyUI Manager: search "WAS Node Suite," install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/WASasquatch/was-node-suite-comfyui

install requirements.txt against your ComfyUI Python, restart. No model, no extra dependency specific to this node - it rides along with the rest of the suite's install.

Common issues & troubleshooting

There's genuinely very little to go wrong here - a fixed-value source node can't really misbehave on its own. The one thing worth knowing is the same pack-wide caveat that applies to every node in this suite: WAS Node Suite has been unmaintained since the author marked it retired in December 2023, and the recurring failure the community reports is the whole suite failing to import after a ComfyUI update - not individual nodes like this one breaking in isolation. If Number PI (or anything else from WAS) is missing from your node search, check your ComfyUI startup log for an import error on the suite as a whole before assuming this specific node is the problem - it almost never is.