Moving images directory into modules.

cmusatyalab · Nov 29, 2023 · 31518c5 · 31518c5
1 parent 84ed907
commit 31518c5
Show file tree

Hide file tree

Showing 19 changed files with 14 additions and 14 deletions.
diff --git a/docs/modules/cnc.md b/docs/modules/cnc.md
@@ -129,7 +129,7 @@ The openscout-vol directory will not exist until the containers are launched for
 
 view.html can be copied into any/all of the following 3 directories: received, detected, and moa. One can then navigate to http://host:8080/<1 of 3 dirs>/view.html where the directory of images can be iterated through using the left/right arrow keys. Below the current image will be displayed the current image nubmer and the total number of images in the directory.
 
-![view.html example!](../images/viewhtml.png)
+![view.html example!](images/viewhtml.png)
 
 #### live.html
 
@@ -139,7 +139,7 @@ live.html can be copied into openscout-vol root. One can then navigate to http:/
 
 The object detection engine will only output an image if one of the classes is detected above the specified threshold, therefore it will not update as frequently as the other images.
 
-![live.html example!](../images/livehtml.png)
+![live.html example!](images/livehtml.png)
 
 #### go2rtc
 
@@ -155,4 +155,4 @@ streams:
 
 Once configured, navigate to http://host:1984 and select the streams to view and click the stream button. The streams will be rendered in a similar fashion as live.html.
 
-![go2rtc!](../images/go2rtc.png)
+![go2rtc!](images/go2rtc.png)
diff --git a/docs/modules/commander.md b/docs/modules/commander.md
@@ -44,7 +44,7 @@ At a minimum, you will need to provide the commander with the address of the mac
 
 ### Layout/Usage
 
-![Commander Layout!](../images/commander_layout.png)
+![Commander Layout!](images/commander_layout.png)
 
 The above screenshot details the layout of the Commander. The typical usage of the application is as follows: 
 

diff --git a/docs/images/commander_layout.png → docs/modules/images/commander_layout.png b/docs/images/commander_layout.png → docs/modules/images/commander_layout.png
diff --git a/docs/images/go2rtc.png → docs/modules/images/go2rtc.png b/docs/images/go2rtc.png → docs/modules/images/go2rtc.png
diff --git a/docs/images/livehtml.png → docs/modules/images/livehtml.png b/docs/images/livehtml.png → docs/modules/images/livehtml.png
diff --git a/docs/images/mymaps1.png → docs/modules/images/mymaps1.png b/docs/images/mymaps1.png → docs/modules/images/mymaps1.png
diff --git a/docs/images/mymaps2.png → docs/modules/images/mymaps2.png b/docs/images/mymaps2.png → docs/modules/images/mymaps2.png
diff --git a/docs/images/mymaps3.png → docs/modules/images/mymaps3.png b/docs/images/mymaps3.png → docs/modules/images/mymaps3.png
diff --git a/docs/images/mymaps4.png → docs/modules/images/mymaps4.png b/docs/images/mymaps4.png → docs/modules/images/mymaps4.png
diff --git a/docs/images/onion_assembly1.jpg → docs/modules/images/onion_assembly1.jpg b/docs/images/onion_assembly1.jpg → docs/modules/images/onion_assembly1.jpg
diff --git a/docs/images/onion_assembly2.jpg → docs/modules/images/onion_assembly2.jpg b/docs/images/onion_assembly2.jpg → docs/modules/images/onion_assembly2.jpg
diff --git a/docs/images/onion_assembly3.jpg → docs/modules/images/onion_assembly3.jpg b/docs/images/onion_assembly3.jpg → docs/modules/images/onion_assembly3.jpg
diff --git a/docs/images/system-arch.png → docs/modules/images/system-arch.png b/docs/images/system-arch.png → docs/modules/images/system-arch.png
diff --git a/docs/images/viewhtml.png → docs/modules/images/viewhtml.png b/docs/images/viewhtml.png → docs/modules/images/viewhtml.png
diff --git a/docs/images/watch_assembly.jpg → docs/modules/images/watch_assembly.jpg b/docs/images/watch_assembly.jpg → docs/modules/images/watch_assembly.jpg
diff --git a/docs/modules/modules.md b/docs/modules/modules.md
@@ -1,7 +1,7 @@
 ---
 layout: default
 title: Module Documentation
