1. Miscellaneous Notes: This is a bare-bones template – make it fancier if you wish, but be sure to address at least the items listed here. Basically this is the oral version of your written Revision C (due soon), so start at the beginning and go all the way through data analysis and conclusions. The main difference between this and Revision C is that here you will have much less text since you can talk through the issues orally. The graphs, photos, etc. you include here may well be the same as those you include in Revision C. Remember this is a 20 to 25-minute oral presentation – don’t go long, but do make good use of the time you have. Remember that your slides are due by my office hour on Tuesday, Nov. 22 – they may well be too large to send by e-mail (and you will want to look them over once I have them to ensure they play properly on my computer), so I recommend you bring them to me in person during my office hour that day Note: You may assume that your audience has seen your previous presentations which means you are allowed to be very brief with some slides, like schedules, budgets, etc. Leave them in, for completeness, but spend you talking time on new things like the flight experience and especially the data analysis.

2. Team Name Final Team Presentation Consider putting an eye-catching photo or graphic here. Team Members Class and Date

3. Mission Overview (maybe just 1 slide) What are your (multiple) objectives? (there may be visitors listening to your presentation, so don’t assume everyone has heard this before (but do go through it quickly)) What do you expect to show/prove/disprove?

4. Team Management (1 or more slides) Draw a graphical Org Chart explaining who was most responsible for building and testing what part(s) of the payload as well as who worked on what parts of the data analysis, project documentation, oral presentations, etc.

5. Design Overview (multiple slides – be sure to have your actual box nearby but don’t distract the audience by playing with it, but make these slides stand alone – use bulleted text, labeled diagrams, and photographs with captions) List of items in the payload Discussion/figures/photos of box construction Layout of the items in the payload box Functional block diagram – What is attached to what (both electrically and mechanically) and why? Programming (don’t include the actual code (though that should show up in Revision C as an Appendix -- just state clearly what it does like “records temperature and pressure data once every xx minutes” ) Final budgets (cost and mass) – be sure to state final mass or weight

6. Payload Pre-flight Testing (multiple slides) (include both a list of tests that you ran (and those not run) as well as quantitative testing results) What tests were run and what were the results? (Be quantitative when possible.) What changes, if any, were made to the payload based on the testing? What other things could have been tested had there been enough time and/or the right equipment (and why would you test those things and what would you hope the results would be)? What, if anything, didn’t pass the test(s) and needed to be repaired or swapped out before the flight?

7. Expected Science Results (multiple slides) Restate each experiment you ran as well as specific comments about the results you expected. By now you should have actual scientific references for what you expected. For example, every team should include plots of pressure and temperature at various altitudes in the atmosphere – these are not hard to find in the scientific literature if you look for them. You get to choose whether to put your expected results all together (here) or to intersperse them with your experimental results (presented later). Make this section as quantitative as possible – not just qualitative statements like “We expect the pressure to go down.” but rather (delivered orally while looking at a graph) “As seen in this plot from (give reference), the atmospheric pressure is expected to start at about xx at ground level then fall to yy by the time we reach zz in altitude. Had we gone higher still the pressure would have…”

8. Flight Day (multiple slides) Include comments and photos from the flight day itself, both the launch and the chase. Include comments about the status of the payload box when it was recovered (as best you know them), as compared to when it was released: Was there any visible damage inside or outside? Were things still running? Were there any things that didn’t run at properly and have you figured out why? etc.

9. Science Results (multiple slides) Here is where you present your experimental results. You should probably show altitude vs time and the ground track of the mission (both provided by me), but don’t dwell on them since they aren’t specific to your box. Rather, concentrate on showing graphs (not tables) of temperature data, pressure data, radiation data, etc., either versus time (as it was originally collected) or (better still) versus altitude, as determined from the GPS record. You do need to tie altitude to data at least some place in your analysis. Include photos you analyzed and explain what you learned from them. Don’t just say “The sky got darker as we got higher” – try to quantify all statements and show graphs (well-labeled!) whenever possible.

10. Conclusions/Lessons Learned (multiple slides) Give a textual summary of what you learned from the data about each experiment that worked (and what you learned from the one(s), if any, that didn’t work as expected). Make specific comments about what else could be tried along the lines of the experiment(s) you did. For example, if you were to modify your payload and fly it again, what would you change and why? What other experiments now interest you? On a separate slide give some explicit “Words of Wisdom” to students who might take this class in the future about what to do (or not do!). On a separate slide give thanks explicitly to people not on your team who helped you.