[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: [-52.46, 62.27, 22.0, -46.47, -97.59, 0.0]
  Target bbox: [619.04, 328.39, 660.68, 390.84]

Frame 2:
  Drone pose: [-53.39, 61.0, 21.2, -47.45, -93.77, 0.0]
  Target bbox: [619.35, 328.54, 660.35, 390.5]

Frame 3:
  Drone pose: [-53.48, 60.41, 20.67, -47.65, -92.0, 0.0]
  Target bbox: [617.8, 327.46, 661.82, 391.54]

Frame 4:
  Drone pose: [-53.54, 59.82, 20.64, -48.58, -90.21, 0.0]
  Target bbox: [622.86, 328.19, 657.04, 390.77]

Frame 5 (current):
  Drone pose: [-53.55, 59.29, 20.62, -49.42, -88.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": 616.65, "ymin": 320.39, "xmax": 663.33, "ymax": 398.73}, "waypoint_deltas": [{"dx": 0.2, "dy": -0.44, "dz": -0.03, "dpitch": 0.15, "dyaw": 1.01, "droll": 0.0}, {"dx": 0.41, "dy": -0.93, "dz": -0.05, "dpitch": 0.19, "dyaw": 0.31, "droll": 0.0}, {"dx": 0.61, "dy": -1.5, "dz": -0.07, "dpitch": 0.11, "dyaw": -0.37, "droll": 0.0}, {"dx": 0.83, "dy": -2.14, "dz": -0.09, "dpitch": -0.11, "dyaw": -1.13, "droll": 0.0}, {"dx": 1.1, "dy": -2.88, "dz": -0.2, "dpitch": -0.33, "dyaw": -3.8, "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: [-49.49, 50.7, 20.24, -52.41, -112.22, 0.0]
  Target bbox: [618.07, 323.09, 661.78, 395.65]

Frame 2:
  Drone pose: [-49.01, 49.75, 20.22, -52.79, -114.64, 0.0]
  Target bbox: [618.69, 322.99, 661.18, 395.72]

Frame 3:
  Drone pose: [-48.61, 48.86, 20.19, -53.07, -116.71, 0.0]
  Target bbox: [620.36, 323.31, 659.51, 395.38]

Frame 4:
  Drone pose: [-48.31, 48.06, 20.17, -53.29, -118.32, 0.0]
  Target bbox: [623.56, 323.87, 656.67, 394.82]

Frame 5 (current):
  Drone pose: [-48.11, 47.34, 20.15, -52.96, -121.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": 621.3, "ymin": 323.46, "xmax": 658.58, "ymax": 395.25}, "waypoint_deltas": [{"dx": 0.12, "dy": -0.64, "dz": -0.01, "dpitch": -0.37, "dyaw": -3.47, "droll": 0.0}, {"dx": 0.18, "dy": -1.23, "dz": -0.03, "dpitch": -0.63, "dyaw": -6.66, "droll": 0.0}, {"dx": 0.18, "dy": -1.78, "dz": -0.05, "dpitch": -0.81, "dyaw": -9.66, "droll": 0.0}, {"dx": 0.15, "dy": -2.3, "dz": -0.06, "dpitch": -0.93, "dyaw": -12.53, "droll": 0.0}, {"dx": 0.11, "dy": -2.81, "dz": -0.07, "dpitch": -0.99, "dyaw": -15.34, "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: [-48.56, 41.37, 20.03, -53.32, -152.87, 0.0]
  Target bbox: [619.85, 321.29, 660.36, 397.39]

Frame 2:
  Drone pose: [-48.75, 40.88, 20.03, -53.2, -155.23, 0.0]
  Target bbox: [617.17, 316.71, 663.22, 402.03]

Frame 3:
  Drone pose: [-48.98, 40.41, 20.02, -53.08, -157.4, 0.0]
  Target bbox: [621.67, 323.57, 658.51, 395.09]

Frame 4:
  Drone pose: [-49.24, 39.98, 20.02, -52.95, -159.37, 0.0]
  Target bbox: [619.6, 318.33, 660.79, 400.46]

Frame 5 (current):
  Drone pose: [-49.54, 39.58, 20.02, -52.83, -161.14, 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.29, "ymin": 315.9, "xmax": 662.21, "ymax": 402.91}, "waypoint_deltas": [{"dx": -0.31, "dy": -0.36, "dz": -0.01, "dpitch": 0.12, "dyaw": -1.6, "droll": 0.0}, {"dx": -0.65, "dy": -0.69, "dz": -0.01, "dpitch": 0.24, "dyaw": -3.04, "droll": 0.0}, {"dx": -1.01, "dy": -1.0, "dz": -0.01, "dpitch": 0.36, "dyaw": -4.35, "droll": 0.0}, {"dx": -1.37, "dy": -1.28, "dz": -0.01, "dpitch": 0.48, "dyaw": -5.55, "droll": 0.0}, {"dx": -1.75, "dy": -1.54, "dz": -0.01, "dpitch": 0.6, "dyaw": -6.67, "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: [-53.66, 36.7, 20.0, -51.48, -173.31, 0.0]
  Target bbox: [624.42, 319.34, 655.99, 399.47]

Frame 2:
  Drone pose: [-54.04, 36.5, 20.0, -51.29, -174.11, 0.0]
  Target bbox: [625.21, 326.1, 655.03, 392.66]

Frame 3:
  Drone pose: [-54.41, 36.31, 20.0, -51.09, -174.88, 0.0]
  Target bbox: [625.05, 320.26, 655.34, 398.58]

Frame 4:
  Drone pose: [-54.77, 36.12, 20.0, -50.86, -175.63, 0.0]
  Target bbox: [625.09, 319.28, 655.33, 399.59]

Frame 5 (current):
  Drone pose: [-55.13, 35.93, 20.0, -50.63, -176.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": 624.39, "ymin": 318.41, "xmax": 656.1, "ymax": 400.6}, "waypoint_deltas": [{"dx": -0.35, "dy": -0.18, "dz": 0.0, "dpitch": 0.25, "dyaw": -0.7, "droll": 0.0}, {"dx": -0.69, "dy": -0.36, "dz": 0.0, "dpitch": 0.52, "dyaw": -1.39, "droll": 0.0}, {"dx": -1.05, "dy": -0.53, "dz": 0.0, "dpitch": 0.76, "dyaw": -2.01, "droll": 0.0}, {"dx": -1.39, "dy": -0.69, "dz": 0.0, "dpitch": 1.03, "dyaw": -2.59, "droll": 0.0}, {"dx": -1.76, "dy": -0.82, "dz": 0.0, "dpitch": 1.26, "dyaw": -3.07, "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: [-58.75, 34.23, 20.0, -47.42, 177.63, 0.0]
  Target bbox: [626.27, 320.89, 653.34, 398.23]

Frame 2:
  Drone pose: [-58.95, 34.0, 20.0, -46.9, 176.93, 0.0]
  Target bbox: [626.69, 325.8, 653.05, 393.22]

Frame 3:
  Drone pose: [-59.23, 33.67, 20.0, -46.51, 175.93, 0.0]
  Target bbox: [625.45, 322.15, 654.16, 397.11]

Frame 4:
  Drone pose: [-59.67, 33.22, 20.0, -46.37, 174.49, 0.0]
  Target bbox: [626.2, 327.43, 653.58, 391.63]

Frame 5 (current):
  Drone pose: [-60.32, 32.66, 20.0, -46.51, 172.68, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 625.12, "ymin": 325.2, "xmax": 654.6, "ymax": 393.9}, "waypoint_deltas": [{"dx": -0.79, "dy": -0.57, "dz": 0.0, "dpitch": -0.33, "dyaw": -1.95, "droll": 0.0}, {"dx": -1.62, "dy": -1.07, "dz": 0.0, "dpitch": -0.71, "dyaw": -3.73, "droll": 0.0}, {"dx": -2.41, "dy": -1.44, "dz": 0.0, "dpitch": -1.06, "dyaw": -5.11, "droll": 0.0}, {"dx": -3.13, "dy": -1.67, "dz": 0.0, "dpitch": -1.31, "dyaw": -6.04, "droll": 0.0}, {"dx": -3.76, "dy": -1.81, "dz": 0.0, "dpitch": -1.48, "dyaw": -6.59, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-67.57, 30.81, 20.0, -47.95, 165.98, 0.0]
  Target bbox: [624.51, 326.13, 655.29, 392.86]

Frame 2:
  Drone pose: [-68.06, 30.79, 20.0, -47.92, 165.9, 0.0]
  Target bbox: [623.04, 323.19, 656.65, 395.91]

Frame 3:
  Drone pose: [-68.55, 30.77, 20.0, -47.9, 165.84, 0.0]
  Target bbox: [622.17, 319.59, 657.41, 399.57]

Frame 4:
  Drone pose: [-69.03, 30.77, 20.0, -47.87, 165.86, 0.0]
  Target bbox: [622.14, 319.42, 657.42, 399.76]

Frame 5 (current):
  Drone pose: [-69.51, 30.79, 20.0, -47.85, 165.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": 620.7, "ymin": 318.64, "xmax": 658.82, "ymax": 400.58}, "waypoint_deltas": [{"dx": -0.47, "dy": 0.03, "dz": 0.0, "dpitch": 0.04, "dyaw": 0.13, "droll": 0.0}, {"dx": -0.94, "dy": 0.06, "dz": 0.0, "dpitch": 0.07, "dyaw": 0.23, "droll": 0.0}, {"dx": -1.42, "dy": 0.06, "dz": 0.0, "dpitch": 0.1, "dyaw": 0.27, "droll": 0.0}, {"dx": -1.91, "dy": 0.05, "dz": 0.0, "dpitch": 0.12, "dyaw": 0.24, "droll": 0.0}, {"dx": -2.4, "dy": 0.04, "dz": 0.0, "dpitch": 0.14, "dyaw": 0.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: [-75.87, 30.91, 20.0, -47.66, 166.46, 0.0]
  Target bbox: [622.33, 319.47, 657.23, 399.72]

Frame 2:
  Drone pose: [-76.37, 30.88, 20.0, -47.67, 166.36, 0.0]
  Target bbox: [621.04, 318.73, 658.45, 400.63]

Frame 3:
  Drone pose: [-76.9, 30.8, 20.0, -47.67, 166.09, 0.0]
  Target bbox: [620.86, 318.57, 658.63, 400.75]

Frame 4:
  Drone pose: [-77.44, 30.67, 20.0, -47.68, 165.62, 0.0]
  Target bbox: [623.32, 323.98, 656.4, 395.11]

Frame 5 (current):
  Drone pose: [-77.99, 30.49, 20.0, -47.69, 164.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": 622.95, "ymin": 323.33, "xmax": 656.75, "ymax": 395.79}, "waypoint_deltas": [{"dx": -0.57, "dy": -0.21, "dz": 0.0, "dpitch": -0.02, "dyaw": -0.74, "droll": 0.0}, {"dx": -1.15, "dy": -0.44, "dz": 0.0, "dpitch": -0.03, "dyaw": -1.55, "droll": 0.0}, {"dx": -1.73, "dy": -0.68, "dz": 0.0, "dpitch": -0.06, "dyaw": -2.38, "droll": 0.0}, {"dx": -2.33, "dy": -0.9, "dz": 0.0, "dpitch": -0.32, "dyaw": -3.18, "droll": 0.0}, {"dx": -2.93, "dy": -1.09, "dz": 0.0, "dpitch": -0.39, "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: [-84.66, 29.2, 20.0, -47.79, 153.38, 0.0]
  Target bbox: [619.94, 323.03, 660.3, 395.99]

Frame 2:
  Drone pose: [-85.29, 29.3, 20.0, -47.69, 152.0, 0.0]
  Target bbox: [620.34, 322.5, 659.98, 396.67]

Frame 3:
  Drone pose: [-85.93, 29.42, 20.0, -47.59, 150.67, 0.0]
  Target bbox: [620.03, 322.44, 660.32, 396.74]

Frame 4:
  Drone pose: [-86.57, 29.55, 20.0, -47.48, 149.4, 0.0]
  Target bbox: [620.2, 322.49, 660.13, 396.61]

Frame 5 (current):
  Drone pose: [-87.21, 29.7, 20.0, -47.37, 148.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.45, "ymin": 324.65, "xmax": 656.82, "ymax": 394.42}, "waypoint_deltas": [{"dx": -0.62, "dy": 0.16, "dz": 0.0, "dpitch": 0.12, "dyaw": -1.16, "droll": 0.0}, {"dx": -1.24, "dy": 0.33, "dz": 0.0, "dpitch": 0.26, "dyaw": -2.26, "droll": 0.0}, {"dx": -1.86, "dy": 0.5, "dz": 0.0, "dpitch": 0.4, "dyaw": -3.36, "droll": 0.0}, {"dx": -2.51, "dy": 0.67, "dz": 0.0, "dpitch": 0.51, "dyaw": -4.49, "droll": 0.0}, {"dx": -3.2, "dy": 0.85, "dz": 0.0, "dpitch": 0.58, "dyaw": -5.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: [-94.55, 32.47, 20.0, -47.09, 137.48, 0.0]
  Target bbox: [622.46, 324.41, 657.96, 394.73]

Frame 2:
  Drone pose: [-95.14, 32.88, 20.0, -47.1, 137.07, 0.0]
  Target bbox: [623.91, 324.34, 656.46, 394.68]

Frame 3:
  Drone pose: [-95.71, 33.28, 20.0, -47.06, 136.68, 0.0]
  Target bbox: [623.28, 325.41, 657.07, 393.58]

Frame 4:
  Drone pose: [-96.25, 33.66, 20.0, -46.98, 136.31, 0.0]
  Target bbox: [623.72, 325.73, 656.64, 393.33]

Frame 5 (current):
  Drone pose: [-96.78, 34.03, 20.0, -46.86, 135.94, 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.95, "ymin": 324.39, "xmax": 657.47, "ymax": 394.73}, "waypoint_deltas": [{"dx": -0.51, "dy": 0.36, "dz": 0.0, "dpitch": 0.14, "dyaw": -0.35, "droll": 0.0}, {"dx": -1.03, "dy": 0.72, "dz": 0.0, "dpitch": 0.28, "dyaw": -0.7, "droll": 0.0}, {"dx": -1.54, "dy": 1.08, "dz": 0.0, "dpitch": 0.41, "dyaw": -1.05, "droll": 0.0}, {"dx": -2.07, "dy": 1.45, "dz": 0.0, "dpitch": 0.53, "dyaw": -1.4, "droll": 0.0}, {"dx": -2.6, "dy": 1.82, "dz": 0.0, "dpitch": 0.64, "dyaw": -1.75, "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.26, 38.94, 20.0, -45.08, 136.82, 0.0]
  Target bbox: [626.34, 325.74, 653.97, 393.45]

Frame 2:
  Drone pose: [-101.57, 39.46, 20.0, -44.89, 137.24, 0.0]
  Target bbox: [624.01, 327.98, 656.27, 391.14]

Frame 3:
  Drone pose: [-101.88, 39.97, 20.0, -44.7, 137.65, 0.0]
  Target bbox: [626.33, 328.5, 653.91, 390.65]

Frame 4:
  Drone pose: [-102.19, 40.49, 20.0, -44.51, 138.05, 0.0]
  Target bbox: [625.13, 326.75, 655.18, 392.47]

Frame 5 (current):
  Drone pose: [-102.51, 41.0, 20.0, -44.32, 138.45, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 624.19, "ymin": 328.41, "xmax": 656.06, "ymax": 390.74}, "waypoint_deltas": [{"dx": -0.31, "dy": 0.52, "dz": 0.0, "dpitch": 0.19, "dyaw": 0.4, "droll": 0.0}, {"dx": -0.62, "dy": 1.03, "dz": 0.0, "dpitch": 0.38, "dyaw": 0.79, "droll": 0.0}, {"dx": -0.93, "dy": 1.55, "dz": 0.0, "dpitch": 0.8, "dyaw": 1.18, "droll": 0.0}, {"dx": -1.24, "dy": 2.06, "dz": 0.0, "dpitch": 0.54, "dyaw": 2.67, "droll": 0.0}, {"dx": -1.56, "dy": 2.58, "dz": 0.0, "dpitch": 0.29, "dyaw": 4.19, "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: [-52.49, 62.23, 22.03, -49.3, -99.25, 0.0]
  Target bbox: [617.83, 325.23, 662.04, 393.92]

Frame 2:
  Drone pose: [-53.35, 60.97, 21.29, -43.02, -91.04, 0.0]
  Target bbox: [612.2, 333.04, 637.85, 392.62]

Frame 3:
  Drone pose: [-53.29, 60.41, 20.62, -43.74, -92.85, 0.0]
  Target bbox: [623.18, 328.59, 657.02, 390.73]

Frame 4:
  Drone pose: [-53.54, 59.82, 20.64, -48.58, -90.21, 0.0]
  Target bbox: [619.14, 327.5, 660.76, 391.41]

Frame 5 (current):
  Drone pose: [-53.55, 59.29, 20.62, -48.48, -84.06, 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.04, "ymin": 341.63, "xmax": 609.91, "ymax": 411.64}, "waypoint_deltas": [{"dx": 0.2, "dy": -0.44, "dz": -0.03, "dpitch": -0.79, "dyaw": -3.43, "droll": 0.0}, {"dx": 0.41, "dy": -0.93, "dz": -0.05, "dpitch": -0.75, "dyaw": -4.13, "droll": 0.0}, {"dx": 0.61, "dy": -1.5, "dz": -0.07, "dpitch": -0.83, "dyaw": -4.81, "droll": 0.0}, {"dx": 0.83, "dy": -2.14, "dz": -0.09, "dpitch": -1.05, "dyaw": -5.57, "droll": 0.0}, {"dx": 1.1, "dy": -2.88, "dz": -0.2, "dpitch": -1.27, "dyaw": -8.24, "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: [-49.49, 50.7, 20.24, -47.59, -117.22, 0.0]
  Target bbox: [665.13, 402.88, 718.9, 481.47]

Frame 2:
  Drone pose: [-49.01, 49.75, 20.22, -49.17, -114.73, 0.0]
  Target bbox: [620.3, 386.65, 661.27, 453.52]

Frame 3:
  Drone pose: [-48.48, 48.91, 20.07, -54.12, -107.92, 0.0]
  Target bbox: [615.36, 320.74, 664.5, 397.87]

Frame 4:
  Drone pose: [-48.31, 48.06, 20.17, -57.41, -123.32, 0.0]
  Target bbox: [670.82, 255.65, 710.77, 327.98]

Frame 5 (current):
  Drone pose: [-48.1, 47.24, 20.32, -56.61, -113.87, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 611.54, "ymin": 318.21, "xmax": 668.59, "ymax": 400.38}, "waypoint_deltas": [{"dx": 0.11, "dy": -0.54, "dz": -0.18, "dpitch": 3.28, "dyaw": -10.78, "droll": 0.0}, {"dx": 0.17, "dy": -1.13, "dz": -0.2, "dpitch": 3.02, "dyaw": -13.97, "droll": 0.0}, {"dx": 0.17, "dy": -1.68, "dz": -0.22, "dpitch": 2.84, "dyaw": -16.97, "droll": 0.0}, {"dx": 0.14, "dy": -2.2, "dz": -0.23, "dpitch": 2.72, "dyaw": -19.84, "droll": 0.0}, {"dx": 0.1, "dy": -2.71, "dz": -0.24, "dpitch": 2.66, "dyaw": -22.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: [-48.56, 41.37, 20.03, -57.87, -148.61, 0.0]
  Target bbox: [572.99, 241.64, 620.24, 326.5]

Frame 2:
  Drone pose: [-48.75, 40.88, 20.03, -50.73, -150.23, 0.0]
  Target bbox: [567.97, 363.69, 610.57, 441.64]

Frame 3:
  Drone pose: [-48.98, 40.41, 20.02, -57.29, -162.4, 0.0]
  Target bbox: [668.65, 247.43, 714.18, 333.17]

Frame 4:
  Drone pose: [-49.24, 39.98, 20.02, -47.95, -159.89, 0.0]
  Target bbox: [621.21, 400.72, 670.08, 486.49]

Frame 5 (current):
  Drone pose: [-49.57, 39.76, 20.05, -57.87, -154.07, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 589.82, "ymin": 238.66, "xmax": 631.68, "ymax": 312.89}, "waypoint_deltas": [{"dx": -0.28, "dy": -0.54, "dz": -0.04, "dpitch": 5.16, "dyaw": -8.67, "droll": 0.0}, {"dx": -0.62, "dy": -0.87, "dz": -0.04, "dpitch": 5.28, "dyaw": -10.11, "droll": 0.0}, {"dx": -0.98, "dy": -1.18, "dz": -0.04, "dpitch": 5.4, "dyaw": -11.42, "droll": 0.0}, {"dx": -1.34, "dy": -1.46, "dz": -0.04, "dpitch": 5.52, "dyaw": -12.62, "droll": 0.0}, {"dx": -1.72, "dy": -1.72, "dz": -0.04, "dpitch": 5.64, "dyaw": -13.74, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-53.66, 36.7, 20.0, -48.55, -171.03, 0.0]
  Target bbox: [599.89, 373.43, 631.94, 444.27]

Frame 2:
  Drone pose: [-54.04, 36.5, 20.0, -49.82, -179.11, 0.0]
  Target bbox: [677.85, 350.64, 708.17, 421.12]

Frame 3:
  Drone pose: [-54.41, 36.31, 20.0, -49.34, -169.98, 0.0]
  Target bbox: [570.78, 353.89, 605.29, 427.04]

Frame 4:
  Drone pose: [-54.77, 36.12, 20.0, -48.16, -170.63, 0.0]
  Target bbox: [570.35, 368.89, 603.21, 444.42]

Frame 5 (current):
  Drone pose: [-55.13, 35.93, 20.0, -50.63, -176.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": 626.22, "ymin": 324.08, "xmax": 654.08, "ymax": 394.73}, "waypoint_deltas": [{"dx": -0.35, "dy": -0.18, "dz": 0.0, "dpitch": 0.25, "dyaw": -0.7, "droll": 0.0}, {"dx": -0.69, "dy": -0.36, "dz": 0.0, "dpitch": 0.52, "dyaw": -1.39, "droll": 0.0}, {"dx": -1.05, "dy": -0.53, "dz": 0.0, "dpitch": 0.76, "dyaw": -2.01, "droll": 0.0}, {"dx": -1.39, "dy": -0.69, "dz": 0.0, "dpitch": 1.03, "dyaw": -2.59, "droll": 0.0}, {"dx": -1.76, "dy": -0.82, "dz": 0.0, "dpitch": 1.26, "dyaw": -3.07, "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: [-58.63, 34.15, 19.89, -46.92, 179.2, 0.0]
  Target bbox: [556.9, 252.85, 599.25, 329.61]

Frame 2:
  Drone pose: [-58.95, 34.0, 20.0, -41.9, 180.73, 0.0]
  Target bbox: [582.08, 406.63, 609.44, 482.88]

Frame 3:
  Drone pose: [-59.23, 33.67, 20.0, -51.51, 179.12, 0.0]
  Target bbox: [587.24, 237.3, 617.63, 315.17]

Frame 4:
  Drone pose: [-59.67, 33.22, 20.0, -50.27, 169.54, 0.0]
  Target bbox: [681.94, 259.2, 713.53, 332.44]

Frame 5 (current):
  Drone pose: [-60.32, 32.66, 20.0, -46.08, 177.68, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 566.66, "ymin": 332.56, "xmax": 596.82, "ymax": 404.67}, "waypoint_deltas": [{"dx": -0.79, "dy": -0.57, "dz": 0.0, "dpitch": -0.76, "dyaw": -6.95, "droll": 0.0}, {"dx": -1.62, "dy": -1.07, "dz": 0.0, "dpitch": -1.14, "dyaw": -8.73, "droll": 0.0}, {"dx": -2.41, "dy": -1.44, "dz": 0.0, "dpitch": -1.49, "dyaw": -10.11, "droll": 0.0}, {"dx": -3.13, "dy": -1.67, "dz": 0.0, "dpitch": -1.74, "dyaw": -11.04, "droll": 0.0}, {"dx": -3.76, "dy": -1.81, "dz": 0.0, "dpitch": -1.91, "dyaw": -11.59, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-67.57, 30.81, 20.0, -50.1, 163.35, 0.0]
  Target bbox: [651.55, 285.24, 688.06, 362.82]

Frame 2:
  Drone pose: [-68.06, 30.79, 20.0, -43.73, 165.32, 0.0]
  Target bbox: [630.12, 394.35, 662.98, 465.63]

Frame 3:
  Drone pose: [-68.55, 30.77, 20.0, -47.9, 165.84, 0.0]
  Target bbox: [624.57, 326.54, 655.25, 392.43]

Frame 4:
  Drone pose: [-69.03, 30.77, 20.0, -44.3, 160.86, 0.0]
  Target bbox: [677.38, 380.83, 715.81, 462.02]

Frame 5 (current):
  Drone pose: [-69.51, 30.79, 20.0, -49.73, 170.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": 566.34, "ymin": 293.34, "xmax": 599.87, "ymax": 366.28}, "waypoint_deltas": [{"dx": -0.47, "dy": 0.03, "dz": 0.0, "dpitch": 1.92, "dyaw": -4.87, "droll": 0.0}, {"dx": -0.94, "dy": 0.06, "dz": 0.0, "dpitch": 1.95, "dyaw": -4.77, "droll": 0.0}, {"dx": -1.42, "dy": 0.06, "dz": 0.0, "dpitch": 1.98, "dyaw": -4.73, "droll": 0.0}, {"dx": -1.91, "dy": 0.05, "dz": 0.0, "dpitch": 2.0, "dyaw": -4.76, "droll": 0.0}, {"dx": -2.4, "dy": 0.04, "dz": 0.0, "dpitch": 2.02, "dyaw": -4.8, "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: [-75.87, 30.91, 20.0, -47.72, 163.84, 0.0]
  Target bbox: [653.49, 322.47, 686.03, 395.77]

Frame 2:
  Drone pose: [-76.42, 31.05, 19.95, -51.28, 165.23, 0.0]
  Target bbox: [623.49, 324.97, 656.31, 393.76]

Frame 3:
  Drone pose: [-76.9, 30.8, 20.0, -47.08, 171.09, 0.0]
  Target bbox: [565.1, 331.79, 600.63, 411.03]

Frame 4:
  Drone pose: [-77.44, 30.67, 20.0, -42.68, 166.9, 0.0]
  Target bbox: [608.02, 405.28, 641.96, 482.39]

Frame 5 (current):
  Drone pose: [-77.99, 30.49, 20.0, -47.69, 164.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": 623.19, "ymin": 322.2, "xmax": 656.48, "ymax": 396.92}, "waypoint_deltas": [{"dx": -0.57, "dy": -0.21, "dz": 0.0, "dpitch": -0.02, "dyaw": -0.74, "droll": 0.0}, {"dx": -1.15, "dy": -0.44, "dz": 0.0, "dpitch": -0.03, "dyaw": -1.55, "droll": 0.0}, {"dx": -1.73, "dy": -0.68, "dz": 0.0, "dpitch": -0.06, "dyaw": -2.38, "droll": 0.0}, {"dx": -2.33, "dy": -0.9, "dz": 0.0, "dpitch": -0.32, "dyaw": -3.18, "droll": 0.0}, {"dx": -2.93, "dy": -1.09, "dz": 0.0, "dpitch": -0.39, "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: [-84.66, 29.2, 20.0, -42.79, 154.37, 0.0]
  Target bbox: [610.4, 407.37, 647.1, 480.07]

Frame 2:
  Drone pose: [-85.29, 29.3, 20.0, -51.05, 147.89, 0.0]
  Target bbox: [667.56, 267.09, 706.6, 341.56]

Frame 3:
  Drone pose: [-85.93, 29.42, 20.0, -49.82, 148.49, 0.0]
  Target bbox: [651.16, 287.33, 679.16, 357.53]

Frame 4:
  Drone pose: [-86.52, 29.52, 20.06, -48.38, 155.71, 0.0]
  Target bbox: [617.5, 318.0, 662.06, 401.3]

Frame 5 (current):
  Drone pose: [-87.21, 29.7, 20.0, -50.49, 153.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": 563.52, "ymin": 272.64, "xmax": 602.05, "ymax": 345.51}, "waypoint_deltas": [{"dx": -0.62, "dy": 0.16, "dz": 0.0, "dpitch": 3.24, "dyaw": -6.16, "droll": 0.0}, {"dx": -1.24, "dy": 0.33, "dz": 0.0, "dpitch": 3.38, "dyaw": -7.26, "droll": 0.0}, {"dx": -1.86, "dy": 0.5, "dz": 0.0, "dpitch": 3.52, "dyaw": -8.36, "droll": 0.0}, {"dx": -2.51, "dy": 0.67, "dz": 0.0, "dpitch": 3.63, "dyaw": -9.49, "droll": 0.0}, {"dx": -3.2, "dy": 0.85, "dz": 0.0, "dpitch": 3.7, "dyaw": -10.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: [-94.56, 32.48, 19.98, -41.76, 136.01, 0.0]
  Target bbox: [622.37, 326.42, 657.95, 392.99]

Frame 2:
  Drone pose: [-95.14, 32.88, 20.0, -46.13, 142.07, 0.0]
  Target bbox: [566.81, 342.36, 598.6, 413.02]

Frame 3:
  Drone pose: [-95.71, 33.28, 20.0, -50.4, 131.68, 0.0]
  Target bbox: [672.8, 264.48, 722.71, 346.31]

Frame 4:
  Drone pose: [-96.29, 33.64, 20.07, -54.29, 134.56, 0.0]
  Target bbox: [603.37, 254.71, 643.91, 330.26]

Frame 5 (current):
  Drone pose: [-96.78, 34.03, 20.0, -51.86, 137.32, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 611.21, "ymin": 241.42, "xmax": 636.73, "ymax": 309.79}, "waypoint_deltas": [{"dx": -0.51, "dy": 0.36, "dz": 0.0, "dpitch": 5.14, "dyaw": -1.73, "droll": 0.0}, {"dx": -1.03, "dy": 0.72, "dz": 0.0, "dpitch": 5.28, "dyaw": -2.08, "droll": 0.0}, {"dx": -1.54, "dy": 1.08, "dz": 0.0, "dpitch": 5.41, "dyaw": -2.43, "droll": 0.0}, {"dx": -2.07, "dy": 1.45, "dz": 0.0, "dpitch": 5.53, "dyaw": -2.78, "droll": 0.0}, {"dx": -2.6, "dy": 1.82, "dz": 0.0, "dpitch": 5.64, "dyaw": -3.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: [-101.26, 38.94, 20.0, -45.08, 136.82, 0.0]
  Target bbox: [625.91, 325.47, 654.42, 393.71]

Frame 2:
  Drone pose: [-101.57, 39.46, 20.0, -44.89, 137.24, 0.0]
  Target bbox: [623.15, 324.91, 657.26, 394.32]

Frame 3:
  Drone pose: [-101.88, 39.97, 20.0, -44.7, 137.65, 0.0]
  Target bbox: [625.64, 325.36, 654.69, 393.86]

Frame 4:
  Drone pose: [-102.19, 40.49, 20.0, -44.67, 137.14, 0.0]
  Target bbox: [636.41, 322.74, 666.32, 391.27]

Frame 5 (current):
  Drone pose: [-102.51, 41.0, 20.0, -44.32, 138.45, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 623.47, "ymin": 325.39, "xmax": 656.92, "ymax": 393.92}, "waypoint_deltas": [{"dx": -0.31, "dy": 0.52, "dz": 0.0, "dpitch": 0.19, "dyaw": 0.4, "droll": 0.0}, {"dx": -0.62, "dy": 1.03, "dz": 0.0, "dpitch": 0.38, "dyaw": 0.79, "droll": 0.0}, {"dx": -0.93, "dy": 1.55, "dz": 0.0, "dpitch": 0.8, "dyaw": 1.18, "droll": 0.0}, {"dx": -1.24, "dy": 2.06, "dz": 0.0, "dpitch": 0.54, "dyaw": 2.67, "droll": 0.0}, {"dx": -1.56, "dy": 2.58, "dz": 0.0, "dpitch": 0.29, "dyaw": 4.19, "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: [-114.57, 13.22, 22.0, -46.47, -81.47, 0.0]
  Target bbox: [618.92, 323.39, 660.93, 396.02]

Frame 2:
  Drone pose: [-115.43, 11.42, 21.2, -46.87, -76.82, 0.0]
  Target bbox: [620.56, 325.53, 659.77, 393.84]

Frame 3:
  Drone pose: [-115.56, 10.55, 20.67, -46.61, -76.2, 0.0]
  Target bbox: [620.79, 324.62, 659.04, 394.74]

Frame 4:
  Drone pose: [-115.65, 9.74, 20.64, -46.81, -74.19, 0.0]
  Target bbox: [618.34, 321.63, 661.41, 397.7]

Frame 5 (current):
  Drone pose: [-115.64, 9.04, 20.62, -46.83, -72.55, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 618.47, "ymin": 322.48, "xmax": 661.84, "ymax": 396.74}, "waypoint_deltas": [{"dx": 0.0, "dy": -0.7, "dz": -0.03, "dpitch": -0.27, "dyaw": 0.2, "droll": 0.0}, {"dx": 0.12, "dy": -1.22, "dz": -0.05, "dpitch": -0.32, "dyaw": -0.14, "droll": 0.0}, {"dx": 0.22, "dy": -1.73, "dz": -0.07, "dpitch": -0.36, "dyaw": -0.45, "droll": 0.0}, {"dx": 0.32, "dy": -2.24, "dz": -0.09, "dpitch": -0.38, "dyaw": -0.72, "droll": 0.0}, {"dx": 0.4, "dy": -2.75, "dz": -0.2, "dpitch": -0.27, "dyaw": -0.97, "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: [-115.1, 5.28, 20.36, -47.09, -73.95, 0.0]
  Target bbox: [620.01, 323.4, 660.32, 395.87]

Frame 2:
  Drone pose: [-115.03, 4.78, 20.33, -47.08, -74.13, 0.0]
  Target bbox: [617.69, 321.95, 662.66, 397.24]

Frame 3:
  Drone pose: [-114.98, 4.27, 20.3, -47.07, -74.29, 0.0]
  Target bbox: [617.78, 321.72, 662.56, 397.44]

Frame 4:
  Drone pose: [-114.95, 3.77, 20.27, -47.05, -74.4, 0.0]
  Target bbox: [620.02, 323.04, 660.32, 396.22]

Frame 5 (current):
  Drone pose: [-114.92, 3.26, 20.24, -47.03, -74.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": 617.48, "ymin": 321.57, "xmax": 662.87, "ymax": 397.59}, "waypoint_deltas": [{"dx": 0.01, "dy": -0.51, "dz": -0.02, "dpitch": 0.02, "dyaw": -0.02, "droll": 0.0}, {"dx": 0.0, "dy": -1.02, "dz": -0.05, "dpitch": 0.04, "dyaw": 0.0, "droll": 0.0}, {"dx": -0.02, "dy": -1.52, "dz": -0.07, "dpitch": 0.08, "dyaw": 0.06, "droll": 0.0}, {"dx": -0.04, "dy": -2.0, "dz": -0.09, "dpitch": 0.14, "dyaw": 0.12, "droll": 0.0}, {"dx": -0.06, "dy": -2.47, "dz": -0.1, "dpitch": 0.23, "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: [-115.0, -0.09, 20.1, -46.57, -74.36, 0.0]
  Target bbox: [617.08, 322.59, 663.28, 396.72]

Frame 2:
  Drone pose: [-115.0, -0.52, 20.09, -46.45, -74.41, 0.0]
  Target bbox: [617.74, 321.59, 662.61, 397.59]

Frame 3:
  Drone pose: [-115.0, -0.95, 20.08, -46.32, -74.47, 0.0]
  Target bbox: [615.67, 320.83, 664.71, 398.38]

Frame 4:
  Drone pose: [-114.99, -1.39, 20.07, -46.21, -74.55, 0.0]
  Target bbox: [618.48, 322.32, 661.87, 396.94]

Frame 5 (current):
  Drone pose: [-114.99, -1.85, 20.06, -46.14, -74.57, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 620.4, "ymin": 323.69, "xmax": 659.93, "ymax": 395.64}, "waypoint_deltas": [{"dx": 0.01, "dy": -0.47, "dz": -0.01, "dpitch": 0.06, "dyaw": -0.06, "droll": 0.0}, {"dx": 0.18, "dy": -0.85, "dz": -0.02, "dpitch": 0.18, "dyaw": -0.68, "droll": 0.0}, {"dx": 0.56, "dy": -1.24, "dz": -0.02, "dpitch": 0.21, "dyaw": -1.91, "droll": 0.0}, {"dx": 1.27, "dy": -1.53, "dz": -0.03, "dpitch": 0.3, "dyaw": -4.2, "droll": 0.0}, {"dx": 1.52, "dy": -2.34, "dz": -0.03, "dpitch": -0.09, "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: [-113.08, -5.67, 20.02, -46.74, -75.58, 0.0]
  Target bbox: [615.56, 319.84, 664.21, 399.54]

Frame 2:
  Drone pose: [-112.94, -6.37, 20.02, -46.88, -74.3, 0.0]
  Target bbox: [616.94, 319.61, 662.81, 399.64]

Frame 3:
  Drone pose: [-112.81, -7.03, 20.01, -46.96, -73.01, 0.0]
  Target bbox: [619.3, 322.63, 660.5, 396.63]

Frame 4:
  Drone pose: [-112.48, -7.63, 20.01, -47.02, -72.38, 0.0]
  Target bbox: [620.24, 323.25, 659.54, 396.02]

Frame 5 (current):
  Drone pose: [-112.16, -8.23, 20.01, -47.09, -71.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": 617.72, "ymin": 320.41, "xmax": 662.01, "ymax": 398.83}, "waypoint_deltas": [{"dx": 0.31, "dy": -0.62, "dz": 0.0, "dpitch": -0.09, "dyaw": 0.71, "droll": 0.0}, {"dx": 0.59, "dy": -1.26, "dz": 0.0, "dpitch": -0.18, "dyaw": 1.54, "droll": 0.0}, {"dx": 0.84, "dy": -1.92, "dz": -0.01, "dpitch": -0.28, "dyaw": 2.49, "droll": 0.0}, {"dx": 1.05, "dy": -2.6, "dz": -0.01, "dpitch": -0.38, "dyaw": 3.57, "droll": 0.0}, {"dx": 1.24, "dy": -3.28, "dz": -0.01, "dpitch": -0.46, "dyaw": 4.74, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-110.59, -12.88, 20.0, -47.64, -64.5, 0.0]
  Target bbox: [618.3, 320.03, 661.34, 399.11]

Frame 2:
  Drone pose: [-110.43, -13.55, 20.0, -47.65, -63.25, 0.0]
  Target bbox: [619.5, 321.45, 660.17, 397.7]

Frame 3:
  Drone pose: [-110.26, -14.21, 20.0, -47.63, -62.03, 0.0]
  Target bbox: [619.62, 321.85, 660.03, 397.36]

Frame 4:
  Drone pose: [-110.09, -14.85, 20.0, -47.58, -60.84, 0.0]
  Target bbox: [620.92, 323.49, 658.78, 395.66]

Frame 5 (current):
  Drone pose: [-109.91, -15.5, 20.0, -47.52, -59.68, 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.14, "ymin": 324.24, "xmax": 657.56, "ymax": 394.97}, "waypoint_deltas": [{"dx": 0.17, "dy": -0.63, "dz": 0.0, "dpitch": 0.09, "dyaw": 1.14, "droll": 0.0}, {"dx": 0.35, "dy": -1.25, "dz": 0.0, "dpitch": 0.19, "dyaw": 2.24, "droll": 0.0}, {"dx": 0.53, "dy": -1.86, "dz": 0.0, "dpitch": 0.33, "dyaw": 3.31, "droll": 0.0}, {"dx": 0.71, "dy": -2.48, "dz": 0.0, "dpitch": 0.45, "dyaw": 4.38, "droll": 0.0}, {"dx": 0.89, "dy": -3.1, "dz": 0.0, "dpitch": 0.6, "dyaw": 5.43, "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.6, -19.81, 20.0, -47.12, -53.64, 0.0]
  Target bbox: [621.81, 322.92, 657.8, 396.23]

Frame 2:
  Drone pose: [-108.34, -20.4, 20.0, -47.0, -52.82, 0.0]
  Target bbox: [620.08, 322.76, 659.49, 396.42]

Frame 3:
  Drone pose: [-108.06, -20.99, 20.0, -46.89, -52.09, 0.0]
  Target bbox: [623.35, 324.56, 656.31, 394.58]

Frame 4:
  Drone pose: [-107.76, -21.56, 20.0, -46.8, -51.44, 0.0]
  Target bbox: [618.79, 322.46, 660.74, 396.66]

Frame 5 (current):
  Drone pose: [-107.44, -22.13, 20.0, -46.7, -50.87, 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.83, "ymin": 325.35, "xmax": 655.83, "ymax": 393.85}, "waypoint_deltas": [{"dx": 0.35, "dy": -0.56, "dz": 0.0, "dpitch": 0.08, "dyaw": 0.51, "droll": 0.0}, {"dx": 0.71, "dy": -1.12, "dz": 0.0, "dpitch": 0.38, "dyaw": 0.97, "droll": 0.0}, {"dx": 1.09, "dy": -1.67, "dz": 0.0, "dpitch": 0.45, "dyaw": 1.36, "droll": 0.0}, {"dx": 1.48, "dy": -2.21, "dz": 0.0, "dpitch": 0.51, "dyaw": 1.7, "droll": 0.0}, {"dx": 1.89, "dy": -2.74, "dz": 0.0, "dpitch": 0.57, "dyaw": 1.98, "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: [-104.71, -25.9, 20.0, -46.01, -48.45, 0.0]
  Target bbox: [620.2, 323.47, 659.35, 395.62]

Frame 2:
  Drone pose: [-104.28, -26.41, 20.0, -45.94, -48.28, 0.0]
  Target bbox: [622.73, 323.29, 656.86, 395.83]

Frame 3:
  Drone pose: [-103.85, -26.9, 20.0, -45.86, -48.12, 0.0]
  Target bbox: [619.5, 323.33, 660.03, 395.79]

Frame 4:
  Drone pose: [-103.44, -27.38, 20.0, -45.75, -47.95, 0.0]
  Target bbox: [622.74, 325.11, 656.88, 394.05]

Frame 5 (current):
  Drone pose: [-103.05, -27.86, 20.0, -45.61, -47.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": 621.08, "ymin": 323.73, "xmax": 658.45, "ymax": 395.47}, "waypoint_deltas": [{"dx": 0.36, "dy": -0.47, "dz": 0.0, "dpitch": 0.19, "dyaw": 0.26, "droll": 0.0}, {"dx": 0.67, "dy": -0.93, "dz": 0.0, "dpitch": 0.42, "dyaw": 0.58, "droll": 0.0}, {"dx": 0.95, "dy": -1.38, "dz": 0.0, "dpitch": 0.19, "dyaw": -0.15, "droll": 0.0}, {"dx": 1.21, "dy": -1.83, "dz": 0.0, "dpitch": 0.5, "dyaw": 0.3, "droll": 0.0}, {"dx": 1.45, "dy": -2.28, "dz": 0.0, "dpitch": 0.3, "dyaw": -0.34, "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.11, -31.08, 20.0, -45.23, -48.2, 0.0]
  Target bbox: [615.43, 319.77, 664.58, 399.7]

Frame 2:
  Drone pose: [-100.84, -31.56, 20.0, -45.47, -48.84, 0.0]
  Target bbox: [624.81, 325.98, 654.86, 393.25]

Frame 3:
  Drone pose: [-100.57, -32.06, 20.0, -45.24, -48.32, 0.0]
  Target bbox: [615.71, 319.6, 664.3, 399.82]

Frame 4:
  Drone pose: [-100.28, -32.55, 20.0, -45.53, -48.99, 0.0]
  Target bbox: [620.91, 323.99, 658.67, 395.15]

Frame 5 (current):
  Drone pose: [-99.98, -33.06, 20.0, -45.34, -48.51, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 616.95, "ymin": 320.96, "xmax": 663.11, "ymax": 398.47}, "waypoint_deltas": [{"dx": 0.28, "dy": -0.51, "dz": 0.0, "dpitch": -0.29, "dyaw": -0.63, "droll": 0.0}, {"dx": 0.56, "dy": -1.01, "dz": 0.0, "dpitch": -0.06, "dyaw": -0.13, "droll": 0.0}, {"dx": 0.83, "dy": -1.5, "dz": 0.0, "dpitch": -0.56, "dyaw": -0.78, "droll": 0.0}, {"dx": 1.09, "dy": -2.0, "dz": 0.0, "dpitch": -0.32, "dyaw": -0.23, "droll": 0.0}, {"dx": 1.34, "dy": -2.48, "dz": 0.0, "dpitch": -0.54, "dyaw": -0.86, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-98.17, -36.46, 20.0, -45.77, -49.44, 0.0]
  Target bbox: [616.46, 321.57, 663.6, 397.93]

Frame 2:
  Drone pose: [-97.94, -36.92, 20.0, -45.94, -50.06, 0.0]
  Target bbox: [619.46, 323.13, 660.08, 396.04]

Frame 3:
  Drone pose: [-97.73, -37.37, 20.0, -45.6, -49.5, 0.0]
  Target bbox: [616.93, 321.17, 663.13, 398.26]

Frame 4:
  Drone pose: [-97.51, -37.82, 20.0, -45.76, -50.1, 0.0]
  Target bbox: [623.7, 324.45, 655.94, 394.74]

Frame 5 (current):
  Drone pose: [-97.28, -38.28, 20.0, -45.44, -49.55, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 615.71, "ymin": 319.86, "xmax": 664.35, "ymax": 399.58}, "waypoint_deltas": [{"dx": 0.25, "dy": -0.46, "dz": 0.0, "dpitch": -0.2, "dyaw": -0.65, "droll": 0.0}, {"dx": 0.53, "dy": -0.93, "dz": 0.0, "dpitch": -0.43, "dyaw": -1.39, "droll": 0.0}, {"dx": 0.85, "dy": -1.39, "dz": 0.0, "dpitch": -0.22, "dyaw": -1.03, "droll": 0.0}, {"dx": 1.22, "dy": -1.86, "dz": 0.0, "dpitch": -0.05, "dyaw": -0.77, "droll": 0.0}, {"dx": 1.61, "dy": -2.33, "dz": 0.0, "dpitch": 0.09, "dyaw": -0.59, "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.87, -41.55, 20.0, -45.09, -49.79, 0.0]
  Target bbox: [623.22, 323.23, 656.38, 395.99]

Frame 2:
  Drone pose: [-94.51, -42.04, 20.0, -44.93, -49.5, 0.0]
  Target bbox: [624.43, 326.21, 655.25, 393.04]

Frame 3:
  Drone pose: [-94.21, -42.53, 20.0, -44.73, -49.05, 0.0]
  Target bbox: [622.97, 325.23, 656.64, 394.11]

Frame 4:
  Drone pose: [-93.99, -43.03, 20.0, -44.47, -48.43, 0.0]
  Target bbox: [624.58, 326.31, 655.08, 393.01]

Frame 5 (current):
  Drone pose: [-93.83, -43.54, 20.0, -44.14, -47.69, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 615.47, "ymin": 319.95, "xmax": 664.54, "ymax": 399.61}, "waypoint_deltas": [{"dx": 0.11, "dy": -0.48, "dz": 0.0, "dpitch": -0.09, "dyaw": -0.25, "droll": 0.0}, {"dx": 0.18, "dy": -0.96, "dz": 0.0, "dpitch": -0.12, "dyaw": -0.45, "droll": 0.0}, {"dx": 0.22, "dy": -1.41, "dz": 0.0, "dpitch": -0.11, "dyaw": -0.62, "droll": 0.0}, {"dx": 0.23, "dy": -1.85, "dz": 0.0, "dpitch": -0.06, "dyaw": -0.76, "droll": 0.0}, {"dx": 0.21, "dy": -2.28, "dz": 0.0, "dpitch": 0.04, "dyaw": -0.87, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-114.57, 13.22, 22.0, -42.55, -86.47, 0.0]
  Target bbox: [674.4, 390.1, 722.34, 464.91]

Frame 2:
  Drone pose: [-115.32, 11.32, 21.16, -50.4, -76.0, 0.0]
  Target bbox: [607.57, 267.13, 647.32, 337.91]

Frame 3:
  Drone pose: [-115.57, 10.61, 20.77, -46.66, -76.21, 0.0]
  Target bbox: [618.09, 321.78, 661.7, 397.57]

Frame 4:
  Drone pose: [-115.65, 9.74, 20.64, -47.18, -75.47, 0.0]
  Target bbox: [630.37, 314.16, 679.54, 393.07]

Frame 5 (current):
  Drone pose: [-115.64, 9.04, 20.62, -44.17, -74.7, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 643.5, "ymin": 367.86, "xmax": 687.29, "ymax": 441.36}, "waypoint_deltas": [{"dx": 0.0, "dy": -0.7, "dz": -0.03, "dpitch": -2.93, "dyaw": 2.35, "droll": 0.0}, {"dx": 0.12, "dy": -1.22, "dz": -0.05, "dpitch": -2.98, "dyaw": 2.01, "droll": 0.0}, {"dx": 0.22, "dy": -1.73, "dz": -0.07, "dpitch": -3.02, "dyaw": 1.7, "droll": 0.0}, {"dx": 0.32, "dy": -2.24, "dz": -0.09, "dpitch": -3.04, "dyaw": 1.43, "droll": 0.0}, {"dx": 0.4, "dy": -2.75, "dz": -0.2, "dpitch": -2.93, "dyaw": 1.18, "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: [-115.1, 5.28, 20.36, -43.73, -73.45, 0.0]
  Target bbox: [614.21, 380.23, 654.3, 452.11]

Frame 2:
  Drone pose: [-114.92, 4.73, 20.29, -43.12, -78.66, 0.0]
  Target bbox: [668.49, 392.82, 709.31, 464.71]

Frame 3:
  Drone pose: [-114.98, 4.27, 20.3, -45.95, -79.29, 0.0]
  Target bbox: [675.05, 343.32, 720.71, 416.89]

Frame 4:
  Drone pose: [-114.82, 3.89, 20.24, -46.87, -74.88, 0.0]
  Target bbox: [617.66, 321.79, 662.7, 397.39]

Frame 5 (current):
  Drone pose: [-114.85, 3.32, 20.24, -48.06, -69.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": 560.3, "ymin": 305.62, "xmax": 604.46, "ymax": 380.68}, "waypoint_deltas": [{"dx": -0.06, "dy": -0.57, "dz": -0.02, "dpitch": 1.05, "dyaw": -4.74, "droll": 0.0}, {"dx": -0.07, "dy": -1.08, "dz": -0.05, "dpitch": 1.07, "dyaw": -4.72, "droll": 0.0}, {"dx": -0.09, "dy": -1.58, "dz": -0.07, "dpitch": 1.11, "dyaw": -4.66, "droll": 0.0}, {"dx": -0.11, "dy": -2.06, "dz": -0.09, "dpitch": 1.17, "dyaw": -4.6, "droll": 0.0}, {"dx": -0.13, "dy": -2.53, "dz": -0.1, "dpitch": 1.26, "dyaw": -4.57, "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: [-115.0, -0.09, 20.1, -46.57, -74.36, 0.0]
  Target bbox: [620.19, 323.58, 660.14, 395.73]

Frame 2:
  Drone pose: [-115.0, -0.52, 20.09, -50.38, -74.66, 0.0]
  Target bbox: [618.72, 254.71, 667.61, 332.31]

Frame 3:
  Drone pose: [-114.85, -0.89, 20.13, -46.36, -74.96, 0.0]
  Target bbox: [615.56, 321.84, 664.81, 397.43]

Frame 4:
  Drone pose: [-114.97, -1.47, 20.18, -46.51, -74.54, 0.0]
  Target bbox: [615.39, 321.47, 664.98, 397.77]

Frame 5 (current):
  Drone pose: [-114.99, -1.85, 20.06, -46.14, -74.57, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 620.36, "ymin": 323.83, "xmax": 659.97, "ymax": 395.52}, "waypoint_deltas": [{"dx": 0.01, "dy": -0.47, "dz": -0.01, "dpitch": 0.06, "dyaw": -0.06, "droll": 0.0}, {"dx": 0.18, "dy": -0.85, "dz": -0.02, "dpitch": 0.18, "dyaw": -0.68, "droll": 0.0}, {"dx": 0.56, "dy": -1.24, "dz": -0.02, "dpitch": 0.21, "dyaw": -1.91, "droll": 0.0}, {"dx": 1.27, "dy": -1.53, "dz": -0.03, "dpitch": 0.3, "dyaw": -4.2, "droll": 0.0}, {"dx": 1.52, "dy": -2.34, "dz": -0.03, "dpitch": -0.09, "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: [-113.08, -5.67, 20.02, -47.98, -71.67, 0.0]
  Target bbox: [572.95, 303.04, 615.78, 376.95]

Frame 2:
  Drone pose: [-112.94, -6.37, 20.02, -48.27, -77.55, 0.0]
  Target bbox: [654.8, 297.78, 700.57, 376.52]

Frame 3:
  Drone pose: [-112.76, -6.9, 19.87, -44.95, -78.28, 0.0]
  Target bbox: [676.67, 351.12, 719.49, 426.22]

Frame 4:
  Drone pose: [-112.48, -7.63, 20.01, -42.02, -71.08, 0.0]
  Target bbox: [602.65, 405.83, 646.5, 481.99]

Frame 5 (current):
  Drone pose: [-112.27, -8.29, 20.1, -47.61, -67.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": 571.85, "ymin": 315.39, "xmax": 616.74, "ymax": 394.46}, "waypoint_deltas": [{"dx": 0.42, "dy": -0.56, "dz": -0.09, "dpitch": 0.43, "dyaw": -3.65, "droll": 0.0}, {"dx": 0.7, "dy": -1.2, "dz": -0.09, "dpitch": 0.34, "dyaw": -2.82, "droll": 0.0}, {"dx": 0.95, "dy": -1.86, "dz": -0.1, "dpitch": 0.24, "dyaw": -1.87, "droll": 0.0}, {"dx": 1.16, "dy": -2.54, "dz": -0.1, "dpitch": 0.14, "dyaw": -0.79, "droll": 0.0}, {"dx": 1.35, "dy": -3.22, "dz": -0.1, "dpitch": 0.06, "dyaw": 0.38, "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: [-110.59, -12.88, 20.0, -48.98, -60.29, 0.0]
  Target bbox: [571.93, 301.67, 611.77, 375.2]

Frame 2:
  Drone pose: [-110.43, -13.55, 20.0, -43.06, -63.44, 0.0]
  Target bbox: [620.23, 398.75, 663.96, 474.93]

Frame 3:
  Drone pose: [-110.12, -14.3, 20.0, -47.88, -62.28, 0.0]
  Target bbox: [621.37, 323.57, 658.34, 395.6]

Frame 4:
  Drone pose: [-110.25, -14.82, 20.01, -48.21, -60.86, 0.0]
  Target bbox: [626.45, 310.66, 663.35, 382.41]

Frame 5 (current):
  Drone pose: [-110.05, -15.52, 20.14, -48.83, -55.59, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 579.83, "ymin": 305.49, "xmax": 616.08, "ymax": 375.89}, "waypoint_deltas": [{"dx": 0.31, "dy": -0.61, "dz": -0.14, "dpitch": 1.4, "dyaw": -2.95, "droll": 0.0}, {"dx": 0.49, "dy": -1.23, "dz": -0.14, "dpitch": 1.5, "dyaw": -1.85, "droll": 0.0}, {"dx": 0.67, "dy": -1.84, "dz": -0.14, "dpitch": 1.64, "dyaw": -0.78, "droll": 0.0}, {"dx": 0.85, "dy": -2.46, "dz": -0.14, "dpitch": 1.76, "dyaw": 0.29, "droll": 0.0}, {"dx": 1.03, "dy": -3.08, "dz": -0.14, "dpitch": 1.91, "dyaw": 1.34, "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.6, -19.81, 20.0, -43.6, -49.27, 0.0]
  Target bbox: [571.11, 385.24, 607.72, 454.78]

Frame 2:
  Drone pose: [-108.34, -20.4, 20.0, -45.08, -49.98, 0.0]
  Target bbox: [589.04, 355.46, 624.75, 429.43]

Frame 3:
  Drone pose: [-108.07, -20.99, 19.99, -42.41, -53.14, 0.0]
  Target bbox: [634.9, 399.18, 670.3, 470.43]

Frame 4:
  Drone pose: [-107.76, -21.56, 20.0, -46.8, -51.44, 0.0]
  Target bbox: [622.67, 324.01, 656.95, 395.17]

Frame 5 (current):
  Drone pose: [-107.43, -22.07, 20.04, -48.42, -49.83, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 608.99, "ymin": 293.7, "xmax": 643.12, "ymax": 367.22}, "waypoint_deltas": [{"dx": 0.34, "dy": -0.62, "dz": -0.04, "dpitch": 1.8, "dyaw": -0.53, "droll": 0.0}, {"dx": 0.7, "dy": -1.18, "dz": -0.04, "dpitch": 2.1, "dyaw": -0.07, "droll": 0.0}, {"dx": 1.08, "dy": -1.73, "dz": -0.04, "dpitch": 2.17, "dyaw": 0.32, "droll": 0.0}, {"dx": 1.47, "dy": -2.27, "dz": -0.04, "dpitch": 2.23, "dyaw": 0.66, "droll": 0.0}, {"dx": 1.88, "dy": -2.8, "dz": -0.04, "dpitch": 2.29, "dyaw": 0.94, "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: [-104.8, -25.85, 19.86, -45.64, -48.36, 0.0]
  Target bbox: [623.7, 325.33, 655.95, 393.84]

Frame 2:
  Drone pose: [-104.28, -26.41, 20.0, -45.94, -48.28, 0.0]
  Target bbox: [619.56, 323.14, 659.98, 395.93]

Frame 3:
  Drone pose: [-103.95, -26.87, 19.94, -46.36, -45.51, 0.0]
  Target bbox: [595.34, 314.18, 626.64, 381.64]

Frame 4:
  Drone pose: [-103.25, -27.41, 20.04, -46.03, -48.33, 0.0]
  Target bbox: [623.34, 325.31, 656.3, 393.84]

Frame 5 (current):
  Drone pose: [-103.05, -27.76, 19.95, -44.33, -44.01, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 578.1, "ymin": 345.45, "xmax": 608.27, "ymax": 412.49}, "waypoint_deltas": [{"dx": 0.36, "dy": -0.57, "dz": 0.05, "dpitch": -1.09, "dyaw": -3.47, "droll": 0.0}, {"dx": 0.67, "dy": -1.03, "dz": 0.05, "dpitch": -0.86, "dyaw": -3.15, "droll": 0.0}, {"dx": 0.95, "dy": -1.48, "dz": 0.05, "dpitch": -1.09, "dyaw": -3.88, "droll": 0.0}, {"dx": 1.21, "dy": -1.93, "dz": 0.05, "dpitch": -0.78, "dyaw": -3.43, "droll": 0.0}, {"dx": 1.45, "dy": -2.38, "dz": 0.05, "dpitch": -0.98, "dyaw": -4.07, "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.06, -31.18, 19.97, -47.58, -49.87, 0.0]
  Target bbox: [636.75, 282.22, 686.11, 362.9]

Frame 2:
  Drone pose: [-100.7, -31.47, 20.02, -48.04, -46.64, 0.0]
  Target bbox: [590.81, 282.83, 624.19, 353.75]

Frame 3:
  Drone pose: [-100.57, -32.06, 20.0, -45.24, -48.32, 0.0]
  Target bbox: [616.38, 320.38, 663.65, 399.05]

Frame 4:
  Drone pose: [-100.23, -32.59, 19.82, -45.35, -49.04, 0.0]
  Target bbox: [619.75, 323.11, 659.79, 396.0]

Frame 5 (current):
  Drone pose: [-99.94, -33.24, 19.96, -49.73, -47.14, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 603.45, "ymin": 250.83, "xmax": 649.95, "ymax": 327.13}, "waypoint_deltas": [{"dx": 0.24, "dy": -0.33, "dz": 0.04, "dpitch": 4.1, "dyaw": -2.0, "droll": 0.0}, {"dx": 0.52, "dy": -0.83, "dz": 0.04, "dpitch": 4.33, "dyaw": -1.5, "droll": 0.0}, {"dx": 0.79, "dy": -1.32, "dz": 0.04, "dpitch": 3.83, "dyaw": -2.15, "droll": 0.0}, {"dx": 1.05, "dy": -1.82, "dz": 0.04, "dpitch": 4.07, "dyaw": -1.6, "droll": 0.0}, {"dx": 1.3, "dy": -2.3, "dz": 0.04, "dpitch": 3.85, "dyaw": -2.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: [-98.08, -36.35, 20.1, -45.55, -48.82, 0.0]
  Target bbox: [603.93, 326.64, 650.7, 404.08]

Frame 2:
  Drone pose: [-98.03, -36.76, 19.95, -45.58, -50.18, 0.0]
  Target bbox: [624.43, 325.89, 655.25, 393.36]

Frame 3:
  Drone pose: [-97.73, -37.37, 20.0, -45.6, -49.5, 0.0]
  Target bbox: [617.19, 322.08, 662.88, 397.41]

Frame 4:
  Drone pose: [-97.6, -37.85, 19.99, -48.13, -48.38, 0.0]
  Target bbox: [607.89, 285.07, 636.98, 352.09]

Frame 5 (current):
  Drone pose: [-97.31, -38.18, 20.11, -45.53, -49.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": 619.27, "ymin": 320.92, "xmax": 665.95, "ymax": 396.55}, "waypoint_deltas": [{"dx": 0.28, "dy": -0.56, "dz": -0.11, "dpitch": -0.11, "dyaw": -0.31, "droll": 0.0}, {"dx": 0.56, "dy": -1.03, "dz": -0.11, "dpitch": -0.34, "dyaw": -1.05, "droll": 0.0}, {"dx": 0.88, "dy": -1.49, "dz": -0.11, "dpitch": -0.13, "dyaw": -0.69, "droll": 0.0}, {"dx": 1.25, "dy": -1.96, "dz": -0.11, "dpitch": 0.04, "dyaw": -0.43, "droll": 0.0}, {"dx": 1.64, "dy": -2.43, "dz": -0.11, "dpitch": 0.18, "dyaw": -0.25, "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.91, -41.58, 19.81, -44.79, -49.65, 0.0]
  Target bbox: [620.83, 324.05, 658.75, 395.15]

Frame 2:
  Drone pose: [-94.51, -42.04, 20.0, -46.11, -47.5, 0.0]
  Target bbox: [599.48, 304.36, 631.99, 375.9]

Frame 3:
  Drone pose: [-94.2, -42.65, 19.91, -44.74, -48.85, 0.0]
  Target bbox: [623.66, 325.83, 655.99, 393.41]

Frame 4:
  Drone pose: [-93.91, -43.06, 20.0, -39.65, -47.04, 0.0]
  Target bbox: [606.86, 409.69, 635.91, 475.67]

Frame 5 (current):
  Drone pose: [-93.83, -43.54, 20.0, -48.42, -46.57, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 603.74, "ymin": 250.06, "xmax": 648.7, "ymax": 325.5}, "waypoint_deltas": [{"dx": 0.11, "dy": -0.48, "dz": 0.0, "dpitch": 4.19, "dyaw": -1.37, "droll": 0.0}, {"dx": 0.18, "dy": -0.96, "dz": 0.0, "dpitch": 4.16, "dyaw": -1.57, "droll": 0.0}, {"dx": 0.22, "dy": -1.41, "dz": 0.0, "dpitch": 4.17, "dyaw": -1.74, "droll": 0.0}, {"dx": 0.23, "dy": -1.85, "dz": 0.0, "dpitch": 4.22, "dyaw": -1.88, "droll": 0.0}, {"dx": 0.21, "dy": -2.28, "dz": 0.0, "dpitch": 4.32, "dyaw": -1.99, "droll": 0.0}]}