-nav_order: 2
+nav_order: 3
 has_children: true
 permalink: docs/modules
 ---

diff --git a/docs/modules/plan.md b/docs/modules/plan.md
@@ -13,25 +13,25 @@ We leverage the drawing tools of [Google MyMaps](https://www.google.com/maps/abo
 
 ## Drawing Lines/Polygons
 
-![Drawing!](../images/mymaps1.png)
+![Drawing!](images/mymaps1.png)
 
 1. The name of the mission and various layers can be configured on the left hand panel. New lines/polygons will appear here as they are drawn, and are associated to a particular layer.
 2. Click the 'Draw a line' icon to begin drawing a line or polygon.
 3. Clicking anywhere on the map will create a vertex. Click the same vertex again to stop drawing a line segment or click the starting vertex to end a polygon.
 
 ## Adding Task Specifications
 
-![Drawing!](../images/mymaps2.png)
+![Drawing!](images/mymaps2.png)
 
 Once a line or polygon is created, a text box will be displayed for a description. Enter a task and its associated parameters. See the [Task Stubs]({{ site.baseurl }}{% link modules/hermes/tasks.md %}) page for a list of existing tasks. The description can be editing at any time by clicking on the pencil icon. The style of the line/polygon can be changed using the paint bucket icon.
 
-![Drawing!](../images/mymaps4.png)
+![Drawing!](images/mymaps4.png)
 
 Multiple lines/polygons can be added to the map, each with their own task specification. The tasks will be executed in the order they appear in the list (see #1 in the image above). In the above image, that would mean **Area1** is executed first, then **GreenArea**, and finally **Red**. The order can be rearranged by dragging the names of the placemarks in the list at the left.  
 
 ## Exporting to KML
 
-![Drawing!](../images/mymaps3.png)
+![Drawing!](images/mymaps3.png)
 
 1. Click the 3-dots icon and go to 'Export to KML/KMZ'.
 2. Select download. Optionally you can check to the box to export KML instead of KMZ (KMZ is a zipped format so it is smaller, but not human readable). The filename of the exported KML document will match the name that was given to the map and will be located in the Downloads directory.
diff --git a/docs/modules/stl.md b/docs/modules/stl.md
@@ -45,7 +45,7 @@ Since we are optimizing for weight, we have used %5 infill. The .stl files liste
 
 ### Watch
 
-![Watch Assembly!](../images/watch_assembly.jpg)
+![Watch Assembly!](images/watch_assembly.jpg)
 
 1. In order to assemble the watch harness, line up the watch base with the harness body as shown.
 2. Observe the areas that overlap; this is where Gloop needs to be applied.
@@ -59,17 +59,17 @@ Since we are optimizing for weight, we have used %5 infill. The .stl files liste
 
 The LTE module on the Onion Omega can interfere with the GPS of the ANAFI which is near the camera/gimbal. As such, care must be taken to orient the case properly and as far back on the clip as possible when Glooping the pieces together.
 
-![Onion Assembly!](../images/onion_assembly1.jpg)
+![Onion Assembly!](images/onion_assembly1.jpg)
 
 1. Layout the pieces of the harness as show in the first figure.
 
-![Onion Assembly!](../images/onion_assembly2.jpg)
+![Onion Assembly!](images/onion_assembly2.jpg)
 
 2. The onion base should be oriented so that the end with the 3 cutouts (for 2 antennas and the power connector) is facing in the direction of the harness tongue. 
 3. Align the harness as shown so that the back bar of the harness clip overlaps with the crossbar on the bottom of the onion base.
 4. Note the two areas of overlap between the harness and the onion base.
 
-![Onion Assembly!](../images/onion_assembly3.jpg)
+![Onion Assembly!](images/onion_assembly3.jpg)
 
 5. Appy Gloop to the tongue and back bar of the harness, as well as to the cross bar and front edge of the onion base and press the two pieces together as they were previously aligned.
 6. Continue applying moderate pressure for about 30 seconds.

diff --git a/docs/quickstart/quickstart.md b/docs/quickstart/quickstart.md
@@ -1,7 +1,7 @@
 ---
 layout: default
 title: Quickstart
-nav_order: 1
+nav_order: 2
 has_children: true
 permalink: docs/quickstart
 ---