new arch diagram, author name for hackflight

slab14 · Jul 16, 2017 · 3465f07 · 3465f07
1 parent 8873f4f
commit 3465f07
Show file tree

Hide file tree

Showing 8 changed files with 4 additions and 3 deletions.
diff --git a/docs/paper/drone_depth_materials.PNG → docs/paper/drone_depth_materials.png b/docs/paper/drone_depth_materials.PNG → docs/paper/drone_depth_materials.png
diff --git a/docs/paper/figures.pptx b/docs/paper/figures.pptx
diff --git a/docs/paper/forces.PNG → docs/paper/forces.png b/docs/paper/forces.PNG → docs/paper/forces.png
diff --git a/docs/paper/main.pdf b/docs/paper/main.pdf
diff --git a/docs/paper/main.tex b/docs/paper/main.tex
@@ -74,7 +74,7 @@
 
 	\begin{figure}[htbp]
 		\centering
-		\includegraphics[width=\textwidth]{drone_depth_materials.PNG}
+		\includegraphics[width=\textwidth]{drone_depth_materials.png}
 		\caption{A snapshot from AirSim shows an aerial vehicle flying in an urban environment. The inset shows depth, object segmentation and front camera streams generated in real time.}
 		\label{drone_depth_materials}
 	\end{figure}
@@ -99,7 +99,7 @@
 	Our simulator follows a modular design with an emphasis on extensibility. The core components includes environment model, vehicle model, physics engine, sensor models, rendering interface, public API layer and an interface layer for vehicle firmware as depicted in Figure~\ref{fig:arch}.
 
 	\begin{figure}[ttbp]
-		\includegraphics[width=\textwidth]{overview.PNG}
+		\includegraphics[width=\textwidth]{overview.png}
 		\caption{The architecture of the system that depicts the core components and their interactions.}
 		\label{fig:arch}
 	\end{figure}
@@ -121,7 +121,7 @@
 	Formally, a vehicle is defined as a collection of $K$ vertices placed at positions $\{{\bf r}_1, .., {\bf r}_k\}$ and normals $\{{\bf n}_1, .., {\bf n}_k\}$, each of which experience a unitless vehicle specific scaler control input $\{u_1, .., u_k\}$. The forces and torques from these vertices are assumed to be generated in the direction of their normals. However note that the positions as well as normals are allowed to change during the simulation.
 
 	\begin{figure}[ttbp]
-		\includegraphics[width=0.93\textwidth]{forces.PNG}
+		\includegraphics[width=0.93\textwidth]{forces.png}
 		\caption{Vehicle model for the quadrotor. The four blue vertices experience the controls $u_1, .. u_4$, which in turn results in the forces ${\bf F}_1, .., {\bf F}_4$ and the torques ${\bf \tau}_1, .., {\bf \tau}_4$.}
 		\label{fig:quad}
 	\end{figure}

diff --git a/docs/paper/overview.PNG b/docs/paper/overview.PNG
diff --git a/docs/paper/overview.png b/docs/paper/overview.png
diff --git a/docs/paper/references.bib b/docs/paper/references.bib
@@ -208,6 +208,7 @@ @Misc{braeunig
 
 @Misc{levyHackflight,
   title        = {Hackflight: Simple quadcopter flight control firmware and simulator for C++ hackers},
+  author       = {Simon Levy},
   howpublished = {\url{https://github.com/simondlevy/hackflight}},
 }