Sigmas Count

This is the simplest node in RES4LYF's entire sigma toolbox, and it's one of the more genuinely useful ones once you start building schedules by hand with the rest of the pack. Sigmas Count takes a sigma schedule and tells you how many values are in it, as a plain integer.

Why you'd need this

A sigma schedule with N sampling steps is actually stored as N+1 values - the list includes both the starting noise level and the final near-zero endpoint. That's easy to lose track of once you start chaining RES4LYF's other sigma nodes together: Sigmas Append pads extra values on, Sigmas Concat glues two schedules together, Sigmas CatmullRom resamples to a points count you set yourself (and defaults to 100 if you forget to), Sigmas AdaptiveStep can resize the schedule based on a target_steps setting. After a few of these in a row, "how many steps am I actually about to run" stops being obvious from looking at the graph. Sigmas Count answers that directly instead of making you guess or trust the wiring.

How it works

Exactly what it sounds like: counts the entries in the input list, returns that number.

The inputs and outputs that matter

• sigmas (SIGMAS, required) - the schedule to measure.

Output is a single count (INT) - the number of values in the schedule.

How to install it

• ComfyUI Manager - search "RES4LYF", install, restart.
• Manual - activate your venv, cd ComfyUI/custom_nodes && git clone https://github.com/ClownsharkBatwing/RES4LYF, cd RES4LYF, pip install -r requirements.txt (portable builds: use the embedded pip.exe). Restart.

How to actually use it

Wire it to a display or preview node so you can see the number, or feed it into another node's step-count-shaped input - Sigmas AdaptiveStep's target_steps, for instance - so the two stay in sync automatically instead of you hardcoding a number that drifts out of date the moment you tweak something upstream.

Common issues & troubleshooting

There's genuinely not much to go wrong here - it's a query node, not a transform, so there's no parameter to misconfigure and no output shape to get wrong. The only real mistake is not using it: if you're chaining two or three of RES4LYF's other sigma-math nodes together (any combination of Add, Mult, Append, Concat, the arc-trig reshaping nodes, or the chaos/attractor generators), drop a Sigmas Count - and ideally a preview of the actual values - into the chain before you commit a full-resolution render to a schedule you haven't actually checked. None of those other nodes validate their own output, and this is the cheapest way to catch a mistake before it costs you GPU time.