High-Level Rubric for E80 Final Report
1 Overview
This rubric provides suggestions on the topics that each of your sections should address.
2 Report Sections
2.1 Abstract
The abstract articulates what was done, including a concise description of the experimental method, and why (i.e., motivation). The abstract mentions key quantitative (i.e., numerical) conclusions and what they mean.
2.2 Introduction
The introduction motivates the work and explains experimental and modeling methods well enough to orient the reader to the paper. Relevant background information should be cited. The introduction does not explain technical details in more depth than necessary to orient the reader: those details belong in the main body.
The introduction should also include an explanation of the specific phenomena the robot was designed to measure, why these measurements are important, and what can be learned from these measurements. In particular, each goal of the project should be articulated.
2.3 Sensor Design
A discussion of what sensors were chosen and how they relate to the scientific or engineering goals. The discussion should address the sensor input/excitation range and how these compare with the expected excitation during deployment. The discussion should also address the output range and or form (voltage, AC voltage or pulse train, pulse width modulated, pulse height modulated, etc.), and impedance. This should include discussion of the component values which were selected or calculated (e.g., how did you map expected variations in output into the 0-to-3.3V input range of the Teensy.) This section should also explain if the sample rate of 10 Hz was sufficient along with any modifications to the robot which were made to ensure the sensor functioned properly (these may be in a separate mechanical design section).
Successful sensor descriptions should include: - Expected input limits articulated quantitatively and backed with analysis/simulation - Complete schematics for every circuit designed. - Circuit topology, amplifier type, gain, and signal conditioning discussed for each sensor. - Power supplies and their uses enumerated. - Comparison of input range with limits of datasheet specifications. - Discussion of output range and time constant for each sensor. - Mechanical modifications considered and well described.
2.4 Robot Design
This section should include information about the mechanical design of your robot and sensor integration, with a labeled mechanical drawing.
Discussion should include sensors placement and what considerations were made about the mechanical aspects of the design (e.g., buoyancy and ballast calculations, waterproofing) and how it navigates in the water (e.g., diving or surface). This section should also mention any differences between pHake Lake and Dana Point.
2.5 Deployment Details
This section should include:
An explanation of how MATLAB, historical data, or your own models were used to predict the robot’s performance, the sensor measurements versus time, and how the modeling results informed the experimental protocol.
An explanation of the experimental protocol and deployment steps (e.g., the goals for each deployment, prepping the robot, starting the Teensy code, deployment details, recovery details, retrieval of the data, and processing of the data).
An image showing deployment location(s) and launch trajectories.
A discussion of deployment safety.
2.6 Results
This section should include:
- Neatly processed data for all working sensors and plotted figures from your deployments along with discussion about the results and what they mean. Ever figure should have labeled axes and a data legend.
All tables and figures should be numbered and have a concise descriptive caption. Table captions should appear above the table and figure captions should appear below the figure. Every table and figure should also be referenced and described in the main body text, including intepretations of key features.
- A comparison of the modeled (or expected) data, ground truths, and retrieved data from your deployments. Graphical comparison is preferred, but written comparison should be used as appropriate, especially to explain the graphical data. Error bars or estimates should be included in all experimental quantities.
Whether each deployment is compared individually or all deployments compared together will depend on the data sets and the results. Descriptions of the degree of agreement should be made and possible explanations of the discrepancies should be present.
2.7 Conclusion
The conclusions should not be just a summary, but should be a summation of lessons learned, both about the process and of the comparison of the data and models.
It should answer the question, “What does it all mean?”
It should include recommendations for future work and/or future versions of the class.
2.8 Acknowledgements
List all non E80 personnel who helped. Be sure to briefly describe their contribution.
2.9 References
List and cite all relevant references. Be especially careful to cite sources for figures that you have not drawn yourself.
2.10 Overall Writing
Grammar: Free of spelling, capitalization, and usage errors. Few, if any, errors in punctuation. Sophisticated and consistent command of standard English.
Transitions: Ideas/paragraphs/sections are connected by effective transition words and phrases.Precise, interesting, and accurate word choice. Writing style enhances readability of writing.
Focus: Language choices (degree of jargon) and use of background material reflect attention to audience. Writing has a clear, distinct focus.
Organization: Generally well-developed ideas have a logical flow. Introductory and closing material is used effectively. Piece has a sense of completeness.
Elaboration / Support: Each main idea is supported by detailed data or reasoning. All details are related to topic. Complete, correct documentation of a wide variety of sources.