MIT 6 047 - Guidelines for the final project report and presentations

Unformatted text preview:

MIT OpenCourseWare http://ocw.mit.edu 6.047 / 6.878 Computational Biology: Genomes, Networks, Evolution Fall 2008 For information about citing these materials or our Terms of Use, visit: http://ocw.mit.edu/terms.Guidelines for the final project report and presentations. Due: See below for details With just a few days left before the final project deadline, some of you have been asking about how long and how detailed the project reports should be, whether extensions are possible, and finally a bout presentations. This document provides some simple guidelines answering these questions. Final project report Style: Your final project report should essentially read like a research paper. It should be clear and concise, and describe your contributions in the context of the broader literature. Length: We expect most reports to be between 8 and 12 pages. We do impose a hard limit of 15 pages (single spaced, 10pt font, 1-inch margins all around), but you should try to keep your report within the 8-12 range. As with most conferences and journals, you have to make important decisions as to what to include, and that's part of the skillset needed for writing a solid paper. If you absolutely need to include additional graphs that are supporting your results, you can do so in an optional appendix. Contents: You should structure your report around your key contributions, obviously, but make sure you include the following information: Abstract: A 300-500 word summary of the problem statement and its challenge, the state of the art in the field, your approach, your results (this is the most important part, of course), and the broader impact of your contributions. Background: A brief summary (1000 words max) of the problem, the current state of the field and existing literature, situating your work in the context of the more general area of research, and clearly stating how it differs from previous approaches, or from your previous work and other undertakings. Results and discussion (the bulk of your report): While some conferences/journals ask you to separate your results and their discussion, we prefer a single section describing for each aspect of your project, a summary of the challenge undertaken, a detailed description of the method used, and a clear description of the results obtained. With these descriptions, you can intersperse discussion on the rationale of the methods used, and also comment on the interpretation of the results you found. Be precise about your methods, and describe clearly any existing tools you used, and any new methods you developed (and their availability, if applicable). Be critical about your own results and findings, and think about alternative interpretations of your findings. Think a bout alternative approaches you would have considered if time permitted, or if you were to start a new. Future goals (a few paragraphs): Because this is a class project, we want you to think hard not only about what you have accomplished in the period of the term, but also where you want to take this project going forward. This is a great place to describe your plans for publication of this work, what else you would like to include before it is ready for primetime, wether it's a masters thesis, a Nature paper, or your next book. We like to see projects flourish even after the class ends, and great new directions are testament of great projects.6.047/6.878 Fall 2008 Final project guidelines Comparison with Milestones 1and 2: You also must com ment on how the final report compares to what you proposed in milestones 1and 2, in one or two paragraphs. Did you manage to accomplish all your goals, which ones failed and why, which were added and why, was your proposal overly ambitious or vague or short. Explain the differences, what shaped the project away from the original aims, and could you have foreseen that earlier. Commentary on your experience (a couple of paragraphs): We want you to also go back and think critically about your project, and what advice you would give to yourself if you were to start over. Were the datasets well-suited for the approach, did you manage your time well between doing and writing, or between different aims of your project, what aspect of your project proved the most challenging / the most rewarding, what part of the project did you enjoy the most / the least. Division of labor (1paragraph): For people working in groups, describe the contributions of each of the authors. This is standard in most scientific journals nowadays, and you should be completely honest about it, and as precise as possible. You can also comment on the good and the bad aspects of the collaboration, and what advice you would give yourself were you to start over. Final report due date The written reports are due on Friday Dec 5 at 5pm, but extensions are automatically granted (you still have to ask!) until Monday Dec 8 at 8pm. Final report submission Submit a single PDF document by email to. Name your file: "LastnameFirstname-report.pdf (if working in teams, include all names, separated by underscores). Do not send to an individual TA, and do not submit a paper copy. If you cannot print to PDF, we will scan your document for you, but you have to bring us a color printout by 6pm on Monday at the latest. Oral presentation In addition to the written report, an oral presentation of your project in front of the staff and the rest of the class will also be part of your evaluation. You will be evaluated on your ability to clearly communicate your findings in front of a scientific audience in computational biology (even if they're not experts in the particular area of your project), on the clarity with which you communicate your contributions, your ability to manage your time well and finish on time, and of course the overall quality of the work and the presentation. All presentations will be 8mins, leaving a 2min interval for questions and answers. We will be very strict and stop you short if you run over, so manage your time wisely and do not leave the best part for the last minute.6.047/6.878 Fall 2008 Final project guidelines Final project grading Your projects will be graded on overall quality obviously, but to give you a sense of the criteria used, here's a fictitious breakdown of points (the categories are not fictitious, the points are): Originality (-5pts) How original


View Full Document

MIT 6 047 - Guidelines for the final project report and presentations

Download Guidelines for the final project report and presentations
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Guidelines for the final project report and presentations and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Guidelines for the final project report and presentations 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?