Impact Scheduler Adapter
ImpactPack/Util
ImpactSchedulerAdapterExample
JSON Example
{
"class_type": "ImpactSchedulerAdapter",
"inputs": {
"scheduler": "simple",
"extra_scheduler": "None"
}
}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 |
|---|---|---|---|---|
scheduler | ENUM9 options
| required | - | - |
extra_scheduler | ENUM9 options
| required | - | - |
Outputs
| Index | Name | Type | Is List | Connection Reference |
|---|---|---|---|---|
0 | scheduler | simplesgm_uniformkarrasexponentialddim_uniformbetanormallinear_quadratickl_optimalAYS SDXLAYS SD1AYS SVDGITS[coeff=1.2]LTXV[default]OSS FLUXOSS WanOSS Chroma | 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 ImpactSchedulerAdapter node in your workflow, and output_index is the index from the table above.
Example
If this node has ID "5" in your workflow:
scheduler (simplesgm_uniformkarrasexponentialddim_uniformbetanormallinear_quadratickl_optimalAYS SDXLAYS SD1AYS SVDGITS[coeff=1.2]LTXV[default]OSS FLUXOSS WanOSS Chroma):["5", 0]
Was this page helpful?