community
community copied to clipboard
add a new proposal to sig-robotics: Offline Visual Navigation without Metric Map
This is the project of my ICRA paper: SCALE: Self-Correcting Visual Navigation for Mobile Robots via Anti-Novelty Estimation
Welcome @chch9907! It looks like this is your first PR to kubeedge/community 🎉
/assign @hongbingzhang
@chch9907 thanks for the proposal.
Although this is really nice framework for robotics, I would like to have a few questions.
- This seems pretty much system service application, not implemented in KubeEdge. So the proposal is to develop the system application containers, and deploy it on KubeEdge if user wants to do so?
- If that is so, how user call these APIs or interfaces? I guess that image sensing data comes from edge devices where edgecore runs, and some pre-process can be done on edge. but expecting some processes need to be running in the cloud infrastructure, in that case how we can connect those data pipeline at runtime? Or is this supposed to be a single pod to process everything?
I may be missing something, so would like to hear feedback to learn more.
@fujitatomoya Thank you for your comments and useful code review. This proposal is indeed not implemented in KubeEdge but to develop a system application. As this is an offline-learned navigation method without sim-to-real gaps, it requires the real-world offline trajectory datasets that are absent in current open-sourced datasets, particulary those accrosing different illuminations and seasons. Therefore, this proposal aims to leverage KubeEdge to curate the real-world datasets collected from diverse edge devices for training the navigation methods that are generalized to different scenarios and robust to different illuminations or seasons . In return, the end users can then use the trained models from the cloud to conduct the visual navigation and localization in their deployed environments with a image-node topological map representation. This is a promising route for handling real-world visual navigation tasks. Furthermore, this model is not too large to access from cloud at runtime, and can even be directly customized on edge, which has been tested during our experiments.
I will illustrate this idea in the proposal. Thank you for your suggestions!
@chch9907 thanks for the explanation, since this is proposal with concrete algorithm, i am good to go with this. I would like to other reviews to take a look before merge.
I get lost in using PR..
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign hongbingzhang after the PR has been reviewed.
You can assign the PR to them by writing /assign @hongbingzhang in a comment when ready.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign hongbingzhang after the PR has been reviewed.
You can assign the PR to them by writing /assign @hongbingzhang in a comment when ready.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/assign @hongbingzhang
@fisherxu Hello, could you help review my PR? I have improved the proposal according to the comments.
@fisherxu Hi xu, I have deleted the others' commits that confused me before, and squashed my commits into one. But it seems there is something wrong in my operation. Could you help me? If no problem, could you help merge it? Thanks!