[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: [-124.11, -50.06, 22.0, -54.53, 0.0, 0.0]
  Target bbox: [625.22, 322.46, 654.78, 396.42]

Frame 2:
  Drone pose: [-124.77, -49.34, 22.54, -53.16, -2.55, 0.0]
  Target bbox: [624.93, 328.44, 654.81, 390.5]

Frame 3:
  Drone pose: [-124.55, -48.57, 22.56, -52.63, -5.18, 0.0]
  Target bbox: [624.45, 324.55, 655.21, 394.47]

Frame 4:
  Drone pose: [-124.42, -47.91, 22.59, -51.94, -7.26, 0.0]
  Target bbox: [623.46, 323.09, 656.14, 396.09]

Frame 5 (current):
  Drone pose: [-124.16, -47.29, 22.61, -51.44, -9.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": 623.56, "ymin": 329.82, "xmax": 656.24, "ymax": 389.24}, "waypoint_deltas": [{"dx": 0.62, "dy": 0.26, "dz": 0.03, "dpitch": -0.16, "dyaw": -0.91, "droll": 0.0}, {"dx": 1.32, "dy": 0.41, "dz": 0.06, "dpitch": -0.47, "dyaw": -1.52, "droll": 0.0}, {"dx": 2.02, "dy": 0.49, "dz": 0.09, "dpitch": -0.81, "dyaw": -1.95, "droll": 0.0}, {"dx": 2.66, "dy": 0.54, "dz": 0.12, "dpitch": -1.05, "dyaw": -2.19, "droll": 0.0}, {"dx": 3.25, "dy": 0.57, "dz": 0.2, "dpitch": -1.29, "dyaw": -2.36, "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: [-120.91, -46.72, 22.81, -52.73, -11.57, 0.0]
  Target bbox: [622.5, 322.97, 657.11, 396.2]

Frame 2:
  Drone pose: [-120.34, -46.69, 22.86, -52.9, -11.7, 0.0]
  Target bbox: [623.25, 325.54, 656.46, 393.53]

Frame 3:
  Drone pose: [-119.82, -46.69, 22.92, -53.0, -11.72, 0.0]
  Target bbox: [623.82, 330.43, 656.02, 388.6]

Frame 4:
  Drone pose: [-119.34, -46.71, 22.98, -53.06, -11.66, 0.0]
  Target bbox: [623.99, 329.65, 655.82, 389.4]

Frame 5 (current):
  Drone pose: [-118.84, -46.71, 23.05, -53.14, -11.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": 623.26, "ymin": 330.05, "xmax": 656.57, "ymax": 388.96}, "waypoint_deltas": [{"dx": 0.5, "dy": 0.0, "dz": 0.07, "dpitch": -0.08, "dyaw": 0.0, "droll": 0.0}, {"dx": 0.98, "dy": -0.02, "dz": 0.15, "dpitch": -0.15, "dyaw": 0.06, "droll": 0.0}, {"dx": 1.46, "dy": -0.03, "dz": 0.23, "dpitch": -0.23, "dyaw": 0.11, "droll": 0.0}, {"dx": 1.95, "dy": -0.04, "dz": 0.32, "dpitch": -0.33, "dyaw": 0.16, "droll": 0.0}, {"dx": 2.47, "dy": -0.03, "dz": 0.4, "dpitch": -0.46, "dyaw": 0.1, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-116.37, -46.74, 23.45, -53.6, -11.53, 0.0]
  Target bbox: [623.7, 327.97, 656.06, 391.07]

Frame 2:
  Drone pose: [-115.87, -46.72, 23.55, -53.71, -11.58, 0.0]
  Target bbox: [622.99, 324.12, 656.65, 395.04]

Frame 3:
  Drone pose: [-115.39, -46.72, 23.64, -53.79, -11.57, 0.0]
  Target bbox: [623.77, 327.98, 655.99, 391.07]

Frame 4:
  Drone pose: [-114.9, -46.7, 23.73, -53.87, -11.64, 0.0]
  Target bbox: [622.61, 323.95, 657.02, 395.21]

Frame 5 (current):
  Drone pose: [-114.38, -46.66, 23.81, -53.99, -11.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": 624.32, "ymin": 331.45, "xmax": 655.52, "ymax": 387.63}, "waypoint_deltas": [{"dx": 0.52, "dy": -0.02, "dz": 0.15, "dpitch": -0.21, "dyaw": 0.04, "droll": 0.0}, {"dx": 1.07, "dy": -0.03, "dz": 0.26, "dpitch": -0.41, "dyaw": 0.05, "droll": 0.0}, {"dx": 1.44, "dy": -0.14, "dz": 0.37, "dpitch": -0.38, "dyaw": 0.51, "droll": 0.0}, {"dx": 1.76, "dy": -0.26, "dz": 0.47, "dpitch": -0.08, "dyaw": -0.61, "droll": 0.0}, {"dx": 2.17, "dy": -0.59, "dz": 0.6, "dpitch": -0.19, "dyaw": 0.52, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-112.21, -47.25, 24.41, -54.18, -11.27, 0.0]
  Target bbox: [623.76, 325.92, 655.94, 393.18]

Frame 2:
  Drone pose: [-111.82, -47.39, 24.44, -54.1, -10.71, 0.0]
  Target bbox: [623.61, 330.19, 656.18, 388.9]

Frame 3:
  Drone pose: [-111.47, -47.5, 24.45, -53.9, -10.28, 0.0]
  Target bbox: [624.92, 331.7, 654.9, 387.44]

Frame 4:
  Drone pose: [-111.18, -47.62, 24.46, -53.62, -9.77, 0.0]
  Target bbox: [624.28, 326.62, 655.43, 392.51]

Frame 5 (current):
  Drone pose: [-110.91, -47.83, 25.26, -54.24, -8.94, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 624.55, "ymin": 331.1, "xmax": 655.25, "ymax": 388.05}, "waypoint_deltas": [{"dx": 0.31, "dy": -0.05, "dz": -0.22, "dpitch": 0.52, "dyaw": 0.25, "droll": 0.0}, {"dx": 0.62, "dy": -0.06, "dz": -0.13, "dpitch": 0.84, "dyaw": -1.21, "droll": 0.0}, {"dx": 0.94, "dy": 0.05, "dz": -0.23, "dpitch": 1.39, "dyaw": -2.99, "droll": 0.0}, {"dx": 1.27, "dy": 0.25, "dz": 0.27, "dpitch": 1.31, "dyaw": -5.01, "droll": 0.0}, {"dx": 1.61, "dy": 0.66, "dz": -0.53, "dpitch": 2.81, "dyaw": -7.54, "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: [-109.06, -46.71, 23.96, -49.71, -18.99, 0.0]
  Target bbox: [622.61, 326.67, 657.12, 392.69]

Frame 2:
  Drone pose: [-108.72, -46.9, 23.83, -49.41, -18.31, 0.0]
  Target bbox: [621.59, 327.86, 658.55, 391.51]

Frame 3:
  Drone pose: [-108.34, -46.82, 23.68, -48.79, -19.76, 0.0]
  Target bbox: [623.28, 327.91, 656.5, 391.44]

Frame 4:
  Drone pose: [-107.89, -46.78, 23.45, -48.42, -19.85, 0.0]
  Target bbox: [624.05, 329.34, 656.09, 390.02]

Frame 5 (current):
  Drone pose: [-107.47, -46.76, 23.25, -47.8, -21.14, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 624.25, "ymin": 330.76, "xmax": 655.64, "ymax": 388.57}, "waypoint_deltas": [{"dx": 0.5, "dy": -0.05, "dz": -0.22, "dpitch": 0.25, "dyaw": 0.13, "droll": 0.0}, {"dx": 1.61, "dy": -0.12, "dz": -0.44, "dpitch": -0.04, "dyaw": -1.65, "droll": 0.0}, {"dx": 2.81, "dy": 0.03, "dz": -0.7, "dpitch": -0.55, "dyaw": -2.88, "droll": 0.0}, {"dx": 4.22, "dy": -0.32, "dz": -0.88, "dpitch": -1.47, "dyaw": -4.46, "droll": 0.0}, {"dx": 5.8, "dy": -1.15, "dz": -1.05, "dpitch": -3.34, "dyaw": -3.52, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-101.67, -47.91, 22.2, -51.14, -24.66, 0.0]
  Target bbox: [622.31, 328.27, 657.6, 390.8]

Frame 2:
  Drone pose: [-101.18, -49.05, 22.02, -51.63, -21.09, 0.0]
  Target bbox: [616.54, 322.41, 663.7, 396.73]

Frame 3:
  Drone pose: [-100.95, -49.98, 21.85, -51.23, -19.38, 0.0]
  Target bbox: [621.09, 324.17, 658.62, 394.97]

Frame 4:
  Drone pose: [-101.12, -50.85, 21.69, -50.39, -15.9, 0.0]
  Target bbox: [623.65, 326.42, 656.51, 392.7]

Frame 5 (current):
  Drone pose: [-101.11, -51.12, 21.54, -49.32, -16.18, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 621.65, "ymin": 323.7, "xmax": 658.01, "ymax": 395.55}, "waypoint_deltas": [{"dx": 0.03, "dy": -0.29, "dz": -0.15, "dpitch": 0.8, "dyaw": 1.27, "droll": 0.0}, {"dx": 0.1, "dy": -0.49, "dz": -0.28, "dpitch": 1.75, "dyaw": 0.75, "droll": 0.0}, {"dx": 0.18, "dy": -0.68, "dz": -0.41, "dpitch": 2.48, "dyaw": 1.61, "droll": 0.0}, {"dx": 0.57, "dy": -0.83, "dz": -0.52, "dpitch": 2.94, "dyaw": 0.69, "droll": 0.0}, {"dx": 1.0, "dy": -0.97, "dz": -0.63, "dpitch": 3.14, "dyaw": 1.16, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-100.11, -52.09, 20.91, -46.18, -15.02, 0.0]
  Target bbox: [622.1, 325.07, 658.09, 394.29]

Frame 2:
  Drone pose: [-99.66, -52.23, 20.81, -45.82, -16.02, 0.0]
  Target bbox: [621.92, 322.38, 657.69, 397.03]

Frame 3:
  Drone pose: [-99.22, -52.37, 20.72, -45.67, -15.58, 0.0]
  Target bbox: [621.87, 323.08, 657.76, 396.32]

Frame 4:
  Drone pose: [-98.77, -52.51, 20.63, -45.53, -15.13, 0.0]
  Target bbox: [616.71, 321.98, 663.44, 397.46]

Frame 5 (current):
  Drone pose: [-98.32, -52.66, 20.56, -45.21, -16.08, 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.08, "ymin": 323.02, "xmax": 657.55, "ymax": 396.43}, "waypoint_deltas": [{"dx": 0.45, "dy": -0.17, "dz": -0.07, "dpitch": 0.1, "dyaw": 0.51, "droll": 0.0}, {"dx": 0.92, "dy": -0.34, "dz": -0.13, "dpitch": 0.38, "dyaw": -0.38, "droll": 0.0}, {"dx": 1.39, "dy": -0.52, "dz": -0.19, "dpitch": 0.43, "dyaw": 0.15, "droll": 0.0}, {"dx": 1.87, "dy": -0.71, "dz": -0.24, "dpitch": 0.65, "dyaw": -0.71, "droll": 0.0}, {"dx": 2.37, "dy": -0.9, "dz": -0.28, "dpitch": 0.65, "dyaw": -0.18, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-95.45, -53.75, 20.24, -44.37, -17.13, 0.0]
  Target bbox: [621.78, 322.95, 657.84, 396.58]

Frame 2:
  Drone pose: [-94.96, -53.93, 20.2, -44.39, -16.63, 0.0]
  Target bbox: [617.95, 322.9, 662.26, 396.64]

Frame 3:
  Drone pose: [-94.46, -54.1, 20.17, -44.21, -17.53, 0.0]
  Target bbox: [623.16, 327.81, 656.68, 391.49]

Frame 4:
  Drone pose: [-93.96, -54.27, 20.15, -44.24, -17.05, 0.0]
  Target bbox: [623.18, 327.81, 656.66, 391.49]

Frame 5 (current):
  Drone pose: [-93.47, -54.45, 20.12, -44.27, -16.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": 623.66, "ymin": 326.29, "xmax": 656.5, "ymax": 393.08}, "waypoint_deltas": [{"dx": 0.5, "dy": -0.19, "dz": -0.02, "dpitch": 0.16, "dyaw": -0.88, "droll": 0.0}, {"dx": 1.0, "dy": -0.38, "dz": -0.03, "dpitch": 0.11, "dyaw": -0.34, "droll": 0.0}, {"dx": 1.5, "dy": -0.58, "dz": -0.05, "dpitch": 0.26, "dyaw": -1.18, "droll": 0.0}, {"dx": 2.0, "dy": -0.78, "dz": -0.06, "dpitch": 0.2, "dyaw": -0.62, "droll": 0.0}, {"dx": 2.5, "dy": -0.98, "dz": -0.07, "dpitch": 0.34, "dyaw": -1.44, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-90.97, -55.43, 20.05, -43.93, -17.99, 0.0]
  Target bbox: [621.81, 323.99, 657.86, 395.5]

Frame 2:
  Drone pose: [-90.47, -55.63, 20.04, -44.0, -17.43, 0.0]
  Target bbox: [622.22, 324.57, 658.0, 394.88]

Frame 3:
  Drone pose: [-89.97, -55.83, 20.03, -43.86, -18.27, 0.0]
  Target bbox: [622.13, 325.55, 657.62, 393.86]

Frame 4:
  Drone pose: [-89.47, -56.02, 20.03, -43.93, -17.75, 0.0]
  Target bbox: [620.89, 324.67, 659.29, 394.77]

Frame 5 (current):
  Drone pose: [-88.97, -56.2, 20.02, -43.78, -18.62, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 622.66, "ymin": 326.6, "xmax": 657.15, "ymax": 392.73}, "waypoint_deltas": [{"dx": 0.49, "dy": -0.18, "dz": 0.0, "dpitch": -0.07, "dyaw": 0.5, "droll": 0.0}, {"dx": 0.99, "dy": -0.37, "dz": -0.01, "dpitch": -0.14, "dyaw": 1.02, "droll": 0.0}, {"dx": 1.49, "dy": -0.56, "dz": -0.01, "dpitch": 0.0, "dyaw": 0.18, "droll": 0.0}, {"dx": 1.99, "dy": -0.77, "dz": -0.01, "dpitch": -0.09, "dyaw": 0.75, "droll": 0.0}, {"dx": 2.49, "dy": -0.98, "dz": -0.01, "dpitch": 0.04, "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: [-86.48, -57.18, 20.01, -43.74, -18.66, 0.0]
  Target bbox: [621.19, 321.81, 658.41, 397.72]

Frame 2:
  Drone pose: [-85.98, -57.4, 20.0, -43.83, -18.06, 0.0]
  Target bbox: [617.04, 322.24, 663.19, 397.33]

Frame 3:
  Drone pose: [-85.48, -57.62, 20.0, -43.7, -18.82, 0.0]
  Target bbox: [621.65, 323.32, 658.01, 396.18]

Frame 4:
  Drone pose: [-84.99, -57.84, 20.0, -43.8, -18.22, 0.0]
  Target bbox: [622.46, 325.69, 657.71, 393.73]

Frame 5 (current):
  Drone pose: [-84.49, -58.06, 20.0, -43.67, -18.99, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 623.01, "ymin": 327.03, "xmax": 656.8, "ymax": 392.33}, "waypoint_deltas": [{"dx": 0.5, "dy": -0.2, "dz": 0.0, "dpitch": -0.09, "dyaw": 0.56, "droll": 0.0}, {"dx": 1.0, "dy": -0.4, "dz": 0.0, "dpitch": 0.05, "dyaw": -0.26, "droll": 0.0}, {"dx": 1.5, "dy": -0.6, "dz": 0.0, "dpitch": -0.04, "dyaw": 0.28, "droll": 0.0}, {"dx": 2.0, "dy": -0.8, "dz": 0.0, "dpitch": -0.12, "dyaw": 0.82, "droll": 0.0}, {"dx": 2.5, "dy": -1.0, "dz": 0.0, "dpitch": 0.01, "dyaw": 0.0, "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: [-124.21, -50.15, 22.0, -58.41, -4.66, 0.0]
  Target bbox: [673.24, 259.21, 705.31, 326.6]

Frame 2:
  Drone pose: [-124.7, -49.38, 22.48, -53.2, -2.39, 0.0]
  Target bbox: [624.65, 323.13, 654.95, 395.91]

Frame 3:
  Drone pose: [-124.61, -48.65, 22.71, -53.29, -1.65, 0.0]
  Target bbox: [590.76, 317.33, 622.71, 384.28]

Frame 4:
  Drone pose: [-124.42, -47.91, 22.59, -48.55, -9.3, 0.0]
  Target bbox: [644.32, 384.56, 678.46, 448.9]

Frame 5 (current):
  Drone pose: [-124.16, -47.29, 22.61, -54.26, -5.92, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 589.43, "ymin": 279.91, "xmax": 620.64, "ymax": 346.0}, "waypoint_deltas": [{"dx": 0.62, "dy": 0.26, "dz": 0.03, "dpitch": 2.66, "dyaw": -4.2, "droll": 0.0}, {"dx": 1.32, "dy": 0.41, "dz": 0.06, "dpitch": 2.35, "dyaw": -4.81, "droll": 0.0}, {"dx": 2.02, "dy": 0.49, "dz": 0.09, "dpitch": 2.01, "dyaw": -5.24, "droll": 0.0}, {"dx": 2.66, "dy": 0.54, "dz": 0.12, "dpitch": 1.77, "dyaw": -5.48, "droll": 0.0}, {"dx": 3.25, "dy": 0.57, "dz": 0.2, "dpitch": 1.53, "dyaw": -5.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: [-120.91, -46.72, 22.81, -51.84, -15.97, 0.0]
  Target bbox: [667.46, 345.73, 702.62, 405.94]

Frame 2:
  Drone pose: [-120.34, -46.69, 22.86, -52.9, -11.7, 0.0]
  Target bbox: [622.18, 325.89, 657.52, 393.15]

Frame 3:
  Drone pose: [-119.88, -46.81, 23.03, -54.85, -9.66, 0.0]
  Target bbox: [607.18, 301.32, 638.83, 358.73]

Frame 4:
  Drone pose: [-119.23, -46.76, 23.06, -53.34, -11.55, 0.0]
  Target bbox: [623.11, 324.32, 656.55, 394.75]

Frame 5 (current):
  Drone pose: [-118.92, -46.6, 23.1, -53.04, -11.98, 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.07, "ymin": 322.86, "xmax": 657.55, "ymax": 396.26}, "waypoint_deltas": [{"dx": 0.58, "dy": -0.11, "dz": 0.02, "dpitch": -0.18, "dyaw": 0.35, "droll": 0.0}, {"dx": 1.06, "dy": -0.13, "dz": 0.1, "dpitch": -0.25, "dyaw": 0.41, "droll": 0.0}, {"dx": 1.54, "dy": -0.14, "dz": 0.18, "dpitch": -0.33, "dyaw": 0.46, "droll": 0.0}, {"dx": 2.03, "dy": -0.15, "dz": 0.27, "dpitch": -0.43, "dyaw": 0.51, "droll": 0.0}, {"dx": 2.55, "dy": -0.14, "dz": 0.35, "dpitch": -0.56, "dyaw": 0.45, "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: [-116.31, -46.7, 23.27, -54.48, -12.61, 0.0]
  Target bbox: [633.12, 313.03, 665.15, 371.97]

Frame 2:
  Drone pose: [-115.76, -46.84, 23.45, -53.8, -11.26, 0.0]
  Target bbox: [623.45, 325.09, 656.23, 393.99]

Frame 3:
  Drone pose: [-115.4, -46.69, 23.55, -56.34, -16.68, 0.0]
  Target bbox: [671.41, 280.49, 708.72, 351.77]

Frame 4:
  Drone pose: [-114.9, -46.7, 23.73, -53.24, -7.45, 0.0]
  Target bbox: [582.19, 343.31, 613.93, 399.37]

Frame 5 (current):
  Drone pose: [-114.38, -46.66, 23.81, -53.99, -11.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": 623.79, "ymin": 326.51, "xmax": 655.92, "ymax": 392.6}, "waypoint_deltas": [{"dx": 0.52, "dy": -0.02, "dz": 0.15, "dpitch": -0.21, "dyaw": 0.04, "droll": 0.0}, {"dx": 1.07, "dy": -0.03, "dz": 0.26, "dpitch": -0.41, "dyaw": 0.05, "droll": 0.0}, {"dx": 1.44, "dy": -0.14, "dz": 0.37, "dpitch": -0.38, "dyaw": 0.51, "droll": 0.0}, {"dx": 1.76, "dy": -0.26, "dz": 0.47, "dpitch": -0.08, "dyaw": -0.61, "droll": 0.0}, {"dx": 2.17, "dy": -0.59, "dz": 0.6, "dpitch": -0.19, "dyaw": 0.52, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-112.22, -47.33, 24.53, -57.58, -12.01, 0.0]
  Target bbox: [634.04, 277.05, 666.16, 333.58]

Frame 2:
  Drone pose: [-111.82, -47.39, 24.44, -57.78, -5.71, 0.0]
  Target bbox: [573.67, 265.2, 606.69, 333.55]

Frame 3:
  Drone pose: [-111.57, -47.37, 24.57, -53.85, -10.63, 0.0]
  Target bbox: [623.38, 329.07, 656.39, 390.06]

Frame 4:
  Drone pose: [-111.28, -47.61, 24.49, -53.51, -9.73, 0.0]
  Target bbox: [624.35, 326.54, 655.35, 392.6]

Frame 5 (current):
  Drone pose: [-110.82, -47.9, 25.09, -52.26, -3.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": 575.93, "ymin": 368.37, "xmax": 605.16, "ymax": 419.59}, "waypoint_deltas": [{"dx": 0.22, "dy": 0.02, "dz": -0.05, "dpitch": -1.46, "dyaw": -4.91, "droll": 0.0}, {"dx": 0.53, "dy": 0.01, "dz": 0.04, "dpitch": -1.14, "dyaw": -6.37, "droll": 0.0}, {"dx": 0.85, "dy": 0.12, "dz": -0.06, "dpitch": -0.59, "dyaw": -8.15, "droll": 0.0}, {"dx": 1.18, "dy": 0.32, "dz": 0.44, "dpitch": -0.67, "dyaw": -10.17, "droll": 0.0}, {"dx": 1.52, "dy": 0.73, "dz": -0.36, "dpitch": 0.83, "dyaw": -12.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: [-108.95, -46.84, 23.88, -48.97, -22.56, 0.0]
  Target bbox: [662.67, 339.87, 701.07, 410.2]

Frame 2:
  Drone pose: [-108.72, -46.98, 23.82, -50.4, -18.4, 0.0]
  Target bbox: [625.04, 312.12, 662.16, 374.7]

Frame 3:
  Drone pose: [-108.34, -46.82, 23.68, -48.79, -19.76, 0.0]
  Target bbox: [623.72, 330.42, 656.15, 388.88]

Frame 4:
  Drone pose: [-107.85, -46.76, 23.62, -46.83, -21.29, 0.0]
  Target bbox: [638.74, 359.62, 671.98, 422.25]

Frame 5 (current):
  Drone pose: [-107.45, -46.69, 23.31, -43.32, -21.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": 629.92, "ymin": 404.44, "xmax": 663.9, "ymax": 467.96}, "waypoint_deltas": [{"dx": 0.48, "dy": -0.12, "dz": -0.28, "dpitch": -4.23, "dyaw": 0.94, "droll": 0.0}, {"dx": 1.59, "dy": -0.19, "dz": -0.5, "dpitch": -4.52, "dyaw": -0.84, "droll": 0.0}, {"dx": 2.79, "dy": -0.04, "dz": -0.76, "dpitch": -5.03, "dyaw": -2.07, "droll": 0.0}, {"dx": 4.2, "dy": -0.39, "dz": -0.94, "dpitch": -5.95, "dyaw": -3.65, "droll": 0.0}, {"dx": 5.78, "dy": -1.22, "dz": -1.11, "dpitch": -7.82, "dyaw": -2.71, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-101.67, -47.91, 22.2, -49.75, -20.25, 0.0]
  Target bbox: [574.87, 353.22, 611.22, 415.29]

Frame 2:
  Drone pose: [-101.09, -49.15, 21.94, -51.72, -20.9, 0.0]
  Target bbox: [619.78, 323.85, 660.44, 395.22]

Frame 3:
  Drone pose: [-100.95, -49.98, 21.85, -51.03, -15.33, 0.0]
  Target bbox: [577.96, 328.81, 615.7, 399.29]

Frame 4:
  Drone pose: [-101.12, -50.85, 21.69, -50.39, -15.9, 0.0]
  Target bbox: [619.96, 325.42, 660.12, 393.67]

Frame 5 (current):
  Drone pose: [-101.07, -51.1, 21.6, -49.3, -16.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": 620.11, "ymin": 330.32, "xmax": 655.54, "ymax": 394.14}, "waypoint_deltas": [{"dx": -0.01, "dy": -0.31, "dz": -0.21, "dpitch": 0.78, "dyaw": 1.2, "droll": 0.0}, {"dx": 0.06, "dy": -0.51, "dz": -0.34, "dpitch": 1.73, "dyaw": 0.68, "droll": 0.0}, {"dx": 0.14, "dy": -0.7, "dz": -0.47, "dpitch": 2.46, "dyaw": 1.54, "droll": 0.0}, {"dx": 0.53, "dy": -0.85, "dz": -0.58, "dpitch": 2.92, "dyaw": 0.62, "droll": 0.0}, {"dx": 0.96, "dy": -0.99, "dz": -0.69, "dpitch": 3.12, "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: [-100.11, -52.09, 20.91, -46.21, -14.17, 0.0]
  Target bbox: [610.87, 324.79, 649.01, 393.67]

Frame 2:
  Drone pose: [-99.66, -52.23, 20.81, -43.49, -16.56, 0.0]
  Target bbox: [629.33, 365.7, 663.35, 431.83]

Frame 3:
  Drone pose: [-99.28, -52.41, 20.69, -48.0, -12.13, 0.0]
  Target bbox: [584.18, 288.26, 617.76, 350.06]

Frame 4:
  Drone pose: [-98.87, -52.63, 20.56, -45.32, -14.7, 0.0]
  Target bbox: [623.37, 325.87, 656.81, 393.49]

Frame 5 (current):
  Drone pose: [-98.25, -52.85, 20.59, -45.43, -15.61, 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.83, "ymin": 323.2, "xmax": 657.79, "ymax": 396.27}, "waypoint_deltas": [{"dx": 0.38, "dy": 0.02, "dz": -0.1, "dpitch": 0.32, "dyaw": 0.04, "droll": 0.0}, {"dx": 0.85, "dy": -0.15, "dz": -0.16, "dpitch": 0.6, "dyaw": -0.85, "droll": 0.0}, {"dx": 1.32, "dy": -0.33, "dz": -0.22, "dpitch": 0.65, "dyaw": -0.32, "droll": 0.0}, {"dx": 1.8, "dy": -0.52, "dz": -0.27, "dpitch": 0.87, "dyaw": -1.18, "droll": 0.0}, {"dx": 2.3, "dy": -0.71, "dz": -0.31, "dpitch": 0.87, "dyaw": -0.65, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-95.28, -53.75, 20.25, -44.63, -17.27, 0.0]
  Target bbox: [621.63, 322.36, 657.98, 397.13]

Frame 2:
  Drone pose: [-94.91, -53.99, 20.35, -44.7, -16.5, 0.0]
  Target bbox: [624.64, 326.97, 655.5, 392.37]

Frame 3:
  Drone pose: [-94.46, -54.1, 20.17, -44.21, -17.53, 0.0]
  Target bbox: [620.02, 321.74, 659.57, 397.77]

Frame 4:
  Drone pose: [-93.83, -54.23, 20.11, -44.35, -17.3, 0.0]
  Target bbox: [621.49, 325.03, 658.25, 394.34]

Frame 5 (current):
  Drone pose: [-93.52, -54.42, 20.11, -43.3, -20.1, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 662.63, "ymin": 340.06, "xmax": 702.52, "ymax": 409.94}, "waypoint_deltas": [{"dx": 0.55, "dy": -0.22, "dz": -0.01, "dpitch": -0.81, "dyaw": 2.67, "droll": 0.0}, {"dx": 1.05, "dy": -0.41, "dz": -0.02, "dpitch": -0.86, "dyaw": 3.21, "droll": 0.0}, {"dx": 1.55, "dy": -0.61, "dz": -0.04, "dpitch": -0.71, "dyaw": 2.37, "droll": 0.0}, {"dx": 2.05, "dy": -0.81, "dz": -0.05, "dpitch": -0.77, "dyaw": 2.93, "droll": 0.0}, {"dx": 2.55, "dy": -1.01, "dz": -0.06, "dpitch": -0.63, "dyaw": 2.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: [-91.1, -55.42, 20.09, -43.8, -17.91, 0.0]
  Target bbox: [620.76, 321.56, 658.79, 398.08]

Frame 2:
  Drone pose: [-90.43, -55.63, 20.15, -43.92, -12.47, 0.0]
  Target bbox: [561.13, 331.93, 598.08, 401.42]

Frame 3:
  Drone pose: [-89.97, -55.83, 20.03, -43.86, -18.27, 0.0]
  Target bbox: [621.45, 322.47, 658.17, 397.06]

Frame 4:
  Drone pose: [-89.48, -55.86, 20.06, -46.1, -23.17, 0.0]
  Target bbox: [683.38, 292.33, 718.44, 357.05]

Frame 5 (current):
  Drone pose: [-88.87, -56.07, 20.11, -44.0, -19.08, 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.54, "ymin": 326.65, "xmax": 657.26, "ymax": 392.72}, "waypoint_deltas": [{"dx": 0.39, "dy": -0.31, "dz": -0.09, "dpitch": 0.15, "dyaw": 0.96, "droll": 0.0}, {"dx": 0.89, "dy": -0.5, "dz": -0.1, "dpitch": 0.08, "dyaw": 1.48, "droll": 0.0}, {"dx": 1.39, "dy": -0.69, "dz": -0.1, "dpitch": 0.22, "dyaw": 0.64, "droll": 0.0}, {"dx": 1.89, "dy": -0.9, "dz": -0.1, "dpitch": 0.13, "dyaw": 1.21, "droll": 0.0}, {"dx": 2.39, "dy": -1.11, "dz": -0.1, "dpitch": 0.26, "dyaw": 0.42, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [-86.47, -57.04, 20.12, -41.62, -22.07, 0.0]
  Target bbox: [659.0, 365.02, 694.2, 430.81]

Frame 2:
  Drone pose: [-86.12, -57.37, 19.88, -43.45, -18.03, 0.0]
  Target bbox: [623.43, 326.02, 656.75, 393.41]

Frame 3:
  Drone pose: [-85.48, -57.62, 20.0, -43.7, -18.82, 0.0]
  Target bbox: [619.64, 320.89, 659.92, 398.7]

Frame 4:
  Drone pose: [-84.94, -57.75, 20.0, -43.83, -18.52, 0.0]
  Target bbox: [620.78, 323.14, 659.47, 396.31]

Frame 5 (current):
  Drone pose: [-84.49, -58.06, 20.0, -43.67, -18.99, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 620.35, "ymin": 322.42, "xmax": 659.29, "ymax": 397.08}, "waypoint_deltas": [{"dx": 0.5, "dy": -0.2, "dz": 0.0, "dpitch": -0.09, "dyaw": 0.56, "droll": 0.0}, {"dx": 1.0, "dy": -0.4, "dz": 0.0, "dpitch": 0.05, "dyaw": -0.26, "droll": 0.0}, {"dx": 1.5, "dy": -0.6, "dz": 0.0, "dpitch": -0.04, "dyaw": 0.28, "droll": 0.0}, {"dx": 2.0, "dy": -0.8, "dz": 0.0, "dpitch": -0.12, "dyaw": 0.82, "droll": 0.0}, {"dx": 2.5, "dy": -1.0, "dz": 0.0, "dpitch": 0.01, "dyaw": 0.0, "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: [111.37, 26.45, 22.0, -46.48, 177.14, 0.0]
  Target bbox: [619.88, 325.29, 660.19, 394.17]

Frame 2:
  Drone pose: [110.85, 26.73, 21.2, -45.39, 176.53, 0.0]
  Target bbox: [628.66, 328.22, 651.12, 391.04]

Frame 3:
  Drone pose: [110.32, 27.02, 20.67, -44.68, 177.35, 0.0]
  Target bbox: [628.63, 325.4, 651.09, 393.95]

Frame 4:
  Drone pose: [109.8, 27.31, 20.64, -44.69, 178.17, 0.0]
  Target bbox: [628.86, 329.78, 650.94, 389.47]

Frame 5 (current):
  Drone pose: [109.28, 27.6, 20.62, -44.69, 179.0, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 629.05, "ymin": 325.97, "xmax": 650.68, "ymax": 393.35}, "waypoint_deltas": [{"dx": -0.52, "dy": 0.28, "dz": -0.03, "dpitch": 0.0, "dyaw": 0.82, "droll": 0.0}, {"dx": -1.04, "dy": 0.57, "dz": -0.05, "dpitch": 0.0, "dyaw": 1.65, "droll": 0.0}, {"dx": -1.56, "dy": 0.86, "dz": -0.07, "dpitch": 0.01, "dyaw": 2.48, "droll": 0.0}, {"dx": -2.09, "dy": 1.15, "dz": -0.09, "dpitch": 0.03, "dyaw": 3.32, "droll": 0.0}, {"dx": -2.61, "dy": 1.43, "dz": -0.2, "dpitch": 0.17, "dyaw": 4.15, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [106.67, 29.03, 20.42, -44.52, -176.85, 0.0]
  Target bbox: [628.15, 323.97, 652.19, 395.5]

Frame 2:
  Drone pose: [106.15, 29.32, 20.39, -44.48, -176.02, 0.0]
  Target bbox: [628.36, 327.6, 651.88, 391.7]

Frame 3:
  Drone pose: [105.63, 29.61, 20.36, -44.43, -175.18, 0.0]
  Target bbox: [628.16, 328.5, 652.04, 390.71]

Frame 4:
  Drone pose: [105.11, 29.9, 20.33, -44.38, -174.35, 0.0]
  Target bbox: [627.82, 324.65, 652.49, 394.73]

Frame 5 (current):
  Drone pose: [104.59, 30.18, 20.3, -44.33, -173.51, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 627.0, "ymin": 325.03, "xmax": 653.31, "ymax": 394.33}, "waypoint_deltas": [{"dx": -0.53, "dy": 0.29, "dz": -0.03, "dpitch": 0.06, "dyaw": 0.83, "droll": 0.0}, {"dx": -1.05, "dy": 0.58, "dz": -0.06, "dpitch": 0.13, "dyaw": 1.66, "droll": 0.0}, {"dx": -1.57, "dy": 0.87, "dz": -0.08, "dpitch": 0.2, "dyaw": 2.49, "droll": 0.0}, {"dx": -2.09, "dy": 1.15, "dz": -0.11, "dpitch": 0.27, "dyaw": 3.32, "droll": 0.0}, {"dx": -2.61, "dy": 1.44, "dz": -0.13, "dpitch": 0.35, "dyaw": 4.14, "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.98, 31.62, 20.17, -43.98, -169.37, 0.0]
  Target bbox: [626.47, 323.99, 653.85, 395.41]

Frame 2:
  Drone pose: [101.46, 31.91, 20.15, -43.91, -168.55, 0.0]
  Target bbox: [626.36, 324.57, 653.95, 394.83]

Frame 3:
  Drone pose: [100.94, 32.2, 20.13, -43.83, -167.73, 0.0]
  Target bbox: [626.67, 326.39, 653.58, 392.98]

Frame 4:
  Drone pose: [100.44, 32.2, 20.12, -43.8, -167.73, 0.0]
  Target bbox: [624.92, 322.53, 655.48, 397.03]

Frame 5 (current):
  Drone pose: [99.94, 32.2, 20.1, -43.78, -167.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": 624.82, "ymin": 322.39, "xmax": 655.58, "ymax": 397.15}, "waypoint_deltas": [{"dx": -0.5, "dy": 0.0, "dz": -0.01, "dpitch": 0.02, "dyaw": 0.0, "droll": 0.0}, {"dx": -1.0, "dy": 0.0, "dz": -0.02, "dpitch": 0.04, "dyaw": 0.0, "droll": 0.0}, {"dx": -1.5, "dy": 0.0, "dz": -0.03, "dpitch": 0.05, "dyaw": 0.0, "droll": 0.0}, {"dx": -2.0, "dy": 0.0, "dz": -0.04, "dpitch": 0.07, "dyaw": 0.0, "droll": 0.0}, {"dx": -2.5, "dy": 0.0, "dz": -0.05, "dpitch": 0.08, "dyaw": 0.0, "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.44, 32.2, 20.05, -43.7, -167.73, 0.0]
  Target bbox: [624.83, 322.38, 655.56, 397.14]

Frame 2:
  Drone pose: [96.94, 32.2, 20.04, -43.69, -167.73, 0.0]
  Target bbox: [626.79, 328.63, 653.38, 390.6]

Frame 3:
  Drone pose: [96.44, 32.2, 20.04, -43.68, -167.73, 0.0]
  Target bbox: [625.65, 325.41, 654.63, 393.98]

Frame 4:
  Drone pose: [95.94, 32.2, 20.03, -43.67, -167.73, 0.0]
  Target bbox: [626.31, 325.19, 653.98, 394.21]

Frame 5 (current):
  Drone pose: [95.44, 32.2, 20.03, -43.66, -167.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": 625.5, "ymin": 323.51, "xmax": 654.85, "ymax": 396.0}, "waypoint_deltas": [{"dx": -0.5, "dy": 0.0, "dz": -0.01, "dpitch": 0.0, "dyaw": 0.0, "droll": 0.0}, {"dx": -1.0, "dy": 0.5, "dz": -0.01, "dpitch": 0.01, "dyaw": 0.0, "droll": 0.0}, {"dx": -1.5, "dy": 1.0, "dz": -0.01, "dpitch": 0.01, "dyaw": 0.0, "droll": 0.0}, {"dx": -2.0, "dy": 1.5, "dz": -0.02, "dpitch": 0.02, "dyaw": 0.0, "droll": 0.0}, {"dx": -2.7, "dy": 1.57, "dz": -0.02, "dpitch": -0.37, "dyaw": -1.07, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [92.04, 33.81, 20.01, -44.45, -170.02, 0.0]
  Target bbox: [622.46, 326.46, 657.54, 392.85]

Frame 2:
  Drone pose: [91.29, 33.74, 20.01, -44.95, -171.58, 0.0]
  Target bbox: [618.16, 322.81, 661.79, 396.62]

Frame 3:
  Drone pose: [90.52, 33.65, 20.01, -45.46, -173.25, 0.0]
  Target bbox: [620.57, 324.15, 659.41, 395.14]

Frame 4:
  Drone pose: [89.72, 33.35, 20.0, -46.05, -175.6, 0.0]
  Target bbox: [617.66, 321.99, 662.34, 397.38]

Frame 5 (current):
  Drone pose: [88.93, 32.96, 20.0, -46.58, -178.35, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 628.19, "ymin": 327.26, "xmax": 652.04, "ymax": 391.78}, "waypoint_deltas": [{"dx": -0.78, "dy": -0.62, "dz": 0.0, "dpitch": -0.45, "dyaw": -2.0, "droll": 0.0}, {"dx": -1.53, "dy": -1.19, "dz": 0.0, "dpitch": -0.79, "dyaw": -5.47, "droll": 0.0}, {"dx": -2.09, "dy": -1.56, "dz": 0.0, "dpitch": -0.53, "dyaw": -8.34, "droll": 0.0}, {"dx": -2.56, "dy": -1.68, "dz": 0.0, "dpitch": -0.34, "dyaw": -10.33, "droll": 0.0}, {"dx": -3.01, "dy": -1.79, "dz": 0.0, "dpitch": -0.1, "dyaw": -12.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: [85.92, 31.17, 20.0, -46.68, 169.41, 0.0]
  Target bbox: [621.19, 323.33, 658.96, 395.88]

Frame 2:
  Drone pose: [85.51, 31.16, 20.0, -46.37, 167.87, 0.0]
  Target bbox: [622.22, 323.94, 657.96, 395.28]

Frame 3:
  Drone pose: [85.03, 31.09, 20.0, -46.14, 166.12, 0.0]
  Target bbox: [620.34, 322.72, 659.81, 396.48]

Frame 4:
  Drone pose: [84.43, 30.97, 20.0, -46.04, 164.15, 0.0]
  Target bbox: [622.58, 324.03, 657.62, 395.2]

Frame 5 (current):
  Drone pose: [83.72, 30.81, 20.0, -46.06, 161.98, 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.32, "ymin": 323.29, "xmax": 659.84, "ymax": 395.91}, "waypoint_deltas": [{"dx": -0.76, "dy": -0.19, "dz": 0.0, "dpitch": -0.03, "dyaw": -2.29, "droll": 0.0}, {"dx": -1.48, "dy": -0.34, "dz": 0.0, "dpitch": 0.01, "dyaw": -4.46, "droll": 0.0}, {"dx": -2.12, "dy": -0.44, "dz": 0.0, "dpitch": 0.19, "dyaw": -6.37, "droll": 0.0}, {"dx": -2.67, "dy": -0.5, "dz": 0.0, "dpitch": 0.49, "dyaw": -8.0, "droll": 0.0}, {"dx": -3.17, "dy": -0.52, "dz": 0.0, "dpitch": 0.5, "dyaw": -8.05, "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: [80.55, 30.29, 20.0, -45.56, 153.93, 0.0]
  Target bbox: [620.61, 320.95, 659.04, 398.41]

Frame 2:
  Drone pose: [80.0, 30.32, 20.0, -45.65, 153.92, 0.0]
  Target bbox: [621.8, 323.0, 657.94, 396.3]

Frame 3:
  Drone pose: [79.33, 30.39, 20.0, -45.93, 153.88, 0.0]
  Target bbox: [624.3, 326.23, 655.58, 392.89]

Frame 4:
  Drone pose: [78.52, 30.53, 20.0, -46.46, 153.85, 0.0]
  Target bbox: [623.11, 324.03, 656.69, 395.12]

Frame 5 (current):
  Drone pose: [77.66, 30.76, 20.0, -47.16, 154.01, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 620.67, "ymin": 320.99, "xmax": 659.01, "ymax": 398.23}, "waypoint_deltas": [{"dx": -0.83, "dy": 0.33, "dz": 0.0, "dpitch": -0.71, "dyaw": 0.53, "droll": 0.0}, {"dx": -1.52, "dy": 0.73, "dz": 0.0, "dpitch": -1.3, "dyaw": 1.47, "droll": 0.0}, {"dx": -2.07, "dy": 1.15, "dz": 0.0, "dpitch": -1.65, "dyaw": 2.73, "droll": 0.0}, {"dx": -2.47, "dy": 1.52, "dz": 0.0, "dpitch": -1.74, "dyaw": 4.06, "droll": 0.0}, {"dx": -2.77, "dy": 1.78, "dz": 0.0, "dpitch": -1.6, "dyaw": 5.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: [74.61, 32.56, 20.0, -48.41, 159.46, 0.0]
  Target bbox: [623.38, 323.4, 656.37, 395.66]

Frame 2:
  Drone pose: [74.3, 32.53, 20.0, -48.08, 159.61, 0.0]
  Target bbox: [623.24, 323.58, 656.5, 395.52]

Frame 3:
  Drone pose: [74.01, 32.48, 20.0, -47.74, 159.7, 0.0]
  Target bbox: [622.95, 322.55, 656.75, 396.59]

Frame 4:
  Drone pose: [73.62, 32.32, 20.0, -47.48, 159.3, 0.0]
  Target bbox: [622.22, 321.43, 657.43, 397.79]

Frame 5 (current):
  Drone pose: [73.17, 32.13, 20.0, -47.29, 158.8, 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.55, "ymin": 319.45, "xmax": 659.01, "ymax": 399.89}, "waypoint_deltas": [{"dx": -0.5, "dy": -0.18, "dz": 0.0, "dpitch": 0.12, "dyaw": -0.55, "droll": 0.0}, {"dx": -1.23, "dy": -0.22, "dz": 0.0, "dpitch": -0.21, "dyaw": -0.94, "droll": 0.0}, {"dx": -1.95, "dy": -0.25, "dz": 0.0, "dpitch": -0.53, "dyaw": -1.34, "droll": 0.0}, {"dx": -2.68, "dy": -0.29, "dz": 0.0, "dpitch": -0.86, "dyaw": -1.75, "droll": 0.0}, {"dx": -3.41, "dy": -0.33, "dz": 0.0, "dpitch": -1.19, "dyaw": -2.17, "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: [69.76, 31.8, 20.0, -48.48, 156.63, 0.0]
  Target bbox: [621.39, 322.77, 658.84, 396.23]

Frame 2:
  Drone pose: [69.03, 31.77, 20.0, -48.46, 154.64, 0.0]
  Target bbox: [622.66, 324.38, 657.53, 394.57]

Frame 3:
  Drone pose: [68.3, 31.73, 20.0, -48.4, 152.65, 0.0]
  Target bbox: [624.1, 324.72, 656.13, 394.31]

Frame 4:
  Drone pose: [67.57, 31.7, 20.0, -48.31, 150.67, 0.0]
  Target bbox: [624.01, 326.26, 656.16, 392.67]

Frame 5 (current):
  Drone pose: [66.85, 31.66, 20.0, -48.19, 148.71, 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.13, "ymin": 323.64, "xmax": 657.16, "ymax": 395.4}, "waypoint_deltas": [{"dx": -0.73, "dy": -0.04, "dz": 0.0, "dpitch": 0.16, "dyaw": -1.95, "droll": 0.0}, {"dx": -1.46, "dy": -0.07, "dz": 0.0, "dpitch": 0.35, "dyaw": -3.87, "droll": 0.0}, {"dx": -2.12, "dy": -0.05, "dz": 0.0, "dpitch": 0.11, "dyaw": -4.09, "droll": 0.0}, {"dx": -2.75, "dy": -0.01, "dz": 0.0, "dpitch": 0.38, "dyaw": -5.61, "droll": 0.0}, {"dx": -3.31, "dy": 0.1, "dz": 0.0, "dpitch": 0.69, "dyaw": -6.78, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [63.54, 31.76, 20.0, -47.5, 141.93, 0.0]
  Target bbox: [622.89, 323.42, 657.48, 395.66]

Frame 2:
  Drone pose: [62.97, 31.86, 20.0, -47.17, 140.79, 0.0]
  Target bbox: [623.41, 323.91, 656.97, 395.23]

Frame 3:
  Drone pose: [62.41, 31.97, 20.0, -46.84, 139.67, 0.0]
  Target bbox: [625.86, 326.87, 654.38, 392.12]

Frame 4:
  Drone pose: [61.85, 32.07, 20.0, -46.73, 138.58, 0.0]
  Target bbox: [629.12, 326.94, 651.1, 392.18]

Frame 5 (current):
  Drone pose: [61.29, 32.18, 20.0, -46.39, 137.52, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 622.8, "ymin": 325.47, "xmax": 657.15, "ymax": 393.72}, "waypoint_deltas": [{"dx": -0.57, "dy": 0.1, "dz": 0.0, "dpitch": -0.18, "dyaw": 0.11, "droll": 0.0}, {"dx": -1.13, "dy": 0.21, "dz": 0.0, "dpitch": 0.17, "dyaw": -0.94, "droll": 0.0}, {"dx": -1.69, "dy": 0.31, "dz": 0.0, "dpitch": 0.53, "dyaw": -1.96, "droll": 0.0}, {"dx": -2.26, "dy": 0.42, "dz": 0.0, "dpitch": 0.35, "dyaw": -4.07, "droll": 0.0}, {"dx": -2.82, "dy": 0.52, "dz": 0.0, "dpitch": 0.73, "dyaw": -5.05, "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: [111.37, 26.45, 22.0, -42.7, 182.14, 0.0]
  Target bbox: [562.13, 391.52, 601.38, 458.71]

Frame 2:
  Drone pose: [110.85, 26.73, 21.2, -46.09, 176.57, 0.0]
  Target bbox: [625.38, 312.07, 653.24, 383.62]

Frame 3:
  Drone pose: [110.48, 27.07, 20.71, -47.52, 176.54, 0.0]
  Target bbox: [622.39, 322.8, 657.94, 396.43]

Frame 4:
  Drone pose: [109.82, 27.29, 20.74, -43.03, 168.41, 0.0]
  Target bbox: [683.24, 308.68, 722.2, 376.29]

Frame 5 (current):
  Drone pose: [109.28, 27.6, 20.62, -49.45, 181.57, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 597.17, "ymin": 245.88, "xmax": 620.87, "ymax": 314.27}, "waypoint_deltas": [{"dx": -0.52, "dy": 0.28, "dz": -0.03, "dpitch": 4.76, "dyaw": -1.75, "droll": 0.0}, {"dx": -1.04, "dy": 0.57, "dz": -0.05, "dpitch": 4.76, "dyaw": -0.92, "droll": 0.0}, {"dx": -1.56, "dy": 0.86, "dz": -0.07, "dpitch": 4.77, "dyaw": -0.09, "droll": 0.0}, {"dx": -2.09, "dy": 1.15, "dz": -0.09, "dpitch": 4.79, "dyaw": 0.75, "droll": 0.0}, {"dx": -2.61, "dy": 1.43, "dz": -0.2, "dpitch": 4.93, "dyaw": 1.58, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [106.67, 29.03, 20.42, -46.67, -171.85, 0.0]
  Target bbox: [565.98, 289.02, 594.1, 362.04]

Frame 2:
  Drone pose: [106.15, 29.32, 20.39, -43.55, -180.04, 0.0]
  Target bbox: [676.47, 341.66, 700.62, 411.3]

Frame 3:
  Drone pose: [105.63, 29.61, 20.36, -40.39, -180.18, 0.0]
  Target bbox: [687.95, 395.0, 712.96, 464.0]

Frame 4:
  Drone pose: [105.11, 29.9, 20.33, -39.88, -169.35, 0.0]
  Target bbox: [566.35, 404.53, 593.14, 469.91]

Frame 5 (current):
  Drone pose: [104.59, 30.18, 20.3, -44.33, -173.51, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 627.9, "ymin": 326.62, "xmax": 652.35, "ymax": 392.65}, "waypoint_deltas": [{"dx": -0.53, "dy": 0.29, "dz": -0.03, "dpitch": 0.06, "dyaw": 0.83, "droll": 0.0}, {"dx": -1.05, "dy": 0.58, "dz": -0.06, "dpitch": 0.13, "dyaw": 1.66, "droll": 0.0}, {"dx": -1.57, "dy": 0.87, "dz": -0.08, "dpitch": 0.2, "dyaw": 2.49, "droll": 0.0}, {"dx": -2.09, "dy": 1.15, "dz": -0.11, "dpitch": 0.27, "dyaw": 3.32, "droll": 0.0}, {"dx": -2.61, "dy": 1.44, "dz": -0.13, "dpitch": 0.35, "dyaw": 4.14, "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.92, 31.74, 20.13, -46.03, -171.25, 0.0]
  Target bbox: [623.5, 324.35, 656.27, 394.86]

Frame 2:
  Drone pose: [101.46, 31.91, 20.15, -48.91, -169.48, 0.0]
  Target bbox: [637.64, 239.92, 665.87, 311.45]

Frame 3:
  Drone pose: [100.94, 32.2, 20.13, -42.46, -164.44, 0.0]
  Target bbox: [584.92, 347.06, 615.36, 419.92]

Frame 4:
  Drone pose: [100.44, 32.2, 20.12, -43.8, -167.73, 0.0]
  Target bbox: [629.21, 327.37, 650.55, 391.93]

Frame 5 (current):
  Drone pose: [100.01, 32.04, 20.18, -40.44, -162.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": 563.97, "ymin": 315.06, "xmax": 586.13, "ymax": 372.53}, "waypoint_deltas": [{"dx": -0.57, "dy": 0.16, "dz": -0.09, "dpitch": -3.32, "dyaw": -4.94, "droll": 0.0}, {"dx": -1.07, "dy": 0.16, "dz": -0.1, "dpitch": -3.3, "dyaw": -4.94, "droll": 0.0}, {"dx": -1.57, "dy": 0.16, "dz": -0.11, "dpitch": -3.29, "dyaw": -4.94, "droll": 0.0}, {"dx": -2.07, "dy": 0.16, "dz": -0.12, "dpitch": -3.27, "dyaw": -4.94, "droll": 0.0}, {"dx": -2.57, "dy": 0.16, "dz": -0.13, "dpitch": -3.26, "dyaw": -4.94, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [97.44, 32.2, 20.05, -43.7, -167.73, 0.0]
  Target bbox: [625.84, 323.64, 654.49, 395.8]

Frame 2:
  Drone pose: [96.94, 32.2, 20.04, -43.69, -167.73, 0.0]
  Target bbox: [626.55, 327.03, 653.68, 392.32]

Frame 3:
  Drone pose: [96.44, 32.2, 20.04, -43.68, -167.73, 0.0]
  Target bbox: [627.44, 326.67, 652.82, 392.66]

Frame 4:
  Drone pose: [96.01, 32.29, 20.08, -47.25, -161.18, 0.0]
  Target bbox: [566.76, 333.67, 600.27, 409.77]

Frame 5 (current):
  Drone pose: [95.44, 32.2, 20.03, -43.66, -167.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": 625.81, "ymin": 324.13, "xmax": 654.52, "ymax": 395.33}, "waypoint_deltas": [{"dx": -0.5, "dy": 0.0, "dz": -0.01, "dpitch": 0.0, "dyaw": 0.0, "droll": 0.0}, {"dx": -1.0, "dy": 0.5, "dz": -0.01, "dpitch": 0.01, "dyaw": 0.0, "droll": 0.0}, {"dx": -1.5, "dy": 1.0, "dz": -0.01, "dpitch": 0.01, "dyaw": 0.0, "droll": 0.0}, {"dx": -2.0, "dy": 1.5, "dz": -0.02, "dpitch": 0.02, "dyaw": 0.0, "droll": 0.0}, {"dx": -2.7, "dy": 1.57, "dz": -0.02, "dpitch": -0.37, "dyaw": -1.07, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [92.04, 33.81, 20.01, -46.31, -171.73, 0.0]
  Target bbox: [644.75, 295.23, 676.99, 362.33]

Frame 2:
  Drone pose: [91.29, 33.74, 20.01, -44.57, -176.58, 0.0]
  Target bbox: [679.3, 331.66, 720.28, 404.22]

Frame 3:
  Drone pose: [90.52, 33.65, 20.01, -45.46, -173.25, 0.0]
  Target bbox: [628.08, 323.21, 652.25, 396.05]

Frame 4:
  Drone pose: [89.76, 33.2, 19.96, -40.74, -169.9, 0.0]
  Target bbox: [561.75, 365.24, 604.81, 437.34]

Frame 5 (current):
  Drone pose: [88.93, 32.96, 20.0, -45.58, -174.69, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 584.7, "ymin": 341.57, "xmax": 610.68, "ymax": 412.94}, "waypoint_deltas": [{"dx": -0.78, "dy": -0.62, "dz": 0.0, "dpitch": -1.45, "dyaw": -5.66, "droll": 0.0}, {"dx": -1.53, "dy": -1.19, "dz": 0.0, "dpitch": -1.79, "dyaw": -9.13, "droll": 0.0}, {"dx": -2.09, "dy": -1.56, "dz": 0.0, "dpitch": -1.53, "dyaw": -12.0, "droll": 0.0}, {"dx": -2.56, "dy": -1.68, "dz": 0.0, "dpitch": -1.34, "dyaw": -13.99, "droll": 0.0}, {"dx": -3.01, "dy": -1.79, "dz": 0.0, "dpitch": -1.1, "dyaw": -15.9, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [85.92, 31.17, 20.0, -43.72, 164.5, 0.0]
  Target bbox: [677.73, 374.83, 716.46, 447.16]

Frame 2:
  Drone pose: [85.51, 31.16, 20.0, -48.68, 172.87, 0.0]
  Target bbox: [566.04, 290.29, 597.25, 355.21]

Frame 3:
  Drone pose: [84.98, 31.05, 19.91, -49.96, 164.66, 0.0]
  Target bbox: [625.39, 320.18, 654.19, 398.75]

Frame 4:
  Drone pose: [84.43, 30.97, 20.0, -47.84, 163.64, 0.0]
  Target bbox: [630.11, 294.82, 662.42, 364.08]

Frame 5 (current):
  Drone pose: [83.72, 30.81, 20.0, -43.95, 158.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": 662.98, "ymin": 360.82, "xmax": 696.85, "ymax": 430.94}, "waypoint_deltas": [{"dx": -0.76, "dy": -0.19, "dz": 0.0, "dpitch": -2.14, "dyaw": 1.1, "droll": 0.0}, {"dx": -1.48, "dy": -0.34, "dz": 0.0, "dpitch": -2.1, "dyaw": -1.07, "droll": 0.0}, {"dx": -2.12, "dy": -0.44, "dz": 0.0, "dpitch": -1.92, "dyaw": -2.98, "droll": 0.0}, {"dx": -2.67, "dy": -0.5, "dz": 0.0, "dpitch": -1.62, "dyaw": -4.61, "droll": 0.0}, {"dx": -3.17, "dy": -0.52, "dz": 0.0, "dpitch": -1.61, "dyaw": -4.66, "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: [80.55, 30.29, 20.0, -44.62, 158.93, 0.0]
  Target bbox: [563.99, 343.18, 597.61, 411.21]

Frame 2:
  Drone pose: [80.0, 30.32, 20.0, -45.67, 155.64, 0.0]
  Target bbox: [603.44, 325.66, 635.52, 393.01]

Frame 3:
  Drone pose: [79.33, 30.39, 20.0, -45.93, 153.88, 0.0]
  Target bbox: [624.0, 325.79, 655.84, 393.41]

Frame 4:
  Drone pose: [78.52, 30.53, 20.0, -46.46, 153.85, 0.0]
  Target bbox: [621.9, 322.08, 657.81, 397.16]

Frame 5 (current):
  Drone pose: [77.66, 30.76, 20.0, -42.16, 153.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": 627.67, "ymin": 404.77, "xmax": 665.11, "ymax": 482.73}, "waypoint_deltas": [{"dx": -0.83, "dy": 0.33, "dz": 0.0, "dpitch": -5.71, "dyaw": 1.09, "droll": 0.0}, {"dx": -1.52, "dy": 0.73, "dz": 0.0, "dpitch": -6.3, "dyaw": 2.03, "droll": 0.0}, {"dx": -2.07, "dy": 1.15, "dz": 0.0, "dpitch": -6.65, "dyaw": 3.29, "droll": 0.0}, {"dx": -2.47, "dy": 1.52, "dz": 0.0, "dpitch": -6.74, "dyaw": 4.62, "droll": 0.0}, {"dx": -2.77, "dy": 1.78, "dz": 0.0, "dpitch": -6.6, "dyaw": 5.69, "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: [74.61, 32.56, 20.0, -45.9, 159.21, 0.0]
  Target bbox: [623.64, 361.44, 661.71, 442.07]

Frame 2:
  Drone pose: [74.3, 32.53, 20.0, -49.08, 154.61, 0.0]
  Target bbox: [679.09, 310.01, 713.68, 379.29]

Frame 3:
  Drone pose: [74.01, 32.48, 20.0, -47.74, 159.7, 0.0]
  Target bbox: [624.24, 326.06, 655.61, 392.94]

Frame 4:
  Drone pose: [73.62, 32.32, 20.0, -47.48, 159.3, 0.0]
  Target bbox: [622.11, 320.53, 657.53, 398.64]

Frame 5 (current):
  Drone pose: [73.17, 32.13, 20.0, -51.4, 161.66, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 587.64, "ymin": 251.1, "xmax": 625.86, "ymax": 331.18}, "waypoint_deltas": [{"dx": -0.5, "dy": -0.18, "dz": 0.0, "dpitch": 4.23, "dyaw": -3.41, "droll": 0.0}, {"dx": -1.23, "dy": -0.22, "dz": 0.0, "dpitch": 3.9, "dyaw": -3.8, "droll": 0.0}, {"dx": -1.95, "dy": -0.25, "dz": 0.0, "dpitch": 3.58, "dyaw": -4.2, "droll": 0.0}, {"dx": -2.68, "dy": -0.29, "dz": 0.0, "dpitch": 3.25, "dyaw": -4.61, "droll": 0.0}, {"dx": -3.41, "dy": -0.33, "dz": 0.0, "dpitch": 2.92, "dyaw": -5.03, "droll": 0.0}]}


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

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

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

Respond ONLY with a JSON object.

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

Frame 1:
  Drone pose: [69.76, 31.8, 20.0, -48.48, 156.63, 0.0]
  Target bbox: [620.01, 321.64, 660.28, 397.46]

Frame 2:
  Drone pose: [69.03, 31.77, 20.0, -49.19, 149.64, 0.0]
  Target bbox: [676.29, 312.74, 716.24, 385.35]

Frame 3:
  Drone pose: [68.3, 31.73, 20.0, -48.33, 150.06, 0.0]
  Target bbox: [650.5, 325.22, 688.36, 397.05]

Frame 4:
  Drone pose: [67.57, 31.7, 20.0, -53.31, 147.66, 0.0]
  Target bbox: [656.86, 242.7, 691.79, 309.38]

Frame 5 (current):
  Drone pose: [66.92, 31.75, 20.04, -45.81, 147.98, 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.98, "ymin": 325.48, "xmax": 655.27, "ymax": 393.69}, "waypoint_deltas": [{"dx": -0.8, "dy": -0.13, "dz": -0.04, "dpitch": -2.22, "dyaw": -1.22, "droll": 0.0}, {"dx": -1.53, "dy": -0.16, "dz": -0.04, "dpitch": -2.03, "dyaw": -3.14, "droll": 0.0}, {"dx": -2.19, "dy": -0.14, "dz": -0.04, "dpitch": -2.27, "dyaw": -3.36, "droll": 0.0}, {"dx": -2.82, "dy": -0.1, "dz": -0.04, "dpitch": -2.0, "dyaw": -4.88, "droll": 0.0}, {"dx": -3.38, "dy": 0.01, "dz": -0.04, "dpitch": -1.69, "dyaw": -6.05, "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: [63.54, 31.76, 20.0, -47.5, 141.93, 0.0]
  Target bbox: [623.29, 324.06, 657.03, 394.95]

Frame 2:
  Drone pose: [62.97, 31.86, 20.0, -47.17, 140.79, 0.0]
  Target bbox: [621.01, 323.23, 658.83, 395.93]

Frame 3:
  Drone pose: [62.25, 32.06, 19.98, -41.41, 131.37, 0.0]
  Target bbox: [663.52, 408.0, 696.18, 481.14]

Frame 4:
  Drone pose: [61.82, 32.1, 19.98, -42.67, 132.05, 0.0]
  Target bbox: [675.81, 303.17, 712.99, 367.25]

Frame 5 (current):
  Drone pose: [61.29, 32.18, 20.0, -44.52, 141.03, 0.0]

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

[Assistant] {"current_bbox": {"xmin": 577.13, "ymin": 353.64, "xmax": 620.22, "ymax": 430.22}, "waypoint_deltas": [{"dx": -0.57, "dy": 0.1, "dz": 0.0, "dpitch": -2.05, "dyaw": -3.4, "droll": 0.0}, {"dx": -1.13, "dy": 0.21, "dz": 0.0, "dpitch": -1.7, "dyaw": -4.45, "droll": 0.0}, {"dx": -1.69, "dy": 0.31, "dz": 0.0, "dpitch": -1.34, "dyaw": -5.47, "droll": 0.0}, {"dx": -2.26, "dy": 0.42, "dz": 0.0, "dpitch": -1.52, "dyaw": -7.58, "droll": 0.0}, {"dx": -2.82, "dy": 0.52, "dz": 0.0, "dpitch": -1.14, "dyaw": -8.56, "droll": 0.0}]}