Add another point to columns
This commit is contained in:
parent
9c9c687a10
commit
479dd8de23
@ -69,7 +69,6 @@
|
||||
\pagebreak
|
||||
|
||||
\section{Introduction}
|
||||
% TODO briefly recap the project purposes and goals
|
||||
This document describes the current state, problems, and future
|
||||
plans of the Fenceless Grazing Collars project. The FGC system's
|
||||
purpose is to reduce the amount of manual labor required for herding
|
||||
@ -81,7 +80,6 @@ provide a reliable, cost-effective, and accessible replacement
|
||||
for manual farmer labor.
|
||||
|
||||
\section{Current Project State}
|
||||
% TODO describe where you are currently on the project
|
||||
At present, the initial design of the project is complete. The project's structure
|
||||
lends itself very well to division among the three group members, and all
|
||||
team members' responsibilities have been explicitly defined and agreed upon.
|
||||
@ -128,9 +126,6 @@ others, we will peruse the online documents, modules, and extra links provided t
|
||||
that we are not asking questions that have already been answered.
|
||||
|
||||
\section{Weekly Progress}
|
||||
% TODO The document should include a detailed, week-by-week summary of activities,
|
||||
% problems, solutions, and the like (consider using your blogs to inform this report).
|
||||
% The report should not include more than a summary of any bigger documents you produced
|
||||
This section provides weekly summaries for every week of our Fall 2019 term for which the
|
||||
project was active.
|
||||
|
||||
@ -248,10 +243,6 @@ responsibility for parts of each assignment.
|
||||
|
||||
\pagebreak
|
||||
\section{Retrospective}
|
||||
% TODO add retrospective
|
||||
% positives column: anything good that happened
|
||||
% deltas column: changes that need to be implemented
|
||||
% actions column: specific actions that will be implemented in order to create the necessary changes
|
||||
\setlength{\columnseprule}{0.4pt}
|
||||
\begin{parcolumns}[colwidths={1=0.3\textwidth}]{3}
|
||||
\colchunk{
|
||||
@ -311,6 +302,14 @@ responsibility for parts of each assignment.
|
||||
The team must change the means of distributing tasks. The method used in this term,
|
||||
which was heavily based on individual initiative, led to an improper distribution of
|
||||
work and time.
|
||||
|
||||
Although one of the requirements for the project is the usage of the LoRa long range
|
||||
communication protocol, the team is not very familiar with the protocol's details.
|
||||
This has not been an issue for the documentation stage; the design document could
|
||||
be written with sufficient thoroughness. However, to proceed with the implementation
|
||||
of the LoRa gateway (device responsible for communicating with the collars), as well
|
||||
as the collars themselves, a more in-depth understanding of the LoRa protocol
|
||||
is required.
|
||||
}
|
||||
\colchunk{
|
||||
\subsection{Actions}
|
||||
@ -329,6 +328,11 @@ responsibility for parts of each assignment.
|
||||
to assign and manage tasks. This way, a specific person will be responsible for
|
||||
assigning tasks, rather than relying on initiative like was done before. Assigning
|
||||
team members to individual tasks will serve the same purpose.
|
||||
|
||||
To address the lack of understanding of the LoRa protocol, all members of the team will spend
|
||||
the first week of the next term reading the LoRa documentation. Although only
|
||||
two members of the team must work in-depth with LoRa, an understanding of the protocol
|
||||
will be useful to every member.
|
||||
}
|
||||
\end{parcolumns}
|
||||
\end{document}
|
||||
|
Loading…
Reference in New Issue
Block a user