-
Notifications
You must be signed in to change notification settings - Fork 79
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
[feature request] Control Azimuthal Window with Driver #117
Comments
If there's a parameter in the SDK that lets us control that, we can certainly expose it! I see no qualms with that. |
after digging I realized someone else proposed this: #98 and the underlying version here: ouster-lidar/ouster-sdk#366 |
The problem was that after discussing in the main repo it was mentioned that azimuth window change in the lidar config requires a restart of the lidar (not manually but it has to internally restart). Therefore having that as a parameter would make the lidar have to start up twice taking twice as long to start then. |
I can see their worry, but personally I'd say "OK" to that and just make sure its both documented and when its changed a warning is thrown to let someone know. If startup time is something they care about, then they can make that change more permanently elsewhere to help here - but that way they know but isn't blocking others. |
It would be nice to be able to control the azimuthal window of the lidar via a parameter file rather than control it using the firmware page
The text was updated successfully, but these errors were encountered: