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

Restrict navigation to a single floor for 2023 challenge [DO NOT MERGE] #2033

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

srama2512
Copy link
Contributor

Motivation and Context

This change, in conjunction with this commit in habitat-lab, restricts navigation for habitat 2023 challenges to a single floor.

How Has This Been Tested

Tested locally by training ObjectNav agents.

Types of changes

  • New feature (non-breaking change which adds functionality)

Checklist

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have completed my CLA (see CONTRIBUTING)
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@facebook-github-bot facebook-github-bot added the CLA Signed Do not delete this pull request or issue due to inactivity. label Mar 15, 2023
@@ -95,6 +95,8 @@ class AgentState:
class AgentConfiguration:
height: float = 1.5
radius: float = 0.1
cell_height: float = 0.2
Copy link
Contributor

Choose a reason for hiding this comment

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

This has bad code smell. There are a lot of navmesh settings and it would be difficult to keep track of them if we add them all here. Perhaps if we add a dictionary of custom NavMesh settings?

Copy link
Contributor

Choose a reason for hiding this comment

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

Or why don't we just attach a Navmesh settings object here on the extreme case

Copy link
Contributor

Choose a reason for hiding this comment

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

This is fine for a short term thing, but longterm we should consider doing this.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@Skylion007 - refer to conversation here. TL; DR - these changes are only to support the current iteration of the challenge.

@srama2512 srama2512 changed the title Restrict navigation to a single floor for 2023 challenge Restrict navigation to a single floor for 2023 challenge [DO NOT MERGE] Mar 17, 2023
srama2512 added a commit that referenced this pull request Mar 17, 2023
@aclegg3 aclegg3 added the do not merge Not ready to merge. This label should block merging. label Aug 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed Do not delete this pull request or issue due to inactivity. do not merge Not ready to merge. This label should block merging.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants