-
Notifications
You must be signed in to change notification settings - Fork 921
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
[Bug Report] Camera output resolution stays the same across camera instances #165
Closed
2 tasks done
Labels
bug
Something isn't working
Comments
chaofiber
pushed a commit
to chaofiber/Orbit
that referenced
this issue
Dec 14, 2023
# Description Adds `from __future__ import annotations`, cleans up old annotations (`List` -> `list`, `Tuple` -> `tuple`, etc) to conform with formatter, and removes duplicated type hints in docstrings. Fixes isaac-sim#140 ## Type of change - Bug fix (non-breaking change which fixes an issue) ## Checklist - [x] I have run the [`pre-commit` checks](https://pre-commit.com/) with `./orbit.sh --format` - [x] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] I have updated the changelog and the corresponding version in the extension's `config/extension.toml` file --------- Co-authored-by: Mayank Mittal <mittalma@leggedrobotics.com>
Mayankm96
added a commit
that referenced
this issue
Dec 22, 2023
# Description Adds `from __future__ import annotations`, cleans up old annotations (`List` -> `list`, `Tuple` -> `tuple`, etc) to conform with formatter, and removes duplicated type hints in docstrings. Fixes #140 ## Type of change - Bug fix (non-breaking change which fixes an issue) ## Checklist - [x] I have run the [`pre-commit` checks](https://pre-commit.com/) with `./orbit.sh --format` - [x] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] I have updated the changelog and the corresponding version in the extension's `config/extension.toml` file --------- Co-authored-by: Mayank Mittal <mittalma@leggedrobotics.com>
6 tasks
cannot replicate this issue, added a test that it is checked for automatically |
Mayankm96
pushed a commit
that referenced
this issue
Sep 19, 2024
# Description Adds test to check that different image sizes are respected by the camera implementation. Fixes #165 ## Type of change - New feature (non-breaking change which adds functionality) ## Checklist - [x] I have run the [`pre-commit` checks](https://pre-commit.com/) with `./isaaclab.sh --format` - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [ ] I have updated the changelog and the corresponding version in the extension's `config/extension.toml` file - [x] I have added my name to the `CONTRIBUTORS.md` or my name already exists there
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
My current simulation setup is as follows: I have two cameras of different resolutions, and I want one of them to create a RGB point cloud, and the other one to capture a normal image of a scene. This should happen only once for performance reasons, so I create one camera object, take a picture, then delete it, then create the other camera object, create a point cloud and delete it again.
When I do this, the RGB output of the second camera still has the same resolution (i.e., shape of the underlying torch tensor) as the first camera. The "distance_to_image_plane" output (which the first camera obviously does not have) has the correct resolution though.
If I then want to create a point cloud from the data of the second camera, it obviously fails:
Could it be that some buffers are not properly reset when the camera is deleted? And if so, can I do this manually?
Steps to reproduce
So a (very reduced) minimal working example of what I'm trying to do is as follows:
If I print the
camera.data.output[0]
while running this, i get the following for my rgb camera (the one that's supposed to be generating an image:And the following for the depth camera (the one that's supposed to be creating a point cloud):
System Info
Checklist
The text was updated successfully, but these errors were encountered: