H3 Probe Schedule (early-oracle head):
The H3ProbeSchedule node is designed to optimize the initial stages of a sampling process by focusing on the head of the baseline schedule. This approach is particularly beneficial for scenarios where the early stages of a process can provide sufficient information for subsequent steps, allowing for a more efficient execution by skipping a significant portion of the initial pass. The node is tailored to work with the H3 Jerk Oracle and H3 Time Smear, leveraging the early estimates to initiate processes effectively. This method is advantageous when the fine details are not crucial in the early stages, as the injection process tends to obscure these details. The primary goal of the H3ProbeSchedule is to provide a workable initial estimate that can be refined in later stages, thus saving time and computational resources.
H3 Probe Schedule (early-oracle head) Input Parameters:
model
The model parameter represents the model object that the node will operate on. It is a required input and serves as the foundation for the sampling process. The model's structure and capabilities directly influence the node's performance and the quality of the initial estimates it generates.
scheduler
The scheduler parameter determines the scheduling strategy used during the sampling process. It offers several options, including "simple," "normal," "beta," "sgm_uniform," "karras," and "exponential," with "simple" being the default. Each option represents a different approach to managing the sampling steps, impacting the efficiency and outcome of the process.
total_steps
The total_steps parameter specifies the total number of steps in the sampling process. It has a default value of 25, with a minimum of 4 and a maximum of 100. This parameter controls the overall length of the sampling process, influencing the granularity and detail of the final output.
probe_steps
The probe_steps parameter defines how many steps of the schedule to actually run during the initial pass. It has a default value of 6, with a minimum of 2 and a maximum of 100. This parameter allows you to adjust the extent of the initial pass, balancing between efficiency and the level of detail captured in the early stages.
H3 Probe Schedule (early-oracle head) Output Parameters:
SIGMAS
The SIGMAS output represents the truncated sigma schedule generated by the node. This output is crucial for understanding the progression of the sampling process and serves as a guide for subsequent stages. The sigma values provide insight into the noise levels and adjustments made during the initial pass, helping to inform decisions in later stages of the process.
H3 Probe Schedule (early-oracle head) Usage Tips:
- Adjust the
probe_stepsparameter to find the right balance between efficiency and detail for your specific content. A lower value can save time but may miss important details, while a higher value captures more information at the cost of increased computation. - Experiment with different
scheduleroptions to see which one best suits your project's needs. Each scheduler has unique characteristics that can affect the outcome of the sampling process.
H3 Probe Schedule (early-oracle head) Common Errors and Solutions:
"Invalid scheduler option"
- Explanation: This error occurs when an unsupported scheduler option is selected.
- Solution: Ensure that the
schedulerparameter is set to one of the supported options: "simple," "normal," "beta," "sgm_uniform," "karras," or "exponential."
"Probe steps exceed total steps"
- Explanation: This error happens when the
probe_stepsvalue is greater than thetotal_stepsvalue. - Solution: Adjust the
probe_stepsparameter to be less than or equal to thetotal_stepsparameter to ensure a valid configuration.
