Save 4 hours! We auto-setup your workflow! Free!

Drop your workflow.json — we handle every dependency, custom node, and model. Just open the link and run.

Auto-Setup Workflow Json (Free) Now!
ComfyUI > Nodes > ComfyUI-MAINodes > H3 Plan Estimate (alpha)

ComfyUI Node: H3 Plan Estimate (alpha)

Class Name

H3PlanEstimate

Category
latent/minimax/timeline
Author
matlowai (Account age: 1004days)
Extension
ComfyUI-MAINodes
Latest Updated
2026-08-26
Github Stars
0.11K

How to Install ComfyUI-MAINodes

Install this extension via the ComfyUI Manager by searching for ComfyUI-MAINodes
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter ComfyUI-MAINodes in the search bar
After installation, click the Restart button to restart ComfyUI. Then, manually refresh your browser to clear the cache and access the updated list of nodes.

Visit ComfyUI Online for ready-to-use ComfyUI environment

  • Free trial available
  • 16GB VRAM to 80GB VRAM GPU machines
  • 400+ preloaded models/nodes
  • Freedom to upload custom models/nodes
  • 200+ ready-to-run workflows
  • 100% private workspace with up to 200GB storage
  • Dedicated Support

Run ComfyUI Online

H3 Plan Estimate (alpha) Description

Estimate plan execution time and resources for AI artists using H3Backend for accurate project planning and management.

H3 Plan Estimate (alpha):

The H3PlanEstimate node is designed to provide an estimation of a plan's execution within the H3 system, focusing on time and resource allocation. This node is particularly useful for AI artists who need to understand the potential duration and complexity of their creative projects before execution. By analyzing a plan document, it calculates the estimated time in seconds and other relevant metrics, helping users to better plan and manage their timelines. The node leverages the H3Backend to perform these estimations, ensuring that the results are accurate and reliable. This functionality is crucial for optimizing workflows and ensuring that projects are completed efficiently and within expected timeframes.

H3 Plan Estimate (alpha) Input Parameters:

plan_path

The plan_path parameter specifies the file path to the plan document that needs to be estimated. This document contains the timeline surface's JSON, detailing what the shot should do in terms of seconds and densities. Providing a valid path is essential for the node to access and process the plan. There are no explicit minimum or maximum values, but the path must point to a valid and accessible file.

plan_json

The plan_json parameter allows you to input the plan directly as a JSON string. This is particularly useful when you have the plan data available in a digital format, such as from a chat or another application, and want to bypass the need for a file. When both plan_path and plan_json are provided, plan_json takes precedence. This parameter does not have specific value constraints but must be a valid JSON string representing the plan.

ignore_uncompiled_lanes

The ignore_uncompiled_lanes parameter is a boolean flag that determines whether to ignore lanes in the plan that have not been compiled. Setting this to True can be useful if you want to focus only on the compiled parts of the plan, potentially speeding up the estimation process. The default value is False, meaning all lanes are considered by default.

port

The port parameter specifies the network port used for communication with the H3Backend. This is an integer value, with a default of 8188. Adjusting this may be necessary if there are port conflicts or specific network configurations in your environment.

recorder_path

The recorder_path parameter indicates the file path to a recorder file, which may contain additional context or data relevant to the estimation process. If the file exists, it is included in the context for estimation. This parameter is optional, and if not provided, the default path from recorder.DEFAULT_PATH is used.

H3 Plan Estimate (alpha) Output Parameters:

multiplier

The multiplier output represents a scaling factor derived from the estimation process. It indicates how the plan's execution time or resource usage might be scaled relative to a baseline or expected value. This helps in understanding the relative complexity or intensity of the plan.

seconds

The seconds output provides the estimated execution time of the plan in seconds. If the estimation process cannot determine a valid time, this value is set to -1.0, indicating an abstention from providing a guess. This output is crucial for time management and scheduling.

work_units_plan

The work_units_plan output indicates the number of work units required for the plan. This is an integer value representing the computational or resource load expected during execution. Understanding this helps in resource allocation and planning.

fit

The fit output is a string that describes how well the plan fits within the expected parameters or constraints. This qualitative measure can provide insights into potential adjustments or optimizations needed for the plan.

report

The report output is a detailed string containing lines of information about the estimation process, including any skipped steps or abstentions. This report is valuable for debugging and understanding the estimation's context and results.

H3 Plan Estimate (alpha) Usage Tips:

  • Ensure that the plan_path or plan_json is correctly specified and accessible to avoid errors during the estimation process.
  • Use the ignore_uncompiled_lanes parameter to focus on specific parts of the plan, which can help in optimizing the estimation process and reducing unnecessary computations.
  • Review the report output for detailed insights into the estimation process, which can help in identifying areas for improvement or adjustment in your plan.

H3 Plan Estimate (alpha) Common Errors and Solutions:

H3 Plan Estimate: <error_message>

  • Explanation: This error occurs when there is an issue with compiling the plan document, possibly due to an invalid path or malformed JSON.
  • Solution: Verify that the plan_path points to a valid file and that the plan_json is correctly formatted. Ensure that the file or JSON contains all necessary data for compilation.

seconds = -1: layer (b) abstained, and this node will not turn an abstention into a number

  • Explanation: This message indicates that the estimation process could not determine a valid execution time, resulting in an abstention.
  • Solution: Check the plan document for completeness and correctness. Ensure that all necessary components are compiled and that there are no missing or invalid sections.

H3 Plan Estimate (alpha) Related Nodes

Go back to the extension to check out more related nodes.
ComfyUI-MAINodes
RunComfy
Copyright 2025 RunComfy. All Rights Reserved.

RunComfy is the premier ComfyUI platform, offering ComfyUI online environment and services, along with ComfyUI workflows featuring stunning visuals. RunComfy also provides AI Models, enabling artists to harness the latest AI tools to create incredible art.

H3 Plan Estimate (alpha)