Skip to content

Conversation

RandomGitUser321
Copy link
Contributor

Realistically, this should be added to all these nodes, I just happened to need it for this specific node at the moment.

Here's 1:1 parity proof vs the regular BasicScheduler node:
image

"steps": ("INT", {"default": 20, "min": 1, "max": 10000}),
"alpha": ("FLOAT", {"default": 0.6, "min": 0.0, "max": 50.0, "step":0.01, "round": False}),
"beta": ("FLOAT", {"default": 0.6, "min": 0.0, "max": 50.0, "step":0.01, "round": False}),
"steps": ("INT", {"default": 20, "min": 1, "max": 10000}),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

moving steps like this is a workflow-breaking change

@mcmonkey4eva
Copy link
Contributor

I believe the preferred method here is to use the split sigmas nodes iirc?

@mcmonkey4eva mcmonkey4eva added User Support A user needs help with something, probably not a bug. and removed User Support A user needs help with something, probably not a bug. labels Sep 12, 2024
@mcmonkey4eva mcmonkey4eva marked this pull request as draft September 16, 2024 03:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants