Excluded Loras:
The ExcludedLoras node is designed to help you manage and organize your LoRA (Low-Rank Adaptation) files by allowing you to specify which LoRAs should be excluded from certain operations or processes. This node is particularly useful when you have a large collection of LoRAs and need to ensure that specific ones are not included in a given task, such as model training or inference. By providing a straightforward method to list and merge excluded LoRAs, this node simplifies the process of managing your LoRA files, ensuring that only the desired ones are utilized in your workflows. This can be especially beneficial in scenarios where certain LoRAs may not be compatible with others or when you want to focus on a specific subset of your collection.
Excluded Loras Input Parameters:
lora_1
This parameter allows you to specify the first LoRA file to be excluded. You can choose from a list of available LoRAs, or select "None" if you do not wish to exclude any file in this slot. This parameter helps in defining the initial set of exclusions.
lora_2
Similar to lora_1, this parameter lets you specify a second LoRA file to exclude. It provides flexibility in managing multiple exclusions, ensuring that you can tailor the exclusion list to your specific needs.
lora_3
This parameter allows for the exclusion of a third LoRA file. By offering multiple slots for exclusion, the node ensures comprehensive control over which LoRAs are omitted from your processes.
lora_4
With this parameter, you can specify a fourth LoRA file to exclude. This further enhances your ability to manage and organize your LoRA files effectively.
lora_5
This parameter provides the option to exclude a fifth LoRA file. Having multiple exclusion slots allows for detailed customization of your LoRA management strategy.
merge_previous
This optional parameter accepts a list of previously excluded LoRAs, allowing you to merge them with the current exclusions. This is useful for maintaining consistency across different operations or sessions, ensuring that your exclusion list is comprehensive and up-to-date.
Excluded Loras Output Parameters:
excluded_loras
The output parameter excluded_loras provides a list of all the LoRAs that have been excluded based on the input parameters. This list is crucial for ensuring that the specified LoRAs are not included in subsequent operations, allowing for precise control over your workflow and preventing any unintended use of excluded files.
Excluded Loras Usage Tips:
- To effectively manage your LoRA files, ensure that you regularly update the exclusion list to reflect any changes in your collection or workflow requirements.
- Utilize the
merge_previousparameter to maintain a consistent exclusion list across different sessions, which can save time and reduce errors in complex workflows.
Excluded Loras Common Errors and Solutions:
No valid folders or LoRA files found.
- Explanation: This error occurs when the node cannot find any valid LoRA files or folders based on the specified input parameters.
- Solution: Ensure that the paths to your LoRA files are correctly specified and that the files exist in the expected locations. Double-check the folder paths and file names for any typos or errors.
No LoRAs found in metadata
- Explanation: This error indicates that the node was unable to extract any LoRA information from the provided metadata.
- Solution: Verify that the metadata contains the correct format for LoRA entries. Ensure that the metadata extraction process is correctly implemented and that the LoRA files are properly tagged.
