From c16072606397a201fba69811ab0ad9f38afe25f3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=98=D0=B2=D0=B0=D0=BD=20=D0=9F=D0=BE=D0=B4=D0=BC=D0=BE?= =?UTF-8?q?=D0=B3=D0=B8=D0=BB=D1=8C=D0=BD=D1=8B=D0=B9?= Date: Wed, 31 Aug 2022 23:23:22 +0300 Subject: [PATCH] Update 'ReadMe.md' --- ReadMe.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ReadMe.md b/ReadMe.md index ee97bba..1631f35 100644 --- a/ReadMe.md +++ b/ReadMe.md @@ -37,4 +37,4 @@ https://redmine.drivecast.tech/issues/374 There is a problem with publishing the cubes to two different topics: to the VIO and to the GPS-VIO frames. I have to find the workaround for this problem. For now you can see the AR cubes in the rviz which shows VIO (from ov_msckf directory) ### Saving the rendered AR to image sequnece -1. Turn on the CameraPub (TODO: Change the Camera Info Topic in CameraPub to /ov_msckf/cam0_info and save the .rviz config file)) \ No newline at end of file +1. Turn on the CameraPub display. \ No newline at end of file