-
Notifications
You must be signed in to change notification settings - Fork 19
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/add map server #64
Conversation
@adamantivm the code was rebased after merging #63. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor comments then LGTM
@@ -207,6 +210,7 @@ protected void init(NodeMainExecutor nodeMainExecutor) { | |||
configureParameterServer(); | |||
|
|||
startExtrinsicsPublisherNodes(); | |||
startMapServer(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
name nit: startMapServerNode (for consistency)
@@ -316,6 +320,16 @@ private void startExtrinsicsPublisherNodes() { | |||
mNodeMainExecutor.execute(mRobotExtrinsicsTfPublisherNode, nodeConfiguration); | |||
} | |||
|
|||
private void startMapServer() { | |||
// Create ROS node for extrinsics publisher node |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wrong comment?
This PR adds a minimal implementation for a map server, generating and publishing an empty map. The empty map generator can be replaced by something that reads an actual map image and fills the required data. It should be easy to replace the current one by sticking to the defined interface.
This is built on top of #63 to avoid generating unnecessary conflicts; it would be ideal to merge the other PR before reviewing this one.