[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [9.17, 16.91, 22.0, -46.97, -171.47, 0.0]
  Target bbox: [629.43, 340.37, 650.55, 379.4]

Frame 2:
  Drone pose: [7.51, 15.53, 21.2, -47.75, -173.61, 0.0]
  Target bbox: [632.11, 339.01, 647.99, 380.69]

Frame 3:
  Drone pose: [6.5, 14.71, 20.67, -47.91, -176.01, 0.0]
  Target bbox: [629.6, 339.79, 650.38, 379.93]

Frame 4:
  Drone pose: [5.81, 14.23, 20.64, -48.17, -175.91, 0.0]
  Target bbox: [629.41, 339.6, 650.57, 380.11]

Frame 5 (current):
  Drone pose: [5.26, 13.93, 20.62, -48.18, -175.26, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 631.59, "ymin": 339.69, "xmax": 648.52, "ymax": 380.02}, "waypoint_deltas": [{"dx": -0.5, "dy": -0.19, "dz": -0.03, "dpitch": 0.0, "dyaw": -0.61, "droll": 0.0}, {"dx": -1.0, "dy": -0.34, "dz": -0.05, "dpitch": 0.03, "dyaw": -1.08, "droll": 0.0}, {"dx": -1.49, "dy": -0.46, "dz": -0.07, "dpitch": 0.05, "dyaw": -1.47, "droll": 0.0}, {"dx": -1.99, "dy": -0.57, "dz": -0.09, "dpitch": 0.07, "dyaw": -1.81, "droll": 0.0}, {"dx": -2.51, "dy": -0.66, "dz": -0.2, "dpitch": 0.19, "dyaw": -2.09, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [3.27, 13.36, 20.53, -48.11, -177.07, 0.0]
  Target bbox: [632.21, 338.41, 647.91, 381.27]

Frame 2:
  Drone pose: [2.75, 13.27, 20.42, -47.99, -177.35, 0.0]
  Target bbox: [632.39, 338.65, 647.71, 381.01]

Frame 3:
  Drone pose: [2.21, 13.2, 20.39, -48.01, -177.57, 0.0]
  Target bbox: [632.43, 339.36, 647.67, 380.31]

Frame 4:
  Drone pose: [1.66, 13.15, 20.36, -48.05, -177.73, 0.0]
  Target bbox: [631.58, 342.06, 648.5, 377.6]

Frame 5 (current):
  Drone pose: [1.11, 13.11, 20.33, -48.08, -177.84, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 631.96, "ymin": 339.39, "xmax": 648.16, "ymax": 380.31}, "waypoint_deltas": [{"dx": -0.54, "dy": -0.02, "dz": -0.03, "dpitch": -0.03, "dyaw": -0.07, "droll": 0.0}, {"dx": -1.06, "dy": -0.03, "dz": -0.06, "dpitch": -0.03, "dyaw": -0.1, "droll": 0.0}, {"dx": -1.58, "dy": -0.03, "dz": -0.08, "dpitch": -0.01, "dyaw": -0.08, "droll": 0.0}, {"dx": -2.08, "dy": 0.0, "dz": -0.11, "dpitch": 0.03, "dyaw": -0.01, "droll": 0.0}, {"dx": -2.57, "dy": 0.03, "dz": -0.14, "dpitch": 0.08, "dyaw": 0.11, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-1.46, 13.14, 20.19, -48.0, -177.73, 0.0]
  Target bbox: [632.05, 338.54, 648.07, 381.16]

Frame 2:
  Drone pose: [-1.94, 13.2, 20.17, -47.93, -177.55, 0.0]
  Target bbox: [632.02, 338.5, 648.1, 381.19]

Frame 3:
  Drone pose: [-2.41, 13.27, 20.15, -47.85, -177.33, 0.0]
  Target bbox: [631.69, 340.51, 648.41, 379.17]

Frame 4:
  Drone pose: [-2.87, 13.36, 20.14, -47.76, -177.05, 0.0]
  Target bbox: [631.42, 338.29, 648.71, 381.41]

Frame 5 (current):
  Drone pose: [-3.31, 13.46, 20.12, -47.63, -176.73, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 631.83, "ymin": 342.19, "xmax": 648.24, "ymax": 377.47}, "waypoint_deltas": [{"dx": -0.43, "dy": 0.12, "dz": -0.01, "dpitch": 0.14, "dyaw": 0.36, "droll": 0.0}, {"dx": -0.86, "dy": 0.24, "dz": -0.03, "dpitch": 0.28, "dyaw": 0.74, "droll": 0.0}, {"dx": -1.33, "dy": 0.37, "dz": -0.04, "dpitch": 0.36, "dyaw": 1.15, "droll": 0.0}, {"dx": -1.83, "dy": 0.52, "dz": -0.05, "dpitch": 0.4, "dyaw": 1.6, "droll": 0.0}, {"dx": -2.36, "dy": 0.66, "dz": -0.06, "dpitch": 0.39, "dyaw": 2.08, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-5.14, 13.98, 20.07, -47.23, -175.13, 0.0]
  Target bbox: [631.73, 340.82, 648.36, 378.86]

Frame 2:
  Drone pose: [-5.67, 14.12, 20.06, -47.24, -174.65, 0.0]
  Target bbox: [631.62, 340.56, 648.46, 379.11]

Frame 3:
  Drone pose: [-6.23, 14.27, 20.05, -47.3, -174.17, 0.0]
  Target bbox: [631.59, 337.85, 648.54, 381.84]

Frame 4:
  Drone pose: [-6.81, 14.39, 20.04, -47.4, -173.77, 0.0]
  Target bbox: [630.84, 337.86, 649.29, 381.85]

Frame 5 (current):
  Drone pose: [-7.43, 14.45, 20.04, -47.56, -173.51, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 630.84, "ymin": 338.34, "xmax": 649.29, "ymax": 381.36}, "waypoint_deltas": [{"dx": -0.64, "dy": 0.01, "dz": -0.01, "dpitch": -0.22, "dyaw": 0.08, "droll": 0.0}, {"dx": -1.3, "dy": -0.04, "dz": -0.01, "dpitch": -0.38, "dyaw": 1.58, "droll": 0.0}, {"dx": -1.98, "dy": -0.15, "dz": -0.02, "dpitch": -0.57, "dyaw": 2.93, "droll": 0.0}, {"dx": -2.67, "dy": -0.31, "dz": -0.02, "dpitch": -0.77, "dyaw": 4.15, "droll": 0.0}, {"dx": -3.36, "dy": -0.5, "dz": -0.02, "dpitch": -0.97, "dyaw": 5.3, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-10.79, 13.95, 20.02, -48.53, -168.21, 0.0]
  Target bbox: [627.15, 336.81, 652.8, 382.85]

Frame 2:
  Drone pose: [-11.47, 13.76, 20.01, -48.71, -167.1, 0.0]
  Target bbox: [626.8, 336.75, 653.14, 382.94]

Frame 3:
  Drone pose: [-12.14, 13.55, 20.01, -48.86, -166.01, 0.0]
  Target bbox: [628.21, 338.23, 651.75, 381.43]

Frame 4:
  Drone pose: [-12.8, 13.33, 20.01, -49.0, -164.94, 0.0]
  Target bbox: [626.94, 336.79, 653.0, 382.87]

Frame 5 (current):
  Drone pose: [-13.45, 13.11, 20.01, -49.12, -163.88, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 628.76, "ymin": 339.03, "xmax": 651.2, "ymax": 380.65}, "waypoint_deltas": [{"dx": -0.65, "dy": -0.22, "dz": 0.0, "dpitch": 0.11, "dyaw": 1.04, "droll": 0.0}, {"dx": -1.29, "dy": -0.46, "dz": -0.01, "dpitch": 0.03, "dyaw": 2.06, "droll": 0.0}, {"dx": -1.92, "dy": -0.7, "dz": -0.01, "dpitch": -0.05, "dyaw": 3.05, "droll": 0.0}, {"dx": -2.55, "dy": -0.94, "dz": -0.01, "dpitch": -0.11, "dyaw": 4.02, "droll": 0.0}, {"dx": -3.18, "dy": -1.2, "dz": -0.01, "dpitch": -0.16, "dyaw": 4.96, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-16.0, 12.17, 20.0, -49.23, -159.86, 0.0]
  Target bbox: [627.32, 336.85, 652.61, 382.77]

Frame 2:
  Drone pose: [-16.63, 11.91, 20.0, -49.28, -158.92, 0.0]
  Target bbox: [628.53, 337.85, 651.39, 381.81]

Frame 3:
  Drone pose: [-17.25, 11.65, 20.0, -49.32, -158.01, 0.0]
  Target bbox: [627.19, 337.04, 652.73, 382.6]

Frame 4:
  Drone pose: [-17.85, 11.37, 20.0, -49.34, -157.17, 0.0]
  Target bbox: [627.71, 337.2, 652.21, 382.42]

Frame 5 (current):
  Drone pose: [-18.44, 11.06, 20.0, -49.35, -156.42, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 628.14, "ymin": 337.86, "xmax": 651.79, "ymax": 381.77}, "waypoint_deltas": [{"dx": -0.59, "dy": -0.31, "dz": 0.0, "dpitch": -0.01, "dyaw": 0.69, "droll": 0.0}, {"dx": -1.17, "dy": -0.64, "dz": 0.0, "dpitch": -0.02, "dyaw": 1.35, "droll": 0.0}, {"dx": -1.76, "dy": -0.97, "dz": 0.0, "dpitch": -0.03, "dyaw": 2.01, "droll": 0.0}, {"dx": -2.35, "dy": -1.3, "dz": 0.0, "dpitch": -0.03, "dyaw": 2.7, "droll": 0.0}, {"dx": -2.94, "dy": -1.61, "dz": 0.0, "dpitch": -0.03, "dyaw": 3.44, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-21.38, 9.45, 20.0, -49.38, -152.98, 0.0]
  Target bbox: [627.72, 337.29, 652.18, 382.33]

Frame 2:
  Drone pose: [-21.98, 9.16, 20.0, -49.36, -152.2, 0.0]
  Target bbox: [628.99, 338.46, 650.93, 381.18]

Frame 3:
  Drone pose: [-22.57, 8.88, 20.0, -49.33, -151.38, 0.0]
  Target bbox: [628.47, 337.06, 651.62, 382.59]

Frame 4:
  Drone pose: [-23.16, 8.6, 20.0, -49.9, -152.08, 0.0]
  Target bbox: [629.58, 339.91, 650.35, 379.72]

Frame 5 (current):
  Drone pose: [-23.76, 8.32, 20.0, -49.88, -151.24, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 629.14, "ymin": 339.23, "xmax": 650.78, "ymax": 380.38}, "waypoint_deltas": [{"dx": -0.59, "dy": -0.29, "dz": 0.0, "dpitch": 0.04, "dyaw": 0.81, "droll": 0.0}, {"dx": -1.17, "dy": -0.59, "dz": 0.0, "dpitch": 0.09, "dyaw": 1.56, "droll": 0.0}, {"dx": -1.75, "dy": -0.9, "dz": 0.0, "dpitch": 0.15, "dyaw": 2.26, "droll": 0.0}, {"dx": -2.32, "dy": -1.22, "dz": 0.0, "dpitch": 0.2, "dyaw": 2.9, "droll": 0.0}, {"dx": -2.88, "dy": -1.56, "dz": 0.0, "dpitch": 0.25, "dyaw": 3.48, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-26.08, 7.1, 20.0, -49.68, -148.34, 0.0]
  Target bbox: [629.86, 339.78, 650.07, 379.83]

Frame 2:
  Drone pose: [-26.64, 6.76, 20.0, -49.63, -147.76, 0.0]
  Target bbox: [628.31, 338.42, 651.58, 381.23]

Frame 3:
  Drone pose: [-27.19, 6.39, 20.0, -49.58, -147.27, 0.0]
  Target bbox: [629.81, 340.15, 650.11, 379.46]

Frame 4:
  Drone pose: [-27.74, 6.0, 20.0, -49.55, -146.86, 0.0]
  Target bbox: [629.95, 339.76, 649.96, 379.89]

Frame 5 (current):
  Drone pose: [-28.28, 5.59, 20.0, -49.52, -146.51, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 628.44, "ymin": 338.35, "xmax": 651.44, "ymax": 381.3}, "waypoint_deltas": [{"dx": -0.53, "dy": -0.42, "dz": 0.0, "dpitch": 0.02, "dyaw": 0.28, "droll": 0.0}, {"dx": -1.06, "dy": -0.86, "dz": 0.0, "dpitch": 0.05, "dyaw": 0.5, "droll": 0.0}, {"dx": -1.57, "dy": -1.31, "dz": 0.0, "dpitch": 0.07, "dyaw": 0.67, "droll": 0.0}, {"dx": -2.08, "dy": -1.78, "dz": 0.0, "dpitch": 0.1, "dyaw": 0.79, "droll": 0.0}, {"dx": -2.58, "dy": -2.25, "dz": 0.0, "dpitch": 0.13, "dyaw": 0.86, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-30.86, 3.34, 20.0, -49.39, -145.65, 0.0]
  Target bbox: [629.48, 338.54, 650.41, 381.11]

Frame 2:
  Drone pose: [-31.35, 2.86, 20.0, -49.37, -145.63, 0.0]
  Target bbox: [629.29, 338.98, 650.61, 380.63]

Frame 3:
  Drone pose: [-31.83, 2.36, 20.0, -49.33, -145.63, 0.0]
  Target bbox: [629.16, 338.63, 650.74, 380.99]

Frame 4:
  Drone pose: [-32.31, 1.87, 20.0, -49.3, -145.66, 0.0]
  Target bbox: [631.24, 340.15, 648.68, 379.49]

Frame 5 (current):
  Drone pose: [-32.78, 1.39, 20.0, -49.24, -145.67, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 629.72, "ymin": 340.28, "xmax": 650.2, "ymax": 379.36}, "waypoint_deltas": [{"dx": -0.47, "dy": -0.47, "dz": 0.0, "dpitch": 0.07, "dyaw": 0.02, "droll": 0.0}, {"dx": -0.93, "dy": -0.92, "dz": 0.0, "dpitch": 0.18, "dyaw": 0.09, "droll": 0.0}, {"dx": -1.38, "dy": -1.34, "dz": 0.0, "dpitch": 0.33, "dyaw": 0.21, "droll": 0.0}, {"dx": -1.82, "dy": -1.73, "dz": 0.0, "dpitch": 0.04, "dyaw": -1.0, "droll": 0.0}, {"dx": -2.26, "dy": -2.1, "dz": 0.0, "dpitch": 0.25, "dyaw": -0.74, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-34.6, -0.34, 20.0, -49.2, -146.67, 0.0]
  Target bbox: [630.56, 339.63, 649.35, 380.01]

Frame 2:
  Drone pose: [-35.04, -0.71, 20.0, -48.99, -146.41, 0.0]
  Target bbox: [628.51, 337.81, 651.55, 381.85]

Frame 3:
  Drone pose: [-35.47, -1.06, 20.0, -49.22, -147.52, 0.0]
  Target bbox: [628.49, 338.0, 651.4, 381.61]

Frame 4:
  Drone pose: [-35.91, -1.39, 20.0, -48.98, -147.15, 0.0]
  Target bbox: [627.67, 337.48, 652.4, 382.23]

Frame 5 (current):
  Drone pose: [-36.34, -1.7, 20.0, -49.16, -148.17, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 630.97, "ymin": 340.01, "xmax": 648.95, "ymax": 379.63}, "waypoint_deltas": [{"dx": -0.43, "dy": -0.31, "dz": 0.0, "dpitch": 0.27, "dyaw": 0.44, "droll": 0.0}, {"dx": -0.86, "dy": -0.61, "dz": 0.0, "dpitch": 0.11, "dyaw": -0.55, "droll": 0.0}, {"dx": -1.3, "dy": -0.9, "dz": 0.0, "dpitch": -0.06, "dyaw": -1.54, "droll": 0.0}, {"dx": -1.73, "dy": -1.21, "dz": 0.0, "dpitch": 0.21, "dyaw": -1.07, "droll": 0.0}, {"dx": -2.17, "dy": -1.51, "dz": 0.0, "dpitch": 0.04, "dyaw": -2.09, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [9.12, 16.72, 21.97, -47.24, -166.98, 0.0]
  Target bbox: [571.9, 339.6, 593.56, 377.37]

Frame 2:
  Drone pose: [7.51, 15.53, 21.2, -48.33, -169.54, 0.0]
  Target bbox: [585.16, 333.51, 602.73, 369.28]

Frame 3:
  Drone pose: [6.5, 14.71, 20.67, -47.91, -176.01, 0.0]
  Target bbox: [627.2, 337.88, 652.79, 381.87]

Frame 4:
  Drone pose: [5.81, 14.23, 20.64, -48.17, -175.91, 0.0]
  Target bbox: [627.22, 337.38, 652.77, 382.32]

Frame 5 (current):
  Drone pose: [5.26, 13.93, 20.62, -43.55, -173.89, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 616.02, "ymin": 416.6, "xmax": 633.17, "ymax": 459.09}, "waypoint_deltas": [{"dx": -0.5, "dy": -0.19, "dz": -0.03, "dpitch": -4.63, "dyaw": -1.98, "droll": 0.0}, {"dx": -1.0, "dy": -0.34, "dz": -0.05, "dpitch": -4.6, "dyaw": -2.45, "droll": 0.0}, {"dx": -1.49, "dy": -0.46, "dz": -0.07, "dpitch": -4.58, "dyaw": -2.84, "droll": 0.0}, {"dx": -1.99, "dy": -0.57, "dz": -0.09, "dpitch": -4.56, "dyaw": -3.18, "droll": 0.0}, {"dx": -2.51, "dy": -0.66, "dz": -0.2, "dpitch": -4.44, "dyaw": -3.46, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [3.36, 13.25, 20.52, -49.56, -172.42, 0.0]
  Target bbox: [574.81, 312.99, 592.75, 356.69]

Frame 2:
  Drone pose: [2.79, 13.24, 20.24, -52.68, -180.04, 0.0]
  Target bbox: [661.07, 255.16, 677.82, 297.47]

Frame 3:
  Drone pose: [2.02, 13.2, 20.4, -48.33, -177.56, 0.0]
  Target bbox: [631.56, 342.28, 648.51, 377.36]

Frame 4:
  Drone pose: [1.66, 13.15, 20.36, -48.05, -177.73, 0.0]
  Target bbox: [632.0, 340.36, 648.1, 379.33]

Frame 5 (current):
  Drone pose: [1.14, 13.0, 20.32, -49.49, -179.54, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 647.16, "ymin": 315.21, "xmax": 663.42, "ymax": 355.86}, "waypoint_deltas": [{"dx": -0.57, "dy": 0.09, "dz": -0.02, "dpitch": 1.38, "dyaw": 1.63, "droll": 0.0}, {"dx": -1.09, "dy": 0.08, "dz": -0.05, "dpitch": 1.38, "dyaw": 1.6, "droll": 0.0}, {"dx": -1.61, "dy": 0.08, "dz": -0.07, "dpitch": 1.4, "dyaw": 1.62, "droll": 0.0}, {"dx": -2.11, "dy": 0.11, "dz": -0.1, "dpitch": 1.44, "dyaw": 1.69, "droll": 0.0}, {"dx": -2.6, "dy": 0.14, "dz": -0.13, "dpitch": 1.49, "dyaw": 1.81, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-1.46, 13.14, 20.19, -48.0, -177.73, 0.0]
  Target bbox: [631.78, 339.85, 648.33, 379.82]

Frame 2:
  Drone pose: [-1.89, 13.18, 20.08, -49.96, -175.2, 0.0]
  Target bbox: [604.2, 304.86, 621.39, 341.03]

Frame 3:
  Drone pose: [-2.41, 13.27, 20.15, -46.78, -176.91, 0.0]
  Target bbox: [627.28, 356.0, 643.26, 399.52]

Frame 4:
  Drone pose: [-2.91, 13.35, 20.23, -43.8, -177.83, 0.0]
  Target bbox: [640.17, 408.27, 657.21, 451.62]

Frame 5 (current):
  Drone pose: [-3.19, 13.47, 19.99, -45.43, -172.52, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 582.48, "ymin": 369.72, "xmax": 601.49, "ymax": 413.6}, "waypoint_deltas": [{"dx": -0.55, "dy": 0.11, "dz": 0.12, "dpitch": -2.06, "dyaw": -3.85, "droll": 0.0}, {"dx": -0.98, "dy": 0.23, "dz": 0.1, "dpitch": -1.92, "dyaw": -3.47, "droll": 0.0}, {"dx": -1.45, "dy": 0.36, "dz": 0.09, "dpitch": -1.84, "dyaw": -3.06, "droll": 0.0}, {"dx": -1.95, "dy": 0.51, "dz": 0.08, "dpitch": -1.8, "dyaw": -2.61, "droll": 0.0}, {"dx": -2.48, "dy": 0.65, "dz": 0.07, "dpitch": -1.81, "dyaw": -2.13, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-5.14, 13.98, 20.07, -45.51, -180.13, 0.0]
  Target bbox: [688.19, 369.55, 706.1, 411.6]

Frame 2:
  Drone pose: [-5.67, 14.12, 20.06, -50.64, -179.65, 0.0]
  Target bbox: [688.16, 284.29, 706.23, 324.78]

Frame 3:
  Drone pose: [-6.27, 14.36, 20.15, -47.5, -173.88, 0.0]
  Target bbox: [631.33, 342.01, 648.73, 377.64]

Frame 4:
  Drone pose: [-6.81, 14.39, 20.04, -47.4, -173.77, 0.0]
  Target bbox: [631.1, 338.7, 649.02, 381.02]

Frame 5 (current):
  Drone pose: [-7.59, 14.42, 20.01, -47.8, -173.58, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 631.45, "ymin": 340.84, "xmax": 648.63, "ymax": 378.84}, "waypoint_deltas": [{"dx": -0.48, "dy": 0.04, "dz": 0.02, "dpitch": 0.02, "dyaw": 0.15, "droll": 0.0}, {"dx": -1.14, "dy": -0.01, "dz": 0.02, "dpitch": -0.14, "dyaw": 1.65, "droll": 0.0}, {"dx": -1.82, "dy": -0.12, "dz": 0.01, "dpitch": -0.33, "dyaw": 3.0, "droll": 0.0}, {"dx": -2.51, "dy": -0.28, "dz": 0.01, "dpitch": -0.53, "dyaw": 4.22, "droll": 0.0}, {"dx": -3.2, "dy": -0.47, "dz": 0.01, "dpitch": -0.73, "dyaw": 5.37, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-10.79, 13.95, 20.02, -53.53, -171.66, 0.0]
  Target bbox: [665.26, 253.48, 691.89, 299.84]

Frame 2:
  Drone pose: [-11.47, 13.76, 20.01, -47.1, -162.1, 0.0]
  Target bbox: [573.43, 368.11, 595.53, 409.22]

Frame 3:
  Drone pose: [-12.05, 13.54, 20.17, -51.23, -171.1, 0.0]
  Target bbox: [683.08, 302.63, 707.41, 344.61]

Frame 4:
  Drone pose: [-12.91, 13.18, 19.99, -50.43, -160.33, 0.0]
  Target bbox: [572.14, 319.46, 597.89, 363.51]

Frame 5 (current):
  Drone pose: [-13.36, 12.95, 19.98, -49.0, -164.5, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 628.83, "ymin": 338.76, "xmax": 651.14, "ymax": 380.89}, "waypoint_deltas": [{"dx": -0.74, "dy": -0.06, "dz": 0.03, "dpitch": -0.01, "dyaw": 1.66, "droll": 0.0}, {"dx": -1.38, "dy": -0.3, "dz": 0.02, "dpitch": -0.09, "dyaw": 2.68, "droll": 0.0}, {"dx": -2.01, "dy": -0.54, "dz": 0.02, "dpitch": -0.17, "dyaw": 3.67, "droll": 0.0}, {"dx": -2.64, "dy": -0.78, "dz": 0.02, "dpitch": -0.23, "dyaw": 4.64, "droll": 0.0}, {"dx": -3.27, "dy": -1.04, "dz": 0.02, "dpitch": -0.28, "dyaw": 5.58, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-16.0, 12.17, 20.0, -53.69, -162.07, 0.0]
  Target bbox: [653.83, 264.23, 674.88, 306.07]

Frame 2:
  Drone pose: [-16.62, 12.04, 20.1, -49.34, -158.52, 0.0]
  Target bbox: [627.23, 337.44, 652.69, 382.22]

Frame 3:
  Drone pose: [-17.25, 11.65, 20.0, -54.32, -163.01, 0.0]
  Target bbox: [683.53, 256.12, 706.45, 299.11]

Frame 4:
  Drone pose: [-17.75, 11.3, 19.91, -47.78, -153.0, 0.0]
  Target bbox: [577.72, 361.48, 602.96, 405.27]

Frame 5 (current):
  Drone pose: [-18.44, 11.06, 20.0, -49.35, -156.42, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 629.13, "ymin": 339.04, "xmax": 650.81, "ymax": 380.59}, "waypoint_deltas": [{"dx": -0.59, "dy": -0.31, "dz": 0.0, "dpitch": -0.01, "dyaw": 0.69, "droll": 0.0}, {"dx": -1.17, "dy": -0.64, "dz": 0.0, "dpitch": -0.02, "dyaw": 1.35, "droll": 0.0}, {"dx": -1.76, "dy": -0.97, "dz": 0.0, "dpitch": -0.03, "dyaw": 2.01, "droll": 0.0}, {"dx": -2.35, "dy": -1.3, "dz": 0.0, "dpitch": -0.03, "dyaw": 2.7, "droll": 0.0}, {"dx": -2.94, "dy": -1.61, "dz": 0.0, "dpitch": -0.03, "dyaw": 3.44, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-21.29, 9.48, 20.14, -48.3, -148.04, 0.0]
  Target bbox: [573.37, 359.44, 597.13, 401.77]

Frame 2:
  Drone pose: [-21.97, 9.17, 19.9, -49.85, -147.26, 0.0]
  Target bbox: [573.22, 328.32, 598.76, 372.91]

Frame 3:
  Drone pose: [-22.61, 8.84, 20.08, -50.35, -153.24, 0.0]
  Target bbox: [647.05, 322.67, 672.85, 370.51]

Frame 4:
  Drone pose: [-23.12, 8.5, 19.83, -49.64, -156.11, 0.0]
  Target bbox: [666.91, 338.33, 693.05, 384.47]

Frame 5 (current):
  Drone pose: [-23.77, 8.43, 20.01, -49.82, -150.88, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 630.65, "ymin": 339.47, "xmax": 649.27, "ymax": 380.16}, "waypoint_deltas": [{"dx": -0.58, "dy": -0.4, "dz": -0.01, "dpitch": -0.02, "dyaw": 0.45, "droll": 0.0}, {"dx": -1.16, "dy": -0.7, "dz": -0.01, "dpitch": 0.03, "dyaw": 1.2, "droll": 0.0}, {"dx": -1.74, "dy": -1.01, "dz": -0.01, "dpitch": 0.09, "dyaw": 1.9, "droll": 0.0}, {"dx": -2.31, "dy": -1.33, "dz": -0.01, "dpitch": 0.14, "dyaw": 2.54, "droll": 0.0}, {"dx": -2.87, "dy": -1.67, "dz": -0.01, "dpitch": 0.19, "dyaw": 3.12, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-26.08, 7.1, 20.0, -49.68, -148.34, 0.0]
  Target bbox: [628.22, 338.27, 651.67, 381.37]

Frame 2:
  Drone pose: [-26.64, 6.76, 20.0, -46.62, -149.86, 0.0]
  Target bbox: [652.27, 390.31, 673.53, 430.73]

Frame 3:
  Drone pose: [-27.13, 6.54, 19.95, -49.28, -146.93, 0.0]
  Target bbox: [629.89, 339.67, 650.02, 379.98]

Frame 4:
  Drone pose: [-27.69, 5.91, 20.05, -54.44, -142.66, 0.0]
  Target bbox: [578.87, 259.76, 601.27, 301.12]

Frame 5 (current):
  Drone pose: [-28.34, 5.58, 19.91, -51.61, -151.43, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 683.6, "ymin": 305.02, "xmax": 705.61, "ymax": 347.07}, "waypoint_deltas": [{"dx": -0.47, "dy": -0.41, "dz": 0.09, "dpitch": 2.11, "dyaw": 5.2, "droll": 0.0}, {"dx": -1.0, "dy": -0.85, "dz": 0.09, "dpitch": 2.14, "dyaw": 5.42, "droll": 0.0}, {"dx": -1.51, "dy": -1.3, "dz": 0.09, "dpitch": 2.16, "dyaw": 5.59, "droll": 0.0}, {"dx": -2.02, "dy": -1.77, "dz": 0.09, "dpitch": 2.19, "dyaw": 5.71, "droll": 0.0}, {"dx": -2.52, "dy": -2.24, "dz": 0.09, "dpitch": 2.22, "dyaw": 5.78, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-30.86, 3.34, 20.0, -51.57, -146.99, 0.0]
  Target bbox: [644.31, 302.13, 665.11, 344.76]

Frame 2:
  Drone pose: [-31.23, 2.72, 19.99, -50.73, -141.61, 0.0]
  Target bbox: [578.04, 316.4, 600.6, 358.86]

Frame 3:
  Drone pose: [-31.71, 2.31, 19.94, -44.84, -151.03, 0.0]
  Target bbox: [684.19, 413.86, 706.05, 453.63]

Frame 4:
  Drone pose: [-32.31, 1.87, 20.0, -48.84, -143.19, 0.0]
  Target bbox: [601.52, 346.3, 624.03, 389.51]

Frame 5 (current):
  Drone pose: [-32.78, 1.39, 20.0, -47.77, -142.92, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 598.87, "ymin": 364.45, "xmax": 620.43, "ymax": 405.75}, "waypoint_deltas": [{"dx": -0.47, "dy": -0.47, "dz": 0.0, "dpitch": -1.4, "dyaw": -2.73, "droll": 0.0}, {"dx": -0.93, "dy": -0.92, "dz": 0.0, "dpitch": -1.29, "dyaw": -2.66, "droll": 0.0}, {"dx": -1.38, "dy": -1.34, "dz": 0.0, "dpitch": -1.14, "dyaw": -2.54, "droll": 0.0}, {"dx": -1.82, "dy": -1.73, "dz": 0.0, "dpitch": -1.43, "dyaw": -3.75, "droll": 0.0}, {"dx": -2.26, "dy": -2.1, "dz": 0.0, "dpitch": -1.22, "dyaw": -3.49, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-34.59, -0.25, 20.12, -49.28, -146.4, 0.0]
  Target bbox: [629.85, 340.47, 650.08, 379.17]

Frame 2:
  Drone pose: [-35.08, -0.54, 20.08, -53.5, -144.38, 0.0]
  Target bbox: [612.04, 262.77, 635.17, 306.5]

Frame 3:
  Drone pose: [-35.45, -1.08, 20.01, -49.23, -147.63, 0.0]
  Target bbox: [629.47, 340.02, 650.45, 379.62]

Frame 4:
  Drone pose: [-35.91, -1.39, 20.0, -47.94, -145.1, 0.0]
  Target bbox: [604.41, 353.92, 630.17, 401.04]

Frame 5 (current):
  Drone pose: [-36.49, -1.65, 19.94, -48.88, -150.63, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 660.15, "ymin": 345.8, "xmax": 682.95, "ymax": 386.97}, "waypoint_deltas": [{"dx": -0.28, "dy": -0.36, "dz": 0.06, "dpitch": -0.01, "dyaw": 2.9, "droll": 0.0}, {"dx": -0.71, "dy": -0.66, "dz": 0.06, "dpitch": -0.17, "dyaw": 1.91, "droll": 0.0}, {"dx": -1.15, "dy": -0.95, "dz": 0.06, "dpitch": -0.34, "dyaw": 0.92, "droll": 0.0}, {"dx": -1.58, "dy": -1.26, "dz": 0.06, "dpitch": -0.07, "dyaw": 1.39, "droll": 0.0}, {"dx": -2.02, "dy": -1.56, "dz": 0.06, "dpitch": -0.24, "dyaw": 0.37, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-97.17, -80.0, 22.0, -54.26, 25.42, 0.0]
  Target bbox: [626.07, 326.65, 653.79, 391.96]

Frame 2:
  Drone pose: [-96.99, -79.93, 21.96, -53.35, 26.35, 0.0]
  Target bbox: [622.0, 326.35, 657.87, 392.34]

Frame 3:
  Drone pose: [-96.81, -79.86, 21.98, -52.53, 27.22, 0.0]
  Target bbox: [620.28, 323.35, 659.46, 395.5]

Frame 4:
  Drone pose: [-96.64, -79.8, 22.01, -51.74, 28.04, 0.0]
  Target bbox: [620.97, 324.56, 658.79, 394.35]

Frame 5 (current):
  Drone pose: [-96.46, -79.73, 22.05, -51.16, 28.82, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 621.68, "ymin": 323.97, "xmax": 658.05, "ymax": 395.0}, "waypoint_deltas": [{"dx": 0.17, "dy": 0.07, "dz": 0.05, "dpitch": 0.74, "dyaw": 0.73, "droll": 0.0}, {"dx": 0.35, "dy": 0.14, "dz": 0.1, "dpitch": 1.46, "dyaw": 1.42, "droll": 0.0}, {"dx": 0.52, "dy": 0.21, "dz": 0.15, "dpitch": 2.16, "dyaw": 2.07, "droll": 0.0}, {"dx": 0.7, "dy": 0.27, "dz": 0.21, "dpitch": 2.85, "dyaw": 2.69, "droll": 0.0}, {"dx": 0.88, "dy": 0.34, "dz": 0.27, "dpitch": 3.51, "dyaw": 3.27, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-95.76, -79.46, 22.26, -48.31, 31.51, 0.0]
  Target bbox: [625.88, 328.5, 653.95, 390.6]

Frame 2:
  Drone pose: [-95.58, -79.39, 22.32, -47.65, 32.09, 0.0]
  Target bbox: [624.03, 328.34, 655.79, 390.79]

Frame 3:
  Drone pose: [-95.41, -79.32, 22.41, -47.03, 32.65, 0.0]
  Target bbox: [623.82, 327.02, 656.23, 392.14]

Frame 4:
  Drone pose: [-95.23, -79.25, 22.49, -46.81, 31.99, 0.0]
  Target bbox: [625.81, 329.82, 654.2, 389.36]

Frame 5 (current):
  Drone pose: [-95.06, -79.19, 22.65, -46.68, 31.35, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 622.23, "ymin": 325.41, "xmax": 657.96, "ymax": 393.97}, "waypoint_deltas": [{"dx": 0.18, "dy": 0.07, "dz": 0.16, "dpitch": 0.13, "dyaw": -0.63, "droll": 0.0}, {"dx": 0.5, "dy": 0.06, "dz": 0.34, "dpitch": 0.12, "dyaw": -0.86, "droll": 0.0}, {"dx": 0.84, "dy": 0.05, "dz": 0.5, "dpitch": 0.11, "dyaw": -1.05, "droll": 0.0}, {"dx": 1.44, "dy": 0.09, "dz": 0.57, "dpitch": -0.12, "dyaw": -1.0, "droll": 0.0}, {"dx": 1.97, "dy": 0.15, "dz": 0.62, "dpitch": -0.28, "dyaw": -1.1, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-93.09, -79.04, 23.27, -46.96, 30.25, 0.0]
  Target bbox: [626.1, 330.84, 653.92, 388.39]

Frame 2:
  Drone pose: [-92.49, -78.97, 23.32, -47.19, 30.22, 0.0]
  Target bbox: [623.48, 326.56, 656.69, 392.77]

Frame 3:
  Drone pose: [-91.73, -77.47, 23.36, -48.57, 26.84, 0.0]
  Target bbox: [625.45, 328.96, 654.66, 390.25]

Frame 4:
  Drone pose: [-91.08, -74.65, 24.16, -51.4, 19.24, 0.0]
  Target bbox: [626.56, 330.05, 653.57, 389.05]

Frame 5 (current):
  Drone pose: [-90.77, -70.82, 24.57, -52.95, 7.32, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 627.67, "ymin": 334.33, "xmax": 652.42, "ymax": 384.68}, "waypoint_deltas": [{"dx": 0.23, "dy": 4.07, "dz": 0.44, "dpitch": -0.18, "dyaw": -13.08, "droll": 0.0}, {"dx": 0.66, "dy": 7.61, "dz": 0.1, "dpitch": 1.36, "dyaw": -23.85, "droll": 0.0}, {"dx": 1.43, "dy": 9.43, "dz": -0.7, "dpitch": 2.83, "dyaw": -29.31, "droll": 0.0}, {"dx": 1.13, "dy": 9.73, "dz": -1.38, "dpitch": 4.93, "dyaw": -29.26, "droll": 0.0}, {"dx": 1.03, "dy": 9.67, "dz": -1.47, "dpitch": 5.8, "dyaw": -28.47, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-89.64, -61.09, 23.19, -48.02, -21.94, 0.0]
  Target bbox: [625.23, 327.89, 654.61, 391.28]

Frame 2:
  Drone pose: [-89.74, -61.15, 23.1, -47.15, -21.15, 0.0]
  Target bbox: [627.17, 331.61, 652.78, 387.53]

Frame 3:
  Drone pose: [-89.38, -61.08, 23.0, -46.8, -21.21, 0.0]
  Target bbox: [627.49, 331.3, 652.45, 387.84]

Frame 4:
  Drone pose: [-89.05, -61.02, 22.88, -46.4, -21.18, 0.0]
  Target bbox: [624.18, 326.74, 656.01, 392.56]

Frame 5 (current):
  Drone pose: [-88.6, -60.75, 22.69, -46.19, -20.55, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 624.52, "ymin": 328.52, "xmax": 655.6, "ymax": 390.77}, "waypoint_deltas": [{"dx": 0.45, "dy": 0.34, "dz": -0.21, "dpitch": 0.26, "dyaw": 0.46, "droll": 0.0}, {"dx": 0.9, "dy": 0.73, "dz": -0.45, "dpitch": 0.59, "dyaw": 0.8, "droll": 0.0}, {"dx": 1.35, "dy": 1.15, "dz": -0.67, "dpitch": 0.92, "dyaw": 1.05, "droll": 0.0}, {"dx": 1.81, "dy": 1.59, "dz": -0.82, "dpitch": 1.14, "dyaw": 1.23, "droll": 0.0}, {"dx": 2.29, "dy": 2.06, "dz": -0.96, "dpitch": 1.36, "dyaw": 1.35, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-86.31, -58.69, 21.73, -44.83, -19.2, 0.0]
  Target bbox: [622.8, 325.91, 657.37, 393.43]

Frame 2:
  Drone pose: [-85.8, -58.49, 21.58, -44.78, -18.45, 0.0]
  Target bbox: [626.24, 327.31, 653.9, 391.93]

Frame 3:
  Drone pose: [-85.26, -58.49, 21.44, -44.85, -17.16, 0.0]
  Target bbox: [621.64, 325.8, 658.49, 393.56]

Frame 4:
  Drone pose: [-84.71, -58.5, 21.3, -44.92, -15.81, 0.0]
  Target bbox: [625.85, 327.78, 654.2, 391.34]

Frame 5 (current):
  Drone pose: [-84.16, -58.65, 21.17, -45.05, -14.09, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 621.12, "ymin": 324.37, "xmax": 659.02, "ymax": 394.97}, "waypoint_deltas": [{"dx": 0.56, "dy": -0.15, "dz": -0.12, "dpitch": -0.12, "dyaw": 1.76, "droll": 0.0}, {"dx": 1.12, "dy": -0.29, "dz": -0.23, "dpitch": -0.23, "dyaw": 3.56, "droll": 0.0}, {"dx": 1.68, "dy": -0.44, "dz": -0.32, "dpitch": -0.33, "dyaw": 5.38, "droll": 0.0}, {"dx": 2.24, "dy": -0.59, "dz": -0.42, "dpitch": -0.41, "dyaw": 7.24, "droll": 0.0}, {"dx": 2.79, "dy": -0.73, "dz": -0.5, "dpitch": -0.47, "dyaw": 9.13, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-81.37, -59.38, 20.67, -45.52, -4.96, 0.0]
  Target bbox: [619.8, 323.13, 660.22, 396.17]

Frame 2:
  Drone pose: [-80.81, -59.53, 20.59, -45.56, -3.06, 0.0]
  Target bbox: [624.36, 325.83, 655.69, 393.3]

Frame 3:
  Drone pose: [-80.25, -59.68, 20.52, -45.58, -1.14, 0.0]
  Target bbox: [624.39, 325.8, 655.66, 393.32]

Frame 4:
  Drone pose: [-79.69, -59.82, 20.46, -45.57, 0.8, 0.0]
  Target bbox: [625.01, 325.55, 654.96, 393.48]

Frame 5 (current):
  Drone pose: [-79.13, -59.97, 20.4, -45.54, 2.75, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 624.79, "ymin": 325.88, "xmax": 655.21, "ymax": 393.2}, "waypoint_deltas": [{"dx": 0.55, "dy": -0.15, "dz": -0.05, "dpitch": 0.05, "dyaw": 1.95, "droll": 0.0}, {"dx": 1.11, "dy": -0.29, "dz": -0.1, "dpitch": 0.13, "dyaw": 3.91, "droll": 0.0}, {"dx": 1.67, "dy": -0.44, "dz": -0.14, "dpitch": 0.23, "dyaw": 5.86, "droll": 0.0}, {"dx": 2.23, "dy": -0.59, "dz": -0.18, "dpitch": 0.36, "dyaw": 7.8, "droll": 0.0}, {"dx": 2.79, "dy": -0.73, "dz": -0.21, "dpitch": 0.52, "dyaw": 9.73, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-76.9, -60.56, 20.22, -45.18, 10.55, 0.0]
  Target bbox: [619.49, 322.44, 660.4, 396.85]

Frame 2:
  Drone pose: [-76.34, -60.7, 20.19, -45.02, 12.48, 0.0]
  Target bbox: [623.76, 325.81, 656.19, 393.33]

Frame 3:
  Drone pose: [-75.79, -60.85, 20.16, -44.84, 14.4, 0.0]
  Target bbox: [619.46, 321.69, 660.35, 397.6]

Frame 4:
  Drone pose: [-75.23, -61.0, 20.14, -44.63, 16.29, 0.0]
  Target bbox: [622.21, 324.87, 657.7, 394.32]

Frame 5 (current):
  Drone pose: [-74.67, -61.14, 20.12, -44.4, 18.16, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 624.2, "ymin": 326.26, "xmax": 655.73, "ymax": 392.86}, "waypoint_deltas": [{"dx": 0.56, "dy": -0.15, "dz": -0.02, "dpitch": 0.25, "dyaw": 1.84, "droll": 0.0}, {"dx": 1.12, "dy": -0.3, "dz": -0.04, "dpitch": 0.53, "dyaw": 3.65, "droll": 0.0}, {"dx": 1.67, "dy": -0.44, "dz": -0.05, "dpitch": 0.84, "dyaw": 5.43, "droll": 0.0}, {"dx": 2.23, "dy": -0.59, "dz": -0.06, "dpitch": 1.16, "dyaw": 7.17, "droll": 0.0}, {"dx": 2.79, "dy": -0.74, "dz": -0.07, "dpitch": 1.5, "dyaw": 8.87, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-71.88, -61.88, 20.05, -42.9, 27.03, 0.0]
  Target bbox: [622.35, 325.17, 657.44, 394.12]

Frame 2:
  Drone pose: [-71.32, -62.02, 20.04, -42.54, 28.69, 0.0]
  Target bbox: [625.37, 327.71, 654.48, 391.54]

Frame 3:
  Drone pose: [-70.76, -62.17, 20.03, -42.16, 30.31, 0.0]
  Target bbox: [628.2, 326.31, 651.63, 392.89]

Frame 4:
  Drone pose: [-70.2, -62.24, 20.02, -41.83, 31.73, 0.0]
  Target bbox: [623.05, 325.64, 656.69, 393.74]

Frame 5 (current):
  Drone pose: [-69.64, -62.3, 20.02, -41.5, 33.07, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 626.56, "ymin": 328.82, "xmax": 653.3, "ymax": 390.42}, "waypoint_deltas": [{"dx": 0.57, "dy": 0.02, "dz": 0.0, "dpitch": 0.29, "dyaw": 1.17, "droll": 0.0}, {"dx": 1.14, "dy": 0.06, "dz": -0.01, "dpitch": 0.56, "dyaw": 2.27, "droll": 0.0}, {"dx": 1.72, "dy": 0.43, "dz": -0.01, "dpitch": 0.58, "dyaw": 2.66, "droll": 0.0}, {"dx": 2.3, "dy": 0.81, "dz": -0.01, "dpitch": 0.59, "dyaw": 3.03, "droll": 0.0}, {"dx": 2.87, "dy": 1.2, "dz": -0.01, "dpitch": 0.6, "dyaw": 3.39, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-67.34, -61.49, 20.01, -40.91, 36.1, 0.0]
  Target bbox: [628.11, 329.04, 651.73, 390.21]

Frame 2:
  Drone pose: [-66.77, -61.1, 20.01, -40.9, 36.46, 0.0]
  Target bbox: [624.36, 326.13, 655.36, 393.27]

Frame 3:
  Drone pose: [-66.2, -60.71, 20.0, -40.89, 36.8, 0.0]
  Target bbox: [624.8, 326.92, 654.94, 392.44]

Frame 4:
  Drone pose: [-65.63, -60.32, 20.0, -40.87, 37.13, 0.0]
  Target bbox: [628.26, 329.36, 651.59, 389.86]

Frame 5 (current):
  Drone pose: [-65.06, -59.93, 20.0, -40.86, 37.45, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 624.07, "ymin": 326.16, "xmax": 655.62, "ymax": 393.27}, "waypoint_deltas": [{"dx": 0.56, "dy": 0.4, "dz": 0.0, "dpitch": 0.02, "dyaw": 0.32, "droll": 0.0}, {"dx": 1.12, "dy": 0.79, "dz": 0.0, "dpitch": 0.05, "dyaw": 0.65, "droll": 0.0}, {"dx": 1.69, "dy": 1.18, "dz": 0.0, "dpitch": 0.07, "dyaw": 0.97, "droll": 0.0}, {"dx": 2.25, "dy": 1.56, "dz": 0.0, "dpitch": 0.1, "dyaw": 1.31, "droll": 0.0}, {"dx": 2.81, "dy": 1.95, "dz": 0.0, "dpitch": 0.13, "dyaw": 1.65, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-62.25, -57.98, 20.0, -40.73, 39.1, 0.0]
  Target bbox: [624.73, 325.93, 654.94, 393.51]

Frame 2:
  Drone pose: [-61.68, -57.6, 20.0, -40.7, 39.44, 0.0]
  Target bbox: [626.37, 328.86, 653.44, 390.38]

Frame 3:
  Drone pose: [-61.11, -57.2, 20.0, -40.68, 39.76, 0.0]
  Target bbox: [628.33, 330.19, 651.53, 389.02]

Frame 4:
  Drone pose: [-60.55, -56.79, 20.0, -40.67, 40.04, 0.0]
  Target bbox: [627.46, 329.62, 652.36, 389.68]

Frame 5 (current):
  Drone pose: [-59.99, -56.36, 20.0, -40.68, 40.27, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 626.7, "ymin": 329.56, "xmax": 653.13, "ymax": 389.67}, "waypoint_deltas": [{"dx": 0.56, "dy": 0.46, "dz": 0.0, "dpitch": -0.01, "dyaw": 0.18, "droll": 0.0}, {"dx": 1.1, "dy": 0.93, "dz": 0.0, "dpitch": -0.03, "dyaw": 0.31, "droll": 0.0}, {"dx": 1.62, "dy": 1.42, "dz": 0.0, "dpitch": -0.05, "dyaw": 0.37, "droll": 0.0}, {"dx": 2.13, "dy": 1.94, "dz": 0.0, "dpitch": -0.07, "dyaw": 0.35, "droll": 0.0}, {"dx": 2.62, "dy": 2.48, "dz": 0.0, "dpitch": -0.09, "dyaw": 0.26, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-97.16, -80.04, 21.95, -52.82, 29.28, 0.0]
  Target bbox: [585.71, 349.39, 620.44, 416.88]

Frame 2:
  Drone pose: [-97.04, -79.78, 21.88, -53.07, 20.78, 0.0]
  Target bbox: [672.81, 331.48, 708.25, 397.84]

Frame 3:
  Drone pose: [-96.81, -79.86, 21.98, -52.0, 22.22, 0.0]
  Target bbox: [675.69, 337.8, 707.05, 402.36]

Frame 4:
  Drone pose: [-96.51, -79.7, 21.98, -51.97, 23.33, 0.0]
  Target bbox: [669.21, 326.53, 707.05, 394.86]

Frame 5 (current):
  Drone pose: [-96.45, -79.88, 22.15, -51.18, 29.3, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 621.31, "ymin": 323.91, "xmax": 658.41, "ymax": 395.06}, "waypoint_deltas": [{"dx": 0.16, "dy": 0.22, "dz": -0.05, "dpitch": 0.76, "dyaw": 0.25, "droll": 0.0}, {"dx": 0.34, "dy": 0.29, "dz": 0.0, "dpitch": 1.48, "dyaw": 0.94, "droll": 0.0}, {"dx": 0.51, "dy": 0.36, "dz": 0.05, "dpitch": 2.18, "dyaw": 1.59, "droll": 0.0}, {"dx": 0.69, "dy": 0.42, "dz": 0.11, "dpitch": 2.87, "dyaw": 2.21, "droll": 0.0}, {"dx": 0.87, "dy": 0.49, "dz": 0.17, "dpitch": 3.53, "dyaw": 2.79, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-95.76, -79.46, 22.26, -48.31, 31.51, 0.0]
  Target bbox: [628.41, 327.8, 651.43, 391.21]

Frame 2:
  Drone pose: [-95.58, -79.39, 22.32, -47.61, 35.16, 0.0]
  Target bbox: [592.22, 331.63, 617.81, 390.29]

Frame 3:
  Drone pose: [-95.41, -79.32, 22.41, -45.92, 32.69, 0.0]
  Target bbox: [621.55, 343.81, 657.79, 412.77]

Frame 4:
  Drone pose: [-95.23, -79.25, 22.49, -43.91, 34.97, 0.0]
  Target bbox: [589.18, 376.59, 621.62, 441.12]

Frame 5 (current):
  Drone pose: [-95.06, -79.19, 22.65, -46.68, 31.35, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 622.65, "ymin": 326.27, "xmax": 657.5, "ymax": 393.08}, "waypoint_deltas": [{"dx": 0.18, "dy": 0.07, "dz": 0.16, "dpitch": 0.13, "dyaw": -0.63, "droll": 0.0}, {"dx": 0.5, "dy": 0.06, "dz": 0.34, "dpitch": 0.12, "dyaw": -0.86, "droll": 0.0}, {"dx": 0.84, "dy": 0.05, "dz": 0.5, "dpitch": 0.11, "dyaw": -1.05, "droll": 0.0}, {"dx": 1.44, "dy": 0.09, "dz": 0.57, "dpitch": -0.12, "dyaw": -1.0, "droll": 0.0}, {"dx": 1.97, "dy": 0.15, "dz": 0.62, "dpitch": -0.28, "dyaw": -1.1, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-93.13, -79.01, 23.39, -44.3, 32.61, 0.0]
  Target bbox: [595.62, 375.51, 626.71, 438.42]

Frame 2:
  Drone pose: [-92.49, -78.97, 23.32, -47.19, 30.22, 0.0]
  Target bbox: [622.79, 326.48, 657.36, 392.83]

Frame 3:
  Drone pose: [-91.73, -77.47, 23.36, -48.57, 26.84, 0.0]
  Target bbox: [626.35, 331.2, 653.68, 387.93]

Frame 4:
  Drone pose: [-91.08, -74.65, 24.16, -51.4, 19.24, 0.0]
  Target bbox: [625.17, 327.48, 655.02, 391.62]

Frame 5 (current):
  Drone pose: [-90.82, -70.87, 24.48, -50.74, 10.29, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 598.34, "ymin": 366.19, "xmax": 623.55, "ymax": 421.61}, "waypoint_deltas": [{"dx": 0.28, "dy": 4.12, "dz": 0.53, "dpitch": -2.39, "dyaw": -16.05, "droll": 0.0}, {"dx": 0.71, "dy": 7.66, "dz": 0.19, "dpitch": -0.85, "dyaw": -26.82, "droll": 0.0}, {"dx": 1.48, "dy": 9.48, "dz": -0.61, "dpitch": 0.62, "dyaw": -32.28, "droll": 0.0}, {"dx": 1.18, "dy": 9.78, "dz": -1.29, "dpitch": 2.72, "dyaw": -32.23, "droll": 0.0}, {"dx": 1.08, "dy": 9.72, "dz": -1.38, "dpitch": 3.59, "dyaw": -31.44, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-89.55, -61.01, 23.09, -51.02, -17.26, 0.0]
  Target bbox: [568.72, 280.46, 598.06, 340.16]

Frame 2:
  Drone pose: [-89.86, -61.26, 22.99, -46.9, -20.76, 0.0]
  Target bbox: [627.48, 331.29, 652.46, 387.84]

Frame 3:
  Drone pose: [-89.39, -61.06, 23.19, -47.03, -21.25, 0.0]
  Target bbox: [626.58, 330.4, 653.34, 388.77]

Frame 4:
  Drone pose: [-89.05, -61.02, 22.88, -46.4, -21.18, 0.0]
  Target bbox: [625.77, 329.57, 654.33, 389.7]

Frame 5 (current):
  Drone pose: [-88.52, -60.72, 22.53, -43.28, -24.66, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 669.43, "ymin": 375.65, "xmax": 703.88, "ymax": 439.85}, "waypoint_deltas": [{"dx": 0.37, "dy": 0.31, "dz": -0.05, "dpitch": -2.65, "dyaw": 4.57, "droll": 0.0}, {"dx": 0.82, "dy": 0.7, "dz": -0.29, "dpitch": -2.32, "dyaw": 4.91, "droll": 0.0}, {"dx": 1.27, "dy": 1.12, "dz": -0.51, "dpitch": -1.99, "dyaw": 5.16, "droll": 0.0}, {"dx": 1.73, "dy": 1.56, "dz": -0.66, "dpitch": -1.77, "dyaw": 5.34, "droll": 0.0}, {"dx": 2.21, "dy": 2.03, "dz": -0.8, "dpitch": -1.55, "dyaw": 5.46, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-86.31, -58.69, 21.73, -45.49, -17.08, 0.0]
  Target bbox: [600.76, 317.48, 628.24, 380.25]

Frame 2:
  Drone pose: [-85.77, -58.58, 21.57, -43.09, -15.89, 0.0]
  Target bbox: [593.46, 354.27, 630.21, 424.63]

Frame 3:
  Drone pose: [-85.34, -58.62, 21.5, -43.68, -14.77, 0.0]
  Target bbox: [602.55, 348.47, 630.0, 411.37]

Frame 4:
  Drone pose: [-84.67, -58.42, 21.2, -44.8, -16.07, 0.0]
  Target bbox: [621.85, 324.97, 658.27, 394.31]

Frame 5 (current):
  Drone pose: [-84.16, -58.65, 21.17, -44.45, -15.22, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 638.75, "ymin": 336.83, "xmax": 668.81, "ymax": 402.58}, "waypoint_deltas": [{"dx": 0.56, "dy": -0.15, "dz": -0.12, "dpitch": -0.72, "dyaw": 2.89, "droll": 0.0}, {"dx": 1.12, "dy": -0.29, "dz": -0.23, "dpitch": -0.83, "dyaw": 4.69, "droll": 0.0}, {"dx": 1.68, "dy": -0.44, "dz": -0.32, "dpitch": -0.93, "dyaw": 6.51, "droll": 0.0}, {"dx": 2.24, "dy": -0.59, "dz": -0.42, "dpitch": -1.01, "dyaw": 8.37, "droll": 0.0}, {"dx": 2.79, "dy": -0.73, "dz": -0.5, "dpitch": -1.07, "dyaw": 10.26, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-81.37, -59.38, 20.67, -45.52, -4.96, 0.0]
  Target bbox: [623.35, 324.7, 656.74, 394.46]

Frame 2:
  Drone pose: [-80.99, -59.56, 20.51, -45.18, -2.93, 0.0]
  Target bbox: [620.48, 323.56, 659.53, 395.73]

Frame 3:
  Drone pose: [-80.17, -59.72, 20.38, -46.77, -6.0, 0.0]
  Target bbox: [682.98, 305.68, 715.46, 373.89]

Frame 4:
  Drone pose: [-79.69, -59.82, 20.46, -45.57, 0.8, 0.0]
  Target bbox: [622.83, 324.42, 657.23, 394.71]

Frame 5 (current):
  Drone pose: [-79.09, -59.87, 20.4, -45.62, 2.45, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 622.67, "ymin": 323.77, "xmax": 657.24, "ymax": 395.33}, "waypoint_deltas": [{"dx": 0.51, "dy": -0.25, "dz": -0.05, "dpitch": 0.13, "dyaw": 2.25, "droll": 0.0}, {"dx": 1.07, "dy": -0.39, "dz": -0.1, "dpitch": 0.21, "dyaw": 4.21, "droll": 0.0}, {"dx": 1.63, "dy": -0.54, "dz": -0.14, "dpitch": 0.31, "dyaw": 6.16, "droll": 0.0}, {"dx": 2.19, "dy": -0.69, "dz": -0.18, "dpitch": 0.44, "dyaw": 8.1, "droll": 0.0}, {"dx": 2.75, "dy": -0.83, "dz": -0.21, "dpitch": 0.6, "dyaw": 10.03, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-76.74, -60.58, 20.29, -45.51, 10.7, 0.0]
  Target bbox: [623.02, 324.79, 656.95, 394.28]

Frame 2:
  Drone pose: [-76.39, -60.67, 20.14, -48.16, 7.36, 0.0]
  Target bbox: [679.19, 268.89, 720.77, 344.01]

Frame 3:
  Drone pose: [-75.81, -60.86, 20.25, -44.94, 14.4, 0.0]
  Target bbox: [619.18, 322.42, 660.68, 396.88]

Frame 4:
  Drone pose: [-75.32, -60.86, 20.13, -42.69, 20.83, 0.0]
  Target bbox: [564.14, 359.51, 595.47, 425.58]

Frame 5 (current):
  Drone pose: [-74.67, -61.14, 20.12, -44.4, 18.16, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 621.92, "ymin": 323.18, "xmax": 657.89, "ymax": 396.04}, "waypoint_deltas": [{"dx": 0.56, "dy": -0.15, "dz": -0.02, "dpitch": 0.25, "dyaw": 1.84, "droll": 0.0}, {"dx": 1.12, "dy": -0.3, "dz": -0.04, "dpitch": 0.53, "dyaw": 3.65, "droll": 0.0}, {"dx": 1.67, "dy": -0.44, "dz": -0.05, "dpitch": 0.84, "dyaw": 5.43, "droll": 0.0}, {"dx": 2.23, "dy": -0.59, "dz": -0.06, "dpitch": 1.16, "dyaw": 7.17, "droll": 0.0}, {"dx": 2.79, "dy": -0.74, "dz": -0.07, "dpitch": 1.5, "dyaw": 8.87, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-71.88, -61.88, 20.05, -42.9, 27.03, 0.0]
  Target bbox: [625.13, 327.21, 654.74, 391.94]

Frame 2:
  Drone pose: [-71.23, -62.13, 20.1, -42.67, 29.08, 0.0]
  Target bbox: [622.15, 324.4, 657.56, 395.0]

Frame 3:
  Drone pose: [-70.77, -62.04, 20.0, -42.2, 30.0, 0.0]
  Target bbox: [625.58, 326.47, 654.23, 392.77]

Frame 4:
  Drone pose: [-70.21, -62.35, 19.9, -41.67, 30.86, 0.0]
  Target bbox: [639.57, 325.93, 668.41, 389.71]

Frame 5 (current):
  Drone pose: [-69.72, -62.26, 20.0, -41.41, 32.88, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 626.21, "ymin": 328.73, "xmax": 653.65, "ymax": 390.49}, "waypoint_deltas": [{"dx": 0.65, "dy": -0.02, "dz": 0.02, "dpitch": 0.2, "dyaw": 1.36, "droll": 0.0}, {"dx": 1.22, "dy": 0.02, "dz": 0.01, "dpitch": 0.47, "dyaw": 2.46, "droll": 0.0}, {"dx": 1.8, "dy": 0.39, "dz": 0.01, "dpitch": 0.49, "dyaw": 2.85, "droll": 0.0}, {"dx": 2.38, "dy": 0.77, "dz": 0.01, "dpitch": 0.5, "dyaw": 3.22, "droll": 0.0}, {"dx": 2.95, "dy": 1.16, "dz": 0.01, "dpitch": 0.51, "dyaw": 3.58, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-67.28, -61.4, 20.05, -37.11, 32.06, 0.0]
  Target bbox: [675.99, 396.5, 704.74, 459.27]

Frame 2:
  Drone pose: [-66.77, -61.1, 20.01, -39.08, 41.46, 0.0]
  Target bbox: [562.49, 359.46, 589.84, 424.59]

Frame 3:
  Drone pose: [-66.3, -60.6, 20.04, -40.92, 36.41, 0.0]
  Target bbox: [623.46, 326.53, 656.25, 392.87]

Frame 4:
  Drone pose: [-65.63, -60.32, 20.0, -36.29, 37.83, 0.0]
  Target bbox: [617.68, 406.12, 643.88, 467.4]

Frame 5 (current):
  Drone pose: [-65.17, -59.98, 20.07, -40.82, 37.39, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 626.68, "ymin": 328.18, "xmax": 653.1, "ymax": 391.18}, "waypoint_deltas": [{"dx": 0.67, "dy": 0.45, "dz": -0.07, "dpitch": -0.02, "dyaw": 0.38, "droll": 0.0}, {"dx": 1.23, "dy": 0.84, "dz": -0.07, "dpitch": 0.01, "dyaw": 0.71, "droll": 0.0}, {"dx": 1.8, "dy": 1.23, "dz": -0.07, "dpitch": 0.03, "dyaw": 1.03, "droll": 0.0}, {"dx": 2.36, "dy": 1.61, "dz": -0.07, "dpitch": 0.06, "dyaw": 1.37, "droll": 0.0}, {"dx": 2.92, "dy": 2.0, "dz": -0.07, "dpitch": 0.09, "dyaw": 1.71, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-62.25, -57.98, 20.0, -38.6, 37.19, 0.0]
  Target bbox: [649.53, 361.86, 679.38, 429.55]

Frame 2:
  Drone pose: [-61.68, -57.49, 19.94, -35.69, 41.64, 0.0]
  Target bbox: [594.12, 412.7, 622.95, 475.57]

Frame 3:
  Drone pose: [-61.11, -57.2, 20.0, -40.68, 39.76, 0.0]
  Target bbox: [625.73, 327.47, 654.01, 391.86]

Frame 4:
  Drone pose: [-60.45, -56.93, 20.01, -36.92, 39.02, 0.0]
  Target bbox: [644.2, 389.1, 673.57, 456.63]

Frame 5 (current):
  Drone pose: [-59.99, -56.36, 20.0, -40.68, 40.27, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 627.85, "ymin": 328.78, "xmax": 651.95, "ymax": 390.54}, "waypoint_deltas": [{"dx": 0.56, "dy": 0.46, "dz": 0.0, "dpitch": -0.01, "dyaw": 0.18, "droll": 0.0}, {"dx": 1.1, "dy": 0.93, "dz": 0.0, "dpitch": -0.03, "dyaw": 0.31, "droll": 0.0}, {"dx": 1.62, "dy": 1.42, "dz": 0.0, "dpitch": -0.05, "dyaw": 0.37, "droll": 0.0}, {"dx": 2.13, "dy": 1.94, "dz": 0.0, "dpitch": -0.07, "dyaw": 0.35, "droll": 0.0}, {"dx": 2.62, "dy": 2.48, "dz": 0.0, "dpitch": -0.09, "dyaw": 0.26, "droll": 0.0}]}