ftc-notebook (5feb19)

git-svn-id: svn://tug.org/texlive/trunk@49950 c570f23f-e606-0410-a88d-b1316a301751

19 files changed, 623 insertions, 0 deletions

diff --git a/Master/texmf-dist/doc/latex/ftc-notebook/README.md b/Master/texmf-dist/doc/latex/ftc-notebook/README.md
new file mode 100644
index 00000000000..b6a333dba09
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/ftc-notebook/README.md
@@ -0,0 +1,91 @@
+## ftc-notebook — Formating for FIRST Tech Challenge (FTC)  Notebooks
+
+Team FTC 9773, Robocracy, Released 2019/02, Version 1.0
+
+### Abstract
+
+The ftc-notebook package will greatly simplify filling entries for your FIRST Tech Challenge (FTC) engineering or outreach notebook. We build on top of LaTeX, a robust system that can easily accommodates documents of 100+ pages of entries, figures, and tables while providing support for cross-references.  We developed this package to support most frequently used constructs encountered in an FTC notebook: meetings, tasks, decisions with pros and cons, tables, figures with explanations, team stories and bios, and more. We developed this package during the 2018- season and are using it for our engineering notebook. Team Robocracy is sharing this style in the spirit of coopertition.
+
+### Overview
+
+The LaTeX package ftc-notebook provides help to format a FIRST Tech Challenge (FTC) engineering or outreach notebook. Using this style, you will be able to seamlessly produce a high quality notebook. Its main features are as follows.
+
+- Esthetically pleasing cover pages for the notebook and monthly updates.
+- Easy to use format to enter a team story and a bio for each of the team members.
+- Quick references using list of tasks, figures, and tables.
+- Meeting entries separated into lists of tasks.
+- Each task is visually labeled as one of several kind of activities, such as Strategy, Design, Build, Software,... Activity kind can be customized to reflect a team’s particular focus.
+- Support for supporting your decisions in clear tables that list the pros and cons of each of your decisions.
+- Support for illustrating your robot using pictures with callouts. A callout is text in a box with an arrow pointing toward an interesting feature on your picture.
+- Support for pictures with textual explanation, and groups of picture within a single figure.
+
+We developed this style during the 2018-2019 FTC season and we used it successfully during our competitive season. Compared to other online documents, it is much more robust for large documents. By designing a common style for all frequent patterns, the document also has a much cleaner look. LaTeX is also outstanding at supporting references. Try combining it with an online service like Overleaf, and your team will be generating quality notebooks in no time by actively collaborating online.
+
+We developed this package to require little knowledge of LaTeX. We have tried to hide of the implementation details as much as possible. We explain LaTeX concepts as we encountered them in the document, so we recommend that LaTeX novices read the document once from front to back. Experienced users may jump directly to figures and sections explaining specific environment and commands.
+
+The overall structure of an FTC notebook should be as shown in Figure 1 below.
+
+```
+  \documentclass[11pt]{article}
+  \usepackage[Num=FTC~9773, Name=Robocracy]{ftc-notebook}
+  \begin{document}
+  % 1: cover page and lists
+  \CoverPage{2018-19}{robocracy18.jpg}
+  \ListOfTasks
+  \ListOfFigures
+  \ListOfTables
+
+  % 2: start of the actual notebook with optional team story and bios
+  \StartNotebook
+  \input{src/story.tex}
+  \input{src/bio.tex}
+
+  % 3: meeting entries with optional month delimiters
+  \Month{August}{aug18.jpg}
+  \input{src/aug19.tex}
+  \input{src/aug21.tex}
+  % repeat for successive months until the end of your successful season
+  \end{document}
+
+  Figure 1: Template for notebook.
+```
+
+A document consists of three distinct parts. First, we generate a cover page, followed by lists of tasks, figures, and tables. Pages use alphabetical numbering, as customary for initial front matter. As shown in Figure 1, a LaTeX document starts with a \documentclass command, followed by a list of packages used, and then a \begin{document} command. In LaTeX, comments use the percent character.
+
+Second, we indicate the beginning of the actual notebook using the \StartNotebook command. Pages are then numbered with numerical page numbers starting at 1. A team story and team bio can be entered here, and have specific LaTeX commands detailed in the documentation.  For users unfamiliar with LaTeX, \input commands are used to include separate files whose file names are passed as arguments. The included files are processed as if they were directly listed in the original file. We will use this feature extensively to manage large documents such as an engineering notebook.
+
+Third, we have the actual content of the notebook. We structure entries by meeting and suggest that each meeting uses a distinct input file for its text and a corresponding subdirectory for its supporting material, such as pictures. A meeting entry typically consists of a list of tasks.  Optionally, a new month can be started with a cover page that includes a picture that highlights the accomplishment of the team for that month.
+
+Because you may generate a lot of text, figures, and pictures over the course of your season, we recommend the file structure shown in Figure 2.
+
+```
+Directory structure:
+
+  notebook.tex:     Your main latex file.
+  ftc-notebook.sty: This style files that includes all the formatting,
+                    unless the style file was installed in your
+                    LaTeX directory
+  newmeeting.sh:    A bash script that allows you to create a new
+                    meeting file that is pre-filled. The script can be
+                    customized for your team.
+  src:              Directory where all the meeting info will go.
+  |
+  --> images:       A subdirectory where all the global pictures will go.
+  |                 We recommend to put the team logo, team picture,
+  |                 and monthly pictures (if you chose to use them)
+  |                 Pictures are searched there by default.
+  --> aug19.tex     A file that includes all the text for your
+  |                 (hypothetical) August 19th meeting
+  --> aug19:        A subdirectory where you put all the images
+                    needed in your aug19.tex file
+
+Figure 2. Directory structure.
+```
+
+We recommend to use a pair of "date.tex" LaTeX file and "date" subdirectory for each meeting.  This structure minimizes the risk of name conflicts for pictures and other attachments during the FTC season. Generally, directories logically organized by dates also facilitate searching for specific information.
+
+
+
+
+
+
diff --git a/Master/texmf-dist/doc/latex/ftc-notebook/README.txt b/Master/texmf-dist/doc/latex/ftc-notebook/README.txt
new file mode 100644
index 00000000000..897e0160fc3
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/ftc-notebook/README.txt
@@ -0,0 +1,145 @@
+ftc-notebook — Formating for FIRST Tech Challenge (FTC)  Notebooks
+Team FTC 9773, Robocracy, Released 2019/02, Version 1.0
+
+Abstract
+
+The ftc-notebook package will greatly simplify filling entries for
+your FIRST Tech Challenge (FTC) engineering or outreach notebook. We
+build on top of LaTeX, a robust system that can easily accommodates
+documents of 100+ pages of entries, figures, and tables while
+providing support for cross-references.  We developed this package to
+support most frequently used constructs encountered in an FTC
+notebook: meetings, tasks, decisions with pros and cons, tables,
+figures with explanations, team stories and bios, and more. We
+developed this package during the 2018- season and are using it for
+our engineering notebook. Team Robocracy is sharing this style in the
+spirit of coopertition.
+
+Overview
+
+The LaTeX package ftc-notebook provides help to format a FIRST Tech
+Challenge (FTC) engineering or outreach notebook. Using this style,
+you will be able to seamlessly produce a high quality notebook. Its
+main features are as follows.
+
+- Esthetically pleasing cover pages for the notebook and monthly
+  updates.
+- Easy to use format to enter a team story and a bio for each of
+  the team members.
+- Quick references using list of tasks, figures, and tables.
+- Meeting entries separated into lists of tasks.
+- Each task is visually labeled as one of several kind of activities,
+  such as Strategy, Design, Build, Software,... Activity kind can be
+  customized to reflect a team’s particular focus.
+- Support for supporting your decisions in clear tables that list the
+  pros and cons of each of your decisions.
+- Support for illustrating your robot using pictures with callouts.
+  A callout is text in a box with an arrow pointing toward an
+  interesting feature on your picture.
+- Support for pictures with textual explanation, and groups of picture
+  within a single figure.
+
+We developed this style during the 2018-2019 FTC season and we used it
+successfully during our competitive season. Compared to other online
+documents, it is much more robust for large documents. By designing a
+common style for all frequent patterns, the document also has a much
+cleaner look. LaTeX is also outstanding at supporting references. Try
+combining it with an online service like Overleaf, and your team will
+be generating quality notebooks in no time by actively collaborating
+online.
+
+We developed this package to require little knowledge of LaTeX. We
+have tried to hide of the implementation details as much as
+possible. We explain LaTeX concepts as we encountered them in the
+document, so we recommend that LaTeX novices read the document once
+from front to back. Experienced users may jump directly to figures and
+sections explaining specific environment and commands.
+
+The overall structure of an FTC notebook should be as shown in Figure 1
+below.
+
+  \documentclass[11pt]{article}
+  \usepackage[Num=FTC~9773, Name=Robocracy]{ftc-notebook}
+  \begin{document}
+  % 1: cover page and lists
+  \CoverPage{2018-19}{robocracy18.jpg}
+  \ListOfTasks
+  \ListOfFigures
+  \ListOfTables
+
+  % 2: start of the actual notebook with optional team story and bios
+  \StartNotebook
+  \input{src/story.tex}
+  \input{src/bio.tex}
+
+  % 3: meeting entries with optional month delimiters
+  \Month{August}{aug18.jpg}
+  \input{src/aug19.tex}
+  \input{src/aug21.tex}
+  % repeat for successive months until the end of your successful season
+  \end{document}
+
+  Figure 1: Template for notebook.
+
+A document consists of three distinct parts. First, we generate a
+cover page, followed by lists of tasks, figures, and tables. Pages use
+alphabetical numbering, as customary for initial front matter. As
+shown in Figure 1, a LaTeX document starts with a \documentclass
+command, followed by a list of packages used, and then
+a \begin{document} command. In LaTeX, comments use the percent
+character.
+
+Second, we indicate the beginning of the actual notebook using the
+\StartNotebook command. Pages are then numbered with numerical page
+numbers starting at 1. A team story and team bio can be entered here,
+and have specific LaTeX commands detailed in the documentation.  For
+users unfamiliar with LaTeX, \input commands are used to include
+separate files whose file names are passed as arguments. The included
+files are processed as if they were directly listed in the original
+file. We will use this feature extensively to manage large documents
+such as an engineering notebook.
+
+Third, we have the actual content of the notebook. We structure
+entries by meeting and suggest that each meeting uses a distinct input
+file for its text and a corresponding subdirectory for its supporting
+material, such as pictures. A meeting entry typically consists of a
+list of tasks.  Optionally, a new month can be started with a cover
+page that includes a picture that highlights the accomplishment of the
+team for that month.
+
+Because you may generate a lot of text, figures, and pictures over the
+course of your season, we recommend the file structure shown in Figure 2.
+
+Directory structure:
+
+  notebook.tex:     Your main latex file.
+  ftc-notebook.sty: This style files that includes all the formatting,
+                    unless the style file was installed in your
+                    LaTeX directory
+  newmeeting.sh:    A bash script that allows you to create a new
+                    meeting file that is pre-filled. The script can be
+                    customized for your team.
+  src:              Directory where all the meeting info will go.
+  |
+  --> images:       A subdirectory where all the global pictures will go.
+  |                 We recommend to put the team logo, team picture,
+  |                 and monthly pictures (if you chose to use them)
+  |                 Pictures are searched there by default.
+  --> aug19.tex     A file that includes all the text for your
+  |                 (hypothetical) August 19th meeting
+  --> aug19:        A subdirectory where you put all the images
+                    needed in your aug19.tex file
+
+Figure 2. Directory structure.
+
+We recommend to use a pair of "date.tex" LaTeX file and "date"
+subdirectory for each meeting.  This structure minimizes the risk of
+name conflicts for pictures and other attachments during the FTC
+season. Generally, directories logically organized by dates also
+facilitate searching for specific information.
+
+
+
+
+
+
diff --git a/Master/texmf-dist/doc/latex/ftc-notebook/example-notebook.pdf b/Master/texmf-dist/doc/latex/ftc-notebook/example-notebook.pdf
new file mode 100644
index 00000000000..a8c788f45e1
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/ftc-notebook/example-notebook.pdf
diff --git a/Master/texmf-dist/doc/latex/ftc-notebook/example-notebook.tex b/Master/texmf-dist/doc/latex/ftc-notebook/example-notebook.tex
new file mode 100644
index 00000000000..76eaaeae6d4
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/ftc-notebook/example-notebook.tex
@@ -0,0 +1,21 @@
+\documentclass[11pt]{article}  
+
+\usepackage[Num=FTC~9773, Name=Robocracy]{ftc-notebook}
+
+\begin{document}
+
+    \CoverPage{2018-19}{src/images/robocracy2018.jpg}
+
+    \ListOfTasks
+    \ListOfFigures
+    \ListOfTables
+    
+    \StartNotebook
+    \input{src/story.tex}
+    \input{src/bio.tex}
+    
+    \Month{August}{aug18.jpg}
+    \input{src/aug19.tex}
+    
+\end{document}
+    
diff --git a/Master/texmf-dist/doc/latex/ftc-notebook/ftc-notebook.pdf b/Master/texmf-dist/doc/latex/ftc-notebook/ftc-notebook.pdf
new file mode 100644
index 00000000000..765c15f12b3
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/ftc-notebook/ftc-notebook.pdf
diff --git a/Master/texmf-dist/doc/latex/ftc-notebook/newmeeting.sh b/Master/texmf-dist/doc/latex/ftc-notebook/newmeeting.sh
new file mode 100644
index 00000000000..e00937b198a
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/ftc-notebook/newmeeting.sh
@@ -0,0 +1,83 @@
+#!/bin/bash
+# file name, entry num
+if [ $# -ne 2 ];
+    then echo "
+  USAGE: newmeeting.sh name num
+    create a new directory and tex file for your meeting, where
+      name: file directory and file name for the new entry (e.g. sept06)
+      num:  populate src/name/name.tex with num tasks"
+  exit
+fi
+
+# customize your list of team members
+MEMBERS="Alonso, Aman, Arjun, Cadence, David, Deeya, Divek, Elina, Kaitlyn, Nicky, Zachary"
+
+DIR=src/$1
+FILE=src/$1.tex
+
+if [ -d "$DIR" ]; then
+    # Control will enter here if $DIRECTORY doesn't exist.
+    echo "directory $DIR exists already, pick a new name"
+    exit
+fi
+
+mkdir $DIR
+
+# print new day entry
+echo "
+\begin{Meeting}% [type]% optional type (Preseason, Competition)
+  {}% title
+  {}% date
+  {hours}% duration
+  {$MEMBERS}% members
+  {% list of tasks" > $FILE
+
+# print task within new day entry
+for i in `seq 1 $2`;
+do
+  echo "     %
+     \TaskInfo{}{task:$1:}% title & label
+       {}% reflection" >> $FILE
+done
+echo "}
+
+" >> $FILE
+
+# print tasks
+for i in `seq 1 $2`;
+do
+  echo "
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\Task% optional continuation of task, e.g. [\TaskRef{task:}]
+  {}% {num}[num]: num in 1-6: 1 Strategy; 2 Design; 3 Build; 4 Math/Physic; 5 Software; 6 Team
+
+\MeetingSummary
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\Section{Purpose and Overview}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\Section{Design Process and Decisions}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\Section{Conclusions}
+
+" >> $FILE
+done
+
+# print end of new day entry
+echo "
+ \end{Meeting}
+" >> $FILE
+
+echo "add following in main tex file:
+    \input{src/$1.tex}
+"
+
+
+
+
+
diff --git a/Master/texmf-dist/doc/latex/ftc-notebook/src/aug19.tex b/Master/texmf-dist/doc/latex/ftc-notebook/src/aug19.tex
new file mode 100644
index 00000000000..d932e99a268
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/ftc-notebook/src/aug19.tex
@@ -0,0 +1,210 @@
+ \begin{Meeting}[Preseason]
+      {Programming Chassis Suitable to Test Localization}  
+      {August 19-25}
+      {20 hours}
+      {Nicolas, Zachary}
+      {
+        \TaskInfo{First Iteration Mecanum Drive Module}
+           {aug19: programming chassis first draft}
+           {First attempt at lightweight chassis, worked well but could be made more compact}
+        \TaskInfo{Second Iteration Mecanum Drive and Integration into Chassis}
+           {aug19:programming chassis second draft}
+           {Second attempt is more compact and stronger}
+      }
+ 
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+% meeting summary, or meeting goal
+% high level description of the goal of the meeting, in a paragraph following the command
+\MeetingSummary
+ 
+The goal of this week is to develop new technology for the season. We
+focus on Mecanum wheels, which we have not used for a long time. Our
+immediate goal is design a platform to learn to program encoder
+wheels. We also want to gain experience in using bear motors, namely
+motors without internal gear boxes.
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+% NEW TASK: First Iteration Mecanum Drive Module
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+ %1 Strategy; 2 Design; 3 Build; 4 STEM; 5 Software; 6 Team
+\Task{2}[3]
+ 
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\Section{Goals}
+\begin{itemize}
+  \item Design a mecanum chassis to use for testing localization and autonomous driving.
+  \item Use the chassis to validate (or invalidate) new design ideas (bare motor drivetrain).
+  \item Low cost.
+ \end{itemize}
+
+\Section{Design Process}
+
+First, we plan components to use for the drive train. We do so by
+first considering our design goals for this robot in order of
+importance, then assessing how we can best accomplish these
+goals. Often, one design choice can satisfy many factors
+simultaneously.
+
+\begin{DescriptionTable}{Factors}{Solutions}%
+    {Design goals for the programming chassis}{table:aug19:goals}
+  %
+  \TableEntryTextItem{Testing New Designs}
+    {
+      \item Incorporate odometry wheels (for position tracking)
+      \item Prototype use of motors without gearboxes (With external reduction)
+      \item Test mecanum wheels 
+    } \\ \hline
+  %
+  \TableEntryTextItem{Low Cost}
+    {
+      \item Use motors without gearboxes: this will allow us to use
+        our classic Neverest 20 motors (which we decommissioned due to
+        their fragile gearboxes).
+      \item Design with mostly plywood, EuroBoard, and 3d printed parts.
+      \item Use Nexus mecanum wheels (already on hand).
+      \item Use EMS22Q Bourns encoder for odometry wheels (least
+        expensive compatible encoder that satisfies the design
+        constraints).  } \\ \hline
+  %
+  \TableEntryTextItem{Analogous to Typical Competition Robots}
+  { 
+    \item Make the robot lightweight, so we can add weight to match
+      any future robot?s weight for testing
+    \item Use Mecanum wheels (we already have test tank chassis, and
+      are looking to experiment with mecanum) }
+  %
+\end{DescriptionTable}
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\Section{CAD and Build}
+
+A complete chassis requires 4 identical wheel modules, which contain a
+mecanum wheel and its motor. The CAD model is shown in
+\FigureRef{aug19:first cad}. We CNCed the parts as well as 3D printed
+the large pulley. The result is shown in \FigureRef{aug19:first
+  build}.
+
+\ExplainedPictFigure{src/aug19/first-cad.jpg}[0.4]%
+  {CAD model of mecanum wheel module (first iteration)}{aug19:first cad}
+  {
+  \begin{compactitem}
+    \item Nexus mecanum wheel
+    \item Single belt reduction from bare motor to wheel
+    \item Adjustable tensioner pulley
+    \item EuroBoard side plates
+    \item Churro standoffs
+    \item Extremely compact
+    \end{compactitem}
+  }
+  
+\PictFigure{src/aug19/first-build.jpg}[0.4]%
+  {Prototype of mecanum wheel module (first iteration)}{aug19:first build}%
+  [\Callout{-8, 4}{Unsupported Idle Pulley}{-0.5, -0.5}]         
+
+\begin{DescriptionTable*}{Works}{Need Improvement}%
+  {Conclusion after first build}{table:aug19:improvement}
+  %
+  \TableEntryItemItem{
+    \item Wheel runs smoothly
+    \item Press fit bearings in wheel work flawlessly
+    \item Motor standoffs work well
+    \item EuroBoard is a fantastic prototyping material - cuts easily on the CNC 
+  } {
+    \item Cantilevered idler bearing deforms the EuroBoard under load - %
+      needs support from both sides
+    \item EuroBoard is not very strong - not suitable for competition %
+      robot drivetrain, but works for light 
+  }
+\end{DescriptionTable*}
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\Section{Conclusion}
+
+The module looks promising, and has already successfully demonstrated
+the effectiveness of using EuroBoard as a prototyping material, though
+we should avoid using it structurally on a competition robot. The
+idler pulley needs to be redesigned with support on either side, and
+we can likely make the entire module even more compact by using a
+slightly shorter belt!
+
+
+With these small modifications, the module is ready to be used on the
+programming chassis. We now need to design the chassis itself, as well
+as mounting points for all the sensors.
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+% NEW TASK Second Iteration Mecanum Drive and Integration into Chassis
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\Task[\TaskRef{aug19: programming chassis first draft}]{2}[3]
+
+\Section{Goals}
+\begin{itemize}
+  \item Suggested improvements from \TaskRef{aug19: programming chassis first draft}.
+  \item Design odometry wheel modules.
+  \item Design complete chassis.
+\end{itemize}
+
+\newpage
+
+\Section{Design}
+
+Using the feedback from \TaskRef{aug19: programming chassis first
+  draft}, we redesigned the CAD model for the wheel module, shown in
+\FigureRef{aug19:second cad}. We reused an odometry design, shown in
+\FigureRef{aug19:odometry cad}. The full chassis consists of 4 wheel
+modules and 3 odometry modules. The Chassis CAD is shown in
+\FigureRef{aug19:chassi cad}.
+
+We CNCed the parts as well as 3D printed the large pulley. The result
+is shown in \FigureRef{aug19:first build}.
+
+\ExplainedPictFigure{src/aug19/second-cad.jpg}[0.4]%
+  {CAD model of mecanum wheel module (second iteration)}{aug19:second cad}
+  {
+    Improvements:
+    \begin{compactitem}
+      \item Idler Bearing supported from both sides
+      \item Shorter plate layout
+      \item Slightly smaller pulley on the wheel to avoid scraping on the mat
+    \end{compactitem}
+  }
+  
+\ExplainedPictFigure{src/aug19/encoder-cad.jpg}[0.4]%
+  {CAD model of odometry wheel}{aug19:odometry cad}
+  {
+    Features:
+    \begin{compactitem}
+      \item 38mm omniwheel
+      \item 1024 ppr direct mounted encoder
+      \item Shielding to protect encoder
+      \item Spring-loaded against the mat for improved reliability
+      \item Accurate mounting holes
+    \end{compactitem}
+  }
+
+\ExplainedPictFigure{src/aug19/chassi-cad.jpg}[0.4]%
+  {CAD of entire Chassis}{aug19:chassi cad}
+  {
+    Features:
+    \begin{compactitem}
+      \item Lightweight simple chassis
+      \item Fast Mecanum wheel base
+      \item 3 odometry omniwheels
+      \item 2 light sensors facing the mat
+      \item Plywood base - easy to manufacture
+    \end{compactitem}
+  }
+
+  \PictFigure{src/aug19/build-pict.jpg}[0.7]%
+    {Building of full chassis (second iteration)}{aug19:second build}
+
+
+\end{Meeting}
+
+ 
+
diff --git a/Master/texmf-dist/doc/latex/ftc-notebook/src/aug19/build-pict.jpg b/Master/texmf-dist/doc/latex/ftc-notebook/src/aug19/build-pict.jpg
new file mode 100644
index 00000000000..a4430eb5232
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/ftc-notebook/src/aug19/build-pict.jpg
diff --git a/Master/texmf-dist/doc/latex/ftc-notebook/src/aug19/chassi-cad.jpg b/Master/texmf-dist/doc/latex/ftc-notebook/src/aug19/chassi-cad.jpg
new file mode 100644
index 00000000000..66cf1d79f02
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/ftc-notebook/src/aug19/chassi-cad.jpg
diff --git a/Master/texmf-dist/doc/latex/ftc-notebook/src/aug19/encoder-cad.jpg b/Master/texmf-dist/doc/latex/ftc-notebook/src/aug19/encoder-cad.jpg
new file mode 100644
index 00000000000..3c7ce1ac8d2
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/ftc-notebook/src/aug19/encoder-cad.jpg
diff --git a/Master/texmf-dist/doc/latex/ftc-notebook/src/aug19/first-build.jpg b/Master/texmf-dist/doc/latex/ftc-notebook/src/aug19/first-build.jpg
new file mode 100644
index 00000000000..dc5d30fed7e
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/ftc-notebook/src/aug19/first-build.jpg
diff --git a/Master/texmf-dist/doc/latex/ftc-notebook/src/aug19/first-cad.jpg b/Master/texmf-dist/doc/latex/ftc-notebook/src/aug19/first-cad.jpg
new file mode 100644
index 00000000000..37904c28868
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/ftc-notebook/src/aug19/first-cad.jpg
diff --git a/Master/texmf-dist/doc/latex/ftc-notebook/src/aug19/second-cad.jpg b/Master/texmf-dist/doc/latex/ftc-notebook/src/aug19/second-cad.jpg
new file mode 100644
index 00000000000..9e061400380
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/ftc-notebook/src/aug19/second-cad.jpg
diff --git a/Master/texmf-dist/doc/latex/ftc-notebook/src/bio.tex b/Master/texmf-dist/doc/latex/ftc-notebook/src/bio.tex
new file mode 100644
index 00000000000..4afd71143d2
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/ftc-notebook/src/bio.tex
@@ -0,0 +1,19 @@
+\begin{Bio}
+
+ \BioEntry{Mitsiky}{Member since 2015}{Team Mascot}{Hoping to become a Therapy Dog so 
+  I can participate in the team’s outreach, too!}
+  {src/bio/mitsiki.jpg}
+  {%
+  I am a 4 1/2 year old Coton de Tulear and have been team mascot for
+  two years. I am a wonderful distraction. I take seriously my job,
+  doing my best to make everyone smile. In fact, my name, Mitsiky, means
+  "My Smile" in Malagasy. My favorite hobbies are visiting chipmunk
+  holes, playing tug-of-war with my toy bunny, and just being cute. \vspace{3mm} \\
+  %     
+  My goal this year is to earn my credential as a Therapy Dog so that I
+  can participate in the team’s outreach and make everyone feel good by
+  flashing my warm smile. Also, I hope to finally catch a squirrel.
+  }
+  
+\end{Bio}
+
diff --git a/Master/texmf-dist/doc/latex/ftc-notebook/src/bio/mitsiki.jpg b/Master/texmf-dist/doc/latex/ftc-notebook/src/bio/mitsiki.jpg
new file mode 100644
index 00000000000..ad44c336b57
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/ftc-notebook/src/bio/mitsiki.jpg
diff --git a/Master/texmf-dist/doc/latex/ftc-notebook/src/images/aug18.jpg b/Master/texmf-dist/doc/latex/ftc-notebook/src/images/aug18.jpg
new file mode 100644
index 00000000000..052116dbf10
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/ftc-notebook/src/images/aug18.jpg
diff --git a/Master/texmf-dist/doc/latex/ftc-notebook/src/images/logo.jpg b/Master/texmf-dist/doc/latex/ftc-notebook/src/images/logo.jpg
new file mode 100644
index 00000000000..d61b9c9689b
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/ftc-notebook/src/images/logo.jpg
diff --git a/Master/texmf-dist/doc/latex/ftc-notebook/src/images/robocracy2018.jpg b/Master/texmf-dist/doc/latex/ftc-notebook/src/images/robocracy2018.jpg
new file mode 100644
index 00000000000..0dddbfd6690
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/ftc-notebook/src/images/robocracy2018.jpg
diff --git a/Master/texmf-dist/doc/latex/ftc-notebook/src/story.tex b/Master/texmf-dist/doc/latex/ftc-notebook/src/story.tex
new file mode 100644
index 00000000000..182f00cfa9d
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/ftc-notebook/src/story.tex
@@ -0,0 +1,54 @@
+\begin{TeamStory}{Resilience through Innovation \& Simplicity}
+
+We are a fourth year 4-H team with 3 new members. We are a diverse
+group of 11 boys and girls, in grades 8 to 12 from 6 different school
+districts, and while we may speak up to 6 different languages, we are
+united by a common passion for STEM.\\ \vspace{3mm}
+
+\RawPict{src/images/robocracy2018.jpg}{.6}{} \\ \vspace{3mm}
+
+Our theme this year is resilience through innovation and
+simplicity. Last year, after finishing first place at our Hudson
+Valley Regionals, we came back dead last from Eastern
+SuperRegionals. We took this opportunity to take a hard look at our
+process. After last year’s season, where we strove for innovation for
+the sake of having a cool cutting-edge design, we have learned from
+our mistakes and are now striving for resilience through innovation
+and simplicity.
+
+For the first time, we kick-started our season with the “build a robot
+in 36 hours” challenge. During this time, we were able to efficiently
+flush out a design and develop an intuition for the game. Because of
+this, we were able to break down our process and make sure to have
+deliberate design decisions that focus on resilience and efficient
+simplicity, in addition to innovation. Our process emphasizes analysis
+of competing ideas, developed by competing design groups, which are
+considered head to head until the stronger idea wins.
+
+We maintain our process for sustainability which we cultivated last
+year, to become a more efficient and sustainable team.  We each strive
+to learn two new skills during the season and we have a strong culture
+of mentoring each other. This protects the team from losing skills
+when someone graduates from the team.
+
+An important part of being a member of Team Robocracy is making time
+for our robust outreach in the community. We seek to empower other
+kids to develop skills that they can use for the rest of their lives,
+thereby building their own resilience. We also share our expertise and
+skills where we can have a positive impact in the lives of others. We
+run multiple afterschool enrichment programs targeting underserved
+communities, run robotics camps, 3D print prosthetics, and recycle
+computers to donate to third world schools.
+
+We are very grateful for our membership in 4H. 4H provides for us an
+excellent platform for our outreach and has enabled us to reach many
+communities that would otherwise not be exposed to STEM and
+robotics. 4H also gives us access to important resources such as
+advertisement, Lego Mindstorm kits, and their liability insurance for
+our workshops! Our Off The Streets and Amazing Afternoons programs in
+Mt. Vernon Elementary Schools are both conducted through 4H. As the
+only STEM-based 4H club in our area, we also take seriously our role
+of promoting and inspiring interest in STEM at fairs and all of the
+outreach we do.
+
+\end{TeamStory}