Skip to content

Conversation

@xyao-nv
Copy link
Collaborator

@xyao-nv xyao-nv commented Feb 9, 2026

Summary

Allow object scale to be set when instantiating library objects so users can override default scales without changing asset code. Only add it to Rigid Objs.

Detailed description

  • Users may need configure different scales than what's provided asset library (need it when building a droid multi-objs PnP example).
  • Add optional scale: tuple[float, float, float] | None = None to LibraryObject.__init__. If provided, it overrides the class default; otherwise the class scale is used.
  • Add and forward the scale parameter in all subclasses that define __init__

@xyao-nv xyao-nv marked this pull request as ready for review February 9, 2026 08:18
@xyao-nv xyao-nv changed the title allow user to modfy scale when loading rigid obj asset allow user to modify scale when loading rigid obj asset Feb 9, 2026
@xyao-nv xyao-nv changed the title allow user to modify scale when loading rigid obj asset Add configurable object scale for library objects (Rigid Objs) Feb 9, 2026
Copy link
Collaborator

@alexmillane alexmillane left a comment

Choose a reason for hiding this comment

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

LGTM

Comment on lines 91 to 101
parser.add_argument(
"--object_scale",
nargs=3,
type=float,
default=None,
metavar=("X", "Y", "Z"),
help=(
"Scale (x, y, z) for the pick-up object(s). Example: --object_scale 1.0 1.0 1.0. If not set, uses the"
" object's default scale."
),
)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Do we need this as an argument? Seems like something users wont generally use? Do you forsee this being used?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yeah I was a bit debating when adding it. I agree the chance of using it thru cli args is low. removed.

@xyao-nv xyao-nv force-pushed the xyao/add_obj_scale branch from cbc5eb6 to 587e16e Compare February 9, 2026 18:24
@xyao-nv xyao-nv merged commit 8f442ec into main Feb 9, 2026
5 checks passed
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