[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: [-88.16, -55.94, 22.0, -46.4, 116.57, 0.0]
  Target bbox: [618.89, 324.62, 661.22, 394.68]

Frame 2:
  Drone pose: [-89.38, -56.47, 21.2, -44.67, 112.23, 0.0]
  Target bbox: [615.74, 324.19, 664.44, 395.3]

Frame 3:
  Drone pose: [-90.07, -56.47, 20.67, -43.61, 109.92, 0.0]
  Target bbox: [625.41, 325.41, 654.82, 393.91]

Frame 4:
  Drone pose: [-90.52, -56.18, 20.64, -43.5, 108.55, 0.0]
  Target bbox: [616.73, 321.8, 663.03, 397.76]

Frame 5 (current):
  Drone pose: [-90.85, -55.75, 20.62, -43.3, 108.95, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 616.93, "ymin": 321.87, "xmax": 662.86, "ymax": 397.62}, "waypoint_deltas": [{"dx": -0.28, "dy": 0.48, "dz": -0.03, "dpitch": 0.17, "dyaw": 0.55, "droll": 0.0}, {"dx": -0.53, "dy": 0.96, "dz": -0.05, "dpitch": 0.33, "dyaw": 1.17, "droll": 0.0}, {"dx": -0.78, "dy": 1.44, "dz": -0.07, "dpitch": 0.28, "dyaw": 0.51, "droll": 0.0}, {"dx": -1.04, "dy": 1.91, "dz": -0.09, "dpitch": 0.23, "dyaw": -0.19, "droll": 0.0}, {"dx": -1.34, "dy": 2.38, "dz": -0.2, "dpitch": 0.3, "dyaw": -1.01, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-92.19, -53.37, 20.42, -43.0, 107.94, 0.0]
  Target bbox: [621.5, 324.22, 658.77, 395.16]

Frame 2:
  Drone pose: [-92.55, -52.9, 20.39, -43.06, 106.98, 0.0]
  Target bbox: [618.79, 323.34, 661.0, 396.23]

Frame 3:
  Drone pose: [-92.97, -52.42, 20.36, -42.96, 107.17, 0.0]
  Target bbox: [621.74, 324.69, 658.05, 394.81]

Frame 4:
  Drone pose: [-93.44, -51.94, 20.33, -42.88, 107.24, 0.0]
  Target bbox: [616.81, 321.52, 663.01, 397.98]

Frame 5 (current):
  Drone pose: [-93.95, -51.45, 20.3, -42.83, 107.21, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 616.26, "ymin": 321.3, "xmax": 663.5, "ymax": 398.32}, "waypoint_deltas": [{"dx": -0.51, "dy": 0.5, "dz": -0.03, "dpitch": 0.04, "dyaw": -0.05, "droll": 0.0}, {"dx": -1.01, "dy": 0.99, "dz": -0.06, "dpitch": 0.09, "dyaw": -0.06, "droll": 0.0}, {"dx": -1.48, "dy": 1.47, "dz": -0.08, "dpitch": 0.17, "dyaw": 0.02, "droll": 0.0}, {"dx": -1.89, "dy": 1.94, "dz": -0.11, "dpitch": 0.28, "dyaw": 0.23, "droll": 0.0}, {"dx": -2.25, "dy": 2.41, "dz": -0.13, "dpitch": 0.21, "dyaw": -0.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: [-96.52, -48.59, 20.15, -42.65, 105.59, 0.0]
  Target bbox: [621.21, 324.66, 659.04, 394.66]

Frame 2:
  Drone pose: [-96.79, -48.14, 20.13, -42.66, 104.82, 0.0]
  Target bbox: [614.96, 323.77, 665.35, 395.69]

Frame 3:
  Drone pose: [-97.05, -47.69, 20.12, -42.66, 104.12, 0.0]
  Target bbox: [615.4, 323.37, 664.94, 396.06]

Frame 4:
  Drone pose: [-97.28, -47.24, 20.1, -42.64, 103.44, 0.0]
  Target bbox: [620.01, 324.87, 660.26, 394.45]

Frame 5 (current):
  Drone pose: [-97.52, -46.79, 20.09, -42.63, 102.79, 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.47, "ymin": 324.92, "xmax": 663.85, "ymax": 394.51}, "waypoint_deltas": [{"dx": -0.23, "dy": 0.45, "dz": -0.01, "dpitch": 0.02, "dyaw": -0.66, "droll": 0.0}, {"dx": -0.46, "dy": 0.89, "dz": -0.02, "dpitch": 0.05, "dyaw": -1.31, "droll": 0.0}, {"dx": -0.69, "dy": 1.34, "dz": -0.03, "dpitch": 0.07, "dyaw": -1.97, "droll": 0.0}, {"dx": -0.91, "dy": 1.79, "dz": -0.04, "dpitch": 0.1, "dyaw": -2.59, "droll": 0.0}, {"dx": -1.13, "dy": 2.25, "dz": -0.05, "dpitch": 0.12, "dyaw": -3.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: [-98.87, -44.08, 20.04, -42.5, 98.98, 0.0]
  Target bbox: [624.3, 326.5, 655.99, 392.87]

Frame 2:
  Drone pose: [-99.08, -43.62, 20.03, -42.48, 98.38, 0.0]
  Target bbox: [620.33, 324.49, 660.03, 394.81]

Frame 3:
  Drone pose: [-99.28, -43.15, 20.03, -42.47, 97.82, 0.0]
  Target bbox: [622.84, 326.34, 657.47, 393.02]

Frame 4:
  Drone pose: [-99.46, -42.7, 20.02, -42.44, 97.3, 0.0]
  Target bbox: [617.37, 324.58, 663.04, 394.73]

Frame 5 (current):
  Drone pose: [-99.65, -42.24, 20.02, -42.41, 96.78, 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.94, "ymin": 325.0, "xmax": 663.48, "ymax": 394.32}, "waypoint_deltas": [{"dx": -0.18, "dy": 0.47, "dz": 0.0, "dpitch": 0.02, "dyaw": -0.5, "droll": 0.0}, {"dx": -0.34, "dy": 0.94, "dz": -0.01, "dpitch": 0.04, "dyaw": -0.96, "droll": 0.0}, {"dx": -0.49, "dy": 1.41, "dz": -0.01, "dpitch": 0.06, "dyaw": -1.36, "droll": 0.0}, {"dx": -0.62, "dy": 1.89, "dz": -0.01, "dpitch": 0.09, "dyaw": -1.74, "droll": 0.0}, {"dx": -0.75, "dy": 2.36, "dz": -0.01, "dpitch": 0.11, "dyaw": -2.09, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-100.51, -39.4, 20.01, -42.28, 94.38, 0.0]
  Target bbox: [628.05, 326.09, 652.2, 393.2]

Frame 2:
  Drone pose: [-100.61, -38.93, 20.0, -42.26, 94.11, 0.0]
  Target bbox: [623.74, 325.5, 656.61, 393.79]

Frame 3:
  Drone pose: [-100.69, -38.45, 20.0, -42.24, 93.89, 0.0]
  Target bbox: [626.12, 327.71, 654.16, 391.65]

Frame 4:
  Drone pose: [-100.75, -37.96, 20.0, -42.22, 93.71, 0.0]
  Target bbox: [621.34, 326.78, 659.02, 392.5]

Frame 5 (current):
  Drone pose: [-100.8, -37.48, 20.0, -42.2, 93.58, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 622.62, "ymin": 326.49, "xmax": 657.71, "ymax": 392.74}, "waypoint_deltas": [{"dx": -0.03, "dy": 0.49, "dz": 0.0, "dpitch": 0.02, "dyaw": -0.09, "droll": 0.0}, {"dx": -0.05, "dy": 0.97, "dz": 0.0, "dpitch": 0.04, "dyaw": -0.14, "droll": 0.0}, {"dx": -0.06, "dy": 1.46, "dz": 0.0, "dpitch": 0.06, "dyaw": -0.16, "droll": 0.0}, {"dx": -0.05, "dy": 1.95, "dz": 0.0, "dpitch": 0.07, "dyaw": -0.15, "droll": 0.0}, {"dx": -0.04, "dy": 2.44, "dz": 0.0, "dpitch": 0.08, "dyaw": -0.13, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-100.83, -34.54, 20.0, -42.11, 93.49, 0.0]
  Target bbox: [623.3, 327.05, 657.04, 392.28]

Frame 2:
  Drone pose: [-100.82, -34.04, 20.0, -42.12, 93.52, 0.0]
  Target bbox: [622.58, 327.09, 657.76, 392.23]

Frame 3:
  Drone pose: [-100.82, -33.53, 20.0, -42.13, 93.51, 0.0]
  Target bbox: [623.96, 327.15, 656.36, 392.19]

Frame 4:
  Drone pose: [-100.84, -33.0, 20.0, -42.16, 93.47, 0.0]
  Target bbox: [618.7, 325.27, 661.74, 394.0]

Frame 5 (current):
  Drone pose: [-100.88, -32.47, 20.0, -42.21, 93.36, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 623.79, "ymin": 327.66, "xmax": 656.53, "ymax": 391.68}, "waypoint_deltas": [{"dx": -0.06, "dy": 0.53, "dz": 0.0, "dpitch": -0.05, "dyaw": -0.15, "droll": 0.0}, {"dx": -0.13, "dy": 1.08, "dz": 0.0, "dpitch": -0.07, "dyaw": 1.03, "droll": 0.0}, {"dx": -0.21, "dy": 1.62, "dz": 0.0, "dpitch": -0.14, "dyaw": 0.81, "droll": 0.0}, {"dx": -0.3, "dy": 2.16, "dz": 0.0, "dpitch": -0.15, "dyaw": 1.95, "droll": 0.0}, {"dx": -0.39, "dy": 2.69, "dz": 0.0, "dpitch": -0.2, "dyaw": 1.72, "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.27, -29.78, 20.0, -42.41, 95.08, 0.0]
  Target bbox: [621.23, 324.33, 658.59, 395.19]

Frame 2:
  Drone pose: [-101.35, -29.24, 20.0, -42.4, 96.23, 0.0]
  Target bbox: [620.21, 326.25, 660.13, 393.02]

Frame 3:
  Drone pose: [-101.42, -28.71, 20.0, -42.46, 96.03, 0.0]
  Target bbox: [621.29, 324.26, 658.52, 395.26]

Frame 4:
  Drone pose: [-101.5, -28.18, 20.0, -42.43, 97.21, 0.0]
  Target bbox: [616.24, 325.33, 664.18, 394.03]

Frame 5 (current):
  Drone pose: [-101.57, -27.65, 20.0, -42.49, 97.02, 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.51, "ymin": 325.8, "xmax": 660.84, "ymax": 393.49}, "waypoint_deltas": [{"dx": -0.08, "dy": 0.53, "dz": 0.0, "dpitch": -0.05, "dyaw": -0.21, "droll": 0.0}, {"dx": -0.17, "dy": 1.06, "dz": 0.0, "dpitch": -0.02, "dyaw": 0.94, "droll": 0.0}, {"dx": -0.26, "dy": 1.59, "dz": 0.0, "dpitch": -0.08, "dyaw": 0.68, "droll": 0.0}, {"dx": -0.37, "dy": 2.12, "dz": 0.0, "dpitch": -0.04, "dyaw": 1.78, "droll": 0.0}, {"dx": -0.48, "dy": 2.65, "dz": 0.0, "dpitch": -0.1, "dyaw": 1.48, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-102.17, -24.48, 20.0, -42.54, 99.56, 0.0]
  Target bbox: [626.65, 325.24, 653.61, 394.04]

Frame 2:
  Drone pose: [-102.29, -23.95, 20.0, -42.6, 99.24, 0.0]
  Target bbox: [618.52, 322.45, 661.49, 396.98]

Frame 3:
  Drone pose: [-102.41, -23.43, 20.0, -42.55, 100.29, 0.0]
  Target bbox: [622.49, 324.47, 657.83, 394.87]

Frame 4:
  Drone pose: [-102.53, -22.91, 20.0, -42.6, 99.97, 0.0]
  Target bbox: [620.82, 323.14, 659.04, 396.27]

Frame 5 (current):
  Drone pose: [-102.65, -22.39, 20.0, -42.54, 101.02, 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.17, "ymin": 325.42, "xmax": 660.14, "ymax": 393.94}, "waypoint_deltas": [{"dx": -0.12, "dy": 0.52, "dz": 0.0, "dpitch": -0.06, "dyaw": -0.31, "droll": 0.0}, {"dx": -0.24, "dy": 1.04, "dz": 0.0, "dpitch": -0.12, "dyaw": -0.65, "droll": 0.0}, {"dx": -0.38, "dy": 1.57, "dz": 0.0, "dpitch": -0.05, "dyaw": 0.35, "droll": 0.0}, {"dx": -0.52, "dy": 2.09, "dz": 0.0, "dpitch": -0.12, "dyaw": -0.02, "droll": 0.0}, {"dx": -0.68, "dy": 2.61, "dz": 0.0, "dpitch": -0.05, "dyaw": 0.93, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-103.48, -19.27, 20.0, -42.66, 101.53, 0.0]
  Target bbox: [616.48, 321.43, 663.35, 398.23]

Frame 2:
  Drone pose: [-103.65, -18.75, 20.0, -42.59, 102.46, 0.0]
  Target bbox: [624.8, 326.37, 655.45, 393.01]

Frame 3:
  Drone pose: [-103.81, -18.23, 20.0, -42.66, 102.03, 0.0]
  Target bbox: [617.73, 321.92, 662.23, 397.51]

Frame 4:
  Drone pose: [-103.97, -17.71, 20.0, -42.58, 102.95, 0.0]
  Target bbox: [618.52, 324.71, 661.77, 394.63]

Frame 5 (current):
  Drone pose: [-104.13, -17.19, 20.0, -42.65, 102.54, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 616.03, "ymin": 320.48, "xmax": 663.85, "ymax": 399.06}, "waypoint_deltas": [{"dx": -0.15, "dy": 0.51, "dz": 0.0, "dpitch": 0.08, "dyaw": 0.94, "droll": 0.0}, {"dx": -0.31, "dy": 1.03, "dz": 0.0, "dpitch": 0.01, "dyaw": 0.52, "droll": 0.0}, {"dx": -0.48, "dy": 1.54, "dz": 0.0, "dpitch": -0.06, "dyaw": 0.09, "droll": 0.0}, {"dx": -0.65, "dy": 2.06, "dz": 0.0, "dpitch": 0.03, "dyaw": 0.99, "droll": 0.0}, {"dx": -0.83, "dy": 2.57, "dz": 0.0, "dpitch": -0.05, "dyaw": 0.5, "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: [-105.15, -14.11, 20.0, -42.62, 103.89, 0.0]
  Target bbox: [626.34, 325.13, 653.91, 394.17]

Frame 2:
  Drone pose: [-105.35, -13.59, 20.0, -42.7, 103.37, 0.0]
  Target bbox: [617.53, 321.21, 662.25, 398.38]

Frame 3:
  Drone pose: [-105.54, -13.08, 20.0, -42.62, 104.19, 0.0]
  Target bbox: [624.18, 326.22, 656.07, 393.17]

Frame 4:
  Drone pose: [-105.74, -12.57, 20.0, -42.7, 103.67, 0.0]
  Target bbox: [621.34, 323.61, 658.53, 395.75]

Frame 5 (current):
  Drone pose: [-105.94, -12.06, 20.0, -42.61, 104.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": 621.67, "ymin": 325.49, "xmax": 658.61, "ymax": 393.91}, "waypoint_deltas": [{"dx": -0.18, "dy": 0.51, "dz": 0.0, "dpitch": -0.08, "dyaw": -0.5, "droll": 0.0}, {"dx": -0.37, "dy": 1.02, "dz": 0.0, "dpitch": 0.02, "dyaw": 0.36, "droll": 0.0}, {"dx": -0.55, "dy": 1.53, "dz": 0.0, "dpitch": -0.06, "dyaw": -0.12, "droll": 0.0}, {"dx": -0.73, "dy": 2.04, "dz": 0.0, "dpitch": -0.13, "dyaw": -0.61, "droll": 0.0}, {"dx": -0.92, "dy": 2.55, "dz": 0.0, "dpitch": -0.04, "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: [-88.25, -56.08, 22.05, -48.12, 109.1, 0.0]
  Target bbox: [613.58, 320.44, 666.43, 398.99]

Frame 2:
  Drone pose: [-89.38, -56.47, 21.2, -48.87, 113.97, 0.0]
  Target bbox: [602.08, 255.94, 635.65, 322.9]

Frame 3:
  Drone pose: [-90.07, -56.47, 20.67, -43.61, 109.92, 0.0]
  Target bbox: [616.86, 324.53, 663.36, 394.96]

Frame 4:
  Drone pose: [-90.52, -56.18, 20.64, -43.5, 108.55, 0.0]
  Target bbox: [622.11, 324.64, 657.73, 394.7]

Frame 5 (current):
  Drone pose: [-90.85, -55.75, 20.62, -42.17, 110.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": 601.2, "ymin": 342.44, "xmax": 637.75, "ymax": 415.36}, "waypoint_deltas": [{"dx": -0.28, "dy": 0.48, "dz": -0.03, "dpitch": -0.96, "dyaw": -1.09, "droll": 0.0}, {"dx": -0.53, "dy": 0.96, "dz": -0.05, "dpitch": -0.8, "dyaw": -0.47, "droll": 0.0}, {"dx": -0.78, "dy": 1.44, "dz": -0.07, "dpitch": -0.85, "dyaw": -1.13, "droll": 0.0}, {"dx": -1.04, "dy": 1.91, "dz": -0.09, "dpitch": -0.9, "dyaw": -1.83, "droll": 0.0}, {"dx": -1.34, "dy": 2.38, "dz": -0.2, "dpitch": -0.83, "dyaw": -2.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: [-91.63, -54.31, 20.55, -43.02, 109.46, 0.0]
  Target bbox: [624.76, 326.15, 654.97, 393.13]

Frame 2:
  Drone pose: [-91.78, -53.86, 20.63, -44.15, 116.06, 0.0]
  Target bbox: [619.72, 323.75, 659.99, 395.72]

Frame 3:
  Drone pose: [-92.19, -53.37, 20.42, -43.0, 107.94, 0.0]
  Target bbox: [621.82, 324.3, 658.44, 395.08]

Frame 4:
  Drone pose: [-92.55, -52.9, 20.39, -47.15, 106.61, 0.0]
  Target bbox: [625.06, 255.33, 664.01, 326.85]

Frame 5 (current):
  Drone pose: [-92.97, -52.42, 20.36, -42.96, 107.17, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 616.54, "ymin": 321.34, "xmax": 663.27, "ymax": 398.17}, "waypoint_deltas": [{"dx": -0.47, "dy": 0.48, "dz": -0.03, "dpitch": 0.08, "dyaw": 0.07, "droll": 0.0}, {"dx": -0.98, "dy": 0.97, "dz": -0.06, "dpitch": 0.13, "dyaw": 0.04, "droll": 0.0}, {"dx": -1.49, "dy": 1.47, "dz": -0.09, "dpitch": 0.17, "dyaw": -0.01, "droll": 0.0}, {"dx": -1.99, "dy": 1.96, "dz": -0.12, "dpitch": 0.22, "dyaw": -0.02, "droll": 0.0}, {"dx": -2.46, "dy": 2.44, "dz": -0.14, "dpitch": 0.3, "dyaw": 0.06, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-94.46, -50.95, 20.27, -41.61, 109.76, 0.0]
  Target bbox: [588.68, 345.36, 626.45, 414.58]

Frame 2:
  Drone pose: [-94.96, -50.46, 20.24, -42.74, 107.15, 0.0]
  Target bbox: [621.44, 323.74, 658.38, 395.65]

Frame 3:
  Drone pose: [-95.43, -49.98, 20.22, -45.9, 106.77, 0.0]
  Target bbox: [622.98, 267.7, 668.4, 343.21]

Frame 4:
  Drone pose: [-95.84, -49.51, 20.19, -42.18, 102.44, 0.0]
  Target bbox: [686.05, 333.59, 718.47, 401.98]

Frame 5 (current):
  Drone pose: [-96.2, -49.04, 20.17, -42.62, 106.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": 621.24, "ymin": 325.31, "xmax": 659.02, "ymax": 394.12}, "waypoint_deltas": [{"dx": -0.32, "dy": 0.45, "dz": -0.02, "dpitch": -0.03, "dyaw": -0.87, "droll": 0.0}, {"dx": -0.59, "dy": 0.9, "dz": -0.04, "dpitch": -0.04, "dyaw": -1.64, "droll": 0.0}, {"dx": -0.85, "dy": 1.35, "dz": -0.05, "dpitch": -0.04, "dyaw": -2.34, "droll": 0.0}, {"dx": -1.08, "dy": 1.8, "dz": -0.07, "dpitch": -0.02, "dyaw": -3.02, "droll": 0.0}, {"dx": -1.32, "dy": 2.25, "dz": -0.08, "dpitch": -0.01, "dyaw": -3.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: [-97.05, -47.69, 20.12, -39.24, 105.99, 0.0]
  Target bbox: [594.4, 381.83, 638.58, 452.79]

Frame 2:
  Drone pose: [-97.28, -47.24, 20.1, -40.6, 98.44, 0.0]
  Target bbox: [686.66, 361.45, 717.75, 430.0]

Frame 3:
  Drone pose: [-97.52, -46.79, 20.09, -45.38, 98.07, 0.0]
  Target bbox: [675.59, 277.16, 721.86, 353.15]

Frame 4:
  Drone pose: [-97.78, -46.27, 20.24, -44.5, 99.05, 0.0]
  Target bbox: [642.85, 296.5, 672.18, 362.04]

Frame 5 (current):
  Drone pose: [-97.83, -46.0, 20.1, -39.21, 99.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": 619.47, "ymin": 343.29, "xmax": 660.37, "ymax": 412.88}, "waypoint_deltas": [{"dx": -0.38, "dy": 0.55, "dz": -0.04, "dpitch": -3.35, "dyaw": 1.32, "droll": 0.0}, {"dx": -0.6, "dy": 1.0, "dz": -0.05, "dpitch": -3.32, "dyaw": 0.7, "droll": 0.0}, {"dx": -0.82, "dy": 1.46, "dz": -0.06, "dpitch": -3.3, "dyaw": 0.09, "droll": 0.0}, {"dx": -1.04, "dy": 1.92, "dz": -0.06, "dpitch": -3.29, "dyaw": -0.52, "droll": 0.0}, {"dx": -1.25, "dy": 2.38, "dz": -0.07, "dpitch": -3.27, "dyaw": -1.12, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-98.87, -44.08, 20.04, -45.85, 93.98, 0.0]
  Target bbox: [680.61, 272.52, 724.62, 337.91]

Frame 2:
  Drone pose: [-99.08, -43.62, 20.03, -41.77, 102.21, 0.0]
  Target bbox: [573.57, 339.23, 611.24, 406.21]

Frame 3:
  Drone pose: [-99.28, -43.15, 20.03, -42.47, 97.82, 0.0]
  Target bbox: [619.78, 325.98, 660.55, 393.3]

Frame 4:
  Drone pose: [-99.46, -42.7, 20.02, -41.15, 100.67, 0.0]
  Target bbox: [573.46, 346.58, 622.47, 417.68]

Frame 5 (current):
  Drone pose: [-99.65, -42.24, 20.02, -40.92, 91.78, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 681.21, "ymin": 352.28, "xmax": 724.07, "ymax": 420.58}, "waypoint_deltas": [{"dx": -0.18, "dy": 0.47, "dz": 0.0, "dpitch": -1.47, "dyaw": 4.5, "droll": 0.0}, {"dx": -0.34, "dy": 0.94, "dz": -0.01, "dpitch": -1.45, "dyaw": 4.04, "droll": 0.0}, {"dx": -0.49, "dy": 1.41, "dz": -0.01, "dpitch": -1.43, "dyaw": 3.64, "droll": 0.0}, {"dx": -0.62, "dy": 1.89, "dz": -0.01, "dpitch": -1.4, "dyaw": 3.26, "droll": 0.0}, {"dx": -0.75, "dy": 2.36, "dz": -0.01, "dpitch": -1.38, "dyaw": 2.91, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-100.14, -40.83, 20.01, -46.14, 96.23, 0.0]
  Target bbox: [609.78, 262.49, 649.89, 329.43]

Frame 2:
  Drone pose: [-100.27, -40.35, 20.01, -42.32, 95.04, 0.0]
  Target bbox: [619.24, 326.89, 661.14, 392.46]

Frame 3:
  Drone pose: [-100.4, -39.88, 20.01, -42.3, 94.69, 0.0]
  Target bbox: [617.19, 326.41, 663.25, 392.94]

Frame 4:
  Drone pose: [-100.51, -39.4, 20.01, -41.92, 91.19, 0.0]
  Target bbox: [666.29, 334.5, 693.63, 398.25]

Frame 5 (current):
  Drone pose: [-100.61, -38.93, 20.0, -40.37, 96.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": 592.22, "ymin": 357.09, "xmax": 626.96, "ymax": 426.36}, "waypoint_deltas": [{"dx": -0.08, "dy": 0.48, "dz": 0.0, "dpitch": -1.87, "dyaw": -2.66, "droll": 0.0}, {"dx": -0.14, "dy": 0.97, "dz": 0.0, "dpitch": -1.85, "dyaw": -2.84, "droll": 0.0}, {"dx": -0.19, "dy": 1.45, "dz": 0.0, "dpitch": -1.83, "dyaw": -2.97, "droll": 0.0}, {"dx": -0.22, "dy": 1.94, "dz": 0.0, "dpitch": -1.81, "dyaw": -3.06, "droll": 0.0}, {"dx": -0.24, "dy": 2.42, "dz": 0.0, "dpitch": -1.79, "dyaw": -3.11, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-100.78, -37.43, 20.16, -44.53, 95.66, 0.0]
  Target bbox: [585.16, 248.23, 627.76, 319.57]

Frame 2:
  Drone pose: [-100.86, -37.0, 19.81, -39.76, 96.19, 0.0]
  Target bbox: [642.97, 364.84, 685.22, 437.24]

Frame 3:
  Drone pose: [-100.85, -36.51, 20.0, -46.91, 92.51, 0.0]
  Target bbox: [628.98, 246.4, 675.08, 313.43]

Frame 4:
  Drone pose: [-100.86, -36.02, 20.0, -39.75, 98.42, 0.0]
  Target bbox: [555.32, 365.95, 599.67, 437.44]

Frame 5 (current):
  Drone pose: [-100.85, -35.53, 20.0, -42.13, 93.43, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 621.55, "ymin": 325.33, "xmax": 658.85, "ymax": 393.96}, "waypoint_deltas": [{"dx": 0.01, "dy": 0.49, "dz": 0.0, "dpitch": 0.01, "dyaw": 0.02, "droll": 0.0}, {"dx": 0.02, "dy": 0.99, "dz": 0.0, "dpitch": 0.02, "dyaw": 0.06, "droll": 0.0}, {"dx": 0.03, "dy": 1.49, "dz": 0.0, "dpitch": 0.01, "dyaw": 0.09, "droll": 0.0}, {"dx": 0.03, "dy": 2.0, "dz": 0.0, "dpitch": 0.0, "dyaw": 0.08, "droll": 0.0}, {"dx": 0.01, "dy": 2.53, "dz": 0.0, "dpitch": -0.03, "dyaw": 0.04, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-100.81, -33.37, 20.05, -45.36, 88.18, 0.0]
  Target bbox: [675.71, 315.53, 724.17, 387.21]

Frame 2:
  Drone pose: [-100.84, -33.0, 20.0, -42.16, 93.47, 0.0]
  Target bbox: [624.5, 327.73, 655.8, 391.6]

Frame 3:
  Drone pose: [-100.88, -32.47, 20.0, -40.68, 94.8, 0.0]
  Target bbox: [609.69, 351.74, 634.46, 419.28]

Frame 4:
  Drone pose: [-100.94, -31.94, 20.0, -42.26, 93.21, 0.0]
  Target bbox: [616.95, 320.7, 663.09, 398.86]

Frame 5 (current):
  Drone pose: [-101.01, -31.39, 20.0, -42.28, 94.39, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 616.91, "ymin": 321.92, "xmax": 662.99, "ymax": 397.57}, "waypoint_deltas": [{"dx": -0.08, "dy": 0.54, "dz": 0.0, "dpitch": -0.07, "dyaw": -0.22, "droll": 0.0}, {"dx": -0.17, "dy": 1.08, "dz": 0.0, "dpitch": -0.08, "dyaw": 0.92, "droll": 0.0}, {"dx": -0.26, "dy": 1.61, "dz": 0.0, "dpitch": -0.13, "dyaw": 0.69, "droll": 0.0}, {"dx": -0.34, "dy": 2.15, "dz": 0.0, "dpitch": -0.12, "dyaw": 1.84, "droll": 0.0}, {"dx": -0.41, "dy": 2.68, "dz": 0.0, "dpitch": -0.18, "dyaw": 1.64, "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.27, -29.78, 20.0, -42.41, 95.08, 0.0]
  Target bbox: [618.8, 325.18, 661.35, 394.16]

Frame 2:
  Drone pose: [-101.26, -29.21, 20.03, -43.67, 97.89, 0.0]
  Target bbox: [633.28, 305.17, 670.1, 376.9]

Frame 3:
  Drone pose: [-101.42, -28.71, 20.0, -42.46, 96.03, 0.0]
  Target bbox: [618.42, 322.12, 661.62, 397.35]

Frame 4:
  Drone pose: [-101.5, -28.18, 20.0, -39.68, 102.21, 0.0]
  Target bbox: [555.57, 372.9, 599.89, 442.7]

Frame 5 (current):
  Drone pose: [-101.57, -27.65, 20.0, -45.3, 101.75, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 564.52, "ymin": 280.82, "xmax": 597.92, "ymax": 347.49}, "waypoint_deltas": [{"dx": -0.08, "dy": 0.53, "dz": 0.0, "dpitch": 2.76, "dyaw": -4.94, "droll": 0.0}, {"dx": -0.17, "dy": 1.06, "dz": 0.0, "dpitch": 2.79, "dyaw": -3.79, "droll": 0.0}, {"dx": -0.26, "dy": 1.59, "dz": 0.0, "dpitch": 2.73, "dyaw": -4.05, "droll": 0.0}, {"dx": -0.37, "dy": 2.12, "dz": 0.0, "dpitch": 2.77, "dyaw": -2.95, "droll": 0.0}, {"dx": -0.48, "dy": 2.65, "dz": 0.0, "dpitch": 2.71, "dyaw": -3.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: [-101.83, -26.06, 20.0, -47.57, 97.57, 0.0]
  Target bbox: [620.02, 237.13, 663.21, 314.19]

Frame 2:
  Drone pose: [-101.94, -25.53, 20.0, -43.86, 99.79, 0.0]
  Target bbox: [607.43, 301.67, 647.81, 373.13]

Frame 3:
  Drone pose: [-102.05, -25.0, 20.0, -42.59, 98.5, 0.0]
  Target bbox: [619.39, 322.21, 660.39, 397.34]

Frame 4:
  Drone pose: [-102.17, -24.48, 20.0, -42.27, 104.56, 0.0]
  Target bbox: [555.35, 331.07, 600.37, 401.06]

Frame 5 (current):
  Drone pose: [-102.29, -23.95, 20.0, -41.14, 97.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": 640.4, "ymin": 350.78, "xmax": 684.34, "ymax": 418.03}, "waypoint_deltas": [{"dx": -0.12, "dy": 0.52, "dz": 0.0, "dpitch": -1.41, "dyaw": 2.84, "droll": 0.0}, {"dx": -0.24, "dy": 1.04, "dz": 0.0, "dpitch": -1.46, "dyaw": 2.52, "droll": 0.0}, {"dx": -0.36, "dy": 1.56, "dz": 0.0, "dpitch": -1.4, "dyaw": 3.57, "droll": 0.0}, {"dx": -0.48, "dy": 2.08, "dz": 0.0, "dpitch": -1.46, "dyaw": 3.26, "droll": 0.0}, {"dx": -0.6, "dy": 2.6, "dz": 0.0, "dpitch": -1.52, "dyaw": 2.92, "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: [-128.65, 10.68, 22.0, -55.25, -71.7, 0.0]
  Target bbox: [612.7, 320.82, 667.58, 397.9]

Frame 2:
  Drone pose: [-129.48, 10.14, 21.2, -54.24, -66.0, 0.0]
  Target bbox: [613.56, 318.45, 666.68, 400.22]

Frame 3:
  Drone pose: [-129.51, 9.96, 20.67, -53.4, -63.82, 0.0]
  Target bbox: [612.13, 317.17, 668.08, 401.55]

Frame 4:
  Drone pose: [-129.49, 9.77, 20.64, -53.26, -61.76, 0.0]
  Target bbox: [615.37, 318.76, 664.26, 399.87]

Frame 5 (current):
  Drone pose: [-129.42, 9.6, 20.62, -52.3, -60.91, 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.44, "ymin": 318.45, "xmax": 664.15, "ymax": 400.3}, "waypoint_deltas": [{"dx": 0.3, "dy": -0.16, "dz": -0.03, "dpitch": 0.75, "dyaw": 0.0, "droll": 0.0}, {"dx": 0.65, "dy": -0.38, "dz": -0.05, "dpitch": 1.37, "dyaw": -0.01, "droll": 0.0}, {"dx": 1.0, "dy": -0.64, "dz": -0.07, "dpitch": 1.89, "dyaw": 0.05, "droll": 0.0}, {"dx": 1.36, "dy": -0.96, "dz": -0.09, "dpitch": 2.32, "dyaw": 0.17, "droll": 0.0}, {"dx": 1.72, "dy": -1.32, "dz": -0.2, "dpitch": 2.81, "dyaw": 0.35, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-127.34, 7.89, 20.39, -49.16, -60.34, 0.0]
  Target bbox: [616.93, 319.89, 662.7, 399.03]

Frame 2:
  Drone pose: [-127.0, 7.46, 20.36, -48.89, -59.98, 0.0]
  Target bbox: [618.07, 319.45, 661.51, 399.55]

Frame 3:
  Drone pose: [-126.73, 6.95, 20.33, -48.66, -59.28, 0.0]
  Target bbox: [615.58, 318.23, 663.91, 400.89]

Frame 4:
  Drone pose: [-126.46, 6.41, 20.3, -48.69, -58.52, 0.0]
  Target bbox: [619.41, 321.55, 660.24, 397.41]

Frame 5 (current):
  Drone pose: [-125.67, 6.18, 20.27, -48.52, -59.86, 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.82, "ymin": 321.97, "xmax": 658.89, "ymax": 396.92}, "waypoint_deltas": [{"dx": 1.0, "dy": -0.08, "dz": -0.03, "dpitch": 0.25, "dyaw": -2.12, "droll": 0.0}, {"dx": 1.99, "dy": -0.16, "dz": -0.05, "dpitch": 0.53, "dyaw": -4.21, "droll": 0.0}, {"dx": 3.19, "dy": -0.13, "dz": -0.08, "dpitch": 0.89, "dyaw": -7.03, "droll": 0.0}, {"dx": 4.39, "dy": 0.01, "dz": -0.1, "dpitch": 1.46, "dyaw": -9.89, "droll": 0.0}, {"dx": 5.49, "dy": 0.09, "dz": -0.12, "dpitch": 1.81, "dyaw": -13.83, "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: [-119.23, 6.26, 20.14, -46.31, -76.98, 0.0]
  Target bbox: [618.81, 321.5, 661.58, 397.66]

Frame 2:
  Drone pose: [-118.9, 5.94, 20.12, -46.12, -78.09, 0.0]
  Target bbox: [618.47, 321.31, 661.94, 397.84]

Frame 3:
  Drone pose: [-118.74, 5.51, 20.11, -46.03, -78.63, 0.0]
  Target bbox: [621.64, 322.28, 658.73, 396.86]

Frame 4:
  Drone pose: [-118.62, 5.03, 20.09, -46.02, -79.0, 0.0]
  Target bbox: [615.33, 322.23, 665.08, 396.93]

Frame 5 (current):
  Drone pose: [-118.47, 4.53, 20.08, -46.05, -79.48, 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.08, "ymin": 321.93, "xmax": 661.31, "ymax": 397.17}, "waypoint_deltas": [{"dx": 0.22, "dy": -0.5, "dz": -0.01, "dpitch": -0.05, "dyaw": -0.67, "droll": 0.0}, {"dx": 0.53, "dy": -0.99, "dz": -0.02, "dpitch": 0.04, "dyaw": -0.08, "droll": 0.0}, {"dx": 0.92, "dy": -1.49, "dz": -0.03, "dpitch": 0.08, "dyaw": 0.25, "droll": 0.0}, {"dx": 1.37, "dy": -1.99, "dz": -0.04, "dpitch": 0.11, "dyaw": 0.39, "droll": 0.0}, {"dx": 1.86, "dy": -2.48, "dz": -0.04, "dpitch": 0.13, "dyaw": 0.44, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-115.61, 1.09, 20.03, -45.83, -79.07, 0.0]
  Target bbox: [617.91, 320.33, 661.96, 398.87]

Frame 2:
  Drone pose: [-115.1, 0.62, 20.02, -45.79, -79.12, 0.0]
  Target bbox: [614.4, 318.46, 665.43, 400.94]

Frame 3:
  Drone pose: [-114.59, 0.15, 20.02, -45.75, -79.18, 0.0]
  Target bbox: [619.0, 320.93, 660.87, 398.23]

Frame 4:
  Drone pose: [-114.06, -0.34, 20.02, -45.73, -79.26, 0.0]
  Target bbox: [617.51, 320.48, 662.36, 398.79]

Frame 5 (current):
  Drone pose: [-113.54, -0.83, 20.01, -45.72, -79.33, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 612.6, "ymin": 317.17, "xmax": 667.21, "ymax": 402.32}, "waypoint_deltas": [{"dx": 0.52, "dy": -0.5, "dz": 0.0, "dpitch": 0.0, "dyaw": -0.06, "droll": 0.0}, {"dx": 1.03, "dy": -1.02, "dz": 0.0, "dpitch": -0.03, "dyaw": -0.07, "droll": 0.0}, {"dx": 1.52, "dy": -1.55, "dz": 0.0, "dpitch": -0.07, "dyaw": -0.03, "droll": 0.0}, {"dx": 1.99, "dy": -2.09, "dz": 0.0, "dpitch": -0.12, "dyaw": 0.07, "droll": 0.0}, {"dx": 2.45, "dy": -2.64, "dz": -0.01, "dpitch": -0.18, "dyaw": 0.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: [-110.64, -4.03, 20.0, -45.97, -78.91, 0.0]
  Target bbox: [612.77, 317.35, 667.01, 402.15]

Frame 2:
  Drone pose: [-110.2, -4.59, 20.0, -46.05, -78.71, 0.0]
  Target bbox: [614.34, 317.59, 665.42, 401.79]

Frame 3:
  Drone pose: [-109.75, -5.13, 20.0, -46.1, -78.52, 0.0]
  Target bbox: [615.25, 318.74, 664.61, 400.54]

Frame 4:
  Drone pose: [-109.32, -5.65, 20.0, -46.11, -78.3, 0.0]
  Target bbox: [614.99, 318.13, 664.78, 401.21]

Frame 5 (current):
  Drone pose: [-108.93, -6.16, 20.0, -46.09, -77.96, 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.73, "ymin": 319.46, "xmax": 663.13, "ymax": 399.75}, "waypoint_deltas": [{"dx": 0.34, "dy": -0.51, "dz": 0.0, "dpitch": 0.04, "dyaw": 0.52, "droll": 0.0}, {"dx": 0.64, "dy": -1.04, "dz": 0.0, "dpitch": 0.07, "dyaw": 1.15, "droll": 0.0}, {"dx": 0.94, "dy": -1.57, "dz": 0.0, "dpitch": -0.08, "dyaw": 0.24, "droll": 0.0}, {"dx": 1.28, "dy": -2.08, "dz": 0.0, "dpitch": -0.21, "dyaw": -0.81, "droll": 0.0}, {"dx": 1.66, "dy": -2.58, "dz": 0.0, "dpitch": -0.16, "dyaw": -0.44, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-106.58, -9.7, 20.0, -46.09, -77.46, 0.0]
  Target bbox: [614.6, 318.48, 665.22, 400.85]

Frame 2:
  Drone pose: [-106.34, -10.2, 20.0, -46.0, -76.68, 0.0]
  Target bbox: [622.6, 321.76, 657.74, 397.33]

Frame 3:
  Drone pose: [-106.14, -10.71, 20.0, -46.09, -77.28, 0.0]
  Target bbox: [621.47, 321.86, 658.89, 397.28]

Frame 4:
  Drone pose: [-105.92, -11.23, 20.0, -46.19, -77.92, 0.0]
  Target bbox: [620.57, 321.51, 659.81, 397.6]

Frame 5 (current):
  Drone pose: [-105.66, -11.75, 20.0, -46.3, -78.73, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 616.35, "ymin": 319.36, "xmax": 663.49, "ymax": 399.9}, "waypoint_deltas": [{"dx": 0.35, "dy": -0.51, "dz": 0.0, "dpitch": 0.03, "dyaw": 0.48, "droll": 0.0}, {"dx": 0.78, "dy": -1.0, "dz": 0.0, "dpitch": 0.06, "dyaw": 0.69, "droll": 0.0}, {"dx": 1.28, "dy": -1.47, "dz": 0.0, "dpitch": 0.1, "dyaw": 0.67, "droll": 0.0}, {"dx": 1.8, "dy": -1.94, "dz": 0.0, "dpitch": 0.15, "dyaw": 0.6, "droll": 0.0}, {"dx": 2.23, "dy": -2.43, "dz": 0.0, "dpitch": 0.19, "dyaw": 0.79, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-103.42, -14.88, 20.0, -46.24, -76.31, 0.0]
  Target bbox: [615.7, 318.97, 664.09, 400.32]

Frame 2:
  Drone pose: [-103.45, -15.6, 20.0, -46.37, -74.51, 0.0]
  Target bbox: [612.98, 317.4, 666.72, 402.05]

Frame 3:
  Drone pose: [-103.5, -16.34, 20.0, -46.48, -72.6, 0.0]
  Target bbox: [614.39, 318.44, 665.34, 400.89]

Frame 4:
  Drone pose: [-103.68, -17.13, 20.0, -46.59, -70.25, 0.0]
  Target bbox: [619.47, 321.0, 660.31, 398.07]

Frame 5 (current):
  Drone pose: [-104.21, -18.12, 20.0, -46.7, -66.63, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 614.08, "ymin": 318.05, "xmax": 665.5, "ymax": 401.31}, "waypoint_deltas": [{"dx": -0.63, "dy": -1.04, "dz": 0.0, "dpitch": -0.01, "dyaw": 4.01, "droll": 0.0}, {"dx": -1.28, "dy": -2.13, "dz": 0.0, "dpitch": 0.08, "dyaw": 8.13, "droll": 0.0}, {"dx": -1.85, "dy": -3.18, "dz": 0.0, "dpitch": 0.51, "dyaw": 11.94, "droll": 0.0}, {"dx": -2.06, "dy": -4.05, "dz": 0.0, "dpitch": 0.71, "dyaw": 14.43, "droll": 0.0}, {"dx": -2.21, "dy": -4.89, "dz": 0.0, "dpitch": 0.93, "dyaw": 16.7, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-106.44, -23.78, 20.0, -45.56, -48.16, 0.0]
  Target bbox: [619.29, 321.53, 660.15, 397.71]

Frame 2:
  Drone pose: [-106.31, -24.48, 20.0, -45.4, -46.89, 0.0]
  Target bbox: [621.8, 323.51, 657.78, 395.53]

Frame 3:
  Drone pose: [-106.17, -25.17, 20.0, -45.23, -45.7, 0.0]
  Target bbox: [622.34, 323.59, 657.24, 395.5]

Frame 4:
  Drone pose: [-105.81, -25.76, 20.0, -45.17, -45.2, 0.0]
  Target bbox: [620.87, 323.43, 659.01, 395.69]

Frame 5 (current):
  Drone pose: [-105.43, -26.33, 20.0, -45.12, -44.79, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 621.68, "ymin": 323.36, "xmax": 658.45, "ymax": 395.77}, "waypoint_deltas": [{"dx": 0.4, "dy": -0.57, "dz": 0.0, "dpitch": 0.04, "dyaw": 0.37, "droll": 0.0}, {"dx": 0.8, "dy": -1.13, "dz": 0.0, "dpitch": 0.08, "dyaw": 0.72, "droll": 0.0}, {"dx": 1.2, "dy": -1.69, "dz": 0.0, "dpitch": 0.12, "dyaw": 1.06, "droll": 0.0}, {"dx": 1.6, "dy": -2.25, "dz": 0.0, "dpitch": 0.17, "dyaw": 1.4, "droll": 0.0}, {"dx": 2.0, "dy": -2.81, "dz": 0.0, "dpitch": 0.23, "dyaw": 1.73, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-102.66, -30.25, 20.0, -44.76, -42.36, 0.0]
  Target bbox: [621.59, 321.55, 658.93, 397.68]

Frame 2:
  Drone pose: [-102.27, -30.81, 20.0, -44.69, -41.98, 0.0]
  Target bbox: [620.44, 321.85, 660.11, 397.44]

Frame 3:
  Drone pose: [-101.88, -31.37, 20.0, -44.63, -41.62, 0.0]
  Target bbox: [621.1, 321.6, 659.43, 397.65]

Frame 4:
  Drone pose: [-101.46, -31.93, 20.0, -44.6, -41.32, 0.0]
  Target bbox: [624.35, 324.48, 655.98, 394.58]

Frame 5 (current):
  Drone pose: [-101.0, -32.47, 20.0, -44.59, -41.17, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 620.44, "ymin": 322.64, "xmax": 660.05, "ymax": 396.57}, "waypoint_deltas": [{"dx": 0.49, "dy": -0.53, "dz": 0.0, "dpitch": -0.03, "dyaw": 0.07, "droll": 0.0}, {"dx": 0.7, "dy": -1.34, "dz": 0.0, "dpitch": 0.0, "dyaw": 1.35, "droll": 0.0}, {"dx": 0.84, "dy": -2.21, "dz": 0.0, "dpitch": 0.07, "dyaw": 2.9, "droll": 0.0}, {"dx": 0.84, "dy": -3.22, "dz": 0.0, "dpitch": 0.21, "dyaw": 5.03, "droll": 0.0}, {"dx": 0.66, "dy": -4.4, "dz": 0.0, "dpitch": 0.46, "dyaw": 7.81, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-100.78, -38.31, 20.0, -43.67, -29.57, 0.0]
  Target bbox: [620.79, 322.86, 659.54, 396.45]

Frame 2:
  Drone pose: [-100.92, -39.46, 20.0, -43.32, -27.05, 0.0]
  Target bbox: [618.83, 320.68, 661.57, 398.79]

Frame 3:
  Drone pose: [-101.02, -40.59, 20.0, -42.92, -24.69, 0.0]
  Target bbox: [619.95, 322.45, 660.34, 396.96]

Frame 4:
  Drone pose: [-101.03, -41.61, 20.0, -42.57, -22.79, 0.0]
  Target bbox: [619.06, 322.01, 661.2, 397.42]

Frame 5 (current):
  Drone pose: [-100.72, -42.29, 20.0, -42.42, -22.11, 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.92, "ymin": 322.66, "xmax": 660.34, "ymax": 396.8}, "waypoint_deltas": [{"dx": 0.41, "dy": -0.55, "dz": 0.0, "dpitch": 0.09, "dyaw": 0.21, "droll": 0.0}, {"dx": 0.87, "dy": -1.01, "dz": 0.0, "dpitch": 0.17, "dyaw": 0.16, "droll": 0.0}, {"dx": 1.34, "dy": -1.43, "dz": 0.0, "dpitch": 0.24, "dyaw": 0.0, "droll": 0.0}, {"dx": 1.8, "dy": -1.86, "dz": 0.0, "dpitch": 0.07, "dyaw": 1.14, "droll": 0.0}, {"dx": 2.25, "dy": -2.33, "dz": 0.0, "dpitch": 0.15, "dyaw": 1.09, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-128.65, 10.68, 22.0, -52.1, -66.7, 0.0]
  Target bbox: [566.79, 374.65, 616.36, 453.23]

Frame 2:
  Drone pose: [-129.48, 10.14, 21.2, -52.0, -66.32, 0.0]
  Target bbox: [619.16, 356.46, 667.64, 437.35]

Frame 3:
  Drone pose: [-129.51, 9.96, 20.67, -53.4, -63.82, 0.0]
  Target bbox: [610.72, 316.53, 669.48, 402.17]

Frame 4:
  Drone pose: [-129.49, 9.77, 20.64, -53.26, -61.76, 0.0]
  Target bbox: [614.57, 316.7, 664.96, 401.99]

Frame 5 (current):
  Drone pose: [-129.42, 9.6, 20.62, -52.3, -60.91, 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.97, "ymin": 319.66, "xmax": 662.68, "ymax": 399.03}, "waypoint_deltas": [{"dx": 0.3, "dy": -0.16, "dz": -0.03, "dpitch": 0.75, "dyaw": 0.0, "droll": 0.0}, {"dx": 0.65, "dy": -0.38, "dz": -0.05, "dpitch": 1.37, "dyaw": -0.01, "droll": 0.0}, {"dx": 1.0, "dy": -0.64, "dz": -0.07, "dpitch": 1.89, "dyaw": 0.05, "droll": 0.0}, {"dx": 1.36, "dy": -0.96, "dz": -0.09, "dpitch": 2.32, "dyaw": 0.17, "droll": 0.0}, {"dx": 1.72, "dy": -1.32, "dz": -0.2, "dpitch": 2.81, "dyaw": 0.35, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-127.34, 7.89, 20.39, -49.16, -60.34, 0.0]
  Target bbox: [616.14, 319.36, 663.45, 399.63]

Frame 2:
  Drone pose: [-127.0, 7.46, 20.36, -48.89, -59.98, 0.0]
  Target bbox: [616.54, 319.85, 663.08, 399.1]

Frame 3:
  Drone pose: [-126.73, 6.95, 20.33, -49.45, -55.12, 0.0]
  Target bbox: [571.33, 309.15, 614.95, 385.49]

Frame 4:
  Drone pose: [-126.46, 6.41, 20.3, -45.47, -58.82, 0.0]
  Target bbox: [617.85, 371.86, 668.67, 455.49]

Frame 5 (current):
  Drone pose: [-125.77, 6.16, 20.24, -43.74, -58.05, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 676.7, "ymin": 353.42, "xmax": 722.05, "ymax": 431.3}, "waypoint_deltas": [{"dx": 1.1, "dy": -0.06, "dz": 0.0, "dpitch": -4.53, "dyaw": -3.93, "droll": 0.0}, {"dx": 2.09, "dy": -0.14, "dz": -0.02, "dpitch": -4.25, "dyaw": -6.02, "droll": 0.0}, {"dx": 3.29, "dy": -0.11, "dz": -0.05, "dpitch": -3.89, "dyaw": -8.84, "droll": 0.0}, {"dx": 4.49, "dy": 0.03, "dz": -0.07, "dpitch": -3.32, "dyaw": -11.7, "droll": 0.0}, {"dx": 5.59, "dy": 0.11, "dz": -0.09, "dpitch": -2.97, "dyaw": -15.64, "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: [-119.23, 6.26, 20.14, -43.85, -81.66, 0.0]
  Target bbox: [670.85, 365.3, 719.3, 439.49]

Frame 2:
  Drone pose: [-118.9, 5.94, 20.12, -46.47, -74.44, 0.0]
  Target bbox: [572.15, 316.16, 622.19, 393.43]

Frame 3:
  Drone pose: [-118.74, 5.51, 20.11, -46.03, -78.63, 0.0]
  Target bbox: [618.2, 321.9, 662.19, 397.23]

Frame 4:
  Drone pose: [-118.62, 5.03, 20.09, -43.27, -74.0, 0.0]
  Target bbox: [558.26, 369.2, 604.49, 446.0]

Frame 5 (current):
  Drone pose: [-118.38, 4.51, 19.97, -46.83, -81.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": 613.92, "ymin": 319.26, "xmax": 665.78, "ymax": 400.01}, "waypoint_deltas": [{"dx": 0.13, "dy": -0.48, "dz": 0.1, "dpitch": 0.73, "dyaw": 1.17, "droll": 0.0}, {"dx": 0.44, "dy": -0.97, "dz": 0.09, "dpitch": 0.82, "dyaw": 1.76, "droll": 0.0}, {"dx": 0.83, "dy": -1.47, "dz": 0.08, "dpitch": 0.86, "dyaw": 2.09, "droll": 0.0}, {"dx": 1.28, "dy": -1.97, "dz": 0.07, "dpitch": 0.89, "dyaw": 2.23, "droll": 0.0}, {"dx": 1.77, "dy": -2.46, "dz": 0.07, "dpitch": 0.91, "dyaw": 2.28, "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.61, 1.09, 20.03, -48.02, -74.07, 0.0]
  Target bbox: [556.7, 285.64, 604.75, 363.65]

Frame 2:
  Drone pose: [-114.93, 0.68, 19.99, -41.69, -77.41, 0.0]
  Target bbox: [620.77, 325.0, 658.89, 394.36]

Frame 3:
  Drone pose: [-114.59, 0.15, 20.02, -48.4, -75.0, 0.0]
  Target bbox: [563.44, 274.17, 616.9, 358.84]

Frame 4:
  Drone pose: [-114.06, -0.34, 20.02, -47.72, -74.66, 0.0]
  Target bbox: [562.72, 288.51, 608.13, 366.66]

Frame 5 (current):
  Drone pose: [-113.54, -0.83, 20.01, -45.72, -79.33, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 613.41, "ymin": 317.31, "xmax": 666.36, "ymax": 402.15}, "waypoint_deltas": [{"dx": 0.52, "dy": -0.5, "dz": 0.0, "dpitch": 0.0, "dyaw": -0.06, "droll": 0.0}, {"dx": 1.03, "dy": -1.02, "dz": 0.0, "dpitch": -0.03, "dyaw": -0.07, "droll": 0.0}, {"dx": 1.52, "dy": -1.55, "dz": 0.0, "dpitch": -0.07, "dyaw": -0.03, "droll": 0.0}, {"dx": 1.99, "dy": -2.09, "dz": 0.0, "dpitch": -0.12, "dyaw": 0.07, "droll": 0.0}, {"dx": 2.45, "dy": -2.64, "dz": -0.01, "dpitch": -0.18, "dyaw": 0.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: [-110.64, -4.03, 20.0, -45.38, -76.75, 0.0]
  Target bbox: [588.35, 328.67, 639.98, 411.31]

Frame 2:
  Drone pose: [-110.2, -4.59, 20.0, -46.05, -78.71, 0.0]
  Target bbox: [613.48, 317.49, 666.34, 401.89]

Frame 3:
  Drone pose: [-109.75, -5.13, 20.0, -42.15, -83.52, 0.0]
  Target bbox: [672.61, 386.02, 725.08, 469.64]

Frame 4:
  Drone pose: [-109.32, -5.65, 20.0, -46.11, -78.3, 0.0]
  Target bbox: [618.97, 320.8, 660.88, 398.35]

Frame 5 (current):
  Drone pose: [-108.93, -6.16, 20.0, -48.9, -82.96, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 672.02, "ymin": 271.85, "xmax": 725.68, "ymax": 356.64}, "waypoint_deltas": [{"dx": 0.34, "dy": -0.51, "dz": 0.0, "dpitch": 2.85, "dyaw": 5.52, "droll": 0.0}, {"dx": 0.64, "dy": -1.04, "dz": 0.0, "dpitch": 2.88, "dyaw": 6.15, "droll": 0.0}, {"dx": 0.94, "dy": -1.57, "dz": 0.0, "dpitch": 2.73, "dyaw": 5.24, "droll": 0.0}, {"dx": 1.28, "dy": -2.08, "dz": 0.0, "dpitch": 2.6, "dyaw": 4.19, "droll": 0.0}, {"dx": 1.66, "dy": -2.58, "dz": 0.0, "dpitch": 2.65, "dyaw": 4.56, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-106.58, -9.7, 20.0, -46.83, -72.46, 0.0]
  Target bbox: [554.53, 308.13, 607.56, 390.25]

Frame 2:
  Drone pose: [-106.34, -10.2, 20.0, -49.1, -77.79, 0.0]
  Target bbox: [632.65, 269.47, 674.5, 345.82]

Frame 3:
  Drone pose: [-106.14, -10.71, 20.0, -46.61, -72.83, 0.0]
  Target bbox: [561.26, 313.17, 614.29, 391.63]

Frame 4:
  Drone pose: [-105.92, -11.23, 20.0, -46.74, -72.92, 0.0]
  Target bbox: [554.89, 311.19, 607.43, 393.42]

Frame 5 (current):
  Drone pose: [-105.58, -11.86, 20.07, -44.6, -82.37, 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.33, "ymin": 401.5, "xmax": 671.14, "ymax": 483.74}, "waypoint_deltas": [{"dx": 0.27, "dy": -0.4, "dz": -0.07, "dpitch": -1.67, "dyaw": 4.12, "droll": 0.0}, {"dx": 0.7, "dy": -0.89, "dz": -0.07, "dpitch": -1.64, "dyaw": 4.33, "droll": 0.0}, {"dx": 1.2, "dy": -1.36, "dz": -0.07, "dpitch": -1.6, "dyaw": 4.31, "droll": 0.0}, {"dx": 1.72, "dy": -1.83, "dz": -0.07, "dpitch": -1.55, "dyaw": 4.24, "droll": 0.0}, {"dx": 2.15, "dy": -2.32, "dz": -0.07, "dpitch": -1.51, "dyaw": 4.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: [-103.51, -14.89, 20.14, -49.77, -80.47, 0.0]
  Target bbox: [614.35, 317.35, 665.5, 401.65]

Frame 2:
  Drone pose: [-103.45, -15.6, 20.0, -46.37, -74.51, 0.0]
  Target bbox: [615.56, 319.68, 664.12, 399.5]

Frame 3:
  Drone pose: [-103.7, -16.34, 19.99, -54.43, -78.39, 0.0]
  Target bbox: [648.37, 244.01, 705.01, 331.98]

Frame 4:
  Drone pose: [-103.68, -17.13, 20.0, -46.59, -70.25, 0.0]
  Target bbox: [618.19, 320.4, 661.58, 398.71]

Frame 5 (current):
  Drone pose: [-104.21, -18.12, 20.0, -46.7, -66.63, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 615.69, "ymin": 319.2, "xmax": 663.99, "ymax": 399.98}, "waypoint_deltas": [{"dx": -0.63, "dy": -1.04, "dz": 0.0, "dpitch": -0.01, "dyaw": 4.01, "droll": 0.0}, {"dx": -1.28, "dy": -2.13, "dz": 0.0, "dpitch": 0.08, "dyaw": 8.13, "droll": 0.0}, {"dx": -1.85, "dy": -3.18, "dz": 0.0, "dpitch": 0.51, "dyaw": 11.94, "droll": 0.0}, {"dx": -2.06, "dy": -4.05, "dz": 0.0, "dpitch": 0.71, "dyaw": 14.43, "droll": 0.0}, {"dx": -2.21, "dy": -4.89, "dz": 0.0, "dpitch": 0.93, "dyaw": 16.7, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-106.44, -23.78, 20.0, -41.31, -53.16, 0.0]
  Target bbox: [679.91, 394.67, 718.25, 470.97]

Frame 2:
  Drone pose: [-106.31, -24.48, 20.0, -50.4, -51.89, 0.0]
  Target bbox: [673.86, 235.63, 725.59, 319.12]

Frame 3:
  Drone pose: [-106.11, -25.28, 20.06, -49.34, -57.13, 0.0]
  Target bbox: [664.9, 237.43, 711.57, 316.06]

Frame 4:
  Drone pose: [-105.81, -25.76, 20.0, -45.17, -45.2, 0.0]
  Target bbox: [615.99, 320.77, 664.33, 398.51]

Frame 5 (current):
  Drone pose: [-105.35, -26.45, 20.06, -48.13, -42.82, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 566.12, "ymin": 241.57, "xmax": 619.38, "ymax": 325.73}, "waypoint_deltas": [{"dx": 0.32, "dy": -0.45, "dz": -0.06, "dpitch": 3.05, "dyaw": -1.6, "droll": 0.0}, {"dx": 0.72, "dy": -1.01, "dz": -0.06, "dpitch": 3.09, "dyaw": -1.25, "droll": 0.0}, {"dx": 1.12, "dy": -1.57, "dz": -0.06, "dpitch": 3.13, "dyaw": -0.91, "droll": 0.0}, {"dx": 1.52, "dy": -2.13, "dz": -0.06, "dpitch": 3.18, "dyaw": -0.57, "droll": 0.0}, {"dx": 1.92, "dy": -2.69, "dz": -0.06, "dpitch": 3.24, "dyaw": -0.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: [-102.75, -30.19, 19.97, -49.34, -41.66, 0.0]
  Target bbox: [651.05, 321.95, 695.69, 403.23]

Frame 2:
  Drone pose: [-102.21, -30.9, 20.08, -44.47, -48.13, 0.0]
  Target bbox: [674.26, 367.82, 720.25, 450.21]

Frame 3:
  Drone pose: [-101.88, -31.37, 20.0, -44.63, -41.62, 0.0]
  Target bbox: [619.56, 321.99, 660.98, 397.23]

Frame 4:
  Drone pose: [-101.46, -31.93, 20.0, -44.6, -41.32, 0.0]
  Target bbox: [622.37, 322.25, 658.09, 396.97]

Frame 5 (current):
  Drone pose: [-101.0, -32.47, 20.0, -44.59, -41.17, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 619.42, "ymin": 321.87, "xmax": 661.14, "ymax": 397.42}, "waypoint_deltas": [{"dx": 0.49, "dy": -0.53, "dz": 0.0, "dpitch": -0.03, "dyaw": 0.07, "droll": 0.0}, {"dx": 0.7, "dy": -1.34, "dz": 0.0, "dpitch": 0.0, "dyaw": 1.35, "droll": 0.0}, {"dx": 0.84, "dy": -2.21, "dz": 0.0, "dpitch": 0.07, "dyaw": 2.9, "droll": 0.0}, {"dx": 0.84, "dy": -3.22, "dz": 0.0, "dpitch": 0.21, "dyaw": 5.03, "droll": 0.0}, {"dx": 0.66, "dy": -4.4, "dz": 0.0, "dpitch": 0.46, "dyaw": 7.81, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-100.78, -38.31, 20.0, -43.67, -29.57, 0.0]
  Target bbox: [620.54, 322.51, 659.8, 396.82]

Frame 2:
  Drone pose: [-100.92, -39.46, 20.0, -43.32, -27.05, 0.0]
  Target bbox: [616.6, 320.45, 663.84, 399.12]

Frame 3:
  Drone pose: [-101.02, -40.59, 20.0, -42.92, -24.69, 0.0]
  Target bbox: [619.4, 322.02, 660.91, 397.43]

Frame 4:
  Drone pose: [-101.03, -41.61, 20.0, -43.32, -22.44, 0.0]
  Target bbox: [615.28, 309.89, 656.18, 384.69]

Frame 5 (current):
  Drone pose: [-100.72, -42.29, 20.0, -46.08, -18.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": 581.77, "ymin": 264.41, "xmax": 612.82, "ymax": 333.59}, "waypoint_deltas": [{"dx": 0.41, "dy": -0.55, "dz": 0.0, "dpitch": 3.75, "dyaw": -3.22, "droll": 0.0}, {"dx": 0.87, "dy": -1.01, "dz": 0.0, "dpitch": 3.83, "dyaw": -3.27, "droll": 0.0}, {"dx": 1.34, "dy": -1.43, "dz": 0.0, "dpitch": 3.9, "dyaw": -3.43, "droll": 0.0}, {"dx": 1.8, "dy": -1.86, "dz": 0.0, "dpitch": 3.73, "dyaw": -2.29, "droll": 0.0}, {"dx": 2.25, "dy": -2.33, "dz": 0.0, "dpitch": 3.81, "dyaw": -2.34, "droll": 0.0}]}