Final version done

This commit is contained in:
2017-12-03 15:31:48 -08:00
parent 4a0bd4462c
commit 0614f8b8e7
2 changed files with 5 additions and 5 deletions

View File

@@ -83,7 +83,7 @@ class VideoTest(QtCore.QThread):
self.raw_image = message
\end{lstlisting}
\subsubsection{Description}
Yet another QThread class, this example subscribes to the ROS topic that is passed in under the sub\_path argument in order to get video stream data.
This example subscribes to the ROS topic that is passed in under the sub\_path argument in order to get video stream data.
An example of this topic might be "/cam1/usb\_cam1/image\_raw/compressed".
Inside of the body of the thread, it checks if there is image data, and if so decompresses it into a raw 8-bit image using ROS's OpenCV bridge libraries.
Finally, it converts the OpenCV image into a QImage and then into a QPixmap before broadcasting an update signal so the main GUI thread can show the image on the QLabel.

View File

@@ -1,18 +1,18 @@
\subsection{Deliverables}
\subsubsection{Github Repository}
Our group gained access to and set up the Github repository for storing the group's ground station code and documentation.
All documentation was put into this repository as it was completed.
Our group gained access to and set up directories in the Github repository for storing the group's ground station code and documentation.
All documentation was put into this repository as it was started and/or completed.
As our team has begun testing code, useful sections of it have been added to the repository for reference during future development of the full ground station software.
\subsubsection{Problem Statement Document}
A thorough problem statement document has been created by the group.
The document helps to focus the group and gives a high level view of the scope and goals for the project going forward.
The document helps to direct the group and gives a high level view of the scope and goals for the project going forward.
Work on the document began on October 17th, a rough draft of this document was completed on October 10th and the final draft was completed and delivered to the client on October 20th.
The problem statement was approved by the client via email on October 24th.
\subsubsection{Requirements Document}
The requirements document lays out tasks that have to be completed in order for the project to be considered successful.
The document also includes a Gannt chart that serves as a rough time table for each module that must be completed.
The document also includes a Gantt chart that serves as a rough time table and dependencies for each module that must be completed.
By following this document and completing each task on time, the team can be sure to complete the software within the required timetable.
Writing of the document began on October 26th.
A rough draft was completed on October 27th and a final version of the requirements document was delivered to the client for review on November 3rd.