From d4c15bfd0a77b02914b7d8bb2a5e53384367e4ed 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:28:19 +0300 Subject: [PATCH] Update 'ReadMe.md' --- ReadMe.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/ReadMe.md b/ReadMe.md index 0e449b4..9e24ba0 100644 --- a/ReadMe.md +++ b/ReadMe.md @@ -1,4 +1,5 @@ # open_vins for AR. +Link to the original repository: # Features 1. GPS loosely coupled sensor fusion taken from VINS-Fusion. @@ -37,4 +38,5 @@ 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 display. The image sequnece will be stored to ~/.ros/ directory \ No newline at end of file +1. To the catkin_ws_ov/src directory clone the https://git.drivecast.tech/pi/rviz_camera_stream_ar repository. And build it from catkin_ws_ov directory with `catkin build` command +2. In rviz with running ov_msckf turn on the CameraPub display. The image sequnece will be stored to ~/.ros/ directory \ No newline at end of file