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

--[TEMP DO NOT MERGE] Hssd ao utilities jt #2379

Draft
wants to merge 225 commits into
base: main
Choose a base branch
from
Draft

Conversation

jturner65
Copy link
Contributor

Motivation and Context

This is a version of the HSSD ao utilities that has been rebased onto the markerset PR here and has had the work from @aclegg3 's alex-04_22-marker_set_util branch for handling marker placement merged into examples/viewer.py

How Has This Been Tested

Types of changes

  • Docs change / refactoring / dependency upgrade
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

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.

…d output directory. Import Habitat-lab features.
… Validate proxy bounding box is similar to ground truth. Prepare for Recetpacle sampling TODO.
… found in a single scene. Re-organize receptacle metrics caching.
…ation feature (note: does not correctly re-orient receptacles yet)
…te_collision_shape func. output_dir is now optional
@jturner65 jturner65 force-pushed the hssd_ao_utilities_JT branch 2 times, most recently from 75ff464 to d23fe7d Compare May 3, 2024 16:11
Enable eventually being able to move the functions to a utility
jturner65 and others added 11 commits May 6, 2024 10:05
… to inappropriate COM correction.

Due to a quirk with how object attributes are read and saved, and how a specified COM vector vs an unspecified COM vector in the configuration json is treated by the engine when determining the object origin location, points that were saved with the original configs (which had no COM specified and so therefore relied on rigid object COMs being determined based on bbox center) would be saved in configs that would get a 0,0,0 COM saved as well, inappropriately. Upon subsequent load, this 0,0,0 would be used to determine the object's origin, instead of the bbox COM that was used initially, and the marker points would be displaced from where they belonged. This PR enables the reversal of this displacement.

PR#2382 will correct the inappropriate save of COM location, and a subsequent PR will include the internal bindings to the uncorrected COM location that are added to this commit as well.
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants