======All Hands Meeting- September 26, 2015======
**Attended: Dr. Kuh, Kenny, Jon, Jason, Christie, Garrett, Brian, Brandon, Kim, Tyrin, Tryston, Kaeo, Kristie, May, Scott, Ryan, Ernesto, Raydan, Raegan, Daisy, Jeremy, Keoni, Travis**

=====Reminders=====
  * Calendar email responses
    * Calendar email responses will have the same deadline as emails- 24 hours!
    * You can use the "maybe" option
    * Make sure you are responding to your personal calendar- not the SCEL one
  * Open food on table
    * Please do not leave food or drinks open in the lab
    * We will get ants...
  * Using the water pot heater
    * Please empty excess water from the pot if you use it

=====Proposal Presentation Comments=====
  * Put numbers on slides so it is easier to reference
  * Use less distracting pictures on slides
  * Hardware teams should include block diagrams
  * Less laughter
  * Do not stick your hands in your pockets or cover them with your sleeves
  * Find a good balance between text and pictures on slides- try to avoid slides with all text
  * Use bullet points

=====Proposal Presentation Technical Notes=====
  * **Dragonfruit Design Team**
    * Focus on getting a working board
  * **Cranberry Design Team**
    * Make an outline of steps to complete when debugging Cranberry
  * **Apple Design Team**
    * Remote programming = wireless programming
    * Better to say implement data routing instead of "implement parent module data"
    * Split up tasks between members- programming and hardware
      * Can ask Cranberry and Dragonfruit teams for help
  * **Verification Team**
    * Unit testing of Apple board to ensure hardware is working properly
    * Think about how boards will work with software
  * **Firmware Team**
    * Difference between Git and GitHub
    * No SPI for XBee
    * Look at Apple repo
      * Libraries and how to get sensor readings
  * **XBee Team**
    * Collaborate with other teams
    * Create a test plan
      * Find range between two XBees in the real world
      * Allow for variances and find them
  *** Server Team**
    * Create a block diagram of the server translator
    * Collaborate with firmware team on Git/GitHub stuff
  *** Wind Sensor Team**
    * Reason for no moving parts on the wind sensor:
      * Facilities will not allow us to have moving parts on the roof
      * Moving parts can also break and do not last as long as stationary parts
  *** Forecasting Team**
    * Dr. Kuh's task: Least squares programming
    * UC Irvine machine learning repo and Kaggle
      * Regression least squares- did previously in MATLAB
      * Can do in R, MATLAB, Python
        * Everyone on the team must write it in the same language
        * Backend in R and display in iPython
      * Can also get data from Kenny