From 8d50ecdfc3fd5fa9fefeb01d7328d60639f08d70 Mon Sep 17 00:00:00 2001
From: Ryan Dick <ryanjdick3@gmail.com>
Date: Wed, 25 Sep 2024 13:20:53 +0000
Subject: [PATCH] Update docs explaining inpainting trajectory guidance.

---
 invokeai/backend/flux/trajectory_guidance_extension.py | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/invokeai/backend/flux/trajectory_guidance_extension.py b/invokeai/backend/flux/trajectory_guidance_extension.py
index 4ea8a4b675..9beb0bce17 100644
--- a/invokeai/backend/flux/trajectory_guidance_extension.py
+++ b/invokeai/backend/flux/trajectory_guidance_extension.py
@@ -59,6 +59,9 @@ class TrajectoryGuidanceExtension:
         #
         # We experimented with a number of related guidance strategies, but not exhaustively. It's entirely possible
         # that there's a much better way to do this.
+        #
+        # Update: This decision was made when we were relying more heavily on this guidance strategy. Now that it is
+        # only really applied to the inpaint gradient regions, this decision could be re-visited.
 
         # Calculate noise guidance
         # What noise should the model have predicted at this timestep to step towards self._init_latents?