also looking at this
feat: add explicit VTOL crosswind heading plans
#90
21 files
+815
-36
| @@ -84,8 +84,13 @@ mode observations. Named scenarios expose phase-bound sensor/manual/host loss, c | ||
| 84 | 84 | declared front/back abort and recovery, pusher open-circuit timeout and global endurance expiry. |
| 85 | 85 | Add `--electrical` to either command for fictional propulsion/battery load and delayed energy measurements. |
| 86 | 86 | Plans can explicitly declare bounded hover-and-land transition recovery. Complete recovery/abort envelopes |
| 87 | and measured hybrid energy qualification remain open. The VTOL workspace selects the same 14 named | |
| 87 | and measured hybrid energy qualification remain open. The VTOL workspace selects the same 20 named | |
| 88 | 88 | cases, fault phases and optional electrical model, with captured mode and battery playback. |
| 89 | The 2 m/s headwind and tailwind cases complete their routes. Separate east/west crosswind plans | |
| 90 | complete with explicitly wind-facing back-hover headings. Their original fixed north-facing limit | |
| 91 | cases retain blocked envelope outcomes, without confirmed hover or landing. Reports and playback | |
| 92 | show the requested heading and distinguish declared world wind from observed exposure checks; | |
| 93 | controller inputs contain no wind oracle. These are bounded fictional plans, not arbitrary-wind support. | |
| 89 | 94 | |
| 90 | 95 | ## Simulated carried load |
| 91 | 96 | |