docs(wiki): fix remaining image and asset paths across all articles

Author: nevalsar

wiki/actuation/Pure-Pursuit-Controller-for-Skid-Steering-Robot.md

@@ -25,7 +25,7 @@ This goal position keeps on changing and is a point on the trajectory to be foll
 
 The following image explains the concept of lookahead distance and the arc to follow.
 
-![Geometry of Pure Pursuit Algorithm [1]](assets/images/pure_pursuit_geometry.png)
+![Geometry of Pure Pursuit Algorithm [1]](/assets/images/pure_pursuit_geometry.png)
 
 In the image above, we see that given a point at a particular location from the robot say at location (x,y) in the robot's frame (the frame fixed on the robot). The point is at a distance l from the current location of the robot. Using a geometrical derivation, we can derive the radius of curvature of this arc as -
 

wiki/actuation/__all_subsections.md

@@ -500,7 +500,7 @@ rosrun moveit_setup_assistant setup_assistant.launch
 
 From here, you will be launched into a MoveIt setup assistant menu, as shown below:
 
-![moveit_setup_assistant_start[(assets/moveit_setup_assistant_start.png)
+![moveit_setup_assistant_start](/assets/images/moveit_setup_assistant_start.png)
 
 Select “Create New MoveIt Configuration Package” then select the URDF model file created earlier. Select “Load Files” to load the URDF file.
 
@@ -737,7 +737,7 @@ This goal position keeps on changing and is a point on the trajectory to be foll
 
 The following image explains the concept of lookahead distance and the arc to follow.
 
-![Geometry of Pure Pursuit Algorithm [1]](assets/images/pure_pursuit_geometry.png)
+![Geometry of Pure Pursuit Algorithm [1]](/assets/images/pure_pursuit_geometry.png)
 
 In the image above, we see that given a point at a particular location from the robot say at location (x,y) in the robot's frame (the frame fixed on the robot). The point is at a distance l from the current location of the robot. Using a geometrical derivation, we can derive the radius of curvature of this arc as -
 
@@ -1074,4 +1074,4 @@ The main webpage of the Vedder Esc project is [found here](http://vedder.se/2015
 The speed controller can be built from scratch, but it is far more time-effective to purchase a model from a supplier. These can be purchased for between $80 - $150 with various design modifications. A proven model is the VESC-X from Enertion. Despite being an Australian company, the controllers are produced and distributed in the US with a 3-5 day lead time. There is a quantity discount for 4+ controllers and if you place the controllers in your cart after registering and wait a bit, you'll get a 10% off coupon code by e-mail. The current code as of 3/5/2017 was *"pushingsucks".*
 
 ## Sample Arduino Code
-The [code in this zip file](assets/DriveCharacterization.zip) interfaces an Arduino Mega 2560 to a VESC-X over serial. The sketch runs an open loop characterization routine that drives the motor in each direction. Motor braking is applied when a duty cycle command is set to 0. Motor freewheeling occurs when a current command is set to 0.
+The [code in this zip file](/wiki/actuation/assets/DriveCharacterization.zip) interfaces an Arduino Mega 2560 to a VESC-X over serial. The sketch runs an open loop characterization routine that drives the motor in each direction. Motor braking is applied when a duty cycle command is set to 0. Motor freewheeling occurs when a current command is set to 0.

wiki/actuation/moveit-and-HEBI-integration.md

@@ -58,7 +58,7 @@ rosrun moveit_setup_assistant setup_assistant.launch
 
 From here, you will be launched into a MoveIt setup assistant menu, as shown below:
 
-![moveit_setup_assistant_start[(assets/moveit_setup_assistant_start.png)
+![moveit_setup_assistant_start](/assets/images/moveit_setup_assistant_start.png)
 
 Select “Create New MoveIt Configuration Package” then select the URDF model file created earlier. Select “Load Files” to load the URDF file.
 

wiki/actuation/vedder-electronic-speed-controller.md

@@ -34,4 +34,4 @@ The main webpage of the Vedder Esc project is [found here](http://vedder.se/2015
 The speed controller can be built from scratch, but it is far more time-effective to purchase a model from a supplier. These can be purchased for between $80 - $150 with various design modifications. A proven model is the VESC-X from Enertion. Despite being an Australian company, the controllers are produced and distributed in the US with a 3-5 day lead time. There is a quantity discount for 4+ controllers and if you place the controllers in your cart after registering and wait a bit, you'll get a 10% off coupon code by e-mail. The current code as of 3/5/2017 was *"pushingsucks".*
 
 ## Sample Arduino Code
-The [code in this zip file](assets/DriveCharacterization.zip) interfaces an Arduino Mega 2560 to a VESC-X over serial. The sketch runs an open loop characterization routine that drives the motor in each direction. Motor braking is applied when a duty cycle command is set to 0. Motor freewheeling occurs when a current command is set to 0.
+The [code in this zip file](/wiki/actuation/assets/DriveCharacterization.zip) interfaces an Arduino Mega 2560 to a VESC-X over serial. The sketch runs an open loop characterization routine that drives the motor in each direction. Motor braking is applied when a duty cycle command is set to 0. Motor freewheeling occurs when a current command is set to 0.

wiki/common-platforms/ros/ros-cost-maps.md

@@ -74,10 +74,10 @@ The following tutorial uses a Quadrotor with RGB-D Sensor as the base platform.
 Here is the setup:
 
 Quadrotor (`base_link`): [3DR Iris+](https://store.3dr.com/products/IRIS)
-![3DR Iris+](assets/ROSCostMaps-90ce8.png)
+![3DR Iris+](/assets/images/ROSCostMaps-90ce8.png)
 
 Depth Sensor (`camera_link`): [Xtion Pro Live](https://www.asus.com/us/3D-Sensor/Xtion_PRO_LIVE/)
-![Xtion Pro Live](assets/ROSCostMaps-fad65.png)
+![Xtion Pro Live](/assets/images/ROSCostMaps-fad65.png)
 
 ### Setup of the camera
 
@@ -162,7 +162,7 @@ The source code for MAVROS, which will be similar to the folder you will find by
 
 You will want to find the file named `px4_config.yaml` or `apm_config.yaml` depending on which of the flight controller firmware you are running. If you are running the PX4 firmware, you are going to want to open `px4_config.yaml` and find this section:
 
-![Code Snippet](assets/ROSCostMaps-2dba7.png)
+![Code Snippet](/assets/images/ROSCostMaps-2dba7.png)
 
 Once you find it, you will want to change:
 
@@ -253,7 +253,7 @@ Our setup can be run by issuing the following commands in separate terminals or
 ### Output
 
 The output of the costmap is shown here.
-![CostMap Output](assets/ROSCostMaps-8c746.png)
+![CostMap Output](/assets/images/ROSCostMaps-8c746.png)
 
 ## Communications with PIXHAWK
 

wiki/common-platforms/ros/ros-navigation.md

@@ -31,11 +31,11 @@ This will generate a file 'frames.pdf' in the current directory which will conta
 
 ### Debugging example
 An example tf tree with a robot setup with a laser scanner that uses hector mapping for scan matching and visual odometry is shown in the figure below.
-![Example TF Tree with Laser Scanner](assets/ROSNavigation-d06e2.png)
+![Example TF Tree with Laser Scanner](/assets/images/ROSNavigation-d06e2.png)
 
 If someone is expecting their robot to navigate with the above tf configuration, they will have a hard time seeing anything move. As you can guess from the above coordinate transform tree, the tf tree is not complete. The path planner will be happy with the above configuration because it can get the laser scan matching at /laser with respect to the world coordinate frame but the robot base will not be able to command the wheel actuators. The error can be fixed by adding the transform between the world coordinate frame and the wheel odometry frame of the robot and the resulting tf tree is shown below:
 
-![Correct TF Tree with Laser Scanner](assets/ROSNavigation-7d9d1.png)
+![Correct TF Tree with Laser Scanner](/assets/images/ROSNavigation-7d9d1.png)
 
 Other useful tf tools for debugging are `tf_echo` and `tf_monitor`
 
@@ -71,7 +71,7 @@ If you have tried at least once to look at the navigation stack in ROS, you must
 4. Robot_Localization:
   - When to use this?
     - Use this when `robot_pose_ekf` is not enough for your robot! This package offers all the goodness of robot_pose_ekf and more. It provides non-linear state estimation using the Extended Kalman Filter (EKF) and the Unscented Kalman Filter (UKF) to fuse information from arbitrary number of sensors. It also provides `navsat_transform_node` which helps in integrating GPS data (fixes) for the robot's localization. The following picture from the Wiki is informative:
-![Robot_Localization Diagram](assets/ROSNavigation-72039.png)
+![Robot_Localization Diagram](/assets/images/ROSNavigation-72039.png)
   - What does it require?
     - It requires `/odometry/filtered` topic of type `nav_msgs/Odometry`, `/imu/data` topic of type `sensor_msgs/Imu` and the `/gps/fix` topic of type `sensor_msgs/NavSatFix`
 

wiki/computing/__all_subsections.md

@@ -285,7 +285,7 @@ Download the CUDA driver from the [official nvidia website here](https://develop
 
 *At the time of writing this document, the latest stable version is CUDA 10.0*.
 
-![](https://roboticsknowledgebase.com/wiki/computing/assets/nvidia-cuda.png)
+![](/assets/images/nvidia-cuda.png)
 
 After downloading the file, go to the folder where you have downloaded the file and run the following commands from the terminal to install the CUDA drivers. Please make sure that the filename used in the command below is the same as the downloaded file and replace the `<version>` number.
 
@@ -314,7 +314,7 @@ Go to official cuDNN website [official cuDNN website](https://developer.nvidia.c
 
 **Make sure you download the correct cuDNN version which matches with you CUDA version.**
 
-![](https://roboticsknowledgebase.com/wiki/computing/assets/nvidia-cudnn.png)
+![](/assets/images/nvidia-cudnn.png)
 
 ### Installing from TAR file (Recommended Method)
 For cuDNN downloaded using _cuDNN Library for Linux_ method, go to the folder where you have downloaded the “.tgz” file and from the command line execute the following (update the filename).

wiki/computing/setup-gpus-for-computer-vision.md

@@ -94,7 +94,7 @@ Download the CUDA driver from the [official nvidia website here](https://develop
 
 *At the time of writing this document, the latest stable version is CUDA 10.0*.
 
-![](https://roboticsknowledgebase.com/wiki/computing/assets/nvidia-cuda.png)
+![](/assets/images/nvidia-cuda.png)
 
 After downloading the file, go to the folder where you have downloaded the file and run the following commands from the terminal to install the CUDA drivers. Please make sure that the filename used in the command below is the same as the downloaded file and replace the `<version>` number.
 
@@ -123,7 +123,7 @@ Go to official cuDNN website [official cuDNN website](https://developer.nvidia.c
 
 **Make sure you download the correct cuDNN version which matches with you CUDA version.**
 
-![](https://roboticsknowledgebase.com/wiki/computing/assets/nvidia-cudnn.png)
+![](/assets/images/nvidia-cudnn.png)
 
 ### Installing from TAR file (Recommended Method)
 For cuDNN downloaded using _cuDNN Library for Linux_ method, go to the folder where you have downloaded the “.tgz” file and from the command line execute the following (update the filename).

wiki/fabrication/__all_subsections.md

@@ -337,7 +337,7 @@ This is a good starting points for anyone looking to convert files from their So
 ### Space Jockey Custom Profile
 This is 2013-14 Team B's Makerbot slicer profile designed for faster, stronger parts (faster infill, 3 shells), with the temperature settings already tweaked for the MRSD MakerBot. Download and unzip to User/My Things/Profiles, and then select "Space Jockey Hull Parts" in your print settings in Makerware.
 
-[Download Space_Jockey_Profile.zip](assets/Space_Jockey_Profile.zip)
+[Download Space_Jockey_Profile.zip](/wiki/fabrication/assets/Space_Jockey_Profile.zip)
 
 ## Issues Log
 1. **Issue:** Large objects would start peeling off the left side of the plate.
@@ -434,7 +434,7 @@ The Series A Pro printer generally uses PLA (as opposed to ABS). PLA requires ve
 
 ### Print Profiles
 The standard profile is a good compromise between speed and print quality for PLA on the Series A Pro. 
-[Download SeriesA_Standard_Profile.zip](assets/SeriesA_Standard_Profile.zip)
+[Download SeriesA_Standard_Profile.zip](/wiki/fabrication/assets/SeriesA_Standard_Profile.zip)
 ![Print Quality of Standard Profile](/assets/images/SeriesA_PLA_SP.jpg)
 
 ## Tips

wiki/fabrication/makerbot-replicator-2x.md

@@ -34,7 +34,7 @@ This is a good starting points for anyone looking to convert files from their So
 ### Space Jockey Custom Profile
 This is 2013-14 Team B's Makerbot slicer profile designed for faster, stronger parts (faster infill, 3 shells), with the temperature settings already tweaked for the MRSD MakerBot. Download and unzip to User/My Things/Profiles, and then select "Space Jockey Hull Parts" in your print settings in Makerware.
 
-[Download Space_Jockey_Profile.zip](assets/Space_Jockey_Profile.zip)
+[Download Space_Jockey_Profile.zip](/wiki/fabrication/assets/Space_Jockey_Profile.zip)
 
 ## Issues Log
 1. **Issue:** Large objects would start peeling off the left side of the plate.