horde_sdk.generation_parameters.image.consts¶
KNOWN_IMAGE_SAMPLERS ¶
Bases: StrEnum
The samplers that are known to the API.
(k_lms, k_heun, DDIM, etc)
The members below DDIM are the extended solvers, which only bridges new enough to render them
are offered. They carry the image backend's own spelling rather than the k_ prefix of the
k-diffusion block, because they are backend-native solvers rather than k-diffusion samplers.
The members below sa_solver complete the backend's non-_gpu solver list. The _gpu variants
are deliberately absent: they differ from their counterparts only in which device draws the noise,
which is a worker-side concern rather than a request-side choice. Like the block above them these
names are shared letter for letter with the backend.
Source code in horde_sdk/generation_parameters/image/consts.py
res_multistep_ancestral_cfg_pp
class-attribute
instance-attribute
¶
KNOWN_IMAGE_SCHEDULERS ¶
Bases: StrEnum
The schedulers that are known to the API.
(normal, karras, exponential, etc)
align_your_steps and gits are not schedules the backend names alongside the others: they are
sigma generators supplied by separate nodes, and each is only defined for a subset of the known
baselines. See
SCHEDULER_BASELINE_APPLICABILITY
for where they may be requested.
Source code in horde_sdk/generation_parameters/image/consts.py
KNOWN_IMAGE_CONTROLNETS ¶
Bases: StrEnum
The controlnets that are known to the API.
This is the full image-generation control_type surface: every member of
:class:horde_sdk.generation_parameters.alchemy.consts.KNOWN_ANNOTATION_CONTROL_TYPES plus hough,
the legacy image-generation spelling of the mlsd line detector. Both spellings validate; hough
is kept so existing clients keep working.
Source code in horde_sdk/generation_parameters/image/consts.py
KNOWN_IMAGE_SOURCE_PROCESSING ¶
Bases: StrEnum
The source processing methods that are known to the API.
(txt2img, img2img, inpainting, etc)
Source code in horde_sdk/generation_parameters/image/consts.py
TI_TRIGGER_INJECT_CHOICE ¶
Bases: StrEnum
The TI trigger inject choices that are known to the API.
Source code in horde_sdk/generation_parameters/image/consts.py
NO_INJECT
class-attribute
instance-attribute
¶
No injection - the model either does not require it or the user will add the trigger manually.
POSITIVE_PROMPT
class-attribute
instance-attribute
¶
Injects into the 'positive' prompt.
NEGATIVE_PROMPT
class-attribute
instance-attribute
¶
Injects into the 'negative' prompt.
LORA_TRIGGER_INJECT_CHOICE ¶
Bases: StrEnum
The LoRa trigger inject choices that are known to the API.
Source code in horde_sdk/generation_parameters/image/consts.py
NO_INJECT
class-attribute
instance-attribute
¶
No injection - the model either does not require it or the user will add the trigger manually.
EXACT_POSITIVE
class-attribute
instance-attribute
¶
Injects the exact specified trigger term into the 'positive' prompt.
EXACT_NEGATIVE
class-attribute
instance-attribute
¶
Injects the exact specified trigger term into the 'negative' prompt.
FUZZY_POSITIVE
class-attribute
instance-attribute
¶
Attempt to match the specified trigger term to a published trigger term into the 'positive' prompt.
FUZZY_NEGATIVE
class-attribute
instance-attribute
¶
Attempt to match the specified trigger term to a published trigger term into the 'negative' prompt.
KNOWN_IMAGE_WORKFLOWS ¶
Bases: StrEnum
The controlnets that are known to the API.
Source code in horde_sdk/generation_parameters/image/consts.py
CLIP_SKIP_REPRESENTATION ¶
Bases: StrEnum
The CLIP skip representations that are known.
Source code in horde_sdk/generation_parameters/image/consts.py
NEGATIVE_OFFSET
class-attribute
instance-attribute
¶
CLIP skip is used with a negative offset.
For example, -1 means "no skipped layers" and -2 means "skip the last layer". This is the case for comfyui.
POSITIVE_OFFSET
class-attribute
instance-attribute
¶
CLIP skip is used with a positive offset.
For example, 1 means "skip no layers" and 2 means "skip the first layer". This is the case for many frontends.