Removing tabs

book/opmanual_autolab/20_charging_setup/60_SOFTWARE_software_architecture_maintenance_area.md

@@ -2,80 +2,80 @@
 
 In this part it is explained how the system for module 1 and 2 works.
 
-## Responsibilities of overall managing the chargers  
+## Responsibilities of overall managing the chargers
 There are 3 main tasks that have to be accomplished :
 
 **TASK 1**- Evaluating the April tag’s position in order to understand where the reference tags are located and in which direction the duckiebot went  
 **TASK 2**- Gathering information on charger sizes and finding the next free charger a duckiebot newly arriving the maintenance area should go  
-**TASK 3**- Selecting the frequency with which the LED should blink 
+**TASK 3**- Selecting the frequency with which the LED should blink
 
-In Modul 1, all the responsibilities are done by the charging manager. 
-The output of tasks above feeds information to other tasks, for example, in task 1, it will be found out, which duckiebot entered or left the charger and this will be saved in a data structure that can be accessed by the charging manager. 
-In task 2, charging manager will iterate over the data structure in order to discover how many duckiebots occupy the chargers. Through linear search, the most unoccupied charger will be determined and the frequency of LEDs corresponding charger id will be changed accordingly. In task 3 LEDs will blink with the mentioned frequency. 
+In Modul 1, all the responsibilities are done by the charging manager.
+The output of tasks above feeds information to other tasks, for example, in task 1, it will be found out, which duckiebot entered or left the charger and this will be saved in a data structure that can be accessed by the charging manager.
+In task 2, charging manager will iterate over the data structure in order to discover how many duckiebots occupy the chargers. Through linear search, the most unoccupied charger will be determined and the frequency of LEDs corresponding charger id will be changed accordingly. In task 3 LEDs will blink with the mentioned frequency.
 
-In Modul 2, the tasks are completed in separate devices. Task 1 is accomplished by doorkeepers and the rest will be done by the charging manager. The output of task 1 will be shared with the charging manager through a communication server. For this objective, charging manager serves a python-dictionary of duckiebot Apriltags as keys and charger indices as values (initially all charger indices are set to zero to indicate that the duckiebot does not occupy any charger.). The clients, in this case the doorkeepers, will update this dictionary according to their evaluation of April tag positions, for example, if duckiebot with April tag 400 enters charger 3 then the doorkeeper will change the value of 400 from 0 to 3. 
+In Modul 2, the tasks are completed in separate devices. Task 1 is accomplished by doorkeepers and the rest will be done by the charging manager. The output of task 1 will be shared with the charging manager through a communication server. For this objective, charging manager serves a python-dictionary of duckiebot Apriltags as keys and charger indices as values (initially all charger indices are set to zero to indicate that the duckiebot does not occupy any charger.). The clients, in this case the doorkeepers, will update this dictionary according to their evaluation of April tag positions, for example, if duckiebot with April tag 400 enters charger 3 then the doorkeeper will change the value of 400 from 0 to 3.
 
 
 
 ## Workflow in detail
 Here you can find step-by-step workflow of module 1 and module 2
 
 ### Preliminary information:
-Before starting to read,note that every frequency with which the LED blinks, implies a charger the duckiebot should go. Also, CSLAM Acquisiton node provides many information. Only the data about the position of the center on the image will be used by charging manager(for module 1) or doorkeeper(for module 2). 
+Before starting to read,note that every frequency with which the LED blinks, implies a charger the duckiebot should go. Also, CSLAM Acquisiton node provides many information. Only the data about the position of the center on the image will be used by charging manager(for module 1) or doorkeeper(for module 2).
 
 ### Module 1:
 #### Charging Manager
 
 0. Charging Manager’s LED blinks with the initial frequency
 1. **(TASK 1)** CSLAM Acquisition node provides information on the Apriltags in the scope of camera  
-	In the scope of the camera, lies the reference tags and duckiebots’ Apriltags if there are any duckiebots arrived to the intersection.   
-	The positions of duckiebots’ Apriltags and reference tags will be saved and updated, as the node publishes the topic.   
-	Upon receiving these, the closest neighbor reference tag to duckiebot's apriltag and the timestamp will be computed and saved (Here minimal distance is defined by the minimal euclidean distance of two points on the image.)  
-	(The first computed closest neighbor reference tag will be saved under the variable “first_neighbor” and the other results will be updated and saved under “last_neighbor”.)  
-	
+    In the scope of the camera, lies the reference tags and duckiebots’ Apriltags if there are any duckiebots arrived to the intersection.  
+    The positions of duckiebots’ Apriltags and reference tags will be saved and updated, as the node publishes the topic.  
+    Upon receiving these, the closest neighbor reference tag to duckiebot's apriltag and the timestamp will be computed and saved (Here minimal distance is defined by the minimal euclidean distance of two points on the image.)  
+    (The first computed closest neighbor reference tag will be saved under the variable “first_neighbor” and the other results will be updated and saved under “last_neighbor”.)
+
 2. **(TASK 1)** Apriltag Evalutaion:  
-	After not seeing an Apriltag of a duckiebot for more than threshold time, the “first_neighbor” and “last_neighbor” will be evaluated. That means, if the first_neighbor is the entrance tag and the last_neighbor is the direction2_tag, then Duckiebot went in direction2. Since direction2 corresponds to , for example, charger 2, the Duckiebot went in charger 2. 
-	According to this outcome the chargers dictionary will be updated and the tag of duckiebot which has entered/exited the charger i and the timestamp of entrance/exit will be saved/deleted under/from charger i’s list. 
+    After not seeing an Apriltag of a duckiebot for more than threshold time, the “first_neighbor” and “last_neighbor” will be evaluated. That means, if the first_neighbor is the entrance tag and the last_neighbor is the direction2_tag, then Duckiebot went in direction2. Since direction2 corresponds to , for example, charger 2, the Duckiebot went in charger 2.
+    According to this outcome the chargers dictionary will be updated and the tag of duckiebot which has entered/exited the charger i and the timestamp of entrance/exit will be saved/deleted under/from charger i’s list.
 3. **(TASK 2)** Charger sizes will be updated according to step 2  
-	If the most unoccupied charger is changed, it will be noticed and new frequency corresponding the new charger with the most free spaces will be determined.
+    If the most unoccupied charger is changed, it will be noticed and new frequency corresponding the new charger with the most free spaces will be determined.
 
 4. **(TASK 3)** LED blinks with the determined frequency in step 3
 
 These steps will be repeated upon receiving the messages from acquisition node’s topic
-	
-	
+
+
 
 ### Module 2:
 
 #### Preliminary information:
-In this module a dictionary where keys are the duckiebots Apriltags and values are the charger indices or zero(indicating that the duckiebot is currently not occupying any charger) is served by the charging manager. The clients,namely the doorkeepers, will update this dictionary with charger indices if a Duckiebot enters a charger or with zero if a Duckiebot leaves a charger. 
+In this module a dictionary where keys are the duckiebots Apriltags and values are the charger indices or zero(indicating that the duckiebot is currently not occupying any charger) is served by the charging manager. The clients,namely the doorkeepers, will update this dictionary with charger indices if a Duckiebot enters a charger or with zero if a Duckiebot leaves a charger.
 
 
 #### Doorkeeper
 
 1. **(TASK 1)** CSLAM Acquisition node provides information on the Apriltags in the scope of camera  
-	In the scope of the camera, lies the reference tags and duckiebots’ Apriltags if there are any duckiebots arrived to the intersection.   
-	The positions of duckiebots’ Apriltags and reference tags will be saved and updated, as the node publishes the topic.   
-	Upon receiving these, the closest neighbor reference tag to duckiebot's apriltag and the timestamp will be computed and saved (Here minimal distance is defined by the minimal euclidean distance of two points on the image.)  
-	(The first computed closest neighbor reference tag will be saved under the variable “first_neighbor” and the other results will be updated and saved under “last_neighbor”.)  
-	
+    In the scope of the camera, lies the reference tags and duckiebots’ Apriltags if there are any duckiebots arrived to the intersection.  
+    The positions of duckiebots’ Apriltags and reference tags will be saved and updated, as the node publishes the topic.  
+    Upon receiving these, the closest neighbor reference tag to duckiebot's apriltag and the timestamp will be computed and saved (Here minimal distance is defined by the minimal euclidean distance of two points on the image.)  
+    (The first computed closest neighbor reference tag will be saved under the variable “first_neighbor” and the other results will be updated and saved under “last_neighbor”.)
+
 2. **(TASK 1)** Apriltag Evalutaion:
