ComfyUI Node: Save Tuner Data

Save Tuner Data:

The SaveTunerData node is designed to store the results of an AutoTuner process into a file format that can be easily reloaded for future use. This functionality is particularly beneficial for users who wish to preserve the outcomes of their tuning sessions without having to rerun the entire tuning process each time. By saving the tuner data, you can efficiently manage and organize your tuning results, making it easier to revisit and apply them in subsequent projects. The node ensures that all relevant information, including optional metadata like prompts and descriptions, is embedded within the saved file, providing a comprehensive record of the tuning session. This capability not only saves time but also enhances workflow efficiency by allowing seamless integration of previously tuned data into new projects.

Save Tuner Data Input Parameters:

TUNER_DATA

This parameter represents the data output from the LoRA AutoTuner that you wish to save. It is crucial as it contains the tuning results that will be stored in the file. There are no specific minimum or maximum values, but it must be a valid tuner data object.

save_folder

This parameter specifies the folder where the tuner data file will be saved. It lists all configured paths from extra_model_paths.yaml and defaults. The choice of folder impacts where the file is stored, which can be important for organization and retrieval purposes.

filename

This parameter allows you to define the name of the file in which the tuner data will be saved. Subdirectories can be included in the filename (e.g., results/experiment1), and the extension .tuner is added automatically unless .json is specified. The default value is tuner_data.

overwrite

This boolean parameter determines whether existing files with the same name should be overwritten. If set to True, existing files will be replaced. If False, the node will append a numerical suffix (e.g., _001, _002) to avoid overwriting. The default value is True.

prompt

An optional string parameter that allows you to include an example prompt or trigger words in the tuner file. This can be useful for providing context or guidance when the file is loaded later. It supports multiline input and defaults to an empty string.

description

Another optional string parameter that lets you add a description or notes about the tuner run. This information is stored in the file and can be helpful for documentation or reference purposes. It also supports multiline input and defaults to an empty string.

Save Tuner Data Output Parameters:

file_path

This output parameter provides the path to the saved tuner data file. It is a string that indicates where the file has been stored, allowing you to easily locate and access the saved data for future use.

Save Tuner Data Usage Tips:

• Ensure that the TUNER_DATA input is correctly connected to the output from the LoRA AutoTuner to avoid saving incomplete or incorrect data.
• Use descriptive filenames and include relevant subdirectories to keep your saved tuner data organized and easily accessible.
• Consider using the prompt and description fields to add context and notes to your saved files, which can be helpful when revisiting the data later.

Save Tuner Data Common Errors and Solutions:

Path escapes tuner_data directory: <filename>

• Explanation: This error occurs when the specified save path attempts to escape the designated tuner_data directory, which is not allowed for security reasons.
• Solution: Ensure that the filename and save_folder parameters are set correctly so that the save path remains within the allowed directory.

Invalid tuner data

• Explanation: This error may occur if the TUNER_DATA input is not properly connected or contains invalid data.
• Solution: Verify that the TUNER_DATA input is correctly connected to the output from the LoRA AutoTuner and that the data is valid.

File already exists and cannot be overwritten

• Explanation: This error can happen if the overwrite parameter is set to False and a file with the same name already exists.
• Solution: Either enable the overwrite option or modify the filename to ensure a unique file name is used.