-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Add RTX Lidar Sensor #1372
base: main
Are you sure you want to change the base?
Add RTX Lidar Sensor #1372
Conversation
# lazy allocation of data dictionary | ||
# since the size of the output data is not known in advance, we leave it as None | ||
# the memory will be allocated when the buffer() function is called for the first time. | ||
self._data.output = TensorDict({}, batch_size=self._view.count, device=self.device) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is TensorDict necessary here? we had a change that went in to remove TensorDict from the tiled camera class because it was causing performance issues
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I bet we can remove it, just following the camera and tiled_camera patterns.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey I just checked both tiled_camera and camera use TensorDict for data.output. Did the change you mentioned go into the Nvidia internal fork?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm I think it was updated in #1348
source/extensions/omni.isaac.lab/omni/isaac/lab/sensors/rtx_lidar/rtx_lidar.py
Outdated
Show resolved
Hide resolved
class OffsetCfg: | ||
"""The offset pose of the sensor's frame from the sensor's parent frame.""" | ||
|
||
pos: tuple[float, float, float] = (0.0, 0.0, 1.0) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why (0, 0, 1) instead of (0, 0, 0)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good catch I was using that during manual testing
source/extensions/omni.isaac.lab/omni/isaac/lab/sensors/rtx_lidar/rtx_lidar_data.py
Outdated
Show resolved
Hide resolved
env_ids = self._ALL_INDICES | ||
# reset the data | ||
# note: this recomputation is useful if one performs events such as randomizations on the camera poses. | ||
# self._update_poses(env_ids) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would it still make sense to do this call?
@jtigue-bdai will you get a chance to look into this one today? I can also try to get this one merged in. |
I don't think I will be able to get to it today. |
…dar/rtx_lidar.py Signed-off-by: Kelly Guo <[email protected]>
…dar/rtx_lidar_data.py Signed-off-by: Kelly Guo <[email protected]>
Description
This PR creates a sensor based on the RTX Lidar:
Fixes #865
Type of change
Screenshots
Please attach before and after screenshots of the change if applicable.
Checklist
pre-commit
checks with./isaaclab.sh --format
config/extension.toml
fileCONTRIBUTORS.md
or my name already exists there