ComfyUI Node: Parameter History (C2C)

Parameter History (C2C):

The ParameterHistoryMEC node is designed to provide a comprehensive view and query capability for the parameter history database within ComfyUI. This node connects to a SQLite database that is populated by a JavaScript extension, which captures real-time changes in widget parameters across all nodes. The primary purpose of this node is to offer a structured output of parameter change history, allowing you to track and analyze how parameters have evolved over time. This can be particularly beneficial for understanding the impact of different parameter settings on your workflows and for debugging purposes. By storing only the changes from default values, the node ensures efficient data management and retrieval, making it easier to focus on significant modifications. The node also supports filtering by node class and provides options to view all history or just the differences from the last run, offering flexibility in how you access and utilize the historical data.

Parameter History (C2C) Input Parameters:

mode

The mode parameter determines the scope of the parameter history you wish to view. It offers three options: all_history, last_run_diff, and node_class_filter. Selecting all_history will display the complete record of parameter changes across all nodes, providing a broad overview of historical modifications. The last_run_diff option focuses on the changes that occurred between the last two runs, which is useful for quickly identifying recent adjustments. The node_class_filter allows you to filter the history based on a specific node class, enabling targeted analysis of parameter changes for particular types of nodes. The default value for this parameter is all_history, and it is accompanied by tooltips to guide you in selecting the appropriate mode for your needs.

Parameter History (C2C) Output Parameters:

parameter_history

The parameter_history output provides a detailed account of the parameter changes as per the selected mode. This output is crucial for understanding the evolution of parameters over time and can be used to analyze the effects of different settings on your workflows. It includes information such as the node ID, node title, node class, parameter name, and the values before and after the change. This structured output allows for easy interpretation and can be instrumental in debugging and optimizing your workflows.

Parameter History (C2C) Usage Tips:

• Use the all_history mode to get a comprehensive view of all parameter changes, which can be helpful for long-term analysis and understanding trends in parameter adjustments.
• Opt for the last_run_diff mode when you need to quickly identify what has changed between the most recent runs, which can be particularly useful for debugging and fine-tuning your workflows.
• Utilize the node_class_filter to focus on specific types of nodes, allowing for a more targeted analysis of parameter changes and their impacts on particular node classes.

Parameter History (C2C) Common Errors and Solutions:

[MEC] param_history diff error

• Explanation: This error occurs when there is an issue calculating the differences between parameter runs, possibly due to missing or corrupted data.
• Solution: Ensure that the database is intact and that the data for the runs you are comparing is complete. Check for any recent changes to the database schema or data that might have caused this issue.

[MEC] param_history DB write error

• Explanation: This error indicates a problem with writing parameter changes to the database, which could be due to a locked database or insufficient permissions.
• Solution: Verify that the database file is not being accessed by another process and that you have the necessary permissions to write to the database. Restarting the application might also resolve temporary locking issues.