Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

0 altitude in coverage path planning #185

Closed
AskewParity opened this issue May 8, 2024 · 0 comments · Fixed by #186
Closed

0 altitude in coverage path planning #185

AskewParity opened this issue May 8, 2024 · 0 comments · Fixed by #186
Assignees
@AskewParity
Labels
bug Something isn't working CRASH-RISK THIS WILL CAUSE A CRASH mission-critical MUST HAVE BEFORE COMPETITION

Comments

@AskewParity
Copy link
Contributor

🐛 Bug

Similar to all the other pathing options, coverage path planning is altitude agnostic, and by default zeroes out all the attitudes for the vectors generated.

Expected behavior

Altitude should be fixed to 100 ft (30.48 m) when in

Possible Complications

Rate of descent may be too steep if we force the plane to fly to 100ft alt fro its start - provided the plane starts close to the airdrop search zone.
@AskewParity AskewParity added bug Something isn't working mission-critical MUST HAVE BEFORE COMPETITION CRASH-RISK THIS WILL CAUSE A CRASH labels May 8, 2024
@AskewParity AskewParity self-assigned this May 8, 2024
@AskewParity AskewParity mentioned this issue May 10, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AskewParity AskewParity

Labels
bug Something isn't working CRASH-RISK THIS WILL CAUSE A CRASH mission-critical MUST HAVE BEFORE COMPETITION
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Chore/coverage altitude tritonuas/obcpp
1 participant
@AskewParity