Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
all_hands_meetings:february_6_2016 [2016/02/06 20:10] cobatake created |
all_hands_meetings:february_6_2016 [2021/09/19 21:59] (current) |
||
|---|---|---|---|
| Line 24: | Line 24: | ||
| * Week of 4/11/2016: 296 weatherbox projects due | * Week of 4/11/2016: 296 weatherbox projects due | ||
| * **Get ahead on work and account for debug time and unforeseen setbacks** | * **Get ahead on work and account for debug time and unforeseen setbacks** | ||
| - | |||
| ===== Proposal Presentation Notes ===== | ===== Proposal Presentation Notes ===== | ||
| Line 36: | Line 35: | ||
| * Need to verify sensor and Xbee testing | * Need to verify sensor and Xbee testing | ||
| * Need to talk with Firmware, Verification, and XBee | * Need to talk with Firmware, Verification, and XBee | ||
| + | |||
| + | ==== Apple Design Team ==== | ||
| + | * Finishing PCB so dimensions for housing are obtained | ||
| + | * 3D print housing that will fit all generations of design | ||
| ==== Firmware Team ==== | ==== Firmware Team ==== | ||
| Line 49: | Line 52: | ||
| ==== XBee Team ==== | ==== XBee Team ==== | ||
| + | * Surrounding environment will affect XBee transmission | ||
| + | * Cars and other obstacles, etc. | ||
| + | * Rain should affect XBee transmission | ||
| + | * Other conditions to test in | ||
| + | * Humid | ||
| + | * Dry | ||
| - | ==== Team Nova ==== | + | ==== Wind Sensor ==== |
| - | + | * Why Fritzing? | |
| - | ==== Team Black Hole ==== | + | * Talked to people in Dr. Garmire's lab |
| - | + | * Lab works on Fritzing | |
| - | ==== Team Asteroid ==== | + | * Need to export as a Gerber file |
| - | + | * Easier for newer people | |
| - | ==== Team Quasar ==== | + | * Ask Andy for direction |
| + | * Dr. Kuh would like to explore both options but would like Andy's advice | ||
| + | * 4 controllers and 1 processor | ||
| + | * Could be difficult to sync | ||
| + | * Consider complexity | ||
| + | * Teensy 3.2 | ||
| + | * Compatible with Arduino IDE | ||
| - | ==== Team Rocket ==== | + | ==== Forecasting ==== |
| + | * Improve forecasting techniques | ||
| + | * Use data from Weatherhawk and HNEI to compare our data | ||
| + | * Documentation | ||
| + | * Current algorithm is less accurate the further you look into the future | ||
| + | * Current algorithm can see 30 minutes into the future | ||
| - | ==== Project Badger ==== | + | ==== Instrumentation ==== |
| + | * Current voltage logger | ||
| + | * Firmware | ||
| + | * Software- GUI | ||
| + | * Hardware | ||
| + | ==== 196/296 Presentations ==== | ||
| + | * General Presentation Improvements | ||
| + | * Talk loudly so everyone can hear | ||
| + | * Do not read off of slides | ||
| + | * Do not lean on table with keyboard and mouse | ||
| + | * Do not move the mouse while presenting- its distracting | ||
| + | * Put page numbers on slides | ||
| + | * Be careful of how much text is put on the slides | ||
| + | * General Presentation Remarks | ||
| + | * Overall, presentation slides were nice | ||
| + | * Content was explained and covered well | ||
| + | * Questions for 296 projects | ||
| + | * Who will be completing what on the gantt chart? | ||
| + | * Will people be assigned roles? | ||
| + | ==== Tryston's Presentation Comments ==== | ||
| + | * General Presentation Remarks | ||
| + | * Appropriate PowerPoint presentation slide. Some groups use pictures, which is okay and is encouraged if it helps explaining the slide, but don't use pictures that would distract the audience (which no team did). | ||
| + | * Each team explained the project clearly. | ||
| + | * Presentation Improvements | ||
| + | * When presenting, do not read off slides. You should know what you want to say and use slides as a reference. | ||
| + | * Try not to use too much text. You want your audience to listen to you, not read what you are saying. | ||
| + | * Practice presentation as a team. This makes transitions smoother. | ||
| + | * Include slide numbers so the audience can refer back if they have questions. | ||
| + | * Include a presentation overview, which is like a table of contents. It should include what you will be presenting. | ||
| + | * Talk about potential problems. Explain reasons that would prolong or conflict with project goals. This shows that you thought about what could go wrong with this project. | ||
| + | * If you talk about potential problems always include a solution or ways to avoid the problem. | ||
| + | * Include member roles and your approach to completing your project. | ||
| + | * Advice for next presentation | ||
| + | * Expect technical questions | ||
| + | * Ask questions if something is unclear | ||
| + | * You have 6 minuets to present which is just enough time to explain everything in detail. | ||