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

Provide API ? #5

Open
artivis opened this issue Apr 26, 2017 · 3 comments
Open

Provide API ? #5

artivis opened this issue Apr 26, 2017 · 3 comments

Comments

@artivis
Copy link

artivis commented Apr 26, 2017

Hi,
I would like to use your scan matcher within another project but it seems that the whole implementation takes places in the node itself.
Is there any plan to separate the actual scan matching from the node therefore providing a usable API ??

Cheers.

@JGMonroy
Copy link
Member

Hi artivis,
Originally the RF2O code was not a ROS node, but given that most people use ROS we created this wrapper version.

We are currently working in a new, more robust and precise version of this "scan-matcher", called SRF (to appear soon). As soon as we have it implemented I'll publish it and if you are interested I can also make public a version just containing the classes and the API to use it from a non-ROS system.

@artivis
Copy link
Author

artivis commented Apr 26, 2017

Thanks for the quick answer !

Long story short, I'm writing a pluginlib based ROS package that aims at facilitating switching from a scan matcher to another as simply as setting a parameter in a launch file.
I would like to make a plugin for RF2O as well so that it is available in this scheme, but if you are working on a newer version maybe should I wait for it ?

@YoshuaNava
Copy link

Hi,
@JGMonroy I think rf2o works great, thank you for making it available to the community, I'm very interested in testing out SRF. Will this be open-sourced in the near future?

Thank you.
Yoshua Nava

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