-
Notifications
You must be signed in to change notification settings - Fork 26
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
nested parameters #54
Comments
Hi, thanks for the comment. What would you expect |
Yes exactly. Practical example : a pid controller. The param yaml would be something like : controller_name : test
some_other_param : 2
pid:
p: [ 1, 2, 3 ]
i: [ 1, 2, 3 ]
d: [ 1, 2, 3 ] But for that I would have to define a config for each 'level' ( the level that contains controller_name and some_other_param and another for the pid alone) |
I definitely see the interest in this feature, but it would be a little tricky to implement. Since a nested namespace could be provided for each parameter, one as to keep tracks of the associated namespaces. I'll have a look but I can't make it a priority right now, I'm open to discussion if you want to tackle it yourself ;) . |
I can add that in the end I'd like to have : ros::NodeHandle nh("~");
ParamType testParams(nh);
testParams.fromParamServer();
testParams.pid().p; // --> vector of double or eigen vector
I was counting on you guys :) But i'll definitely have a look. |
You actually expect a nested |
It would be awesome if we could do :
I though it was the purpose of 'groups', but it's only a dynamic reconfigure goodie.
The text was updated successfully, but these errors were encountered: