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

'CUSTOM' parameter is not clear #956

Open
2 tasks done
anakita opened this issue Sep 25, 2024 · 0 comments
Open
2 tasks done

'CUSTOM' parameter is not clear #956

anakita opened this issue Sep 25, 2024 · 0 comments

Comments

@anakita
Copy link

anakita commented Sep 25, 2024

Preliminary Checks

  • This issue is not a duplicate. Before opening a new issue, please search existing issues.
  • This issue is not a question, bug report, or anything other than a feature request directly related to this project.

Proposal

I have recorded a svo file using the zed ros wrapper. The resolution in the zed2i file is set to HD720 but in the common.yaml, the pub_resolution: 'CUSTOM' and pub_downscale_factor: 2.0, so the images are published at 640x360. But in this case what exactly happens to the depth data, as it has been captured at HD720 right?
But in case of the custom parameter being set, just like the image is downscaled, can I use the downscaled depth as it is ? Or am I suppose to use the resolution as specified as grab_resolution in zed2i param file.

Is it possible to have different downscale parameters for the depth?
I would also suggest to put some more documentation on the CUSTOM parameter and how it affects the depth.

Use-Case

No response

Anything else?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant