You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inside the MaRRTPathPlanNode.py there are 4 non standard ROS messages imported:
Map
CarSensors
WaypointsArray
Waypoint
My understanding is that those messages are custom made for the E-gnition vehicle and are not copied to this repository. They seem to be included in the package.xml and the in the package's makefile but they can't be found.
I was able to bypass those dependencies by recreating the messages out of their used attributes in the functions of the script, but it would be awesome if you included a copy of the *.msg files.
The text was updated successfully, but these errors were encountered:
Hi @ekampourakis ,
I did not publish these messages on purpose, cause they were not part of my own code and I didn't have permission for that. Additionally they could expose some other details of software implementation of the system, which is not public now.
You did a good job by recreating the messages out of my code, and this is exactly what I expected from users of my code. Would be nice if you would like to contribute to my repository by submitting Pull-Request with your version of messages, so others could profit from that as well. Just drop them maybe in some "msg" folder in the root.
I'm currently working on a FS driverless car myself and trying your algorithm for the initial mapping of the track. When I'm done with the testing and the implementation I'll submit a pull request with all my supplementary messages and couple of changes for you to review.
Inside the
MaRRTPathPlanNode.py
there are 4 non standard ROS messages imported:Map
CarSensors
WaypointsArray
Waypoint
My understanding is that those messages are custom made for the E-gnition vehicle and are not copied to this repository. They seem to be included in the
package.xml
and the in the package's makefile but they can't be found.I was able to bypass those dependencies by recreating the messages out of their used attributes in the functions of the script, but it would be awesome if you included a copy of the
*.msg
files.The text was updated successfully, but these errors were encountered: