Sigmas SetFloor

Most sigma schedules end on the same handful of "standard" floor values, because that's what the common schedulers converge to for a given model. This node finds occurrences of a specific value in your schedule - the floor - and swaps them for a different one, new_floor. Simple find-and-replace, applied to a noise schedule.

The default for both is 0.0291675, which isn't a random-looking number by accident - it's the same minimum sigma SD1.5's own default schedule bottoms out at. That's the obvious use case: your schedule ends right at that familiar floor, and you want the final step to land somewhere else instead. Reasons to want that include leaving a touch more noise at the very end deliberately (useful heading into a resample pass, where you don't want the image fully "locked in" yet), or lining a schedule up with a different model's expected minimum before handing it off.

The inputs and outputs that matter

sigmas is the schedule to edit. floor is the value to search for; new_floor is what it gets replaced with. Both are FLOATs defaulting to that same SD1.5 minimum, so if you're working with a schedule that bottoms out somewhere else, change floor to match before expecting anything to happen. One output: SIGMAS.

It's a narrower tool than it might first look like. This isn't a general "clamp anything below X" operation - Sigmas Percentile handles that kind of range work - it's specifically a substitution for one exact value. That precision is the point: you're not reshaping the schedule's low end, you're correcting or repurposing the one specific number a scheduler chose to end on, and leaving everything else exactly as it was.

Installing it

ComfyUI Manager: search RES4LYF, install, restart. Manual install:

cd ComfyUI/custom_nodes
git clone https://github.com/ClownsharkBatwing/RES4LYF/
cd RES4LYF
pip install -r requirements.txt

Use the embedded pip.exe on a portable ComfyUI build. Restart and hard-refresh the page afterward.

Where people get tripped up

The most likely reason this node "does nothing" is that floor doesn't actually match any value present in your schedule. Different schedulers, and different models, don't all bottom out at the exact same minimum sigma - before assuming the node is broken, check what your schedule's final value actually is (a print or preview node helps) and set floor to match it precisely, since this is a lookup, not a fuzzy "replace whatever the minimum happens to be."