Skip to content
This repository has been archived by the owner on Apr 24, 2023. It is now read-only.

Traversability Analysis #663

Closed
oswinso opened this issue Feb 23, 2020 · 0 comments
Closed

Traversability Analysis #663

oswinso opened this issue Feb 23, 2020 · 0 comments
Labels
area ➤ computer vision Issues relating to non-NN computer vision area ➤ localization Issues related to localization area ➤ mapping Issues relating to mapping Epic Zenhub Epics level ➤ hard Hard issues type ➤ new feature New features, improvements to existing features. type ➤ refactor Issues related to refactoring code

Comments

@oswinso
Copy link
Contributor

oswinso commented Feb 23, 2020

A big component we're missing currently in our stack is traversability analysis, aka actually handling the ramp properly.

The two main components needed to do this are #629 for the actual analysis of traversability, and #662 for not having fucked up projections while we're on the ramp and don't have z=0 and pitch=0.

AC: Be able to autonomously get past the ramp in simulation (without moving the ramp away)
@oswinso oswinso added type ➤ new feature New features, improvements to existing features. area ➤ computer vision Issues relating to non-NN computer vision area ➤ mapping Issues relating to mapping level ➤ hard Hard issues type ➤ refactor Issues related to refactoring code area ➤ localization Issues related to localization Epic Zenhub Epics labels Feb 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area ➤ computer vision Issues relating to non-NN computer vision area ➤ localization Issues related to localization area ➤ mapping Issues relating to mapping Epic Zenhub Epics level ➤ hard Hard issues type ➤ new feature New features, improvements to existing features. type ➤ refactor Issues related to refactoring code
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@oswinso @matthewhannay567