Make diagnostic aggregator composable#435
Conversation
|
Hi @nnarain, Is this PR still being worked on? |
|
hey @frozenreboot Ya I should be able to get back to this. If I don't find the time this week I'll give you a ping. Hey @ct2034 any initial feedback on this PR? |
| * the aggregator will report the error and publish it in the aggregated output. | ||
| */ | ||
| class Aggregator | ||
| class Aggregator : public rclcpp::Node |
There was a problem hiding this comment.
This is not required for composable nodes.
Franky: I would advise against it. It's hard if you want this class as a member of another class.
This pr would be much smaller if you kept the node member and the logger member.
7ea3c1d to
933726f
Compare
933726f to
7e891e0
Compare
ct2034
left a comment
There was a problem hiding this comment.
Thanks. This looks very good.
Could I please ask you to provide a small launch test. It could be based in the nice example diagnostic_aggregator/example/compose_example.launch.py.in.
And please also add a small section on this to the diagnostic_aggregator/README.md
|
Will do |
Heya.
This PR makes the
diagnostic_aggregatornode composable (see #321 )Summary of changes:
Aggregatorclass implementget_node_base_interfaceso it can be registered as a componentrclcpp_componentAnalyzerGroupplugin as existing the analyzers library. When composing the nodes I found thatAnalyzerGroupwould not load. I assume it has worked up to this point because everything was linked into the same executable.