[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: [106.36, 85.72, 22.0, -46.4, -98.53, 0.0]
  Target bbox: [621.9, 327.37, 658.06, 391.95]

Frame 2:
  Drone pose: [104.71, 84.0, 21.2, -47.3, -95.61, 0.0]
  Target bbox: [625.58, 327.34, 654.16, 391.81]

Frame 3:
  Drone pose: [103.77, 82.84, 20.67, -47.67, -92.8, 0.0]
  Target bbox: [616.41, 320.75, 663.62, 398.55]

Frame 4:
  Drone pose: [103.22, 82.04, 20.64, -48.13, -92.71, 0.0]
  Target bbox: [618.94, 321.1, 661.2, 397.98]

Frame 5 (current):
  Drone pose: [102.91, 81.39, 20.62, -48.31, -93.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": 618.53, "ymin": 325.73, "xmax": 661.09, "ymax": 393.2}, "waypoint_deltas": [{"dx": -0.2, "dy": -0.54, "dz": -0.03, "dpitch": -0.05, "dyaw": 0.66, "droll": 0.0}, {"dx": -0.35, "dy": -1.05, "dz": -0.05, "dpitch": -0.04, "dyaw": 1.14, "droll": 0.0}, {"dx": -0.47, "dy": -1.56, "dz": -0.07, "dpitch": -0.03, "dyaw": 1.53, "droll": 0.0}, {"dx": -0.57, "dy": -2.06, "dz": -0.09, "dpitch": -0.01, "dyaw": 1.86, "droll": 0.0}, {"dx": -0.65, "dy": -2.57, "dz": -0.2, "dpitch": 0.14, "dyaw": 2.15, "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: [101.91, 75.79, 20.24, -47.99, -90.05, 0.0]
  Target bbox: [619.93, 325.8, 660.05, 393.06]

Frame 2:
  Drone pose: [101.89, 75.28, 20.22, -47.96, -90.01, 0.0]
  Target bbox: [620.31, 323.99, 659.68, 394.87]

Frame 3:
  Drone pose: [101.9, 74.76, 20.19, -47.94, -90.03, 0.0]
  Target bbox: [618.72, 326.0, 661.27, 392.89]

Frame 4:
  Drone pose: [101.93, 74.25, 20.17, -47.94, -90.12, 0.0]
  Target bbox: [616.52, 325.84, 663.42, 393.1]

Frame 5 (current):
  Drone pose: [101.98, 73.73, 20.15, -47.94, -90.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": 619.4, "ymin": 325.41, "xmax": 660.46, "ymax": 393.48}, "waypoint_deltas": [{"dx": 0.06, "dy": -0.52, "dz": -0.01, "dpitch": -0.01, "dyaw": -0.23, "droll": 0.0}, {"dx": 0.15, "dy": -1.05, "dz": -0.03, "dpitch": -0.03, "dyaw": -0.53, "droll": 0.0}, {"dx": 0.26, "dy": -1.58, "dz": -0.05, "dpitch": -0.06, "dyaw": -0.9, "droll": 0.0}, {"dx": 0.39, "dy": -2.12, "dz": -0.06, "dpitch": -0.1, "dyaw": -1.34, "droll": 0.0}, {"dx": 0.54, "dy": -2.66, "dz": -0.07, "dpitch": -0.14, "dyaw": -1.82, "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: [103.1, 67.69, 20.03, -48.59, -94.13, 0.0]
  Target bbox: [616.04, 317.69, 664.14, 401.33]

Frame 2:
  Drone pose: [103.06, 67.09, 20.03, -48.68, -95.73, 0.0]
  Target bbox: [615.15, 316.89, 665.03, 402.14]

Frame 3:
  Drone pose: [102.99, 66.48, 20.02, -48.78, -97.23, 0.0]
  Target bbox: [619.5, 323.05, 660.44, 395.96]

Frame 4:
  Drone pose: [102.91, 65.86, 20.02, -48.88, -98.71, 0.0]
  Target bbox: [617.55, 318.39, 662.69, 400.6]

Frame 5 (current):
  Drone pose: [102.83, 65.24, 20.02, -48.97, -100.21, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 617.28, "ymin": 319.53, "xmax": 662.8, "ymax": 399.39}, "waypoint_deltas": [{"dx": -0.07, "dy": -0.63, "dz": -0.01, "dpitch": -0.06, "dyaw": -1.55, "droll": 0.0}, {"dx": -0.13, "dy": -1.24, "dz": -0.01, "dpitch": -0.09, "dyaw": -3.15, "droll": 0.0}, {"dx": -0.18, "dy": -1.86, "dz": -0.01, "dpitch": -0.29, "dyaw": -3.07, "droll": 0.0}, {"dx": -0.24, "dy": -2.47, "dz": -0.01, "dpitch": -0.5, "dyaw": -2.95, "droll": 0.0}, {"dx": -0.32, "dy": -3.08, "dz": -0.01, "dpitch": -0.72, "dyaw": -2.77, "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: [101.03, 57.88, 20.0, -49.97, -110.7, 0.0]
  Target bbox: [615.16, 317.97, 665.16, 401.05]

Frame 2:
  Drone pose: [100.72, 57.25, 20.0, -50.06, -111.48, 0.0]
  Target bbox: [614.7, 318.81, 665.54, 400.08]

Frame 3:
  Drone pose: [100.39, 56.65, 20.0, -49.89, -112.17, 0.0]
  Target bbox: [615.19, 315.84, 665.22, 403.09]

Frame 4:
  Drone pose: [100.04, 56.07, 20.0, -49.92, -112.81, 0.0]
  Target bbox: [618.19, 322.11, 662.0, 396.79]

Frame 5 (current):
  Drone pose: [99.7, 55.48, 20.0, -49.96, -113.46, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 614.8, "ymin": 318.41, "xmax": 665.52, "ymax": 400.52}, "waypoint_deltas": [{"dx": -0.34, "dy": -0.55, "dz": 0.0, "dpitch": 0.04, "dyaw": -0.59, "droll": 0.0}, {"dx": -0.69, "dy": -1.08, "dz": 0.0, "dpitch": 0.1, "dyaw": -1.13, "droll": 0.0}, {"dx": -1.06, "dy": -1.6, "dz": 0.0, "dpitch": 0.17, "dyaw": -1.61, "droll": 0.0}, {"dx": -1.44, "dy": -2.11, "dz": 0.0, "dpitch": 0.24, "dyaw": -1.99, "droll": 0.0}, {"dx": -1.85, "dy": -2.6, "dz": 0.0, "dpitch": -0.05, "dyaw": -0.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: [95.03, 49.91, 20.0, -49.82, -114.65, 0.0]
  Target bbox: [620.87, 318.83, 659.48, 400.0]

Frame 2:
  Drone pose: [94.58, 49.45, 20.0, -49.73, -114.77, 0.0]
  Target bbox: [615.02, 317.49, 665.39, 401.52]

Frame 3:
  Drone pose: [94.21, 49.03, 20.0, -49.5, -115.07, 0.0]
  Target bbox: [613.97, 319.0, 665.85, 399.93]

Frame 4:
  Drone pose: [93.92, 48.65, 20.0, -49.53, -113.93, 0.0]
  Target bbox: [620.42, 320.39, 659.33, 398.41]

Frame 5 (current):
  Drone pose: [93.68, 48.27, 20.0, -49.49, -112.99, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 617.9, "ymin": 321.38, "xmax": 661.87, "ymax": 397.59}, "waypoint_deltas": [{"dx": -0.17, "dy": -0.37, "dz": 0.0, "dpitch": -0.13, "dyaw": 0.76, "droll": 0.0}, {"dx": -0.31, "dy": -0.74, "dz": 0.0, "dpitch": -0.01, "dyaw": 1.37, "droll": 0.0}, {"dx": -0.41, "dy": -1.12, "dz": 0.0, "dpitch": 0.11, "dyaw": 1.86, "droll": 0.0}, {"dx": -0.49, "dy": -1.51, "dz": 0.0, "dpitch": 0.24, "dyaw": 2.25, "droll": 0.0}, {"dx": -0.56, "dy": -1.92, "dz": 0.0, "dpitch": 0.35, "dyaw": 2.6, "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: [92.37, 43.02, 20.0, -49.3, -107.71, 0.0]
  Target bbox: [611.31, 319.64, 668.39, 399.33]

Frame 2:
  Drone pose: [92.21, 42.52, 20.0, -49.37, -107.18, 0.0]
  Target bbox: [622.22, 321.74, 657.51, 397.09]

Frame 3:
  Drone pose: [92.06, 42.05, 20.0, -49.4, -106.65, 0.0]
  Target bbox: [611.14, 320.04, 668.54, 398.95]

Frame 4:
  Drone pose: [91.92, 41.59, 20.0, -49.4, -106.16, 0.0]
  Target bbox: [617.31, 321.75, 662.39, 397.17]

Frame 5 (current):
  Drone pose: [91.73, 41.22, 20.0, -49.28, -105.38, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 619.12, "ymin": 320.82, "xmax": 660.56, "ymax": 398.04}, "waypoint_deltas": [{"dx": -0.11, "dy": -0.37, "dz": 0.0, "dpitch": 0.17, "dyaw": 0.49, "droll": 0.0}, {"dx": -0.18, "dy": -0.76, "dz": 0.0, "dpitch": 0.33, "dyaw": 0.82, "droll": 0.0}, {"dx": -0.18, "dy": -1.17, "dz": 0.0, "dpitch": 0.46, "dyaw": 0.92, "droll": 0.0}, {"dx": -0.07, "dy": -1.62, "dz": 0.0, "dpitch": 0.6, "dyaw": 0.57, "droll": 0.0}, {"dx": 0.94, "dy": -2.73, "dz": 0.0, "dpitch": 0.11, "dyaw": -3.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: [106.22, 25.8, 20.0, -43.73, -162.73, 0.0]
  Target bbox: [619.16, 318.59, 661.34, 400.92]

Frame 2:
  Drone pose: [106.61, 24.73, 20.0, -43.42, -164.63, 0.0]
  Target bbox: [621.83, 320.81, 658.6, 398.69]

Frame 3:
  Drone pose: [106.97, 23.68, 20.0, -43.34, -166.4, 0.0]
  Target bbox: [622.48, 324.1, 657.85, 395.3]

Frame 4:
  Drone pose: [107.01, 22.8, 20.0, -43.4, -167.48, 0.0]
  Target bbox: [616.64, 319.47, 663.11, 400.06]

Frame 5 (current):
  Drone pose: [106.81, 22.06, 20.0, -43.05, -168.33, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 619.16, "ymin": 323.99, "xmax": 660.77, "ymax": 395.51}, "waypoint_deltas": [{"dx": -0.22, "dy": -0.73, "dz": 0.0, "dpitch": 0.31, "dyaw": -0.78, "droll": 0.0}, {"dx": -0.73, "dy": -1.31, "dz": 0.0, "dpitch": 0.28, "dyaw": -1.0, "droll": 0.0}, {"dx": -1.25, "dy": -1.87, "dz": 0.0, "dpitch": 0.24, "dyaw": -1.14, "droll": 0.0}, {"dx": -1.77, "dy": -2.41, "dz": 0.0, "dpitch": 0.2, "dyaw": -1.24, "droll": 0.0}, {"dx": -2.28, "dy": -2.93, "dz": 0.0, "dpitch": 0.18, "dyaw": -1.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: [101.51, 16.09, 20.0, -42.92, -169.74, 0.0]
  Target bbox: [621.11, 322.76, 658.69, 396.65]

Frame 2:
  Drone pose: [100.99, 15.7, 20.0, -42.91, -169.41, 0.0]
  Target bbox: [617.28, 321.94, 662.69, 397.56]

Frame 3:
  Drone pose: [100.49, 15.37, 20.0, -42.87, -168.96, 0.0]
  Target bbox: [622.44, 321.27, 658.05, 398.38]

Frame 4:
  Drone pose: [99.99, 15.07, 20.0, -42.94, -169.79, 0.0]
  Target bbox: [619.96, 323.04, 659.98, 396.33]

Frame 5 (current):
  Drone pose: [99.5, 14.79, 20.0, -42.88, -169.18, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 623.3, "ymin": 323.57, "xmax": 657.08, "ymax": 395.88}, "waypoint_deltas": [{"dx": -0.5, "dy": -0.27, "dz": 0.0, "dpitch": -0.06, "dyaw": -0.75, "droll": 0.0}, {"dx": -1.0, "dy": -0.54, "dz": 0.0, "dpitch": -0.01, "dyaw": -0.09, "droll": 0.0}, {"dx": -1.51, "dy": -0.79, "dz": 0.0, "dpitch": -0.08, "dyaw": -0.79, "droll": 0.0}, {"dx": -2.02, "dy": -1.03, "dz": 0.0, "dpitch": -0.03, "dyaw": -0.06, "droll": 0.0}, {"dx": -2.51, "dy": -1.25, "dz": 0.0, "dpitch": -0.07, "dyaw": -0.68, "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.78, 11.9, 20.0, -42.36, -170.38, 0.0]
  Target bbox: [616.64, 321.24, 663.27, 398.36]

Frame 2:
  Drone pose: [93.32, 11.65, 20.0, -42.24, -169.73, 0.0]
  Target bbox: [621.97, 320.12, 658.57, 399.57]

Frame 3:
  Drone pose: [92.88, 11.39, 20.0, -42.22, -170.45, 0.0]
  Target bbox: [619.45, 324.22, 660.51, 395.32]

Frame 4:
  Drone pose: [92.42, 11.15, 20.0, -42.1, -169.77, 0.0]
  Target bbox: [624.15, 327.06, 656.11, 392.32]

Frame 5 (current):
  Drone pose: [91.95, 10.93, 20.0, -42.12, -170.38, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 619.53, "ymin": 321.46, "xmax": 660.25, "ymax": 398.03}, "waypoint_deltas": [{"dx": -0.48, "dy": -0.21, "dz": 0.0, "dpitch": 0.09, "dyaw": 0.79, "droll": 0.0}, {"dx": -0.98, "dy": -0.41, "dz": 0.0, "dpitch": 0.05, "dyaw": 0.25, "droll": 0.0}, {"dx": -1.5, "dy": -0.61, "dz": 0.0, "dpitch": -0.03, "dyaw": -0.31, "droll": 0.0}, {"dx": -2.03, "dy": -0.83, "dz": 0.0, "dpitch": 0.0, "dyaw": 0.47, "droll": 0.0}, {"dx": -2.56, "dy": -1.06, "dz": 0.0, "dpitch": -0.09, "dyaw": -0.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: [86.35, 8.51, 20.0, -42.23, -170.11, 0.0]
  Target bbox: [620.54, 323.41, 659.39, 396.0]

Frame 2:
  Drone pose: [85.86, 8.33, 20.0, -42.15, -169.24, 0.0]
  Target bbox: [623.54, 325.0, 656.79, 394.45]

Frame 3:
  Drone pose: [85.37, 8.16, 20.0, -42.18, -169.72, 0.0]
  Target bbox: [624.04, 327.52, 656.19, 391.8]

Frame 4:
  Drone pose: [84.88, 7.98, 20.0, -42.21, -170.22, 0.0]
  Target bbox: [615.67, 320.28, 664.15, 399.42]

Frame 5 (current):
  Drone pose: [84.38, 7.78, 20.0, -42.13, -169.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": 622.17, "ymin": 320.32, "xmax": 658.36, "ymax": 399.37}, "waypoint_deltas": [{"dx": -0.5, "dy": -0.2, "dz": 0.0, "dpitch": -0.05, "dyaw": -0.55, "droll": 0.0}, {"dx": -1.0, "dy": -0.42, "dz": 0.0, "dpitch": 0.02, "dyaw": 0.22, "droll": 0.0}, {"dx": -1.5, "dy": -0.64, "dz": 0.0, "dpitch": -0.03, "dyaw": -0.38, "droll": 0.0}, {"dx": -2.0, "dy": -0.86, "dz": 0.0, "dpitch": 0.04, "dyaw": 0.37, "droll": 0.0}, {"dx": -2.5, "dy": -1.08, "dz": 0.0, "dpitch": -0.02, "dyaw": -0.21, "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: [106.41, 85.87, 21.88, -48.7, -100.95, 0.0]
  Target bbox: [649.43, 281.08, 686.18, 349.31]

Frame 2:
  Drone pose: [104.77, 83.87, 21.09, -43.46, -98.61, 0.0]
  Target bbox: [650.67, 389.52, 693.39, 460.91]

Frame 3:
  Drone pose: [103.77, 82.84, 20.67, -47.67, -92.8, 0.0]
  Target bbox: [618.59, 322.79, 661.36, 396.46]

Frame 4:
  Drone pose: [103.23, 82.05, 20.63, -48.08, -92.73, 0.0]
  Target bbox: [620.21, 323.71, 659.73, 395.43]

Frame 5 (current):
  Drone pose: [102.95, 81.47, 20.55, -47.8, -88.47, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 563.47, "ymin": 332.53, "xmax": 603.14, "ymax": 399.46}, "waypoint_deltas": [{"dx": -0.24, "dy": -0.62, "dz": 0.04, "dpitch": -0.56, "dyaw": -4.22, "droll": 0.0}, {"dx": -0.39, "dy": -1.13, "dz": 0.02, "dpitch": -0.55, "dyaw": -3.74, "droll": 0.0}, {"dx": -0.51, "dy": -1.64, "dz": 0.0, "dpitch": -0.54, "dyaw": -3.35, "droll": 0.0}, {"dx": -0.61, "dy": -2.14, "dz": -0.02, "dpitch": -0.52, "dyaw": -3.02, "droll": 0.0}, {"dx": -0.69, "dy": -2.65, "dz": -0.13, "dpitch": -0.37, "dyaw": -2.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: [101.91, 75.79, 20.24, -47.99, -90.05, 0.0]
  Target bbox: [624.64, 324.82, 655.33, 394.03]

Frame 2:
  Drone pose: [101.89, 75.28, 20.22, -45.03, -93.02, 0.0]
  Target bbox: [658.94, 375.49, 689.26, 443.27]

Frame 3:
  Drone pose: [101.85, 74.83, 20.24, -52.9, -91.21, 0.0]
  Target bbox: [640.17, 242.07, 670.9, 308.99]

Frame 4:
  Drone pose: [102.1, 74.29, 20.13, -49.42, -95.69, 0.0]
  Target bbox: [675.54, 299.77, 717.83, 368.95]

Frame 5 (current):
  Drone pose: [101.86, 73.58, 20.13, -48.15, -89.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": 618.7, "ymin": 325.74, "xmax": 661.35, "ymax": 393.1}, "waypoint_deltas": [{"dx": 0.18, "dy": -0.37, "dz": 0.01, "dpitch": 0.2, "dyaw": -0.61, "droll": 0.0}, {"dx": 0.27, "dy": -0.9, "dz": -0.01, "dpitch": 0.18, "dyaw": -0.91, "droll": 0.0}, {"dx": 0.38, "dy": -1.43, "dz": -0.03, "dpitch": 0.15, "dyaw": -1.28, "droll": 0.0}, {"dx": 0.51, "dy": -1.97, "dz": -0.04, "dpitch": 0.11, "dyaw": -1.72, "droll": 0.0}, {"dx": 0.66, "dy": -2.51, "dz": -0.05, "dpitch": 0.07, "dyaw": -2.2, "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: [103.1, 67.69, 20.03, -46.04, -99.13, 0.0]
  Target bbox: [670.75, 363.06, 721.68, 445.17]

Frame 2:
  Drone pose: [103.18, 67.06, 20.17, -48.15, -96.14, 0.0]
  Target bbox: [615.65, 332.5, 664.27, 412.64]

Frame 3:
  Drone pose: [103.06, 66.36, 20.06, -49.03, -97.52, 0.0]
  Target bbox: [616.91, 319.34, 663.11, 399.59]

Frame 4:
  Drone pose: [102.91, 65.86, 20.02, -44.62, -95.18, 0.0]
  Target bbox: [579.44, 395.03, 621.43, 469.01]

Frame 5 (current):
  Drone pose: [102.83, 65.24, 20.02, -50.13, -95.21, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 556.16, "ymin": 298.12, "xmax": 612.31, "ymax": 385.76}, "waypoint_deltas": [{"dx": -0.07, "dy": -0.63, "dz": -0.01, "dpitch": 1.1, "dyaw": -6.55, "droll": 0.0}, {"dx": -0.13, "dy": -1.24, "dz": -0.01, "dpitch": 1.07, "dyaw": -8.15, "droll": 0.0}, {"dx": -0.18, "dy": -1.86, "dz": -0.01, "dpitch": 0.87, "dyaw": -8.07, "droll": 0.0}, {"dx": -0.24, "dy": -2.47, "dz": -0.01, "dpitch": 0.66, "dyaw": -7.95, "droll": 0.0}, {"dx": -0.32, "dy": -3.08, "dz": -0.01, "dpitch": 0.44, "dyaw": -7.77, "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: [101.03, 57.93, 20.13, -50.09, -110.62, 0.0]
  Target bbox: [618.59, 323.15, 661.54, 395.77]

Frame 2:
  Drone pose: [100.7, 57.14, 19.84, -51.09, -111.58, 0.0]
  Target bbox: [615.11, 300.22, 665.75, 382.64]

Frame 3:
  Drone pose: [100.38, 56.67, 19.83, -49.61, -112.12, 0.0]
  Target bbox: [616.87, 316.11, 663.54, 402.77]

Frame 4:
  Drone pose: [100.13, 55.93, 20.01, -50.09, -113.29, 0.0]
  Target bbox: [617.91, 321.59, 662.31, 397.31]

Frame 5 (current):
  Drone pose: [99.75, 55.38, 19.98, -50.28, -108.95, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 560.89, "ymin": 316.11, "xmax": 613.8, "ymax": 398.49}, "waypoint_deltas": [{"dx": -0.39, "dy": -0.45, "dz": 0.02, "dpitch": 0.36, "dyaw": -5.1, "droll": 0.0}, {"dx": -0.74, "dy": -0.98, "dz": 0.02, "dpitch": 0.42, "dyaw": -5.64, "droll": 0.0}, {"dx": -1.11, "dy": -1.5, "dz": 0.02, "dpitch": 0.49, "dyaw": -6.12, "droll": 0.0}, {"dx": -1.49, "dy": -2.01, "dz": 0.02, "dpitch": 0.56, "dyaw": -6.5, "droll": 0.0}, {"dx": -1.9, "dy": -2.5, "dz": 0.02, "dpitch": 0.27, "dyaw": -5.16, "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.03, 49.84, 20.04, -50.66, -109.77, 0.0]
  Target bbox: [560.26, 311.34, 610.69, 389.1]

Frame 2:
  Drone pose: [94.58, 49.45, 20.0, -48.38, -109.85, 0.0]
  Target bbox: [563.56, 347.59, 608.61, 419.94]

Frame 3:
  Drone pose: [94.21, 49.03, 20.0, -54.5, -114.97, 0.0]
  Target bbox: [616.71, 236.35, 660.9, 314.36]

Frame 4:
  Drone pose: [94.07, 48.75, 20.07, -44.35, -116.25, 0.0]
  Target bbox: [636.74, 403.32, 687.63, 484.49]

Frame 5 (current):
  Drone pose: [93.7, 48.2, 19.93, -46.02, -111.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": 600.19, "ymin": 377.44, "xmax": 646.08, "ymax": 458.47}, "waypoint_deltas": [{"dx": -0.19, "dy": -0.3, "dz": 0.07, "dpitch": -3.6, "dyaw": -0.57, "droll": 0.0}, {"dx": -0.33, "dy": -0.67, "dz": 0.07, "dpitch": -3.48, "dyaw": 0.04, "droll": 0.0}, {"dx": -0.43, "dy": -1.05, "dz": 0.07, "dpitch": -3.36, "dyaw": 0.53, "droll": 0.0}, {"dx": -0.51, "dy": -1.44, "dz": 0.07, "dpitch": -3.23, "dyaw": 0.92, "droll": 0.0}, {"dx": -0.58, "dy": -1.85, "dz": 0.07, "dpitch": -3.12, "dyaw": 1.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: [92.26, 43.08, 20.1, -49.41, -107.31, 0.0]
  Target bbox: [617.4, 322.32, 662.32, 396.66]

Frame 2:
  Drone pose: [92.21, 42.52, 20.0, -50.43, -102.18, 0.0]
  Target bbox: [560.4, 306.81, 608.77, 380.29]

Frame 3:
  Drone pose: [92.11, 42.2, 20.05, -48.66, -107.48, 0.0]
  Target bbox: [624.52, 329.9, 673.29, 406.75]

Frame 4:
  Drone pose: [91.92, 41.59, 20.0, -49.93, -103.42, 0.0]
  Target bbox: [584.29, 313.49, 634.29, 388.62]

Frame 5 (current):
  Drone pose: [91.73, 41.22, 20.0, -44.28, -106.49, 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.11, "ymin": 405.6, "xmax": 674.39, "ymax": 481.75}, "waypoint_deltas": [{"dx": -0.11, "dy": -0.37, "dz": 0.0, "dpitch": -4.83, "dyaw": 1.6, "droll": 0.0}, {"dx": -0.18, "dy": -0.76, "dz": 0.0, "dpitch": -4.67, "dyaw": 1.93, "droll": 0.0}, {"dx": -0.18, "dy": -1.17, "dz": 0.0, "dpitch": -4.54, "dyaw": 2.03, "droll": 0.0}, {"dx": -0.07, "dy": -1.62, "dz": 0.0, "dpitch": -4.4, "dyaw": 1.68, "droll": 0.0}, {"dx": 0.94, "dy": -2.73, "dz": 0.0, "dpitch": -4.89, "dyaw": -2.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: [106.22, 25.8, 20.0, -43.73, -162.73, 0.0]
  Target bbox: [621.24, 320.4, 659.18, 399.08]

Frame 2:
  Drone pose: [106.58, 24.81, 20.13, -43.13, -161.12, 0.0]
  Target bbox: [579.54, 328.63, 620.93, 409.15]

Frame 3:
  Drone pose: [106.97, 23.68, 20.0, -43.34, -166.4, 0.0]
  Target bbox: [622.8, 322.01, 657.59, 397.42]

Frame 4:
  Drone pose: [106.95, 22.96, 19.99, -46.86, -170.2, 0.0]
  Target bbox: [658.96, 267.6, 699.91, 337.82]

Frame 5 (current):
  Drone pose: [106.81, 22.06, 20.0, -47.45, -167.36, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 607.6, "ymin": 250.37, "xmax": 647.88, "ymax": 321.41}, "waypoint_deltas": [{"dx": -0.22, "dy": -0.73, "dz": 0.0, "dpitch": 4.71, "dyaw": -1.75, "droll": 0.0}, {"dx": -0.73, "dy": -1.31, "dz": 0.0, "dpitch": 4.68, "dyaw": -1.97, "droll": 0.0}, {"dx": -1.25, "dy": -1.87, "dz": 0.0, "dpitch": 4.64, "dyaw": -2.11, "droll": 0.0}, {"dx": -1.77, "dy": -2.41, "dz": 0.0, "dpitch": 4.6, "dyaw": -2.21, "droll": 0.0}, {"dx": -2.28, "dy": -2.93, "dz": 0.0, "dpitch": 4.58, "dyaw": -2.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: [101.59, 16.12, 19.85, -39.93, -166.24, 0.0]
  Target bbox: [577.79, 368.53, 615.71, 441.41]

Frame 2:
  Drone pose: [100.84, 15.73, 20.08, -42.89, -164.26, 0.0]
  Target bbox: [554.1, 329.1, 602.45, 405.48]

Frame 3:
  Drone pose: [100.49, 15.37, 20.0, -42.87, -168.96, 0.0]
  Target bbox: [623.38, 321.85, 657.04, 397.65]

Frame 4:
  Drone pose: [99.89, 15.04, 20.01, -41.89, -169.99, 0.0]
  Target bbox: [618.99, 341.36, 665.66, 418.73]

Frame 5 (current):
  Drone pose: [99.58, 14.74, 19.9, -43.34, -174.34, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 684.72, "ymin": 313.04, "xmax": 719.93, "ymax": 386.07}, "waypoint_deltas": [{"dx": -0.58, "dy": -0.22, "dz": 0.1, "dpitch": 0.4, "dyaw": 4.41, "droll": 0.0}, {"dx": -1.08, "dy": -0.49, "dz": 0.1, "dpitch": 0.45, "dyaw": 5.07, "droll": 0.0}, {"dx": -1.59, "dy": -0.74, "dz": 0.1, "dpitch": 0.38, "dyaw": 4.37, "droll": 0.0}, {"dx": -2.1, "dy": -0.98, "dz": 0.1, "dpitch": 0.43, "dyaw": 5.1, "droll": 0.0}, {"dx": -2.59, "dy": -1.2, "dz": 0.1, "dpitch": 0.39, "dyaw": 4.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: [93.85, 11.97, 20.08, -40.0, -171.56, 0.0]
  Target bbox: [636.51, 363.88, 677.68, 435.06]

Frame 2:
  Drone pose: [93.3, 11.71, 20.18, -46.39, -168.27, 0.0]
  Target bbox: [605.78, 255.77, 642.34, 334.14]

Frame 3:
  Drone pose: [92.88, 11.39, 20.0, -42.22, -170.45, 0.0]
  Target bbox: [616.03, 319.73, 663.76, 399.92]

Frame 4:
  Drone pose: [92.42, 11.15, 20.0, -43.98, -172.59, 0.0]
  Target bbox: [657.77, 290.5, 693.73, 367.18]

Frame 5 (current):
  Drone pose: [91.95, 10.93, 20.0, -42.12, -170.38, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 617.17, "ymin": 321.81, "xmax": 662.79, "ymax": 397.76}, "waypoint_deltas": [{"dx": -0.48, "dy": -0.21, "dz": 0.0, "dpitch": 0.09, "dyaw": 0.79, "droll": 0.0}, {"dx": -0.98, "dy": -0.41, "dz": 0.0, "dpitch": 0.05, "dyaw": 0.25, "droll": 0.0}, {"dx": -1.5, "dy": -0.61, "dz": 0.0, "dpitch": -0.03, "dyaw": -0.31, "droll": 0.0}, {"dx": -2.03, "dy": -0.83, "dz": 0.0, "dpitch": 0.0, "dyaw": 0.47, "droll": 0.0}, {"dx": -2.56, "dy": -1.06, "dz": 0.0, "dpitch": -0.09, "dyaw": -0.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: [86.33, 8.56, 20.04, -40.62, -168.86, 0.0]
  Target bbox: [607.8, 354.16, 644.35, 421.98]

Frame 2:
  Drone pose: [85.93, 8.23, 20.03, -47.12, -171.87, 0.0]
  Target bbox: [651.39, 237.59, 687.92, 314.44]

Frame 3:
  Drone pose: [85.3, 8.27, 20.13, -41.07, -167.44, 0.0]
  Target bbox: [599.52, 350.11, 632.2, 415.02]

Frame 4:
  Drone pose: [84.83, 8.02, 20.18, -43.59, -173.15, 0.0]
  Target bbox: [657.94, 304.88, 698.71, 380.3]

Frame 5 (current):
  Drone pose: [84.38, 7.78, 20.0, -42.13, -169.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": 623.1, "ymin": 322.43, "xmax": 657.36, "ymax": 397.2}, "waypoint_deltas": [{"dx": -0.5, "dy": -0.2, "dz": 0.0, "dpitch": -0.05, "dyaw": -0.55, "droll": 0.0}, {"dx": -1.0, "dy": -0.42, "dz": 0.0, "dpitch": 0.02, "dyaw": 0.22, "droll": 0.0}, {"dx": -1.5, "dy": -0.64, "dz": 0.0, "dpitch": -0.03, "dyaw": -0.38, "droll": 0.0}, {"dx": -2.0, "dy": -0.86, "dz": 0.0, "dpitch": 0.04, "dyaw": 0.37, "droll": 0.0}, {"dx": -2.5, "dy": -1.08, "dz": 0.0, "dpitch": -0.02, "dyaw": -0.21, "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.11, 49.94, 22.0, -46.1, -75.96, 0.0]
  Target bbox: [629.37, 341.37, 650.69, 378.36]

Frame 2:
  Drone pose: [-96.13, 48.08, 21.2, -46.48, -72.11, 0.0]
  Target bbox: [628.39, 340.11, 651.66, 379.59]

Frame 3:
  Drone pose: [-96.28, 47.3, 20.67, -46.06, -71.41, 0.0]
  Target bbox: [631.61, 340.98, 648.45, 378.75]

Frame 4:
  Drone pose: [-96.4, 46.54, 20.64, -46.33, -70.82, 0.0]
  Target bbox: [629.23, 340.07, 650.84, 379.67]

Frame 5 (current):
  Drone pose: [-96.41, 45.9, 20.62, -46.48, -70.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": 627.84, "ymin": 339.42, "xmax": 652.22, "ymax": 380.31}, "waypoint_deltas": [{"dx": 0.05, "dy": -0.58, "dz": -0.03, "dpitch": -0.1, "dyaw": -0.05, "droll": 0.0}, {"dx": 0.11, "dy": -1.14, "dz": -0.05, "dpitch": -0.18, "dyaw": -0.17, "droll": 0.0}, {"dx": 0.23, "dy": -1.64, "dz": -0.07, "dpitch": -0.22, "dyaw": -0.53, "droll": 0.0}, {"dx": 0.35, "dy": -2.14, "dz": -0.09, "dpitch": -0.25, "dyaw": -0.87, "droll": 0.0}, {"dx": 0.47, "dy": -2.65, "dz": -0.2, "dpitch": -0.16, "dyaw": -1.2, "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.42, 40.73, 20.27, -46.7, -73.35, 0.0]
  Target bbox: [628.37, 339.59, 651.69, 380.09]

Frame 2:
  Drone pose: [-95.33, 40.22, 20.24, -46.71, -73.62, 0.0]
  Target bbox: [631.85, 340.71, 648.21, 379.0]

Frame 3:
  Drone pose: [-95.24, 39.72, 20.22, -46.5, -73.88, 0.0]
  Target bbox: [628.26, 339.31, 651.82, 380.4]

Frame 4:
  Drone pose: [-95.15, 39.21, 20.19, -46.51, -74.14, 0.0]
  Target bbox: [627.47, 339.31, 652.61, 380.4]

Frame 5 (current):
  Drone pose: [-95.06, 38.7, 20.17, -46.53, -74.41, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 632.11, "ymin": 340.14, "xmax": 647.96, "ymax": 379.56}, "waypoint_deltas": [{"dx": 0.09, "dy": -0.49, "dz": -0.02, "dpitch": -0.01, "dyaw": -0.27, "droll": 0.0}, {"dx": 0.17, "dy": -0.98, "dz": -0.04, "dpitch": 0.0, "dyaw": -0.54, "droll": 0.0}, {"dx": 0.25, "dy": -1.48, "dz": -0.05, "dpitch": 0.0, "dyaw": -0.76, "droll": 0.0}, {"dx": 0.31, "dy": -2.0, "dz": -0.07, "dpitch": -0.04, "dyaw": -0.92, "droll": 0.0}, {"dx": 0.37, "dy": -2.57, "dz": -0.08, "dpitch": -0.36, "dyaw": -1.06, "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.28, 32.61, 20.04, -48.11, -79.52, 0.0]
  Target bbox: [631.56, 340.34, 648.52, 379.33]

Frame 2:
  Drone pose: [-92.94, 32.08, 20.03, -48.25, -80.62, 0.0]
  Target bbox: [631.18, 340.34, 648.9, 379.33]

Frame 3:
  Drone pose: [-92.61, 31.55, 20.03, -48.37, -81.69, 0.0]
  Target bbox: [628.19, 340.04, 651.91, 379.61]

Frame 4:
  Drone pose: [-92.29, 31.03, 20.02, -48.47, -82.73, 0.0]
  Target bbox: [630.76, 340.69, 649.33, 378.97]

Frame 5 (current):
  Drone pose: [-91.99, 30.53, 20.02, -48.53, -83.72, 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.76, "ymin": 340.09, "xmax": 652.35, "ymax": 379.56}, "waypoint_deltas": [{"dx": 0.28, "dy": -0.5, "dz": 0.0, "dpitch": -0.03, "dyaw": -0.93, "droll": 0.0}, {"dx": 0.53, "dy": -0.98, "dz": -0.01, "dpitch": -0.03, "dyaw": -1.76, "droll": 0.0}, {"dx": 0.74, "dy": -1.46, "dz": -0.01, "dpitch": -0.03, "dyaw": -2.45, "droll": 0.0}, {"dx": 0.89, "dy": -1.96, "dz": -0.01, "dpitch": -0.03, "dyaw": -2.96, "droll": 0.0}, {"dx": 0.97, "dy": -2.47, "dz": -0.01, "dpitch": -0.05, "dyaw": -3.23, "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: [-91.7, 25.4, 20.0, -48.88, -91.36, 0.0]
  Target bbox: [626.67, 336.43, 653.33, 383.24]

Frame 2:
  Drone pose: [-91.99, 24.87, 20.0, -48.92, -92.09, 0.0]
  Target bbox: [627.21, 337.71, 652.79, 382.0]

Frame 3:
  Drone pose: [-92.28, 24.34, 20.0, -48.94, -92.79, 0.0]
  Target bbox: [629.2, 339.21, 650.79, 380.46]

Frame 4:
  Drone pose: [-92.56, 23.82, 20.0, -48.74, -93.54, 0.0]
  Target bbox: [628.99, 338.96, 651.01, 380.71]

Frame 5 (current):
  Drone pose: [-92.82, 23.31, 20.0, -48.73, -94.38, 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.16, "ymin": 339.09, "xmax": 650.84, "ymax": 380.58}, "waypoint_deltas": [{"dx": -0.21, "dy": -0.51, "dz": 0.0, "dpitch": 0.03, "dyaw": -0.96, "droll": 0.0}, {"dx": -0.39, "dy": -1.0, "dz": 0.0, "dpitch": 0.01, "dyaw": -0.35, "droll": 0.0}, {"dx": -0.54, "dy": -1.49, "dz": 0.0, "dpitch": 0.02, "dyaw": 0.15, "droll": 0.0}, {"dx": -0.66, "dy": -1.97, "dz": 0.0, "dpitch": 0.03, "dyaw": 0.56, "droll": 0.0}, {"dx": -0.76, "dy": -2.45, "dz": 0.0, "dpitch": 0.05, "dyaw": 0.91, "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: [-94.15, 17.97, 20.0, -48.53, -91.53, 0.0]
  Target bbox: [628.34, 340.58, 651.54, 379.03]

Frame 2:
  Drone pose: [-94.26, 17.49, 20.0, -48.5, -91.19, 0.0]
  Target bbox: [632.97, 340.85, 646.95, 378.78]

Frame 3:
  Drone pose: [-94.35, 17.01, 20.0, -48.47, -90.85, 0.0]
  Target bbox: [631.09, 341.01, 648.82, 378.62]

Frame 4:
  Drone pose: [-94.45, 16.53, 20.0, -48.44, -90.52, 0.0]
  Target bbox: [633.75, 340.64, 646.18, 379.0]

Frame 5 (current):
  Drone pose: [-94.55, 16.04, 20.0, -48.42, -90.2, 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.47, "ymin": 340.86, "xmax": 648.48, "ymax": 378.76}, "waypoint_deltas": [{"dx": -0.09, "dy": -0.48, "dz": 0.0, "dpitch": 0.03, "dyaw": 0.31, "droll": 0.0}, {"dx": -0.18, "dy": -0.96, "dz": 0.0, "dpitch": 0.06, "dyaw": 0.61, "droll": 0.0}, {"dx": -0.27, "dy": -1.45, "dz": 0.0, "dpitch": 0.09, "dyaw": 0.9, "droll": 0.0}, {"dx": -0.35, "dy": -1.93, "dz": 0.0, "dpitch": 0.11, "dyaw": 1.16, "droll": 0.0}, {"dx": -0.42, "dy": -2.42, "dz": 0.0, "dpitch": 0.14, "dyaw": 1.42, "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.38, 11.03, 20.0, -47.59, -87.49, 0.0]
  Target bbox: [630.27, 340.73, 649.83, 378.9]

Frame 2:
  Drone pose: [-95.46, 10.63, 20.0, -47.42, -87.25, 0.0]
  Target bbox: [629.28, 340.37, 650.83, 379.28]

Frame 3:
  Drone pose: [-95.55, 10.22, 20.0, -47.27, -86.97, 0.0]
  Target bbox: [632.78, 341.12, 647.3, 378.55]

Frame 4:
  Drone pose: [-95.65, 9.8, 20.0, -47.14, -86.65, 0.0]
  Target bbox: [629.05, 340.35, 651.05, 379.26]

Frame 5 (current):
  Drone pose: [-95.77, 9.36, 20.0, -47.03, -86.28, 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.25, "ymin": 340.12, "xmax": 651.87, "ymax": 379.53}, "waypoint_deltas": [{"dx": -0.15, "dy": -0.44, "dz": 0.0, "dpitch": 0.12, "dyaw": 0.44, "droll": 0.0}, {"dx": -0.32, "dy": -0.84, "dz": 0.0, "dpitch": 0.29, "dyaw": 0.97, "droll": 0.0}, {"dx": -0.54, "dy": -1.19, "dz": 0.0, "dpitch": 0.55, "dyaw": 1.61, "droll": 0.0}, {"dx": -0.82, "dy": -1.52, "dz": 0.0, "dpitch": 0.86, "dyaw": 2.43, "droll": 0.0}, {"dx": -1.19, "dy": -1.88, "dz": 0.0, "dpitch": 1.14, "dyaw": 3.51, "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: [-98.85, 4.27, 20.0, -46.44, -76.62, 0.0]
  Target bbox: [626.9, 337.09, 653.05, 382.66]

Frame 2:
  Drone pose: [-99.02, 3.67, 20.0, -46.72, -77.56, 0.0]
  Target bbox: [628.0, 337.97, 651.94, 381.77]

Frame 3:
  Drone pose: [-99.21, 3.11, 20.0, -46.9, -78.47, 0.0]
  Target bbox: [629.21, 338.86, 650.74, 380.87]

Frame 4:
  Drone pose: [-99.48, 2.58, 20.0, -47.03, -79.18, 0.0]
  Target bbox: [629.17, 338.83, 650.78, 380.89]

Frame 5 (current):
  Drone pose: [-99.82, 2.05, 20.0, -47.12, -79.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": 628.51, "ymin": 338.54, "xmax": 651.44, "ymax": 381.19}, "waypoint_deltas": [{"dx": -0.39, "dy": -0.52, "dz": 0.0, "dpitch": -0.07, "dyaw": -0.33, "droll": 0.0}, {"dx": -0.8, "dy": -1.03, "dz": 0.0, "dpitch": -0.11, "dyaw": -0.61, "droll": 0.0}, {"dx": -1.21, "dy": -1.54, "dz": 0.0, "dpitch": -0.13, "dyaw": -0.87, "droll": 0.0}, {"dx": -1.62, "dy": -2.04, "dz": 0.0, "dpitch": -0.17, "dyaw": -1.17, "droll": 0.0}, {"dx": -2.01, "dy": -2.55, "dz": 0.0, "dpitch": -0.43, "dyaw": -1.52, "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: [-103.89, -3.79, 20.0, -48.21, -84.11, 0.0]
  Target bbox: [629.6, 339.16, 650.37, 380.51]

Frame 2:
  Drone pose: [-104.17, -4.37, 20.0, -48.39, -84.79, 0.0]
  Target bbox: [627.66, 337.71, 652.31, 381.99]

Frame 3:
  Drone pose: [-104.44, -4.96, 20.0, -48.56, -85.55, 0.0]
  Target bbox: [627.02, 336.62, 652.96, 383.04]

Frame 4:
  Drone pose: [-104.69, -5.54, 20.0, -48.72, -86.36, 0.0]
  Target bbox: [628.46, 338.2, 651.52, 381.47]

Frame 5 (current):
  Drone pose: [-104.94, -6.11, 20.0, -48.87, -87.2, 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.79, "ymin": 337.55, "xmax": 652.19, "ymax": 382.12}, "waypoint_deltas": [{"dx": -0.25, "dy": -0.56, "dz": 0.0, "dpitch": -0.12, "dyaw": -0.84, "droll": 0.0}, {"dx": -0.5, "dy": -1.11, "dz": 0.0, "dpitch": -0.22, "dyaw": -1.66, "droll": 0.0}, {"dx": -0.76, "dy": -1.66, "dz": 0.0, "dpitch": -0.29, "dyaw": -2.48, "droll": 0.0}, {"dx": -1.02, "dy": -2.19, "dz": 0.0, "dpitch": -0.35, "dyaw": -3.31, "droll": 0.0}, {"dx": -1.26, "dy": -2.72, "dz": 0.0, "dpitch": -0.38, "dyaw": -4.2, "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: [-106.96, -11.3, 20.0, -49.19, -92.22, 0.0]
  Target bbox: [628.51, 340.28, 651.38, 379.28]

Frame 2:
  Drone pose: [-107.04, -11.77, 20.0, -49.16, -91.94, 0.0]
  Target bbox: [629.63, 340.7, 650.27, 378.89]

Frame 3:
  Drone pose: [-107.11, -12.25, 20.0, -49.12, -91.68, 0.0]
  Target bbox: [628.35, 340.38, 651.54, 379.19]

Frame 4:
  Drone pose: [-107.19, -12.73, 20.0, -49.08, -91.43, 0.0]
  Target bbox: [632.8, 340.59, 647.12, 379.04]

Frame 5 (current):
  Drone pose: [-107.26, -13.2, 20.0, -49.05, -91.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": 628.5, "ymin": 340.28, "xmax": 651.38, "ymax": 379.32}, "waypoint_deltas": [{"dx": -0.08, "dy": -0.48, "dz": 0.0, "dpitch": 0.04, "dyaw": 0.27, "droll": 0.0}, {"dx": -0.16, "dy": -0.95, "dz": 0.0, "dpitch": 0.08, "dyaw": 0.54, "droll": 0.0}, {"dx": -0.25, "dy": -1.43, "dz": 0.0, "dpitch": 0.11, "dyaw": 0.83, "droll": 0.0}, {"dx": -0.33, "dy": -1.91, "dz": 0.0, "dpitch": 0.15, "dyaw": 1.11, "droll": 0.0}, {"dx": -0.41, "dy": -2.39, "dz": 0.0, "dpitch": 0.19, "dyaw": 1.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: [-108.13, -18.48, 20.0, -48.66, -88.25, 0.0]
  Target bbox: [630.9, 340.6, 649.2, 379.03]

Frame 2:
  Drone pose: [-108.19, -18.96, 20.0, -48.63, -88.03, 0.0]
  Target bbox: [629.04, 340.77, 651.07, 378.87]

Frame 3:
  Drone pose: [-108.26, -19.45, 20.0, -48.6, -87.82, 0.0]
  Target bbox: [631.16, 340.83, 648.93, 378.79]

Frame 4:
  Drone pose: [-108.32, -19.93, 20.0, -48.58, -87.62, 0.0]
  Target bbox: [629.45, 340.73, 650.65, 378.87]

Frame 5 (current):
  Drone pose: [-108.38, -20.42, 20.0, -48.55, -87.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": 628.44, "ymin": 340.34, "xmax": 651.67, "ymax": 379.25}, "waypoint_deltas": [{"dx": -0.05, "dy": -0.48, "dz": 0.0, "dpitch": 0.03, "dyaw": 0.19, "droll": 0.0}, {"dx": -0.11, "dy": -0.97, "dz": 0.0, "dpitch": 0.05, "dyaw": 0.36, "droll": 0.0}, {"dx": -0.16, "dy": -1.46, "dz": 0.0, "dpitch": 0.08, "dyaw": 0.53, "droll": 0.0}, {"dx": -0.21, "dy": -1.95, "dz": 0.0, "dpitch": 0.1, "dyaw": 0.69, "droll": 0.0}, {"dx": -0.26, "dy": -2.43, "dz": 0.0, "dpitch": 0.13, "dyaw": 0.85, "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.11, 49.94, 22.0, -49.63, -75.41, 0.0]
  Target bbox: [622.32, 282.09, 644.73, 319.32]

Frame 2:
  Drone pose: [-96.13, 48.08, 21.2, -46.48, -72.11, 0.0]
  Target bbox: [629.92, 341.2, 650.15, 378.56]

Frame 3:
  Drone pose: [-96.23, 47.39, 20.55, -47.92, -75.89, 0.0]
  Target bbox: [677.58, 305.48, 702.27, 345.15]

Frame 4:
  Drone pose: [-96.44, 46.73, 20.66, -44.21, -73.83, 0.0]
  Target bbox: [665.63, 373.06, 682.74, 410.31]

Frame 5 (current):
  Drone pose: [-96.41, 45.9, 20.62, -43.43, -71.56, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 642.47, "ymin": 391.89, "xmax": 658.42, "ymax": 430.25}, "waypoint_deltas": [{"dx": 0.05, "dy": -0.58, "dz": -0.03, "dpitch": -3.15, "dyaw": 0.85, "droll": 0.0}, {"dx": 0.11, "dy": -1.14, "dz": -0.05, "dpitch": -3.23, "dyaw": 0.73, "droll": 0.0}, {"dx": 0.23, "dy": -1.64, "dz": -0.07, "dpitch": -3.27, "dyaw": 0.37, "droll": 0.0}, {"dx": 0.35, "dy": -2.14, "dz": -0.09, "dpitch": -3.3, "dyaw": 0.03, "droll": 0.0}, {"dx": 0.47, "dy": -2.65, "dz": -0.2, "dpitch": -3.21, "dyaw": -0.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: [-95.42, 40.73, 20.27, -45.55, -74.09, 0.0]
  Target bbox: [636.2, 358.52, 661.14, 399.92]

Frame 2:
  Drone pose: [-95.33, 40.22, 20.24, -50.91, -76.24, 0.0]
  Target bbox: [657.4, 269.15, 683.34, 310.43]

Frame 3:
  Drone pose: [-95.24, 39.72, 20.22, -46.33, -68.88, 0.0]
  Target bbox: [570.22, 344.0, 594.11, 385.3]

Frame 4:
  Drone pose: [-95.26, 39.04, 20.18, -43.45, -76.52, 0.0]
  Target bbox: [663.71, 395.34, 681.64, 434.84]

Frame 5 (current):
  Drone pose: [-95.06, 38.7, 20.17, -50.48, -75.62, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 642.24, "ymin": 273.02, "xmax": 666.13, "ymax": 314.1}, "waypoint_deltas": [{"dx": 0.09, "dy": -0.49, "dz": -0.02, "dpitch": 3.94, "dyaw": 0.94, "droll": 0.0}, {"dx": 0.17, "dy": -0.98, "dz": -0.04, "dpitch": 3.95, "dyaw": 0.67, "droll": 0.0}, {"dx": 0.25, "dy": -1.48, "dz": -0.05, "dpitch": 3.95, "dyaw": 0.45, "droll": 0.0}, {"dx": 0.31, "dy": -2.0, "dz": -0.07, "dpitch": 3.91, "dyaw": 0.29, "droll": 0.0}, {"dx": 0.37, "dy": -2.57, "dz": -0.08, "dpitch": 3.59, "dyaw": 0.15, "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.28, 32.61, 20.04, -44.17, -79.91, 0.0]
  Target bbox: [635.25, 406.7, 653.66, 445.45]

Frame 2:
  Drone pose: [-92.96, 32.19, 20.01, -44.48, -75.61, 0.0]
  Target bbox: [570.8, 400.25, 596.57, 442.09]

Frame 3:
  Drone pose: [-92.6, 31.73, 20.06, -51.51, -84.65, 0.0]
  Target bbox: [663.38, 284.45, 681.35, 323.39]

Frame 4:
  Drone pose: [-92.29, 31.03, 20.02, -46.44, -77.73, 0.0]
  Target bbox: [571.75, 375.31, 596.76, 415.95]

Frame 5 (current):
  Drone pose: [-91.99, 30.53, 20.02, -53.18, -88.65, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 682.59, "ymin": 263.77, "xmax": 707.75, "ymax": 303.25}, "waypoint_deltas": [{"dx": 0.28, "dy": -0.5, "dz": 0.0, "dpitch": 4.62, "dyaw": 4.0, "droll": 0.0}, {"dx": 0.53, "dy": -0.98, "dz": -0.01, "dpitch": 4.62, "dyaw": 3.17, "droll": 0.0}, {"dx": 0.74, "dy": -1.46, "dz": -0.01, "dpitch": 4.62, "dyaw": 2.48, "droll": 0.0}, {"dx": 0.89, "dy": -1.96, "dz": -0.01, "dpitch": 4.62, "dyaw": 1.97, "droll": 0.0}, {"dx": 0.97, "dy": -2.47, "dz": -0.01, "dpitch": 4.6, "dyaw": 1.7, "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: [-91.7, 25.4, 20.0, -49.78, -90.19, 0.0]
  Target bbox: [613.57, 321.95, 640.14, 367.74]

Frame 2:
  Drone pose: [-91.99, 24.87, 20.0, -51.16, -89.34, 0.0]
  Target bbox: [597.29, 301.14, 621.7, 344.31]

Frame 3:
  Drone pose: [-92.28, 24.34, 20.0, -47.89, -91.34, 0.0]
  Target bbox: [611.96, 356.24, 635.56, 398.94]

Frame 4:
  Drone pose: [-92.56, 23.82, 20.0, -48.74, -93.54, 0.0]
  Target bbox: [628.73, 338.7, 651.26, 380.97]

Frame 5 (current):
  Drone pose: [-92.83, 23.37, 20.02, -46.52, -89.31, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 570.29, "ymin": 374.75, "xmax": 598.49, "ymax": 420.7}, "waypoint_deltas": [{"dx": -0.2, "dy": -0.57, "dz": -0.02, "dpitch": -2.18, "dyaw": -6.03, "droll": 0.0}, {"dx": -0.38, "dy": -1.06, "dz": -0.02, "dpitch": -2.2, "dyaw": -5.42, "droll": 0.0}, {"dx": -0.53, "dy": -1.55, "dz": -0.02, "dpitch": -2.19, "dyaw": -4.92, "droll": 0.0}, {"dx": -0.65, "dy": -2.03, "dz": -0.02, "dpitch": -2.18, "dyaw": -4.51, "droll": 0.0}, {"dx": -0.75, "dy": -2.51, "dz": -0.02, "dpitch": -2.16, "dyaw": -4.16, "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: [-94.23, 17.91, 19.95, -50.22, -91.38, 0.0]
  Target bbox: [629.18, 312.69, 652.75, 351.2]

Frame 2:
  Drone pose: [-94.41, 17.51, 19.96, -53.21, -95.49, 0.0]
  Target bbox: [681.0, 261.06, 706.78, 300.98]

Frame 3:
  Drone pose: [-94.35, 17.01, 20.0, -51.78, -90.6, 0.0]
  Target bbox: [625.56, 284.63, 648.61, 324.05]

Frame 4:
  Drone pose: [-94.39, 16.6, 20.03, -43.37, -89.22, 0.0]
  Target bbox: [614.97, 424.67, 631.02, 463.35]

Frame 5 (current):
  Drone pose: [-94.69, 16.01, 20.13, -46.76, -84.74, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 572.38, "ymin": 373.52, "xmax": 596.6, "ymax": 413.58}, "waypoint_deltas": [{"dx": 0.05, "dy": -0.45, "dz": -0.13, "dpitch": -1.63, "dyaw": -5.15, "droll": 0.0}, {"dx": -0.04, "dy": -0.93, "dz": -0.13, "dpitch": -1.6, "dyaw": -4.85, "droll": 0.0}, {"dx": -0.13, "dy": -1.42, "dz": -0.13, "dpitch": -1.57, "dyaw": -4.56, "droll": 0.0}, {"dx": -0.21, "dy": -1.9, "dz": -0.13, "dpitch": -1.55, "dyaw": -4.3, "droll": 0.0}, {"dx": -0.28, "dy": -2.39, "dz": -0.13, "dpitch": -1.52, "dyaw": -4.04, "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.38, 11.03, 20.0, -52.59, -92.49, 0.0]
  Target bbox: [685.75, 257.98, 707.96, 297.29]

Frame 2:
  Drone pose: [-95.29, 10.55, 19.98, -47.53, -87.77, 0.0]
  Target bbox: [632.36, 341.14, 647.72, 378.53]

Frame 3:
  Drone pose: [-95.42, 10.16, 19.99, -51.14, -87.47, 0.0]
  Target bbox: [632.14, 277.74, 650.3, 315.34]

Frame 4:
  Drone pose: [-95.81, 9.87, 19.91, -46.89, -86.16, 0.0]
  Target bbox: [633.11, 340.89, 646.97, 378.78]

Frame 5 (current):
  Drone pose: [-95.77, 9.36, 20.0, -47.03, -86.28, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 633.11, "ymin": 340.99, "xmax": 646.97, "ymax": 378.68}, "waypoint_deltas": [{"dx": -0.15, "dy": -0.44, "dz": 0.0, "dpitch": 0.12, "dyaw": 0.44, "droll": 0.0}, {"dx": -0.32, "dy": -0.84, "dz": 0.0, "dpitch": 0.29, "dyaw": 0.97, "droll": 0.0}, {"dx": -0.54, "dy": -1.19, "dz": 0.0, "dpitch": 0.55, "dyaw": 1.61, "droll": 0.0}, {"dx": -0.82, "dy": -1.52, "dz": 0.0, "dpitch": 0.86, "dyaw": 2.43, "droll": 0.0}, {"dx": -1.19, "dy": -1.88, "dz": 0.0, "dpitch": 1.14, "dyaw": 3.51, "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: [-98.85, 4.27, 20.0, -46.44, -76.62, 0.0]
  Target bbox: [627.11, 337.34, 652.84, 382.41]

Frame 2:
  Drone pose: [-99.17, 3.7, 20.04, -47.79, -72.12, 0.0]
  Target bbox: [571.07, 321.91, 593.47, 363.77]

Frame 3:
  Drone pose: [-99.24, 3.06, 19.88, -46.79, -78.36, 0.0]
  Target bbox: [627.53, 337.8, 652.44, 381.92]

Frame 4:
  Drone pose: [-99.5, 2.44, 19.98, -48.64, -84.02, 0.0]
  Target bbox: [685.97, 316.89, 708.25, 358.19]

Frame 5 (current):
  Drone pose: [-99.81, 2.14, 20.04, -47.05, -79.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": 628.38, "ymin": 338.04, "xmax": 651.58, "ymax": 381.67}, "waypoint_deltas": [{"dx": -0.4, "dy": -0.61, "dz": -0.04, "dpitch": -0.14, "dyaw": -0.25, "droll": 0.0}, {"dx": -0.81, "dy": -1.12, "dz": -0.04, "dpitch": -0.18, "dyaw": -0.53, "droll": 0.0}, {"dx": -1.22, "dy": -1.63, "dz": -0.04, "dpitch": -0.2, "dyaw": -0.79, "droll": 0.0}, {"dx": -1.63, "dy": -2.13, "dz": -0.04, "dpitch": -0.24, "dyaw": -1.09, "droll": 0.0}, {"dx": -2.02, "dy": -2.64, "dz": -0.04, "dpitch": -0.5, "dyaw": -1.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: [-103.89, -3.79, 20.0, -48.21, -84.11, 0.0]
  Target bbox: [628.81, 338.48, 651.16, 381.2]

Frame 2:
  Drone pose: [-104.08, -4.26, 20.09, -46.01, -90.14, 0.0]
  Target bbox: [683.31, 379.11, 708.56, 422.35]

Frame 3:
  Drone pose: [-104.4, -4.79, 19.93, -50.32, -90.71, 0.0]
  Target bbox: [682.34, 302.23, 709.96, 349.01]

Frame 4:
  Drone pose: [-104.69, -5.63, 20.15, -53.42, -87.26, 0.0]
  Target bbox: [638.93, 265.62, 661.84, 308.73]

Frame 5 (current):
  Drone pose: [-104.85, -6.17, 19.85, -48.74, -87.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.92, "ymin": 338.78, "xmax": 651.08, "ymax": 380.89}, "waypoint_deltas": [{"dx": -0.34, "dy": -0.5, "dz": 0.15, "dpitch": -0.25, "dyaw": -0.54, "droll": 0.0}, {"dx": -0.59, "dy": -1.05, "dz": 0.15, "dpitch": -0.35, "dyaw": -1.36, "droll": 0.0}, {"dx": -0.85, "dy": -1.6, "dz": 0.15, "dpitch": -0.42, "dyaw": -2.18, "droll": 0.0}, {"dx": -1.11, "dy": -2.13, "dz": 0.15, "dpitch": -0.48, "dyaw": -3.01, "droll": 0.0}, {"dx": -1.35, "dy": -2.66, "dz": 0.15, "dpitch": -0.51, "dyaw": -3.9, "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: [-106.95, -11.24, 19.87, -48.91, -92.25, 0.0]
  Target bbox: [628.57, 340.19, 651.32, 379.38]

Frame 2:
  Drone pose: [-107.16, -11.7, 20.01, -49.05, -91.53, 0.0]
  Target bbox: [630.56, 340.59, 649.34, 379.03]

Frame 3:
  Drone pose: [-107.11, -12.25, 20.0, -54.0, -96.68, 0.0]
  Target bbox: [686.76, 260.17, 703.51, 299.11]

Frame 4:
  Drone pose: [-107.16, -12.75, 19.83, -48.86, -91.52, 0.0]
  Target bbox: [628.69, 340.26, 651.2, 379.31]

Frame 5 (current):
  Drone pose: [-107.19, -13.09, 19.87, -48.66, -91.41, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 633.22, "ymin": 340.89, "xmax": 646.71, "ymax": 378.75}, "waypoint_deltas": [{"dx": -0.15, "dy": -0.59, "dz": 0.13, "dpitch": -0.35, "dyaw": 0.51, "droll": 0.0}, {"dx": -0.23, "dy": -1.06, "dz": 0.13, "dpitch": -0.31, "dyaw": 0.78, "droll": 0.0}, {"dx": -0.32, "dy": -1.54, "dz": 0.13, "dpitch": -0.28, "dyaw": 1.07, "droll": 0.0}, {"dx": -0.4, "dy": -2.02, "dz": 0.13, "dpitch": -0.24, "dyaw": 1.35, "droll": 0.0}, {"dx": -0.48, "dy": -2.5, "dz": 0.13, "dpitch": -0.2, "dyaw": 1.63, "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: [-108.13, -18.48, 20.0, -43.91, -92.69, 0.0]
  Target bbox: [678.22, 421.69, 700.57, 460.43]

Frame 2:
  Drone pose: [-108.1, -19.05, 20.11, -48.93, -93.36, 0.0]
  Target bbox: [683.1, 342.28, 707.27, 381.4]

Frame 3:
  Drone pose: [-108.21, -19.58, 20.01, -44.66, -91.35, 0.0]
  Target bbox: [665.83, 411.45, 689.26, 450.65]

Frame 4:
  Drone pose: [-108.35, -19.79, 19.87, -48.14, -87.55, 0.0]
  Target bbox: [628.61, 340.25, 651.5, 379.34]

Frame 5 (current):
  Drone pose: [-108.38, -20.42, 20.0, -48.55, -87.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": 628.87, "ymin": 340.38, "xmax": 651.24, "ymax": 379.2}, "waypoint_deltas": [{"dx": -0.05, "dy": -0.48, "dz": 0.0, "dpitch": 0.03, "dyaw": 0.19, "droll": 0.0}, {"dx": -0.11, "dy": -0.97, "dz": 0.0, "dpitch": 0.05, "dyaw": 0.36, "droll": 0.0}, {"dx": -0.16, "dy": -1.46, "dz": 0.0, "dpitch": 0.08, "dyaw": 0.53, "droll": 0.0}, {"dx": -0.21, "dy": -1.95, "dz": 0.0, "dpitch": 0.1, "dyaw": 0.69, "droll": 0.0}, {"dx": -0.26, "dy": -2.43, "dz": 0.0, "dpitch": 0.13, "dyaw": 0.85, "droll": 0.0}]}