Differences

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

wiki:project [2011/12/15 17:30]
yoonguk
wiki:project [2011/12/15 20:04] (current)
yoonguk
Line 74: Line 74:
  * Vector-graphics   * Vector-graphics
    * Latex plays nicely with vector-based graphics (for figures or graphs). If you want to include graphics you generated using Windows-based tools, you'll have to either i) convert them to jpeg/gif/png (which would introduce visual artifacts, more so since you have to shrink/enlarge them), or ii) convert them to eps/pdf (which would not introduce visual artifacts). If you have questions on the latter, we can help.     * Latex plays nicely with vector-based graphics (for figures or graphs). If you want to include graphics you generated using Windows-based tools, you'll have to either i) convert them to jpeg/gif/png (which would introduce visual artifacts, more so since you have to shrink/enlarge them), or ii) convert them to eps/pdf (which would not introduce visual artifacts). If you have questions on the latter, we can help.
- 
-====== Guidelines ====== 
- 
-The following is from an e-mail from Onur regarding the project: 
- 
-Dear 740 students, 
- 
-As you know, the project reports are due December 18, 11:59pm Eastern 
-Time. There are *no extensions* to this deadline, as we will need to 
-turn in the grades soon afterward. 
- 
-The guidelines for the report writeup are in the project 
-handout: 
-http://www.ece.cmu.edu/~ece740/f11/lib/exe/fetch.php?media=wiki:project:project-f11.pdf 
- 
-Basically, write your report as if you are writing a submission to a 
-top conference. You need to motivate the problem, describe its 
-importance, describe related work and its shortcomings, explain the 
-key ideas of your solution, and describe it in detail in a precise 
-manner so that the reader (i.e., we) can understand what you are 
-exactly doing. You should describe your experimental methodology to 
-evaluate your solution and provide an analysis of your results. 
- 
-It is very important that your report have all the sections that 
-comprise a good computer architecture paper: 
-- Abstract 
-- Introduction (Problem and Motivation) 
-- Related Work and its Shortcomings 
-- Description of the Techniques (designed and evaluated) 
-- Evaluation Methodology 
-- Results and Analyses 
-- Conclusion/Summary 
-- References 
- 
-Please incorporate all feedback you received during the poster session 
-when preparing your report and make your reports as strong and as 
-clear as possible. 
- 
-Page limit and format: I am increasing the page limit to 12 pages 
-double-column, single space, including references. You can add an 
-appendix that can be as long as you wish, if you wish to provide 
-supporting data, proofs, explanations, etc. Please use the Latex 
-template (along with instructions) provided on the 740 project 
-website: http://www.ece.cmu.edu/~ece740/f11/doku.php?id=wiki:project 
- 
-A good example of a well-formatted 12-page paper is at: 
-http://www.ece.cmu.edu/~omutlu/pub/tcm_micro10.pdf 
- 
-You have read many seminal and recent research papers during the 
-course of the semester on a very wide variety of research topics, and 
-by now are familiar with the level of clarity, preciseness, insight, 
-and strength of evaluation that makes a paper a good research paper. I 
-expect your reports will reflect similar quality. 
- 
-Looking forward to your clear and insightful reports. 
- 
-Onur 
====== Poster Session ====== ====== Poster Session ======

Personal Tools