Differences

This shows you the differences between two versions of the page.

--- projects [2015/12/06 19:44]
nandita [Final Presentation (December 14th)]
+++ projects [2015/12/06 19:47]
127.0.0.1 external edit
@@ Line 118: / Line 118: @@
 [[http://www.ece.cmu.edu/~ece740/f11/doku.php?id=wiki:project#poster_session|more example posters]]
+===== Final Project Report (December 20th) =====
+You will hand in a report in the conference submission style.
+Your final report should be formatted and written as if you are submitting the report to a top computer architecture conference.
+The report should include the following:
+  * A descriptive title and author names
+  * Abstract
+  * Introduction (Problem and Motivation)
+  * Related Work and its Shortcomings
+  * Description of the Techniques (designed and evaluated)
+  * Evaluation Methodology
+  * Results and Analyses
+  * Conclusion/Summary
+  * Lessons Learned, Shortcomings, and Future Work
+  * Acknowledgements (if any)
+  * References (cited throughout the paper)
+The page limit is 10 double column, single-spaced pages. Make sure your document is spell-checked and grammatically sound. You are encouraged to use the LaTeX template above.
+Advice:
+The key characteristic that distinguishes a “good” research paper from a “bad” one is the existence of “clearly explained insight.” I expect the highest quality of writing as well as clear descriptions of the ideas and techniques from the final report. Even if your research results in a “negative result” (not all research ideas pan out to be useful, in fact few of them do) writing it in a very insightful and intuitive manner can make the research very powerful and important. So, please do spend a significant amount of time and effort to ensure that your report is insightful and explains the ideas very clearly (possibly with examples and good analogies).
+**Examples:**
+See the readings throughout this course for examples. Some selected favorites:
+{{:parbs_isca08.pdf|Mutlu and Moscibroda, “Parallelism-Aware Batch Scheduling,” ISCA 2008.}}
+{{mutlu_micro05.pdf|Onur Mutlu, Hyesoon Kim, and Yale N. Patt, "Address-Value Delta (AVD) Prediction: Increasing the Effectiveness of Runahead Execution by Exploiting Regular Memory Allocation Patterns," MICRO 2005.}}