-	After not seeing an Apriltag of a duckiebot for more than threshold time, the “first_neighbor” and “last_neighbor” will be evaluated. That means, if the first_neighbor is the entrance tag and the last_neighbor is the direction2_tag, then Duckiebot went in direction2. Since direction2 corresponds to , for example, charger 2, the Duckiebot went in charger 2. 
-	According to this outcome the chargers dictionary will be updated and the tag of duckiebot which has entered/exited the charger i and the timestamp of entrance/exit will be saved/deleted under/from charger i’s list. 
+    After not seeing an Apriltag of a duckiebot for more than threshold time, the “first_neighbor” and “last_neighbor” will be evaluated. That means, if the first_neighbor is the entrance tag and the last_neighbor is the direction2_tag, then Duckiebot went in direction2. Since direction2 corresponds to , for example, charger 2, the Duckiebot went in charger 2.
+    According to this outcome the chargers dictionary will be updated and the tag of duckiebot which has entered/exited the charger i and the timestamp of entrance/exit will be saved/deleted under/from charger i’s list.
 
 3. **(Communication Server)** Sharing the information where duckiebot went
-	After finding out where a duckiebot went, its value in the served dictionary will be either set to the charger index if it entered a charger or to zero, if it left a charger. 
+    After finding out where a duckiebot went, its value in the served dictionary will be either set to the charger index if it entered a charger or to zero, if it left a charger.
 
 
-#### Charging Manager 
+#### Charging Manager
 
 
 0. Charging Manager’s LED blinks with the initial frequency
 1. **(Communication Server)** Charging Manager checks the dictionary updated by the doorkeepers periodically
-	If the charger index of an Apriltag in the dictionary is changed, then the tag of duckiebot which has entered/exited the charger i and the timestamp of entrance will be saved/deleted under/from charger i’s list. 
-	
+    If the charger index of an Apriltag in the dictionary is changed, then the tag of duckiebot which has entered/exited the charger i and the timestamp of entrance will be saved/deleted under/from charger i’s list.
+
 3. **(TASK 2)** Charger sizes will be updated according to step 2
-	If the most unoccupied charger is changed, it will be noticed and new frequency corresponding the new charger with the most free spaces will be determined
+    If the most unoccupied charger is changed, it will be noticed and new frequency corresponding the new charger with the most free spaces will be determined
 
 4. **(TASK 3)** LED blinks with the determined frequency in step 3
 
@@ -84,7 +84,7 @@ These steps will be repeated upon receiving the messages from acquisition node
 
 
 
- 
-	
+
+
 
 

book/opmanual_autolab/30_Watchtowers/35_light-sensors.md

@@ -63,7 +63,7 @@ To do so put the pin headers into the big hole and fix it with the screws.
 
 The best way to figure out how to do this is to always take the sensor and turn it until you can read what is written on it and that will be our basic position.
 
-Plugins on the raspberry-pi: 
+Plugins on the raspberry-pi:
 
 o o 1 o o
 
@@ -110,11 +110,15 @@ You can check the calibration by going to the calibration folder, TODO
 
 To run the sensor container first you need to pull the image:
 
-‘docker -H HOSTNAME.local pull gian1717/sensor:p2’
+```
+$ docker -H HOSTNAME.local pull gian1717/sensor:p2
+```
 
 And then start the container:
 
-‘docker -H HOSTNAME.local run -it  --net host --privileged --name light-sensor -v /data:/data gian1717/sensor:p2’
+```
+$ docker -H HOSTNAME.local run -it  --net host --privileged --name light-sensor -v /data:/data gian1717/sensor:p2
+```
 
 If you want to know more:
 

book/opmanual_autolab/45_localization_system_software/48_input_processing.md

@@ -34,7 +34,10 @@ For **online acquisition**, three strategies can be used:
 * Each agent directly sends the images and the central ROS master does the processing for every agent (this implies having a (or many) good computer)
 * A mix of the two is also possible (the Autobots send their images, the Watchtowers process them)
 
+
+<div markdown="1" class="draft">
 As explained in [](#localization-demo), in both cases the Watchtowers and Autobots use the [acquisition bridge](#acquisition-bridge) to send their image streams to a central computer. The Watchtowers only send images when movements are detected, to reduce the number of images to process and record.
+</div>
 
 For offline acquisition, all we need to do is record a rosbag on this computer.