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

Dumping the dynamic parameters and then loading them again throws exception #879

Closed
Kaju-Bubanja opened this issue Aug 6, 2019 · 3 comments

Comments

@Kaju-Bubanja
Copy link

Saving the dynamic parameters into a file for example of the temporal filter: rosrun dynamic_reconfigure dynparam dump /camera/temporal test.yaml and then loading it again rosrun dynamic_reconfigure dynparam load /camera/temporal test.yaml throws following error:
[ERROR] [1565078492.496547243]: Exception thrown while processing service call: Given value -1is outside valid range! The file looks like this:

!!python/object/new:dynamic_reconfigure.encoding.Config
dictitems:
  filter_smooth_alpha: 0.4000000059604645
  filter_smooth_delta: 20
  frames_queue_size: 16
  groups: !!python/object/new:dynamic_reconfigure.encoding.Config
    dictitems:
      filter_smooth_alpha: 0.4000000059604645
      filter_smooth_delta: 20
      frames_queue_size: 16
      groups: !!python/object/new:dynamic_reconfigure.encoding.Config
        state: []
      holes_fill: 3
      id: 0
      name: Default
      parameters: !!python/object/new:dynamic_reconfigure.encoding.Config
        state: []
      parent: 0
      state: true
      stream_filter: 1
      stream_format_filter: 1
      stream_index_filter: -1
      type: ''
    state: []
  holes_fill: 3
  stream_filter: 1
  stream_format_filter: 1
  stream_index_filter: -1
state: []

Is there a way to set the needed dynamic parameters with rqt_reconfigure and then save them and reload them on startup?

@doronhi
Copy link
Contributor

doronhi commented Aug 13, 2019

It seems to be a bug in librealsense, where the minimum value for "stream_index_filter" is set to 0 and it's default value to -1 (meaning any index)
I'll submit a PR to librealsense. Until such time, you can manually set stream_index_filter to 0 in the test.yaml file (assuming you are filtering depth or RGB. If you filter infra1 or infra2, set it to either 1 or 2 accordingly).

@doronhi
Copy link
Contributor

doronhi commented Aug 13, 2019

Add PR#4631 to librealsense.

@RealSenseCustomerSupport
Copy link
Collaborator


The issue has been addressed in RealSense SDK build 2.29.
Closing this ticket unless there is any problem.
Thank you.

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

No branches or pull requests

3 participants