-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
Image instead of robot #174
Comments
Maybe I will add it someday ;) |
Looking for this as well, I know that someone already managed to do this: |
I developed this, have a look if you are interested: #246 . 😉 |
I tried to clone the DEV branch, but I don't know why the map didn't appear, it gave errors in functions that had "vacuum_pos.a" |
Mmmm I see, maybe your robot does not provide the orientation. Try replacing |
I am aware of this issue, it will be addressed 👍 |
Or you (@rospogrigio) can do it if you want to |
I'm a bit busy at the moment, so feel free to fix it the way you find the most suitable... |
I try this, but it didn't work, I have a Viomi, I don't know if it affects.
Nothing is urgent, I was just testing and trying to help, my knowledge is still at the beginning |
Then in viomi/map_data_parser.py, line 323, try replacing |
@rospogrigio @axcs It should be fixed on |
Only with this new fix in DEV it didn't work again. In addition to your fix, it was necessary to change the line that rospogrigio said in viomi/map_data_parser.py |
Yeh it works, thanks @PiotrMachowski . |
It might be possible, I need to take a look at raw map data |
Ok thanks,, I will try to understand the code to try to help in some way. |
@axcs it's really easy if data is there. Unfortunately right now I don't have much free time |
@axcs I have added this feature to viomi 👍 |
Added in v2.2.0 |
It works just by updating and it's bloody awesome! Thanks a lot. |
Since it generates predicted path, I assume, direction of the robot is known property.
It would be great visually to have picture of the actual robo instead of colored circle.
The text was updated successfully, but these errors were encountered: