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.

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

VFH Decision Module #54

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

VFH Decision Module #54

wants to merge 4 commits into from

Conversation

Mmoyv27
Copy link
Contributor

@Mmoyv27 Mmoyv27 commented Nov 19, 2024

Initial commit for vfh_decision.

followed shortly by integration tests

@Mmoyv27 Mmoyv27 changed the title Initial commit for decision module without tests VFH Decision Module Nov 19, 2024
Copy link
Contributor

@ashum68 ashum68 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reviewed

:param wide_valley_threshold: Number of sectors distinguishing wide valleys from narrow ones.
"""
self.density_threshold = density_threshold
self.min_consec_sectors = min_consec_sectors
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

following WARG style guide, this variable name should not be short-form. it can be renamed to min_consecutive_sectors. (https://uwarg-docs.atlassian.net/wiki/spaces/CV/pages/2253226033/Python+Style+Convention#Naming)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

got it, will just do


:param density_threshold: The threshold for identifying candidate valleys.
:param min_consec_sectors: Minimum number of consecutive sectors for a valid valley.
:param wide_valley_threshold: Number of sectors distinguishing wide valleys from narrow ones.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we define a wide valley threshold? is a narrow valley not wide enough? is this the minimum narrow valleys required for the drone to fly down the valley? if so, can the description make this more clear?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's for a refinement outlined in the research paper. Technically we can go lower than the wide_threshold, but that would require us to slow down our flight_speed (formula given in paper, relates to maximal steering speed) so could implement that in the future.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(also its just a bit safer, until we concretely decide on a safe threshold based on tests)

far_angle = valley[-1].angle_end

# Ensure the valley contains 0° and has enough space on both sides
if (
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why does our valley at 0 degrees have to be a wide valley?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i made an oversight. our candidate valley search should also rely on wide-valley threshold. so candidate valleys in the pre-check and in the general search should be > wide_valley threshold, not min_consec_sectors

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants