VPScheduler
sampling/custom_sampling/schedulers
VPSchedulerExample
JSON Example
{
"class_type": "VPScheduler",
"inputs": {
"steps": 20,
"beta_d": 19.9,
"beta_min": 0.1,
"eps_s": 0.001
}
}This example shows required inputs only. Connection values like ["node_id", 0] should reference actual node IDs from your workflow.
Inputs
| Name | Type | Status | Constraints | Default |
|---|---|---|---|---|
steps | INT | required | min: 1, max: 10000 | 20 |
beta_d | FLOAT | required | min: 0, max: 5000, step: 0.01 | 19.9 |
beta_min | FLOAT | required | min: 0, max: 5000, step: 0.01 | 0.1 |
eps_s | FLOAT | required | min: 0, max: 1, step: 0.0001 | 0.001 |
Outputs
| Index | Name | Type | Is List | Connection Reference |
|---|---|---|---|---|
0 | SIGMAS | SIGMAS | No | ["{node_id}", 0] |
How to connect to these outputs
To connect another node's input to an output from this node, use the connection reference format:
["node_id", output_index]Where node_id is the ID of this VPScheduler node in your workflow, and output_index is the index from the table above.
Example
If this node has ID "5" in your workflow:
SIGMAS (SIGMAS):["5", 0]
Was this page helpful?